Skip to main content
Contact us
  • 8 min read
  • Last updated

What a WCAG 2.2 Accessibility Audit Covers, and What It Costs

An audit against WCAG 2.2 Level AA names every failing success criterion on a site and sets out exactly what closes it, not a vague accessibility score.

  • Website accessibility
  • WCAG compliance
  • Website development Australia

Quick answer:A WCAG 2.2 accessibility audit tests a website against the W3C's AA success criteria and reports every failure with a specific fix.

Quick answer

What does a WCAG 2.2 accessibility audit check and cost?

High confidenceVerified

A WCAG 2.2 accessibility audit tests every page against the W3C's AA success criteria and reports each failure with a fix. A one-day audit is priced at $1,495 (Product Support retainer (entry tier, per month)).

Additional Context

The audit tests perceivable, operable, understandable and robust criteria across every template, not a single page, and hands over a prioritised fix list rather than a pass or fail label.

Sources

Scope and standards

What a WCAG 2.2 accessibility audit covers

A WCAG 2.2 accessibility audit tests a website against the W3C's Level AA success criteria across four principles: perceivable, operable, understandable and robust. The auditor checks colour contrast against the 4.5:1 (W3C, 2024) minimum for body text, confirms every clickable element meets the 24 by 24 CSS pixels (W3C, 2024) minimum pointer target, and works through every page with a keyboard alone and with a screen reader. Forms, navigation, video captions and PDF documents are all in scope where they sit on the live site.

Government bodies in Australia must meet WCAG 2.1 AA (Australian Public Service Commission, 2023) for their own digital content, a lower bar than the WCAG 2.2 AA standard this audit tests against, which closes gaps the earlier version left open, including a minimum size for clickable targets. Most businesses commissioning an audit are not under that legal obligation, yet accessibility by design is increasingly what a client, a funder or a procurement panel expects to see evidenced before a contract proceeds.

Accessibility compliance

Why inaccessible sites cost more than they save

Problem

Websites built without accessibility in mind exclude a meaningful share of visitors, create legal exposure under the Disability Discrimination Act, and generate rework when a government funder or large customer asks for a conformance report late in a project.

Common Pain Points

  • Legal exposure Unremediated accessibility barriers can trigger complaints under the Disability Discrimination Act 1992.
  • Excluded users Keyboard-only and screen-reader users abandon a site the moment a form or menu cannot be operated without a mouse.
  • Procurement blockers Government and enterprise buyers increasingly ask for a WCAG 2.2 conformance statement before a contract proceeds.

Business Impact

  • Time Wasted Each round of post-launch fixes pulls developers off other work to retrofit pages that should have passed accessibility testing the first time.
  • Cost Implication Retrofitting an existing build after a client or funder flags non-conformance costs more than designing to WCAG 2.2 AA from the first sprint.
  • Opportunity Cost Site experiences that exclude part of the 5.5 million Australians living with disability forgo a market segment competitors are starting to design for.

Solution

National Digital's WCAG 2.2 audit combines automated scanning with manual keyboard and screen-reader testing, then hands over a prioritised fix list mapped to each failing success criterion.

Our Approach

  1. Automated scan and crawl (Initial pass)Every template and page type is crawled and run through automated accessibility testing tools to catch programmatic failures such as missing alt text and invalid markup.
  2. Manual keyboard and screen reader testing (Core testing)An auditor works through key user journeys using only a keyboard and a screen reader, since automated tools alone cannot catch focus order, colour contrast in context or unclear link labels.
  3. Prioritised findings report (Reporting)Each failing success criterion is logged against its WCAG 2.2 reference with a severity rating and a specific fix, not a generic recommendation.
  4. Fix verification (Follow-up)Once the development team has made changes, the flagged items are retested to confirm the fix closes the criterion rather than hiding the symptom.

Expected Outcome

A written conformance report against WCAG 2.2 AA, with every fail prioritised and a clear path to close it.

Key Takeaways

