Open CJE001 opened 1 month ago
Guideline 2.4: Navigable "Provide ways to help users navigate, find content and determine where they are."
2.4.3 Focus Order (In Context) WCAG 2.0 Level A
If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability.
Both screen reader users and sighted keyboard users access page content sequentially. To avoid confusing them, links and other interactive components must receive the keyboard focus in a meaningful order.
Summary
Via Vision Australia assessment: August 2024
Impact: medium
Note: DTA have a 90 day remediation period to address the identified issues within the audit, all issues must be resolved to obtain WCAG 2.2 certification for digital.gov.au.
Steps to reproduce
Global issue – Left side navigation Digital Service Standard services | digital.gov.au (https://www.digital.gov.au/policy/digital-experience/digital-service-standard/services)
Observed outcome
When activating the "Skip to main content" link in the side navigation, focus moves to the correct target (#main-content), however, focus then moves back to the skip link and keyboard users are unable to bypass the navigation.
This is because the target of the skip link comes before the navigation list in the code.
Code used
Why this matters
Keyboard-only users will be forced to navigate through all focusable elements within the side navigation each time they visit a new page.
This increases the number of tab stops, which can dramatically slow users down and cause frustration. It can be particularly problematic for those who experience pain while navigating or have limited dexterity.
Expected outcome
As the side navigation sits within the landmark for the page, update the skip link target to the primary heading of the main content.
This heading comes after the navigation in the code, allowing keyboard users to effectively skip the navigation. The heading should be given a unique id attribute that is referenced in the href attribute of the skip link. The heading element should also be given a tabindex="-1" to ensure that the skip link works for users across various operating systems.
Preferably, update the link text to 'Skip navigation' so the link purpose is clear, and users can differentiate its purpose from the 'Skip to main content' link that appears at the top of the page.
Code example