Accessibility ≠ Overlay: when a form cannot be completed with a screen reader
An accessible form is more than a collection of fields. Everyone should be able to understand it, fill it in, review their answers and submit it using a keyboard and screen reader.
The problem starts before typing
A field may look obvious on screen but be announced only as “edit box”. Without an associated label, a person cannot tell whether it asks for a name, email address or telephone number.
Labels, instructions and required fields
Every control needs an accessible name and a properly associated HTML label where appropriate. Required fields, expected formats and instructions should be communicated before errors occur; placeholder text is not a substitute for a label.
Keyboard order matters
Tab should move through controls in a logical sequence. Select boxes, checkboxes, buttons and date pickers must work without a mouse, with a visible focus indicator and no unexpected jumps.
Errors people can understand and fix
A red border does not explain what went wrong. Identify errors in text, associate messages with affected controls and allow corrections without losing entered data. Dynamic error messages should be announced appropriately.
Review and confirm before submission
For purchases, applications and important transactions, provide an opportunity to review and confirm information when appropriate. Submit buttons need clear names, and the result must be communicated accessibly.
What WCAG says
WCAG 2.2 covers labels or instructions (3.3.2), error identification (3.3.1), the name, role and value of controls (4.1.2), and keyboard operation (2.1.1). Testing real behavior matters as much as visual appearance.
How Blind Reader helps
Blind Reader can explain a page’s purpose, help locate forms, support navigation and assist with voice interaction. It also applies targeted automatic fixes to certain barriers, including how required fields are announced. These improvements work alongside properly built forms.
A simple test before publishing
Complete the form with a keyboard and NVDA, VoiceOver or another screen reader. Identify each field, trigger an error, correct it and confirm submission. If any step cannot be understood or completed, a barrier remains.
Sources and references
A form is accessible when people can complete the task, not merely when the form is visible.
Edition 18 · Accessibility ≠ Overlay