Automated audits
Collects representative pages and checks them automatically with axe-core and custom rules (a catalog of 113 rules).
WCAG 2.2 AA and KWCAG 2.2 in one report
Web Accessibility Checker
Is your website open to everyone ?
Enter one URL — we collect representative pages, audit them against WCAG 2.2 and KWCAG 2.2, and produce an audit report with practical remediation guides.
The card above is an illustrative sample. Running an audit produces a real report in this format.
From audit to remediation, in one place
WCAG + KWCAG mapping
See WCAG 2.2 and all 33 KWCAG 2.2 checkpoints together in one report.
Reports & PDF export
Review violations with code locations and remediation guides, then download as PDF.
Manual checks, disclosed
We never hide what automation can't judge — each manual checkpoint ships with testing instructions.
What we check
Image alt text
Missing/filename/generic alt, decorative handling
Forms & labels
Label association and autocomplete checked automatically; error messaging as a manual check
Keyboard & focus
Focus order/visibility, skip links, positive tabindex
Structure & landmarks
Headings, landmarks and tables checked automatically; reading order as a manual check
Link text
Descriptive link names, new-window notice
Language
Page lang, language of parts, valid codes
Media
Caption tracks, autoplay control
Colour contrast
Body/large-text ratios (4.5:1 / 3:1)
WCAG 2.2 additions
Target size (24px) checked automatically; focus not obscured and redundant entry as manual checks
Our catalog of 113 rules links automated rules to 30 of the 55 WCAG 2.2 A/AA success criteria (54.5%). Our manual review workflow guides you through the rest — no automated tool alone can guarantee conformance.
How it works
Enter a URL
Sign in and enter your site address; representative pages are collected automatically.
Automated audit
A headless browser opens each page and audits it against WCAG · KWCAG.
Get the report
Compliance rate, checkpoint matrix, and remediation guides — on the web and in PDF.
Honest automation
Automated tools can only find part of all accessibility issues. A11y Check states its limits clearly and guides you through the checks that require a human.
Built in the open on GitHub
The audit engine and rule catalog are developed on GitHub. Contributions to the guides are welcome.
github.com/isaaceryn/a11ychk ↗Frequently asked questions
- How do I check a website for accessibility?
- Start with an automated checker to clear the issues a machine can decide, then review the rest by hand. A11y Check takes a single URL, collects representative pages, audits them with an axe-core based engine, and hands you testing instructions for everything automation cannot settle.
- What is KWCAG, and how does it differ from WCAG?
- WCAG 2.2 is the W3C's international standard. KWCAG 2.2 is South Korea's national guideline, organised as 33 checkpoints, and it is what Korean accessibility certification is assessed against. A11y Check maps every finding to both at once, so one report serves both audiences.
- Can an automated checker prove WCAG conformance?
- No. Automation finds only part of the picture — whether alt text is meaningful or a keyboard order is logical still needs a person. A11y Check does not hide what it cannot decide; it lists those criteria with instructions for testing them manually.
- Is it free?
- Yes. You can audit one page without signing in. A free account adds site-wide scans, the 33-checkpoint KWCAG matrix, the manual review workflow, and PDF and CSV export.
- We ship a product in Korea. Do we need KWCAG as well as WCAG?
- If your service is used in South Korea, KWCAG 2.2 is the standard local assessments and certification use. Much of it overlaps with WCAG 2.2, but the wording, grouping, and a few requirements differ. Running both together is the cheapest way to avoid a surprise late in the process.