Make your WordPress site usable by people who rely on assistive technology
A manual audit against WCAG 2.1 AA, followed by the actual code fixes: keyboard navigation, screen reader labels, colour contrast, form errors. Not a script that bolts a widget onto your homepage.
- Standard
- WCAG 2.1 AA
- Method
- Manual audit, not an overlay
- Legal advice
- Not offered, this is engineering
- Quote
- Fixed price before work starts
The honest answer
Do accessibility overlay plugins make a WordPress site ADA compliant?
No, and we will not tell you otherwise to sell you one. An overlay plugin adds a script that tries to adjust the page in the browser: bigger text, more contrast, a screen-reader menu. It does not fix a form with no label, a button that only a mouse can click, or an image with no useful alt text, and several overlay vendors have themselves been sued for the accessibility of their own tools. A WCAG audit reads your actual markup, keyboard behaviour and screen reader output, then fixes the code, so the fix is real and does not disappear if you remove a script.
- Keyboard navigation tested without a mouse, on every interactive element
- Screen reader output checked with real assistive technology, not simulated
- Colour contrast measured against WCAG 2.1 AA thresholds
- Forms checked for labels, error messages and focus order
- Fixes made in your theme and plugin code, not a third-party overlay script
- Written report mapping each issue to the WCAG success criterion it fails
Honest comparison
An overlay widget, or a manual WCAG audit and fix?
An overlay is quick to install and better than nothing for a handful of adjustments. It is not evidence of compliance and does not touch the underlying code.
Overlay plugin | Manual audit and fixes (us) | |
|---|---|---|
| Time to install | Minutes | An audit takes longer, fixes are scoped and quoted |
| Fixes missing form labels or alt text | Yes, in the actual code | |
| Works with real screen reader software | Inconsistently | Tested directly |
| Recognised as evidence of compliance effort | Disputed, some overlays have faced their own lawsuits | A documented, code-level fix |
| Removable without losing the fix | The fix goes with the script | Stays in your code |
How it works
How does a WordPress accessibility audit work?
We audit against WCAG 2.1 AA
Manual testing with keyboard navigation and screen reader software, plus automated checks for what those tools catch reliably.
You get a written report and a fixed price
Every issue found, mapped to the WCAG criterion it fails, with a fixed price to fix it, usually within 48 hours.
We fix the code and test on staging
Fixes go into your theme and plugin code, tested with the same tools used in the audit.
Re-test and hand over
A final pass confirms the fixes hold, with the report and the code delivered to your repository.
Related
Related services
See our coding standard
Accessibility basics are part of every build, review and fix we do, not a separate afterthought.
Engineering standardsSomething custom to fix alongside it
Custom functionality built or changed with accessibility in mind from the start.
Custom plugin developmentKeep it accessible after launch
New content and plugin updates can quietly break accessibility fixes. A care plan catches that.
Maintenance services
