Accessibility isn’t one time thing, it’s a habit

I think that the title says it all and you can stop reading now and can go create a habit of building accessible apps and web sites.

So, you are still here, eh? Alright then let’s talk.

As developers we have a habit of considering only users who behave like we and people around us do. This creates biases which cause us not to think thoroughly why there are elements and attributes in the web standards. We don’t get it. For the long time I didn’t get them even though I’ve been advocating for web standards long before I got paid to code.

I implore1 and challenge you as a designer and/or front-end developer to create a habit of using assistive technology every day. It may be hard at first but I promise you that your empathy for disabled users will grow exponentially during the first couple of days and you will not be the same ever again.

I promise you that you will learn when to use  <a>  and when to use  <button> . You’ll be second guessing yourself, sometimes it’s not a bad thing to do, about usage of  h1 - h6  tags.

You will start seeking out disabled people and you’ll listen to them because you want to create products which as many people as possible can use.

So go out there and build that accessibility habit because you now know that you can’t fix accessibility issues in one big release. It’s a process like coding but more meta.

  1. To beg urgently or earnestly.