Skip to content

Quick Tip: Use More Than Tab in Screen Readers

It’s been a busy week in my house, so I’m going to keep this quick. One of the issues I often see flagged by other accessibility testers is that something doesn’t work with keyboard navigation. The vast majority of times I revisit these, it turns out the tester doesn’t fully understand how screen readers work. I want to highlight a few items for folks.

Modes

Screen readers typically have 3 main modes. The virtual browser, forms, and application.

Virtual Browser

The virtual browser is when the screen reader technology is intercepting the keyboard input and uses that to execute a function in the browser for you. When we press tab we jump to the next active item. Pressing the down arrow will read the next line, chunk, or set number of characters in a paragraph. Here’s a short list of common commands:

  • H: moves through the headings on the page
  • T: moves through the tables on the page
  • Control+Alt+Arrow: Move from one table cell to the next in the direction of the arrow
  • L: moves through the lists

Forms

When a user encounters a form element, the screen reader should automatically shift to the forms mode. There usually is ab audible sound to indicate this. This mode moves the screen reader out of the way to interact directly with the page via the keyboard. This limits how to navigate to using only the Tab and Shift keys to move among the active elements in the form.

Application

In this mode you need to have the role=”application” and then the screen reader again gets out of the way of the keyboard. However, even if you use active controls navigating between them is completely up to the author. They will work with Space & Enter to activate, but the author really needs to define the navigation scheme and controls to use the tool.

Don’t flag an issue for not being keyboard accessible with a screen reader on unless you can identify it is an application or is also not accessible without the screen reader.

There’s way more to this, but the great folks over at Tetralogical have a great screen reader misconceptions article and a full break down of commands.

Published ina11ya11y 101accessibilityblindcognitionTestingWCAGWeb Content Accessibility Guidelines