abroddrick
commented
1 day ago @SamiyahKey for the last AC " Confirm alignment with WCAG 2.1 Success Criterion 1.3.1 (Info and Relationships), categorizing this as a high/must do priority for accessibility." For the dev picking this up this may not read like an actionable AC, mind if I change it to read, "have a design reviewer confirm that the solution aligns with WCAG 2.1 Success Criterion 1.3.1 (Info and Relationships)"? Then we can move the comment about the prioritization into the additional context.
SamiyahKey
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:
[ ] 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