Accessibility Tips in Single-Page Applications
Of course, now that my chapter has been printed into a gorgeous hard-cover book with embossed gold metallic flourishes, I have a few things I wish I could add; particularly to the short list of tips.
- It’s easier and less costly to incorporate accessibility the earlier you tackle it, starting with UX and Design.
- Prototype complex or custom interactions early, and include accessibility.
- Check out the ARIA Authoring Practices for known interaction patterns.
- Be generous with color contrast; it not only both helps people with low vision and color deficiency, but also low-contrast projectors and outdoor displays.
- Screen readers have ways of navigating other than using the TAB key, so you don’t need to make everything focusable.
- Interactive widgets (i.e. “controls”) should be designed to work with the keyboard, not just on hover or swipe.
- Test with accessibility browser extensions and automated testing tools for extra muscle. (Deque’s axe and WorldSpace Attest tools fall into this category)
- Test your app with real users, including users with disabilities. Organizations like Knowbility’s Access Works can help.
And now for the additional stuff:
- Accessibility is about more than developing for users with blindness or low-vision. Familiarize yourself with the needs of people with disabilities with help from the W3C.
- Make sure that client-side view changes are known to screen reader users by announcing the change in page title, using ARIA live regions and/or focus management.