Services · By platform
Drupal Accessibility Audit: Built for the Sites With Deadlines
For the government, university, or enterprise team on Drupal, where accessibility is not optional and the Title II clock is already running.
What We Keep Finding
Drupal's core takes accessibility seriously, and then real sites add themes, Views, Paragraphs, and a decade of content. That is where the gaps open. View filters without announced results, paragraph components stacked into heading chaos, and webforms whose error summaries never reach the screen reader.
Contributed code is where a Drupal site's accessibility is actually decided, and Drupal is refreshingly plain about it. Where Shopify makes theme accessibility a condition of being listed and WordPress reviews themes and hedges about what the review means, Drupal states outright that its own project site certifies nothing for accessibility. So the core gate is real and it stops at core, which is exactly the boundary an audit has to work along.
Your deadline depends on which regime you are under, and a lot of advice published through 2025 has the wrong year on it. State and local government web content is bound to WCAG 2.1 Level AA under the Justice Department's rule. The dates are April 26, 2027 for entities whose population is 50,000 or more and April 26, 2028 for everyone smaller, both a year later than the dates originally set. A federal agency is under Section 508 instead, which points at WCAG 2.0 Level A and AA and has not moved since 2018. So a federal Drupal site is measured against a standard two versions behind what Drupal core targets.
One piece of evidence worth having when somebody asks why a scanner will not cover this. The UK monitored 1,203 public sector websites over three years, and the most common problems it found were insufficient contrast, missing visible focus, keyboard operation, and content that does not reflow. Three of those four are not things a tool settles on its own, and that is a regulator's own dataset rather than ours.
What We Check
- Test your themed output rather than core's promises, so pages, views, forms
- Check exposed filters and search for announced result updates
- Audit paragraph and block components for structure and order
- Run webforms end to end with a screen reader, errors included
- Name the contributed module behind each finding, since core is not usually the cause
- Map findings to the standard your regime names, 2.1 AA under Title II or 2.0 AA under 508
What You Get
Every service on this site runs the same three-pass engine: an automated scan, an expert review of all 55 WCAG 2.2 A and AA rules, and a hands-on session with a professional blind screen-reader user. You get one report with every finding screenshotted, ranked by user impact, and linked to its fix. Your team fixes, we verify: the re-audit is half price within 3 months.
The format is not a mystery either. Read the sample report before you spend anything.
The Honest Limit
One honest limit. Contributed-module internals belong to their maintainers. We name the module behind each finding and, where the community has an accessible alternative or a patch, point at it, and where it does not, we say that instead of implying one exists. Note as well that a public-sector procurement reviewer may measure the report against W3C's own evaluation methodology, which asks for things beyond a findings list, so tell us at scope confirmation if that is the audience.
What It Costs
Rapid Audit: $499, up to 10 pages you pick, report in 5 business days. Standard Audit: $1,499, up to 25 pages in 10 business days. Flat rates, no discovery calls, and a real blind screen-reader user on every engagement. Pick your pages. We bring the humans.
Worth Reading Next
Related on this site
Guides, checklists, tools, and terms that go with this service.