Have you noticed this?
- You can use
โandโto switch Tabs on NVDA - But you canโt use
โandโto switch Carousel slides on NVDA
Why?
The reason is forms mode.
Screen reader modes
Most screen readers (like NVDA) have three operating modes. They are:
- Browse (or read) mode
- Forms (or focus) mode
- Applications
Voiceover does not have forms or application mode. Why? I suspect Voiceover can use Browse mode for everything because it uses VO for browsing shortcuts.
Browse mode
Browse mode (sometimes also called read mode) is the default reading mode for all screen readers.
Users get access to all reading shortcuts when theyโre in browse mode. Here are some examples:
| Shortcut | Command |
|---|---|
โ |
Say previous line |
โ |
Say next line |
โ |
Say previous line |
โ |
Say next line |
H |
Go to next heading |
Shift + H |
Go to previous heading |
Forms (or focus) mode
Forms mode (in JAWS) or focus Mode (in NVDA) are the same thing. They activate when a user enters into elements like an <input>.
When screen readers enter Forms mode, they behave like normal keyboards. Reading shortcuts (like those above) are disabled.
So if a user presses H while in forms mode, screen readers literally hit the H key on the keyboard. They wonโt bring the user to the next heading element.
Users can exit forms mode by pressing the following keys:
- NVDA:
EscapeorNVDA+Space - JAWS:
Numpad +key
Application mode
Thereโs a third operating mode called Application mode. Application mode works like forms mode for web content.
Thereโs one difference: NVDA cannot exit Application mode with the Escape key. But it can exit Forms mode with the Escape key. (Not sure about JAWS).
Note: Accessibility Developer Guidelines mentions that screen readers disable Tabโs default functionality in Application mode. I found this to be false. Tab still works in JAWS and NVDA.
Roles that enter Forms/Application mode
Many aria roles make screen readers enter Forms mode. Most of them are widget roles, but some of them are document structure roles.
Users must Tab (or Shift + Tab) into the element to triggerย automatic transition into Forms/Application mode.
Here are the roles that make screen readers enter Forms mode:
comboboxlistboxandoptiontablistandtabtree,treegridandtreeitemgrid,columnheader,rowheader,row,gridcellandcelltextbox,searchbox,radio,sliderandspinbuttontoolbarmenuandmenubar
These four roles make a screen reader enter Application mode:
applicationmenuitemmenuitemcheckboxmenuitemradio
Be careful when you use any of the roles above. Use them responsibly. Use them only if you need to.
Welcome! Unfortunately, you donโt have access to this lesson. To get access, please purchase the course or enroll in Magical Dev School.
Unlock this lesson