Patterns & Strategies for accessible web-apps

Using animated progressbars is fine for visual users, but more often than not, screen readers remain silent when your app is in an interstitial (e.g. loading) state. Here is a strategy to prevent that.

Web-apps are full of interactive items that show a new container with links and options once you interact with them. A simple user experience pattern, but hard to get right if you want to build it with accessibility in mind

A Single Page Application consists of one single HTML document - anything else is being loaded without ever really navigating off of or reloading the page. This leads to accessibility challenges

A modal dialog requires a user's response and makes it mandatory to interact with it. Focus, both literally and proverbially, can't be moved away from the modal. Learn more about what to look out for when using dialog windows

You have to inform every user about dynamic changes in your web app - not just the ones using a visual browser. Learn more about programmatically exposing asynchronous content changes to screen readers

While the experience of your app could benefit from animations, sudden movements could cause, for example, dizziness, vertigo or nausea for some of your users. Here's a strategy to deal with this.