📋 GRC compliance for CMMC 2.0, CPCSC, CPA Canada, IIROC…SaaS discovery for data governanceFree enriched web chat widget🚀 Enriched remote support without your laptop

Website accessibility scan

Your domain scan now checks accessibility too.

The Lavawall® domain scan tests your web pages against the WCAG 2.0, 2.1, and 2.2 Level A and AA rules, the same guidelines that Ontario, Manitoba, the federal government, Quebec, the UK, the European Union, and the United States build their accessibility laws on. You see what fails, where, and how to fix it, next to your security results.

Scan my website freeStart my free trial (no credit card)

WCAG 2.0, 2.1, and 2.2 · Level A and AA · results per standard · how-to-fix links

What the accessibility results look like

A real scan, shown with example data.

The Accessibility (automated) section of a Lavawall domain scan: five pages tested with the WCAG 2.0, 2.1, and 2.2 Level A and AA rules, a summary for WCAG 2.2 Level AA and for WCAG 2.0 Level AA (the Ontario AODA requirement) with the success criteria that failed, need review, and were covered, and a filterable list of issues with examples and how-to-fix links.
Accessibility (automated). Each standard gets its own result, the success criteria that failed or need review, and how much of it automated rules could check. Every issue links to an example on your page and to how to fix it.

What the scan checks

The scan loads your public pages the way a visitor's browser shows them and runs the automated rules for WCAG 2.0, 2.1, and 2.2 at Level A and AA. The free scan at lavawall.com/scan checks your home page. The scan in the Lavawall console checks more of your public pages and keeps the results with your client's other evidence.

  • A result for each standard. WCAG 2.2 Level AA, and WCAG 2.0 Level AA for the Ontario AODA, each with the success criteria that failed, the ones that need a person to review, and how many success criteria the automated rules could check.
  • Issues you can act on. Each issue names the rule, its impact, the WCAG success criteria and standards it affects, how many elements and pages it was found on, an example with the page and element, and a link to how to fix it. Colour contrast issues include a picture of the element from the test browser.
  • Safe to run. The test browser blocks requests from your pages to internal addresses and unusual ports, and the report says how many it blocked.
  • A look ahead. A separate section, marked as a draft, shows how the same pages do against the testable requirements in the current WCAG 3 Working Draft.
  • In both languages. The results read in English or French, to match your console.

Automated testing finds only some accessibility barriers. Many WCAG success criteria need a person to judge them, such as keyboard use, screen reader use, captions, and whether text alternatives make sense. The scan results are not a conformance claim under WCAG, the AODA, or any other standard.

The laws and standards that use WCAG

Most accessibility laws for websites point to WCAG 2, either directly or through the European standard EN 301 549. Content that meets WCAG 2.2 Level AA also meets WCAG 2.1 and WCAG 2.0, so it satisfies every rule below.

