Problem description: Keyboard only users get an onerous user experience when navigating content on web pages because they can only use the tab key to move through focusable elements.
For example: the guardian.com home page has 535 links, 100 buttons and various other elements that are included in the focus order… It does provide an affordance for keyboard only users via a ‘skip to main content’ link which skips over 135 links. This leaves 400+ focusable elements to tab through. The page has 91 correctly marked up headings. It also has a mixture of ARIA landmark roles and HTML5 elements that map to landmark roles.
Suggestion: By implementing an interoperable keyboard navigation system in UA’s (that support keyboard input) the amount of keystrokes a user requires to navigate to and interact with page content can be significantly reduced. It will also mean that developers don’t have to bolt on navigation affordances (skip links) for users and web content will automatically conform (if headings and/or HTML5 header/main/footer elements are used) to the WCAG 2 bypass blocks criteria.