Figure 1 : Example of a form where screen reader would switch the mode to forms mode
There are two types of modes in screen readers – Browse and Application/Focus/Forms modes.
Browse Mode is used to navigate the webpage content without interacting with any of its
components. This is used to read the contents of a webpage and get an overview.
Forms Mode is used to interact with the elements of a webpage including buttons, forms etc.
In forms mode, users can fill out form fields or interact with form controls without triggering other
keyboard shortcuts meant for browse mode.
NOTE:
New to accessibility or uncertain of requirements, it will be helpful to review all sections below.
Already familiar with requirements, skip to the “Working Example” section for sample HTML, CSS
and JavaScript (when needed), along with a working demo.
AVOID using ARIA role="application" unnecessarily on a web
page unless the interaction requires an application mode to interact efficiently.
The user SHOULD always have control to switch between the 2 modes.
For example, setting the JAWS Forms mode to Manual, the automatic change of mode
CAN be prevented.
Using native semantics helps screen reader users to interact with the webpage efficiently.
Ensure that no keyboard shortcuts used on a webpage interfere with the screen reader user’s ability
to switch between the 2 modes or their interaction with the webpage.
A well-defined web page with screen reader mode majorly benefit the below users.
