Skip to content

Conversation

@ckundo
Copy link
Member

@ckundo ckundo commented Nov 16, 2025

Fixes #50

Changes

  • ✅ Wrap main content in <main> element
  • ✅ Separate header from main content semantically
  • ✅ Enable screen reader landmark navigation
  • ✅ Improve overall document structure

WCAG Compliance

1.3.1 Info and Relationships (Level A) - Structure must be programmatically determined
2.4.1 Bypass Blocks (Level A) - Mechanism to skip blocks of content

Benefits

  • Screen reader users can jump directly to main content
  • Improved navigation for assistive technology
  • Better document outline and semantics
  • Prepares for skip link addition (issue Add skip link to bypass header #61)

Testing

  • Build succeeds
  • Screen reader can navigate to main landmark
  • Only one <main> element on page
  • All primary content within <main>

- Wrap main content in <main> element
- Properly separate header from main content
- Enable screen reader landmark navigation
- Improve document structure and semantics

WCAG: 1.3.1 Info and Relationships (Level A)
WCAG: 2.4.1 Bypass Blocks (Level A)

Screen reader users can now navigate directly to main content
using landmark navigation.
@ckundo ckundo added bug Something isn't working aria ARIA and semantic HTML issues screen-reader Screen reader accessibility issues labels Nov 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

aria ARIA and semantic HTML issues bug Something isn't working screen-reader Screen reader accessibility issues

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants