We run axe DevTools, a developer-oriented automated accessibility scanner, across your key pages and hand you a remediation list — catching a technical rule set that differs somewhat from WAVE’s, with more precise detail on the underlying markup and ARIA usage involved.
axe DevTools audit & remediation list
An axe DevTools scan with developer-ready technical detail on every issue found.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
What we need from you
- Access to browse the specific pages you want scanned
- Confirmation of which pages carry the most weight for this scan
- Whether findings should be handed to a developer directly, or summarised for you first
This or something else?
| You want a developer-focused, automated scan using axe DevTools specifically | This fix covers it |
| You want a comprehensive, manual-and-automated audit against WCAG 2.2 AA | Accessibility audit report – WCAG 2.2 AA, the more thorough, legal-grade version |
| You want the more visual, overlay-style scanning tool instead | WAVE accessibility scan & findings report, a different tool with a different presentation |
| You already know your specific accessibility issues and want them fixed directly | The relevant targeted remediation fix instead |
What we do
- Run axe DevTools across your specified key pages
- Record every issue flagged, with the specific markup or ARIA attribute involved
- Prioritise by the tool’s own severity classification
- Compile findings into a clear, developer-usable remediation list
- Fix straightforward, low-risk issues directly where the cause is clear
What is included
- An axe DevTools scan across your specified pages
- A remediation list with specific technical detail per issue
- Straightforward issues fixed directly
- A quote for anything requiring larger remediation work
Not included
- A comprehensive manual audit against full WCAG 2.2 AA criteria — a separate, more thorough report
- Legal advice on compliance obligations or risk exposure
- Manual, judgement-based accessibility review beyond what an automated tool can flag
- Ongoing scanning after this report is delivered
Questions about this fix
Why would I choose axe DevTools over WAVE?
axe DevTools tends to give more precise, code-level detail suited to a developer actually implementing fixes, while WAVE presents issues more visually — the better fit depends on who's using the findings.
Does passing this scan mean my site is fully accessible?
No — automated tools like axe catch a meaningful but limited subset of accessibility issues; genuine full compliance needs manual review as well, which the comprehensive WCAG audit provides.
Will straightforward issues actually get fixed, or just listed?
Straightforward, low-risk issues are fixed directly as part of this; anything larger is quoted separately once you can see exactly what it involves.
Is this suitable if I have a developer who wants to fix things themselves?
Yes, the remediation list is written with enough technical specificity for a developer to act on directly.
Could this and the WAVE scan find different issues on the same page?
Yes, genuinely — the two tools use different rule sets and can each surface issues the other misses.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.