Website accessibility rules that use WCAG, checked against primary sources on 15 October 2026.
WhereRule and who it coversWCAG version named
OntarioAccessibility for Ontarians with Disabilities Act (AODA), Integrated Accessibility Standards (O. Reg. 191/11), section 14: designated public sector organizations and large organizations (50 or more employees in Ontario)WCAG 2.0 Level AA, other than live captions and prerecorded audio description
ManitobaAccessibility for Manitobans Act, Accessible Information and Communication Standard Regulation: organizations with at least one employee in Manitoba; private sector and non-profit organizations from 1 May 2025WCAG 2.1 Level AA
Canada (federal)Accessible Canada Act, Accessible Canada Regulations as amended on 5 December 2025: the federal public sector from 5 December 2027, and federally regulated businesses with 100 or more employees from 5 December 2028CAN/ASC-EN 301 549:2024, whose web clause requires WCAG 2.1 Level AA
QuebecStandard sur l'accessibilité des sites Web (which replaced SGQRI 008), in effect since 29 April 2024: Quebec government departments and public bodiesWCAG 2.1, plus selected WCAG 2.2 success criteria, with Level AA as the general target
British ColumbiaAccessible British Columbia Act: the employment and service delivery standards are still being drafted. The BC government's own web content standards apply to its websitesThe most current version of WCAG at Level AA (BC government websites)
United KingdomPublic Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018: public sector websites and appsWCAG 2.2 Level AA
European UnionEuropean Accessibility Act (Directive (EU) 2019/882), in application since 28 June 2025, for products and services such as online shops and banking; and the Web Accessibility Directive (Directive (EU) 2016/2102) for public sector websites and appsWCAG 2.1 Level AA through EN 301 549 V3.2.1. Version 4.1.1, published in September 2026, is based on WCAG 2.2 and becomes the reference once the European Commission cites it
United StatesADA Title II rule of the Department of Justice: state and local governments, by 26 April 2027 for those serving 50,000 people or more and 26 April 2028 for the restWCAG 2.1 Level AA
United States (federal)Section 508 of the Rehabilitation Act, Revised 508 Standards: federal agencies and the technology they buyWCAG 2.0 Level AA

Other countries, procurement rules, and contracts also name WCAG 2 or EN 301 549, so check which version yours asks for. This table is general information, not legal advice.

Track the rule that applies to you as a compliance framework in Lavawall: Ontario AODA, ADA Title II, WCAG 2.2, WCAG 2.0, and the WCAG 3 draft.

From scan to evidence

Scan the site

Run the free scan on your home page, or scan from the Lavawall console to cover more of your public pages and keep the history.

Fix what the rules found

Filter the issues, open the example to find the element, and follow the how-to-fix link. Contrast, missing labels, and touch target size are usually quick wins.

Review what a scanner cannot judge

Test with a keyboard and a screen reader, check captions, and read your text alternatives. The results list the criteria that still need a person.

Keep the record

Turn on the framework for your rule in Lavawall GRC, attach the scan reports and your test notes as evidence, and re-scan on a schedule, because content changes every week.

Frequently asked questions

Does the Lavawall domain scan check website accessibility?

Yes. Alongside the security checks, the domain scan tests your public web pages against the automated rules for WCAG 2.0, 2.1, and 2.2 at Level A and AA. The free scan checks your home page, and the scan in the Lavawall console checks more of your public pages. Results are reported per standard, for example WCAG 2.2 Level AA and WCAG 2.0 Level AA for the Ontario AODA.

Which laws use WCAG?

Many. Ontario's AODA names WCAG 2.0 Level AA. Manitoba's Accessible Information and Communication Standard names WCAG 2.1 Level AA. The Accessible Canada Regulations, Quebec's government web standard, and the European Accessibility Act and Web Accessibility Directive rely on EN 301 549 or WCAG 2.1. UK public sector websites must meet WCAG 2.2 Level AA, the US ADA Title II rule names WCAG 2.1 Level AA, and Section 508 names WCAG 2.0 Level AA.

Which WCAG version should I test against?

The one your rule names, and ideally WCAG 2.2 Level AA. Content that meets WCAG 2.2 also meets WCAG 2.1 and WCAG 2.0, so meeting WCAG 2.2 Level AA covers every rule in the table on this page. The scan reports each version separately so you can show the one your regulator or contract asks for.

Does a clean scan mean my website is compliant?

No. Automated testing finds only some accessibility barriers. Many WCAG success criteria need a person to judge them, such as keyboard use, screen reader use, captions, and whether text alternatives make sense. The scan shows how much of each standard it covered and which criteria still need manual review. It is not a conformance claim.

Can I track accessibility as a compliance framework?

Yes. In Lavawall GRC, turn on the WCAG 2.2, WCAG 2.0, Ontario AODA, or ADA Title II frameworks, keep the scan reports and your test notes as evidence, and assign each gap to an owner and a date.

Sources

Last verified 15 October 2026. This page is general information, not legal advice.

Related