What WCAG 2.2 AA asks of a Drupal site
WCAG 2.2 is the technical standard behind most accessibility requirements. Its success criteria are grouped under principles, and on a Drupal site each one lands on something specific:
- Perceivable: text alternatives for images, captions and transcripts for media, and a contrast ratio of at least 4.5:1 for body text.
- Operable: every control usable by keyboard alone without a trap, focus that stays visible, and targets of at least 24 by 24 CSS pixels.
- Understandable: the page language declared, navigation that behaves the same way on every template, and form errors that say what went wrong.
- Robust: markup that assistive technology, including screen readers, can interpret reliably.
WCAG, Section 508 and the European Accessibility Act
WCAG is the standard; Section 508 in the United States and EN 301 549 in Europe are rules that point at it, and the European Accessibility Act has applied to e-commerce services since 28 June 2025. An audit at WCAG 2.2 AA answers the older references at the same time. Which of them applies to you, and in what format the answer is owed, is set out on the Drupal accessibility audit page.
Articles on accessibility
How we run this work
An accessibility audit combines an automated scan with manual testing by keyboard and screen reader, on the templates and components your Drupal site actually uses. Every finding is written against the WCAG 2.2 success criterion it fails, located by component so that one fix closes every instance, and given a recommended fix and an effort. The report is yours: you can take it to your own developers, to another firm, or back to us.
The public-sector sites we can show are SPREP's own site and the sites built from its platform, including PRISMSS in English and French. We designed, built and maintain them; they are the kind of site the audit is written for, not audit results.
- Drupal accessibility audit: WCAG 2.2 and Section 508, by scan, keyboard and screen reader.
- Drupal site audit: accessibility, security, module compatibility and performance in one review, when you are not sure where to start.
- QA and software testing: automated accessibility checks that run on every build.
- Government and public sector: the SPREP sites and how we work with public bodies.