If it’s not progressively enhanced, it’s not accessible

Posted 6th November 2019 in Accessibility

In his latest article, Adam Silver does an excellent job of summarising the many ways JavaScript can fail.

the problem is less about the 1% of users who always visit your site without JavaScript and more about the 1% of visits to your site which result in users experiencing your site without JavaScript. And through no fault of their own

It comes down to lack of progressive enhancement. Websites that don’t work when JavaScript fails should be considered inaccessible.

Accessibility in your inbox

I send an accessibility-centric newsletter on the last day of every month, containing:

  • A roundup of the articles I’ve posted
  • A hot pick from my archives
  • Some interesting posts from around the web

I don’t collect any data on when, where or if people open the emails I send them. Your email will only be used to send you newsletters and will never be passed on. You can unsubscribe at any time.

More posts

Here are a couple more posts for you to enjoy. If that’s not enough, have a look at the full list.

  1. How navigation should work for keyboard users

    The web is a network of pages that are linked together, with those links often grouped in a navigation. Here’s how keyboard users traverse navigation.

  2. How button groups should work for keyboard users

    Menubars, menus, toolbars, and tablists are part of a larger family of ‘button groups’. Here’s how they should behave when using the keyboard.