Fork me on GitHub

Header

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!

Content disclaimer

Or: "Why you shouldn't believe us everything we claim in this guide"

Rembering browser wars?

You remember browser wars, don't you? Different devices and technologies battled for supremacy on the WWW, and it was extremely hard (if not impossible) to create a website that was capable of being displayed correctly on every browser.

In some way, the same applies to accessibility a little bit today - not because of opposing forces fighting each other, but because it's a very broad and long time neglected topic. At the time being, there are now black/white answers to many questions, and there's not a solution to every specific problem. There are standards, and technology vendors all in all are acting in concert, but it will take some time, until the whole topic has gained a mature status in both technical aspects and in public awareness.

What does this mean?

The good message: there are many good solutions to most problems, and pitfalls are well known and thus can be circumvented. At «Access for all», we have many years of experience in distinguishing good practices from problematic ones, and in recommending them to our clients.

Still, we are not all-knowing - the web is evolving every day, and we're trying to keep up with it. So in this guide, we are only providing our own opinions and best practices here. We don't claim them to be the best ones (let be the only ones), but they are based on our profound experience as both users and developers of websites and built upon knowledge of the official resources like WCAG 2.0.

Never forget!

Please keep this in mind while reading this guide. If you stumble over something that seems inadequate or even wrong, you are very welcome to support us with corrections, suggestions, or even plain hard code!

You're still wasting my time! Can we start now, please?