Skip to content

feat(a11y): accessibility baseline — skip link, landmarks, route-change focus#215

Open
JarbasAl wants to merge 1 commit into
devfrom
feat/accessibility
Open

feat(a11y): accessibility baseline — skip link, landmarks, route-change focus#215
JarbasAl wants to merge 1 commit into
devfrom
feat/accessibility

Conversation

@JarbasAl

Copy link
Copy Markdown
Member

Adds the structural WCAG 2.2 baseline to the SPA.

One change, 2 files:

  • index.html — skip-to-content link (hidden until focused); nav[aria-label=Primary]; focusable <main tabindex=-1>; focus management on hash-route change (new view's heading/main receives focus so screen-reader users hear the change — the biggest SPA a11y gap); polite live region on the toast container; :focus-visible rings on all interactive elements.
  • docs/local-development.md — a11y note + honest follow-up list.

Explicitly deferred (follow-ups, noted in docs): an axe-core CI gate (needs a Playwright harness), a per-view single-h1 audit, and a dark-theme contrast pass. Automated tools catch only ~30–40% of issues, so a manual keyboard + screen-reader pass is still required before release.

Local: node --check on the SPA script → OK; full pytest test/ → 169 passed.

…ge focus, live region

Add the structural WCAG 2.2 baseline to the SPA: a skip-to-content link, a
labelled primary nav, focus management on hash-route change (the main
screen-reader gap in SPAs — the new view's heading receives focus), a polite
live region for toasts, and visible :focus-visible rings on interactive
elements.
@coderabbitai

coderabbitai Bot commented Jul 11, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@JarbasAl, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 58 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 60e138ac-6b2d-437a-bf46-22b1ac0a4cec

📥 Commits

Reviewing files that changed from the base of the PR and between 5dc8e63 and e467264.

📒 Files selected for processing (2)
  • docs/local-development.md
  • index.html
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/accessibility

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@JarbasAl JarbasAl marked this pull request as ready for review July 11, 2026 11:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant