Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Correct Heading Levels on get.gov Homepage for Accessibility #3063

Open
SamiyahKey opened this issue Nov 8, 2024 · 0 comments
Open

Correct Heading Levels on get.gov Homepage for Accessibility #3063

SamiyahKey opened this issue Nov 8, 2024 · 0 comments
Labels
accessibility dev skipped design Design artifact(s) will need to be updated story User stories

Comments

@SamiyahKey
Copy link

Story

As a user who relies on screen readers and other assistive technologies, I need the visual and programmatic heading structure on the get.gov homepage to align, so that I can efficiently navigate and understand the hierarchy and importance of content on the page in a logical order.

URL: https://get.gov

Acceptance Criteria

Update the heading levels on the Get.gov homepage as follows:

  • "The latest from .gov" should remain as an < h2 > heading.

  • "Getting a .gov just got easier" and ".Gov register transition update" should be updated to < h3 > headings instead of

  • "Featured .gov" should remain as an < h2 > heading.

  • "EveryKidOutdoors.gov" should be updated to an < h3 > heading instead of < h4 >.

  • Ensure heading levels are properly nested to accurately represent the page's content structure and hierarchy.

  • Confirm alignment with WCAG 2.1 Success Criterion 1.3.1 (Info and Relationships), categorizing this as a high/must do priority for accessibility.

Additional Context

This correction improves accessibility by allowing screen reader users to navigate content sections more intuitively, following a logical and consistent heading structure.

Prioritization Comments

WCAG Conformance Level: 2.1 AA
WCAG Standard that applies: 1.3.1 Info and Relationships
Critical Failure if Not Met?: Yes
Prioritization: High/Must Do
Reason: Proper heading structure is crucial for screen reader navigation and impacts users who depend on semantic structure to understand page hierarchy. Misalignment between visual and programmatic headings can cause confusion and reduce usability.

Issue Links

No response

@SamiyahKey SamiyahKey added dev skipped design Design artifact(s) will need to be updated story User stories labels Nov 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accessibility dev skipped design Design artifact(s) will need to be updated story User stories
Projects
Status: 👶 New
Development

No branches or pull requests

2 participants