Fork me on GitHub


Important notice about the «ADG» project

Important notice: Due to large demand, the «Accessibility Developer Guide» project (currently a proof of concept with low priority) will become a top priority priority in 2017. We will make this guide become what it deserves to be for so long already: a comprehensive resource for all folks interested in accessibility. For this we need your support!


With this pragmatic guide you'll learn how to develop and test accessible websites. It is written for physically non-impaired web developers who want to build accessible websites, but it will be useful for anyone else interested in learning about accessibility (also known under the numeronym A11y).

Why this guide?

My name is Joshua, and I am a sighted web developer. I'm working for the foundation Access for all, which targets to make the internet an accessible place. I already spent a lot of time learning how to create accessible websites, and I know this is not a trivial topic. So I want to share my full knowledge with you to make your life easier.

Everything in this guide is counter-checked by my blind co-workers (Daniele, Petra, and Gianfranco), who are very experienced accessibility consultants.

What you will get

You'll learn in a very pragmatic way many important things you need to know when creating accessible websites. We'll provide you with sensible examples that you can experiment with so you get a profound feeling about what's needed to make a website accessible.

We'll focus on screenreader usage (it's not that hard, you'll see), as it covers most of the important topics. Some other tools will be discussed, too, to give a fuller picture.

This guide is written in a rather shorthand and technical language, so good knowledge of HTML, CSS, JavaScript and commonly used browser technologies is assumed.

Why bother?

Why should anyone be interested to go the extra mile to provide accessible websites - beneath the fact that 14% of the world population (TODO: reference?) suffers from some sort of disability or impairment?

  • Law requirements: many countries have concrete obligations about accessibility, for example (TODO: Links?) Switzerland, Germany, France, and the USA.
  • Moral obligations: for people with disabilities, the internet offers an incredible amount of new ways to communicate, work, and therefore live an autonomous life.
  • Clean code: Accessibility relies heavily on clean HTML code. This means that a website built with accessibility in mind always results in a high quality product.

Don't be the next one of our customers who's asked by us: "Hmmm, so what was your front end web developer's profession again??"

Create accessible websites, starting from the current day! It's not that hard, you'll see!

Enough introduction! What can I learn here?