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!
To develop accessible websites, some specific tools are needed.
In this section, we'll introduce you to the main tool we use in our daily business, the screenreader, and how it can be configured for optimum performance when developing and testing websites on accessibility.
Windows is the most used desktop operating system when it comes to accessibility.
You won't get around having a current version of it running when developing and testing accessible websites.
Screenreaders will be your main evaluation tools when developing accessible websites.
While JAWS is the most used commercial screenreader, NVDA is the most used open source one.
A screenreader sits on top of a browser, so it's important to choose the right ones when developing.
While Internet Explorer is the most used commercial browser, Firefox is the most used open source one (in terms of screenreader usage).
Beneath screenreaders, there are a lot of useful tools available that help developing accessible websites.
Here we suggest our favorites that will be used throughout this guide.
Many assistive technologies don't support pointing devices (like a mouse), so they only rely on keyboard input. It's important to know the basic commands, shortcuts, and idioms of keyboard navigation.
Focus of these examples
Focus on screenreader usage!
The following examples' focus mainly lies on screenreader usage.
You'll learn more about other tools and topics in the "Tools & workshops" section.