I build small business websites on my own, and I want them usable by people who rely on keyboards and assistive technology. I can check semantics, labels, contrast and basic keyboard navigation, but I can't reproduce every browser and screen-reader combination. What minimum hands-on testing would you prioritize before launch? I'm trying to make accessibility part of routine QA rather than a vague promise at the end.
Deciding how much accessibility testing is realistic for a solo freelancer
- webdev
- accessibility
- testing
- realistic
14
3 replies
I’d test keyboard-only navigation on every page, then run one screen reader pass on the main flows: home, forms, menus, and checkout or cont...
I’d test keyboard-only navigation on every page, then run one screen reader pass on the main flows: home, forms, menus, and checkout or contact. That catches the stuff users actually hit first.
Agree, and make sure focus order makes sense without the mouse. If the tab key wanders around like it’s lost, that’s a problem you can spot fast.
I’d also keep a short checklist for headings, labels, error messages, and visible focus states. Those are the boring basics that save you fr...