Accessibility guidelines are versioned, and the current baseline is WCAG 2.2. AllAccessible scans new sites against WCAG 2.2 by default, so your audits are checked against the standards that procurement teams, accessibility reviewers, and regulators reference today. This guide explains what WCAG 2.2 means for your results, where the standards are shown in your dashboard, and — honestly — what you can and can't change yourself right now.

Note: Scanning against WCAG 2.2 tells you how your pages perform on automatically detectable WCAG 2.2 checks. Automated testing covers roughly 57% of WCAG 2.2 success criteria. Full WCAG conformance still requires manual testing — keyboard navigation, screen reader review, content review, and user testing. Scanning against a standard is not the same as being certified compliant with it.

WCAG 2.2 is the current W3C Recommendation and the operative accessibility baseline for 2026. Compared with earlier versions, it adds success criteria that AllAccessible's scanner now checks, including:

Because these are additional checks, a site evaluated against WCAG 2.2 is being held to the most current standard. Throughout the dashboard you'll see WCAG 2.2 referenced — for example, the Scan Score explanation notes it covers "approximately 57% of WCAG 2.2 criteria," and the WCAG coverage badges break your automated results down by Level A, AA, and AAA.

If your site was set up recently, there's nothing to configure — new sites scan against WCAG 2.2 out of the box. Your audits already reference the current standard, and reports and coverage badges reflect WCAG 2.2 criteria.

This is the recommended baseline for almost everyone. Level AA is the level most laws, procurement requirements, and accessibility reviewers reference, and WCAG 2.2 Level AA is what AllAccessible applies by default.

This is the part to be precise about.

Where the standards are shown. In your dashboard, go to Widget Settings for your site and open the Advanced Scanning Options section. There you'll find a Compliance Standards list showing the standards AllAccessible checks, including:

By default this list includes WCAG 2.2 Level AA, alongside the earlier WCAG levels and Section 508.

What you can change yourself today. This is where expectations need to be set honestly: the Advanced Scanning Options panel is currently read-only. It's labelled "Coming Soon," and the panel itself states: "Scanning configuration will be customizable in a future update. Current settings shown are defaults." So the checkboxes show you which standards are applied by default — they are not yet an editable toggle you can flip on your own.

So how does an existing site opt in? There is no self-serve WCAG-version switch in the dashboard at this time. If you want to confirm that an existing site is being scanned against WCAG 2.2 — or you believe it's still on an older baseline and want it moved — contact support and we'll confirm the site's configuration for you.

📷 Widget Settings → Advanced Scanning Options showing the read-only Compliance Standards list with "WCAG 2.2 Level AA (Latest)" and a "Coming Soon" badge

Q: Which WCAG version does AllAccessible use?
A: WCAG 2.2 is the default for new sites, and the dashboard references WCAG 2.2 throughout (Scan Score explanation, coverage badges). WCAG 2.2 Level AA is the applied baseline.

Q: I set up my site recently — do I need to turn on WCAG 2.2?
A: No. New sites scan against WCAG 2.2 by default.

Q: Can I choose my own standards or WCAG level in the dashboard?
A: Not yet. The Compliance Standards list under Widget Settings → Advanced Scanning Options shows the defaults but is currently read-only and marked "Coming Soon." Editable scanning configuration is planned for a future update.

Q: How do I make sure my older site is on WCAG 2.2?
A: Contact support. There isn't a self-serve version toggle today, so we'll confirm or update your site's configuration for you.

Q: Does scanning against WCAG 2.2 mean my site is WCAG 2.2 compliant?
A: No. It means your pages are checked against automatically detectable WCAG 2.2 criteria (about 57% of them). Full conformance requires manual testing and human evaluation. Use the scan to prioritize, not to certify.

Q: Which version do reports use?
A: Reports reference WCAG criteria explicitly — for example, VPAT / Accessibility Conformance Reports state the WCAG edition they cover. See Generating a VPAT / Compliance Report for details on what a given report attests to.

Cause: This is expected. The Advanced Scanning Options / Compliance Standards panel is currently read-only and marked "Coming Soon." It displays the defaults being applied, not an editable configuration.

Solution: No action needed to stay on the WCAG 2.2 default. If you need a non-default configuration, contact support.

Cause: There's no self-serve version indicator you can toggle, and older sites may predate the WCAG 2.2 default.

Solution: Check the Scan Score explanation and WCAG coverage badges (which reference WCAG 2.2), and contact support if you need explicit confirmation for a specific site.

Last Updated: July 2026
​Where: Widget Settings → Advanced Scanning Options (Compliance Standards — currently read-only)
​Default: New sites scan against WCAG 2.2 Level AA