Background
Dashboard-level pages need stronger keyboard and assistive-technology navigation so users can bypass repeated chrome and move directly to core content.
Feature Focus
Add skip-link support and landmark cleanup for dashboard pages.
Where to Implement (Exact Targets)
apps/web/src/layouts/*
apps/web/src/pages/*
apps/web/src/components/navigation/*
apps/web/src/tests/*
What to Implement
- Add a visible-on-focus skip link that jumps to the main dashboard content region.
- Audit and clean up landmark roles and heading structure on top-level pages.
- Ensure repeated navigation and side panels do not create confusing focus order.
- Keep the implementation consistent across major dashboard surfaces.
Interface / Endpoint / Method Details
- Use semantic HTML and ARIA only where necessary.
- Avoid duplicate landmark roles and ensure the skip target is stable per page.
- Preserve current visual layout outside of focused accessibility improvements.
Acceptance Criteria
- Keyboard users can skip repeated navigation on dashboard pages.
- Major pages expose sensible landmark and heading structure.
- Existing navigation behavior remains intact.
Required Tests
- Accessibility-focused tests for skip-link visibility, target focusability, and landmark presence.
- Regression checks for existing navigation interactions.
Definition of Done
- Skip-link and landmark cleanup are implemented across dashboard-level pages.
- Tests verify the behavior and prevent regressions.
Background
Dashboard-level pages need stronger keyboard and assistive-technology navigation so users can bypass repeated chrome and move directly to core content.
Feature Focus
Add skip-link support and landmark cleanup for dashboard pages.
Where to Implement (Exact Targets)
apps/web/src/layouts/*apps/web/src/pages/*apps/web/src/components/navigation/*apps/web/src/tests/*What to Implement
Interface / Endpoint / Method Details
Acceptance Criteria
Required Tests
Definition of Done