Good Accessibility Requirements Prevent Rework
Accessibility requirements do not need to be complicated. They need to be clear enough that the team knows what to build, test, accept, and review.
Tommy Truong
Focus Visible and Focus Order
A practical Field Guide page about making keyboard focus visible, predictable, and ordered so people do not lose their place on the page.
Error Messages and Recovery
A practical Field Guide page about writing and placing error messages so users can understand what went wrong and recover without guessing.
Keyboard-Only Navigation
A practical Field Guide page about checking whether people can move through screens, controls, menus, dialogs, and forms without using a mouse.
Form Review Checklist
A practical checklist for reviewing labels, instructions, required fields, errors, grouping, and recovery before a form goes to accessibility review.
Forms and Labels
A practical Field Guide page about labels, instructions, grouping, and required fields that help forms feel usable instead of like guessing games.
QA Keyboard Check
A practical no-mouse QA checklist for checking keyboard access, visible focus, focus order, traps, dialogs, forms, errors, and common interactive controls.
Review Readiness
A practical field note on checking common accessibility issues before formal review so teams can reduce avoidable rework.
How to Use This Guide
A practical pathfinding page for using the Accessibility Field Guide for immediate work, learning, training, and common accessibility review moments.
Accessibility Requirements Checklist
A checklist for turning early accessibility risks into requirements, acceptance criteria, design notes, and QA checks.