What to expect from a WCAG 2.2 audit

  • An audit tests against WCAG 2.2 Level AA, not an older or informal standard.Critical

    WCAG 2.2 added success criteria that 2.1 audits never checked, including minimum target size for clickable elements, so an audit run to the older version misses real defects.

  • Automated scanners catch only part of the picture.Important

    Tools flag missing alt text and invalid markup well, but focus order, colour contrast in context and unclear link labels need a person testing with a keyboard and a screen reader.

  • The report should map every fail to a specific fix.Important

    A useful audit report names the failing WCAG 2.2 success criterion, where it occurs on the site, and the change that closes it, so a developer can act without further scoping.

  • Retesting after fixes confirms the barrier is actually closed.Helpful

    A fix that hides a symptom without meeting the underlying success criterion can still pass a glance, so the engagement includes a retest to confirm the criterion is actually closed.

A WCAG 2.2 audit combines automated and manual testing, reports against named success criteria, and verifies each fix actually closes the gap it was meant to close.

Reporting and remediation

How findings get reported and fixed

A conformance report lists each WCAG 2.2 success criterion the site fails, where it occurs, and what closes it. A well-written report names the criterion precisely: contrast falls short of the 4.5:1 (W3C, 2024) minimum on the primary navigation menu, and the fix is changing the text colour to one that meets it on that background. A 2026 peer-reviewed study of 42 Australian university websites audited across two phases found that across 42 Australian university websites audited in two phases from 2022 to 2024, detected errors fell, but missing alternative text and unclear link and button labels persisted (Badiuzzaman et al., 2026), which matches a pattern seen in repeat audits generally: structural errors get fixed first because they are easy to spot, and judgement calls such as link labelling linger.

Most businesses do not need a full platform rebuild to close what an audit finds. The majority of fails on a typical commercial site sit in content and component patterns: missing form labels, link text that only makes sense out of context, and colour combinations chosen in a design tool without being tested. These are fixable inside the existing design system. Where the audit does turn up a structural issue, such as a template that cannot be operated by keyboard at all, that is a build problem, and it shows up most often during a website redesign when nobody retested the new components against the standard.

National Digital scopes a standalone WCAG 2.2 audit as one day of focused testing, priced at $1,495 (Product Support retainer (entry tier, per month)), the entry tier of its published day rate. That covers the crawl, the manual pass and the written report. Remediation is scoped separately once the findings are in, since the website accessibility cost of fixing what the audit finds depends on what it finds. National Digital builds client platforms to WCAG 2.2 Level AA.

Ready to see where your site stands against WCAG 2.2?

A single audit gives you a prioritised list of what to fix and why it matters, scoped before any remediation work begins.

WCAG 2.2 accessibility audit: common questions

How much does a WCAG 2.2 accessibility audit cost in Australia?

National Digital scopes a standalone audit as one day of testing, priced at $1,495 (Product Support retainer (entry tier, per month)), the entry tier of its published day rate. That covers the crawl, manual testing and the written report; fixing what it finds is scoped separately.

What does a WCAG 2.2 accessibility audit check?

It tests the site against every Level AA success criterion in WCAG 2.2, covering colour contrast, keyboard operation, screen reader compatibility, form labelling, focus order and pointer target size, across every template and page type in use.

Is WCAG 2.2 a legal requirement for an Australian business?

There is no blanket legal mandate for private businesses, but the Disability Discrimination Act 1992 has supported complaints over inaccessible websites, and Australian Government content must meet WCAG 2.1 AA (Australian Public Service Commission, 2023), a lower bar than WCAG 2.2 AA. Many funders and large customers now ask for conformance evidence directly.

What's the difference between an automated scan and a full accessibility audit?

An automated scan catches programmatic defects such as missing alt text or invalid markup, but it cannot judge whether a focus order makes sense, whether a link label is clear out of context, or whether colour contrast works in its actual setting. A full audit adds manual keyboard and screen reader testing to catch those.

How is a WCAG 2.2 audit different from a WCAG 2.1 audit?

WCAG 2.2 added success criteria that 2.1 never checked, including a minimum pointer target size, and it removed an outdated criterion about markup parsing. A site that passed a 2.1 audit can still fail new checks under 2.2.

References