One page
Free$490 after the beta
Your home page, a landing page, the pricing page or a contact form.
Choose this scopeHuman-reviewed · Report in 48h
Web accessibility audits for modern businesses
Automated analysis plus manual keyboard and screen reader testing. You get the barriers ordered by what they cost, with the evidence, the recommended fix and how to verify it.
Report in 48 hours. No calls.
WCAG 2.2 AA, EN 301 549, European Accessibility Act, Keyboard navigation, NVDA, VoiceOver, Contrast, Forms, Visible focus, Headings, ARIA, Reflow at 320px
Scope
What do you need audited?
Start with whatever costs the most when it fails. Every scope includes automated analysis, manual testing and a report ready for development.
One journey
Free$990 after the beta
Product → cart → checkout. Signup → onboarding. Up to five pages, end to end.
Choose this scope
A site
Free$2,400 after the beta
A representative sample of up to fifteen templates, to know where you really stand.
Choose this scopeProcess
What we do, in order
Five steps, always in the same order. From the source code to verifying the fixes.
01 / 05
Detect
Automated analysis of the source, then every control operated by hand with a keyboard and a screen reader.
02 / 05
Understand
Each finding says what is wrong, who it affects and why it matters — before it names a criterion.
03 / 05
Prioritise
Ordered by what it costs the person who hits it, not by success criterion number.
04 / 05
Fix
Expected behaviour, a recommended implementation and the acceptance criteria.
05 / 05
Verify
A re-test confirms what closed and what is still open.
WCAG 2.2
Why an automated scan is not enough
Around a third of WCAG 2.2 success criteria can be decided automatically. The rest need someone to use the page. A dropdown that traps focus passes every scanner and fails every keyboard user.
~33%
of WCAG 2.2 success criteria can be decided automatically. The rest need a person using the page.
| Barrier | Scanner | Uxerfy |
|---|---|---|
| Images with no alternative text | Yes | Yes |
| A missing language attribute | Yes | Yes |
| Broken heading structure | Yes | Yes |
| Fields with no associated label | Yes | Yes |
| Links with generic text | Yes | Yes |
| Icon-only buttons with no name | Yes | Yes |
| Focus order that does not follow the page | No | Yes |
| Focus traps in dialogs and menus | No | Yes |
| Form errors that are never announced | No | Yes |
| Focus hidden behind a sticky header | No | Yes |
| Dynamic changes that happen silently | No | Yes |
| ARIA describing something that is not there | No | Yes |
The report
What you receive
A report a development team can act on without translating it first.
Every finding carries
- 01 The problem, in one sentence
- 02 Severity, and who it affects
- 03 The WCAG 2.2 criterion and its level
- 04 The evidence and the affected element
- 05 Whether a machine or a person found it
- 06 The recommended fix
- 07 The acceptance criteria that close it
Four levels of severity
Critical
Someone using assistive technology cannot complete the task at all. A checkout that cannot be reached by keyboard, a form whose errors are never announced, a dialog that traps focus. This is the category that ends in a complaint.
Serious
The task can be completed, but only with difficulty, guesswork or luck. An unlabelled field that can be inferred from position, a focus indicator that disappears against one background, a heading structure that makes the page hard to navigate by landmark.
Moderate
A real barrier for some people in some conditions. Contrast that passes on desktop and fails on a phone in daylight, a link whose purpose needs its surrounding sentence, a target smaller than 24px.
Minor
Worth fixing while the file is open. Redundant alternative text, a decorative image that is not hidden, a language attribute missing from a quoted phrase.
This score is an internal Uxerfy assessment indicator based on the checks included in this review. It is not a legal certification or a statement of WCAG conformance.
Add-ons
Add what your team needs
Optional, in the same order. Delivered with the report, or after the fixes.
Coming soon · $390
Remediation Pack
Every finding rewritten as a development ticket your team can pick up without translating it first.
Coming soon · $190
Accessibility Roadmap
What to do now, in 30 days, in 60 and in 90 — with the reasoning for the order.
Coming soon · $190
Accessibility Statement draft
A professionally structured draft statement, based on what the audit actually found.
Coming soon · $290
Re-test after fixes
The same scope audited again once you have shipped the fixes, with each finding marked resolved or still open.
Regulation
Regulatory context
The European Accessibility Act has applied since June 2025, and national implementations introduce obligations that depend on the service, the size of the organisation and other factors. Uxerfy documents what may apply to you, with official sources — and where you need a lawyer instead.
- EAAApplicable since 28 June 2025
- EN 301 549The European standard that points at WCAG
- WCAG 2.2Level AA, the level audited
Guides
Before you decide, read this
What is worth knowing before you order an audit: what web accessibility is, what the law asks for, how we audit and what you will receive.
Web accessibility
The most common barriers, explained without jargon and with their fix.
The regulations
What the European Accessibility Act says and who it may apply to.
The method
What is tested, with which tools, and what is out of scope.
Sample report
A real report from start to finish, to see what you get.
Questions
Frequently asked questions
Does an accessibility audit certify that I comply with the law?
No. Uxerfy carries out accessibility assessments and provides regulatory context; it does not issue conformance certifications or give legal advice. The report documents what was assessed, on what date and with what result — which is what a lawyer or a procurement questionnaire needs as a starting point.
Is an automated scan enough?
Not for anything with consequences. Automated analysis decides around a third of WCAG 2.2 success criteria, and it cannot see focus order, focus traps, errors that are never announced, or what a screen reader actually says. Those are precisely the failures that stop someone completing a purchase.
What is WCAG 2.2, and why Level AA?
WCAG is the W3C technical standard for web accessibility; 2.2 is the current version. Level AA is the level the European standard EN 301 549 points at, and the level most national implementations reference — so it is what audits are carried out against unless you ask for something else.
How long does it take?
A page, 48 hours. A journey of up to five pages, 3 working days. A representative sample, 10 working days. Real capacity is 2 audits a day; if the week is full, the order page says so before you pay.
Can you verify the fixes?
Yes, with the re-test add-on: the same scope is audited again and each finding is marked resolved or still open, including any regression the fixes introduced. It verifies the state on that date — a site's accessibility changes with every deploy.
Do you audit Spanish-language sites?
Yes. Reviews are carried out in Spanish or English, and the report is delivered in whichever you choose.
Start with a page, or a journey?
If you are unsure, start with your highest-traffic page or your checkout. That is where a barrier costs the most.
Report in 48 hours. No calls. · Sergio Gualda, Barcelona, Spain