What Topics Does the Accessibility Developer Guide Cover?

The Accessibility Developer Guide (ADG) covers the full workflow of building accessible websites: design, implementation, and testing. Its content is based strictly on the W3C's Web Content Accessibility Guidelines (WCAG 2.1), and it is organized into distinct content types — Knowledge, Examples, and Setup — so you can move from understanding a concept to seeing a working pattern to configuring a test environment. If your goal is to learn accessibility end to end rather than look up a single rule, the site is structured for exactly that.

The three content types

The site separates its material so that each piece answers a different kind of question:

This split matters because accessibility work fails in different ways at each stage: a designer may not know a pattern exists, a developer may implement it incorrectly, and a tester may not have a working environment to verify it. The ADG addresses each stage separately.

Design and implementation topics

The Examples section documents reusable interface patterns. Three that appear on the site:

• Skip links — usually the first interactive element on a page. They are visually hidden by default, appear on keyboard focus, and let users bypass repeated blocks quickly.
• Accordions — a set of content panels, each of which the user can expand or collapse vertically.
• Tablist widgets (tab panels, tabs) — used to divide complex page content into smaller sections, where each section is represented by a tab label and only one panel is shown at a time. The site describes tablists as small, self-contained page fragments within a larger page.

These are the kinds of patterns where implementation details determine whether the result is actually usable with a keyboard or screen reader, so pairing each example with its underlying concept is the point of the structure.

Testing and environment setup

Accessibility testing often requires running more than one operating system or browser, and the ADG treats that as part of the curriculum rather than an afterthought. One documented example is configuring VMware Fusion on macOS to run Windows as a virtual machine. According to the site, this needs special configuration to integrate Windows seamlessly into a daily workflow, and once set up properly, accessibility testing on macOS becomes considerably more comfortable.

If you are planning a testing routine, that entry is the place to start when your target environment differs from your working machine.

Who the guide is for

The ADG describes itself as the result of many years of hands-on practice in testing websites for accessibility and developing accessible web applications. It was formed by the «Accessibility Alliance», combining the daily experience of user experts with special needs and the technical knowledge of fullstack web developers.

That origin explains the guide's practical tone: it aims to provide the simplest and most effective best practices for designing, implementing, and testing websites with accessibility in mind, rather than restating the WCAG specification.

Regulatory context

The site also covers accessibility law where it affects developers. One entry addresses the European Accessibility Act (EAA), described as key EU legislation designed to harmonise accessibility requirements across all member states, with the purpose of ensuring that people with disabilities can access products and services. If you work on products sold or operated in the EU, this is the relevant background to check alongside the technical material.

How to use the site

A practical path through the content:

1. Start with Knowledge for the concept you need — for example, skip navigation links, which the site presents as a proven way to improve keyboard navigation on real-world websites by letting keyboard users jump directly to main content instead of tabbing through long headers or navigation on every page.
2. Move to Examples to see the pattern implemented — skip links, accordions, and tablists are all documented there.
3. Set up your test environment using the Setup entries when your testing platform differs from your development platform.
4. Check the regulatory entries if your project falls under legislation such as the EAA.

The site also maintains a "Recent changes" list, so you can see what has been added or revised — useful if you are returning to it over time rather than reading it once.