WCAG 2.2 Level AA · automated analysis

Website accessibility audit

Paste your address and the system analyses your site, finds the accessibility barriers and sends you a report with every problem, who it affects and how to fix it.

Standard
WCAG 2.2 AA
Delivery
24–48 hours
Price
Free in beta

The work

How the analysis works

Three steps, and nothing for you to do beyond pasting the address.

  1. It loads your page

    Your page is opened in a real browser, the way any visitor sees it, and its structure, text, colours and controls are collected.

  2. It analyses it

    It is checked against the WCAG 2.2 Level AA criteria, grouped into the four principles.

  3. It explains it

    Every finding is prioritised by what it costs the person who meets it and explained in plain language, with the proposed fix.

The standard

What it is audited against

WCAG 2.2 Level AA, organised by its four principles. Every finding is mapped to one of them and to its specific criterion.

  1. Perceivable

    Whether the information on the page reaches someone who cannot see it, cannot see it well, or cannot distinguish the colours it is drawn in. Content that exists only as a picture, a colour or a contrast too faint to resolve is content that some of your customers do not have.

  2. Operable

    Whether the page can be used without a mouse. Keyboard access is the principle most often broken by modern component libraries: a custom dropdown that traps focus looks perfect with a mouse and locks out every keyboard user.

  3. Understandable

    Whether the page behaves predictably and tells people how to recover. Most of the cost here lands in forms: an error that is announced only in red, a field whose label disappears once it is filled, a session that expires without warning during a checkout.

  4. Robust

    Whether assistive technology can tell what each control is, what state it is in, and when something on the page has changed. This is where custom components fail: a div styled as a button is a button to everyone except the person who cannot see it.

The deliverable

One finding, in full

This is how every barrier arrives in the report: what happens, who it affects, how to fix it and how to confirm it is fixed.

Read a sample report

Example

Critical 3.3.1 Error Identification · Level A

Payment form errors are not announced to assistive technology.

Evidence
Submitting the form with an empty card field renders the message in red beside the field, but it is not associated with the input and is not placed in a live region.
Who it affects
A screen reader user receives no signal that submission failed: the form appears to have done nothing at all.
Recommended fix
Associate the message with the field using aria-describedby, mark the field aria-invalid="true", and either move focus to the first field in error or announce the summary in a container with role="alert".
Acceptance criteria
With a screen reader running, submitting the form with an invalid field announces the error and lets you reach the affected field without looking for it.

One price, more if you need it

A full audit for one base price. Widen the coverage or add extras only if you need them.

one page · 24–48 hours

Accessibility audit

Free$490 after the beta

  • Automated WCAG 2.2 AA analysis
  • Every problem, how serious it is and where it is
  • Why it matters and who it affects
  • How to fix each one
  • Your Uxerfy score
  • In your inbox in 24–48 hours
Audit my site free

See wider coverage and extras

Add-ons

Optional, in the same order.

Coming soon · $290

Code fixes

For each finding: the affected element, the corrected HTML, CSS or ARIA, and a short note on what changed and why. Delivered as a document your developer can work through from top to bottom.

Coming soon · $390

Remediation Pack

Title, severity, the success criterion, the affected location, the problem, the expected behaviour, a recommended implementation and the acceptance criteria that close it. Delivered as structured text you can paste into Jira, Linear or GitHub.

Coming soon · $190

Accessibility Roadmap

Immediate priorities, a 30/60/90-day sequence, the technical debt behind the recurring failures, and recommendations on ownership and process so the same findings do not return next quarter.

Coming soon · $90

Executive summary

The whole report in plain business language: your score, the three problems that matter most, what they put at risk and the order to tackle them. Made to forward to someone who will never read the full report.

Coming soon · $190

European Accessibility Act map

Each finding linked to the requirement it relates to in the European Accessibility Act and EN 301 549, grouped by area. A clear picture of your position for your team, your client or your adviser. It is information, not legal advice or certification.

Coming soon · $190

Accessibility Statement draft

Scope, the standard assessed against, known limitations, the feedback mechanism and the preparation date, written from your findings rather than from a template. It is a draft for your review and your legal counsel, not a certification.

Coming soon · $290

Re-analysis after fixes

Run it within 90 days of the original report. You get an updated score, a result per finding and any new issue the fixes introduced. It states what was checked on that date: a site changes with every deploy, so nothing here implies a permanent result.

Coming soon · $390

Expert review

Sergio goes through your report, tries the key flows with a keyboard and a screen reader, confirms each finding and adds notes from real use. Delivered as an annotated version of your report, a few days after the report itself.

Honesty

What an audit does not do

Regulatory requirements vary by jurisdiction, service, organisation and other factors. Uxerfy provides accessibility assessments and compliance-oriented information, not legal advice or legal certification. Consult qualified legal counsel for a determination of your obligations.

  • It does not certify conformance. Uxerfy issues no certifications and gives no legal advice.

  • It does not establish permanent compliance: it reports the state of the audited scope on the date it was audited. Every deploy can change that.

  • It does not replace usability testing with disabled users, which answers a different question: whether people actually succeed.

  • It does not cover native mobile apps or PDF documents unless they are explicitly included in the scope.

Questions

Frequently asked questions

What is a website accessibility audit?

An assessment of a website against a technical accessibility standard — here, WCAG 2.2 Level AA — identifying the barriers that prevent or hinder use by people with disabilities, and documenting what needs to change. At Uxerfy the analysis is automated: you paste the address and the report reaches your inbox in 24–48 hours.

What is the difference between an audit and remediation?

The audit says what fails, why it matters and what behaviour is expected. Remediation is the work of changing the code. Uxerfy audits and supplies the remediation guidance; with the Remediation Pack add-on, each finding arrives as a development-ready ticket with acceptance criteria.

Do you need access to our code?

No. The audit is carried out against the published site, the way anyone uses it. Access is only needed when part of the scope sits behind a login or in a test environment, and it is requested after payment.

What if the site is not public yet?

A staging environment can be audited. Say so on the order and share access when asked; the report records which environment was assessed.

Can this answer a procurement questionnaire?

The report documents the scope, the standard, the date and the findings, which is the usual starting material. If the questionnaire requires a signed declaration of conformance from an accredited body, that is a different thing and Uxerfy does not issue it.

Order an audit

Start with your highest-traffic page or your checkout. That is where a barrier costs the most.

Sergio Gualda · Barcelona, Spain