Website accessibility test for WCAG 2.2

Find the barriers that stop people who rely on screen readers, keyboards or strong contrast from using your site. This test runs axe-core on your fully rendered page against the WCAG 2.0, 2.1 and 2.2 Level A and AA rules plus accessibility best practices, and lists every failed rule with the affected elements and a link explaining the fix. Automated checks catch only part of all accessibility issues, so treat the report as the starting point for keyboard and screen-reader testing.

Runs only this test. Want everything? Run all 18 tests from the home page.

What this test checks

Color contrast

Text that does not meet the WCAG AA contrast ratio against its background.

Images and alt text

Images, image buttons and image links without a text alternative.

Forms and labels

Inputs, selects and text areas without an accessible label.

Links and buttons

Links and buttons without a name that screen readers can announce.

ARIA usage

Invalid ARIA roles, attributes and values, and hidden elements that can still receive keyboard focus.

Page structure and landmarks

Page language, page title, heading order and landmark regions, partly checked as best-practice rules.

Impact and affected elements

Each failed rule with its impact level, the number of affected elements, sample HTML and the WCAG success criteria it maps to.

Sample result

A real result for devteam.co.kr, tested 18 hours ago.

Accessibility (WCAG)

No WCAG violations detected by axe-core (40 rules passed).

100/100A+
No automatically detectable WCAG issues (Good)
axe-core found no violations of WCAG 2.2 A/AA rules on this page. Automated tools catch roughly a third of issues, so test keyboard and screen-reader use too.
0 issues
0Critical
0Serious
0Moderate
0Minor
40Rules passed

axe-core 4.13.0 · WCAG 2.2 A/AA + best practices on the rendered desktop page. Score = 100 − 15 per critical, 8 per serious, 4 per moderate and 2 per minor rule failed.

How it works

  1. axe-core 4 runs inside headless Chromium on our test server in Virginia, USA, after your page has fully loaded at a 1366×860 desktop size.
  2. It checks the rules tagged WCAG 2.0, 2.1 and 2.2 Level A and AA, plus Deque's best-practice rules, on the rendered page, so content added by JavaScript is included.
  3. Every request the browser makes goes through a network guard that only connects to public IP addresses on ports 80 and 443.
  4. The check shares one browser session with the responsive and mobile tests and usually finishes within a minute.

How it is scored

The score is a deduction formula: it starts at 100 and loses 15 points for each critical rule that fails, 8 for each serious, 4 for each moderate and 2 for each minor, with a floor of 0. A rule counts once however many elements fail it, and grades follow our scale: A+ 95+, A 90+, B 80+, C 70+, D 60+, F below 60.

CheckGoodNeeds workPoor
Critical rule failuresNone—Any (−15 points each)
Serious rule failuresNone—Any (−8 points each)
Moderate rule failuresNoneAny (−4 points each)—
Minor rule failuresNoneAny (−2 points each)—
Score after deductions90–100 (A or A+)70–89 (B or C)Below 70 (D or F)

Grades: A+ 95–100 · A 90–94 · B 80–89 · C 70–79 · D 60–69 · F below 60.

FAQ

How do I check if my website is ADA or WCAG compliant?
Start with an automated test like this one, which checks your page against the WCAG 2.2 Level A and AA rules that axe-core can detect. Automated tools find only part of all issues, so also test with a keyboard alone and with a screen reader. A clean automated result is not proof of legal compliance.
What is axe-core?
axe-core is an open-source accessibility testing engine from Deque Systems and the engine behind Lighthouse's accessibility audits. It checks the rendered page against WCAG rules and reports each failed rule with an impact level from minor to critical.
What does WCAG 2.2 Level AA require?
Level AA includes all Level A and AA success criteria, such as sufficient color contrast, text alternatives for images, labeled form fields, keyboard access and a minimum target size of 24×24 pixels. Many accessibility laws and policies point to WCAG Level AA as the standard to meet.
Why is my accessibility score low when only a few rules fail?
Each failed rule deducts points by its impact, so two critical and two serious failures already cost 46 points. Because a rule counts once however many elements fail it, fixing one shared style, such as a low-contrast text color, can remove a whole deduction.