Still looking over the WAS Body of Knowledge section about creating accessible single-page applications (SPAs), I took my research a step further beyond the items they listed (aria-live and focus management), and started exploring on my own about what else I needed to pay attention to when it came to making SPAs accessible.
Things I accomplished
- Accessibility Tips in Single-Page Applications (Deque)
- Single page applications, Angular.js and accessibility (Simply Accessible)
- Accessible Page Titles in a Single Page Application (hiddedevries)
- Learning to focus() (SitePoint)
What I learned today
- SPAs are not exempt from best practices used on static webpages or full applications. Document structure, native elements, and keyboard navigability are key to creating accessible SPAs.
- The page title should change with each new view.
- tabindex=”-1″ lets scripts bring focus to an element, but not let a user tab to it.