Menu

Post image 1
Post image 2
1 / 2
0

Form accessibility: the checklist nobody actually uses (until users complain)

DEV Community·a11ySolutions·about 1 month ago
#DeCphrD9
#a11y#html#webdev#software#users#form
Reading 0:00
15s threshold

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.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.

Read More