feat: a shared responsive navigation bar

Open
#796 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
28/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
html, rust

Research direction

Read tracking issue #776 first, then the existing Link, Button and Lucide Icon components this is blocked on, since the nav is assembled from them. Build the header nav as a shared component: links plus a disclosure (Button with aria-expanded, or <details>) below the breakpoint, keeping the skip link, landmarks and current-page state. Done means the §13.7.5 checklist is satisfied — gallery entry, axe-core and ARIA snapshot rows, keyboard-only scenarios — plus the §4.5 contract row and WCAG 2.2 AA at 320 px with 200 % text. The issue text alone does not define the acceptance sections, so expect to read the tracking issue before starting.

Written by the indexing model from the issue text.

Description

accessibility enhancement

Part of #776.

The header's navigation as a shared component: the links (Link), and below a breakpoint a disclosure (Button with aria-expanded, or native <details>) holding them, so 320 px with 200 % text doesn't fill the screen (the header critique's open issue). Keeps the skip link, the landmarks and the current page.

Needs first: Link, Button, Icon (Lucide) (see "blocked by").

Acceptance: Meets the bar in the tracking issue: WCAG 2.2 AA in full when it merges, a contract row in §4.5, and every step of §13.7.5 (component, gallery entry, axe-core and ARIA snapshot rows, keyboard-only contract scenarios).

Dominant language
Rust
Stars
0
Forks
0
Avg merge
56m
Merged PRs (30d)
349

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nledford/Ladderback

All issues in nledford/Ladderback

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.