Accessibility Checker
Run automated WCAG checks against a live page and review issues by severity.
Based on: WCAG 2.2 · WAI-ARIA 1.2 WCAG 2.2
About this validation
Runs automated accessibility checks against a live page using axe-core rules mapped to WCAG 2.2 success criteria and WAI-ARIA. Automated checks can identify certain accessibility issues but cannot establish complete WCAG conformance.
- Protocol / standard:
- Validation engine:
- axe-core
- Version:
- WCAG 2.2
- Rules reviewed:
- Sep 8, 2026
SEOTechTests methodology: Data source: axe-core run by SEOTechTests against a live render of the page, checked for issues mapped to WCAG 2.2 success criteria and WAI-ARIA roles/states. Automated axe-core rules are documented by their authors as catching a meaningful minority of WCAG issues -- this check surfaces what's detectable automatically, not a full conformance audit.
Standards and vendor-documented behavior can change. This reflects the source as last reviewed above, not a permanent guarantee.
Automated accessibility checks cannot detect every WCAG issue. This is not a formal compliance certification.
FAQ
Does passing this check mean the page is WCAG 2.2 compliant?
No. Automated tools like axe-core can reliably catch certain classes of issues -- missing alt text, insufficient color contrast, missing form labels -- but many WCAG success criteria (like whether alt text is actually meaningful, or a keyboard flow makes logical sense) require manual, human review to evaluate.[1]
What do the impact levels (critical, serious, moderate, minor) mean?
They're axe-core's own severity classification for how much a given issue is likely to affect a person using assistive technology, with critical typically blocking access to content or functionality entirely and minor being a smaller usability friction.
Why does this check reference WAI-ARIA as well as WCAG?
Many accessibility issues involve ARIA roles, states, and properties -- attributes like role, aria-label, or aria-expanded -- which are defined by the separate WAI-ARIA specification and used to meet certain WCAG success criteria for custom interactive components.[2]
The page looks fine visually -- why does it still show issues?
Most accessibility issues are invisible in a normal sighted walkthrough: a screen reader user, a keyboard-only user, or someone relying on high contrast mode can hit barriers that never show up just by looking at the rendered page.