Day 48: Accessible Single Page Applications

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

Read:

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.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s