Services · By platform
WordPress Accessibility Starts and Mostly Ends With the Theme
For the owner of a WordPress site, which is statistically most owners, who wants to know whether the theme, the builder, or the plugins are the problem.
What We Keep Finding
WordPress runs a huge share of the web, which means WordPress accessibility is mostly just accessibility. The stack decides your fate. A well-built theme gives you headings, landmarks, and focus states for free, while a page-builder stack of nested divs takes them all away.
Our audits keep finding the same trio. Builder sections that read in the wrong order, menu plugins whose dropdowns need a mouse, and forms from a form plugin with labels that never got connected. That last one is worth a second, because blaming the plugin is usually wrong. The most popular contact form plugin ships an accessible default, with a real label on every field and a properly built announcement for validation. What breaks it is a site author stripping the labels out for placeholders, which looks tidier and takes the name off the field. Same shape as most of what we find here. The tool was fine and somebody configured it.
There is one thing worth checking on your own site before you order anything from anyone. The most-installed accessibility plugin on WordPress is an overlay, sitting on more than half a million sites, and a second one adds 80,000 more. If you have one, three things follow. Its own listing says it is not a substitute for an audit and is not intended to make your site legally compliant. It has to be switched off before any audit is worth reading, because otherwise we are testing the widget. And several of these plugins now publish an accessibility statement automatically under your domain, which is a conformance claim in your name that you did not write and cannot currently back up.
What We Check
- Test your real templates, so home, posts, pages, archives, contact
- Check whether an accessibility plugin is injecting anything, and switch it off before testing
- Audit the menu and search, the two plugin hotspots
- Check your page builder's output for order, headings, and landmarks
- Run forms end to end, errors included, with a screen reader
- Name the source of each finding, so theme, builder, or plugin
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. We audit the site the stack produces, not the plugins' source code. Where a plugin is the cause, you get the evidence, the element, and whether a setting exists that changes it, and the plugin's own repairs belong to its maker. We would rather tell you which plugin to look at than promise you a vetted list of replacements we do not maintain.
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.