Forms are where accessibility debt becomes user abandonment.
A form can pass every automated scan and still be completely unusable
for a significant chunk of your users.
Here's what I see skipped constantly in real audits:
Placeholder text used as a label
When the field gets focus, the hint disappears. For users with cognitive disabilities or memory issues, that's a dead end.
Use <label> elements. Always.
Error messages that only exist visually
Red border + error text looks complete. But if the error isn't linked to the input via aria-describedby, screen readers announce nothing.
The user submits. Nothing happens. They don't know why.
Required fields with no accessible indicator
An asterisk (*) is a visual convention. Without aria-required="true" or a text equivalent, it means nothing to assistive tech.
Autocomplete missing on personal data fields
WCAG 1.3.5 exists. Most teams don't know it does. Name, email, phone, address, those fields need proper autocomplete
attributes. For users with motor disabilities, it can be the difference between completing the form or not.
Focus order that fights the visual layout
Tab order follows DOM order, not visual order. If your CSS grid or
flexbox rearranges things visually, keyboard users may be jumping around the form in a completely unexpected sequence.
None of these fail an automated scan.
All of them fail real users.
If you're doing form reviews, what's the first thing you check?
Top comments (0)