SEOMaster
Accessibility test — find automated WCAG violations
Check images, forms, headings, landmarks, zooming and the axe-core violations Lighthouse exposes. The test is free and needs no login — it shows specific evidence, and is honest about not being a full WCAG conformance audit.
What the test checks
Images and alternative text — We find images with no alt attribute, and distinguish a missing description from a correctly empty alt on decorative images.
Names and operability — Form fields, links and buttons without an accessible name, positive tabindex values, and basic keyboard traps.
Document structure — Heading hierarchy, main and nav landmarks, tables without headers, iframes without a title, and duplicate identifiers.
Lighthouse and WCAG criteria — Where a Lighthouse measurement is available, we add axe-core violations mapped to specific WCAG success criteria and levels.
Automation detects a subset of violations — by most estimates, a minority of all real barriers. It cannot judge whether alt text is meaningful, whether focus order is logical, or how the page behaves with a screen reader. That is why we say "automated violations" rather than "WCAG compliant". See also the methodology.
Automation does not issue a WCAG certificate
A full assessment requires a keyboard pass, a screen-reader test and human judgement of the content. That is why the report shows "automated violations" rather than a "conformant / non-conformant" verdict. Treat a clean result as a starting point for manual review, not as an endpoint.
Why this is worth doing even without a legal obligation
The most common automated findings — missing alt text, unlabelled form fields, broken heading order — are the same signals a search engine uses to understand a page. Fixing them improves how assistive technology and crawlers read your site at the same time.
They are also the cheapest class of defect to fix. An unlabelled input is a one-line change; discovering the same problem after a complaint is not.
Frequently asked questions
Does an automated test confirm WCAG 2.2 conformance? No. Automation catches a portion of violations, but it cannot assess whether alternative text is meaningful, whether focus order is logical, or how well the page works with a screen reader. The result is a starting point for a manual audit, not a certificate of conformance.
What does "no automated violations" mean? Only that the tested rules found no error in the fetched version of the page. It does not mean the site is fully accessible. The SEOMaster report deliberately uses the phrase "no automated violations".
Does the test cover sub-pages? Yes. The scanner starts from the home page, discovers representative sub-pages, and checks alt-attribute coverage and HTML structure across the whole available sample.
Do I need to install code or create an account? No. The test runs from the outside against any publicly reachable domain, with no installation, no login and no email address.