Form Accessibility
Make your forms usable by everyone — proper grouping with fieldset/legend, ARIA attributes for help text, error handling, and keyboard navigation.
Why accessible forms matter
Forms are the gatekeepers of the internet. Want to create an account? Fill out a form. Need to buy something? Fill out a form. Applying for a job? Fill out a form. If a form is inaccessible, it doesn't just cause mild inconvenience — it can completely block someone from essential services.
Approximately 15% of the world's population — over one billion people — live with some form of disability. Many of these people rely on assistive technologies like screen readers, voice control software, switch devices, or keyboard-only navigation to use the web. When a form is not built with accessibility in mind, these users may:
- Not know what a field is asking for (missing labels)
- Not understand which fields are required (no clear indication)
- Not be able to navigate to all fields (broken tab order)
- Not receive error messages (errors only communicated visually)
- Not understand how fields are related (no grouping)
The good news is that most form accessibility comes from using standard HTML correctly — elements and attributes you already know. Labels, fieldsets, legends, and proper input types get you 80% of the way there. ARIA attributes handle the remaining edge cases.
Accessibility is not just about compliance or avoiding lawsuits (though inaccessible websites do face legal action). It's about building forms that work for everyone — including users on slow connections, users with temporary injuries, users in bright sunlight, and users in a hurry. Accessible forms are better forms, period.