Forms Mode and Input Testing
You'll learn how screen readers change behavior when encountering form controls and how to verify your forms work correctly.
What is Forms Mode?
When a screen reader user navigates to an interactive form element like a text input, checkbox, or select menu, the screen reader automatically switches to forms mode (also called "focus mode" or "application mode").
In this mode, most navigation keystrokes are passed directly to the form control instead of being interpreted by the screen reader. This lets users type naturally without triggering screen reader commands.
The Mode Switch
Think of it like switching between reading a book and writing in it. In browse mode, you navigate by headings, landmarks, and read static content. In forms mode, you interact directly with inputs—typing, selecting, and submitting data.
The switch typically happens automatically when you tab to or click on a form control. Some screen readers announce "forms mode" or make a sound to indicate the change.
Testing Form Controls
When testing with a screen reader, verify:
- Labels are announced: When focusing an input, you should hear its associated
<label> - Instructions are provided: Any
aria-describedbyhints should be read - Required fields are announced: The
requiredattribute oraria-requiredshould be communicated - Error messages are clear: When validation fails, users should hear what went wrong
- Field type is identified: "Edit text," "checkbox," "combo box," etc.
Tab through your entire form with a screen reader active, listening carefully to what's announced at each field. Missing labels or unclear instructions become immediately obvious.
Key Takeaway: Screen readers switch to forms mode at interactive controls, passing keystrokes directly to the input—test by tabbing through your forms and verifying all labels, instructions, and states are announced correctly.