WCAG Compliance Tool for Issue Review and Re-Testing
Use Accesserty DevCheck to review axe-core findings related to WCAG A/AA and best practices, inspect impact, success-criterion clues, and affected elements, then fix and re-test in the browser.
What this WCAG checker can help you review
DevCheck is not just a score and not a compliance certificate. It locates automatically detectable issues on the current page so the right person can review, fix, and re-test them.
WCAG 2 A/AA related issues
Scan the DOM with axe-core and organize violations related to WCAG 2 A, WCAG 2 AA, and best-practice rules.
Semantics, ARIA, and form labels
Help identify common structure, interactive role, label, and accessible-name issues with affected element clues.
Visual and sensory simulation
Simulate color vision differences, text spacing, reading difficulty, visual field loss, presbyopia, myopia, and cataracts to review readability risks alongside WCAG findings.
AI semantic review
Provide assistive suggestions for link purpose, language marking, and image alt text quality that rule-based checks often cannot judge, including suggested alt text improvements.
PDF structure signals
Inspect signals such as tagged pages, language, images, links, form fields, bookmarks, and page size consistency.
How to run a WCAG check with DevCheck
The workflow stays inside the browser, which makes it practical for PMs, design, QA, engineering, content, and operations to run WCAG-related checks and re-tests across public, local, staging, and authenticated states.
- Step 1
Install the browser extension (Chrome/Edge or Firefox).
- Step 2
Open the page or product flow you want to inspect.
- Step 3
Run the Axe-Core A11Y Test.
- Step 4
Review WCAG, best-practice, and severity summaries.
- Step 5
Select an issue to locate the affected element, then fix and re-test.
Automated checking is not a legal compliance guarantee
DevCheck helps people reviewing pages catch machine-detectable accessibility issues earlier, but no automated tool can fully certify WCAG, ADA, or legal compliance. Formal audits still require manual review, keyboard testing, assistive technology testing, and real-use judgment.
Who should use this tool?
PMs and product people
Run a quick first check during acceptance, flow review, or issue reporting.
QA
Add accessibility checks to regression workflows and reduce late discovery risk.
Designers and engineers
Use simulation modes to review color, readability, and visual contexts, then use scan results to locate affected page elements.
How to choose within the DevCheck cluster
Accesserty DevCheck
The main product page for DevCheck capabilities, target roles, data boundaries, and installation links.
Web Accessibility Checker
Use this entry point for general page checking, local builds, staging, authenticated screens, and interactive states.
Automated Accessibility Checks Guide
Use this guide to understand what automated scans can find, what they miss, and when human confirmation is still required.
Frequently asked questions
DevCheck is available from the Chrome Web Store and Firefox Add-ons for automated accessibility scans, manual review lenses, simulation checks, AI semantic review, and PDF structure signal checks. Current availability and capabilities should be confirmed on the store listings.
No. DevCheck can detect many machine-testable issues, but full compliance still requires manual review, assistive technology testing, keyboard testing, and contextual judgment.
Level AA is the practical target commonly used in accessibility guidelines, policies, and procurement workflows to address many common barriers. DevCheck can help surface some A/AA-related clues, but it does not claim that a website has an official label or complete conformance proof.
No. DevCheck can support preliminary accessibility and regression checks, but it does not provide an ADA legal compliance decision and does not replace a formal audit or legal advice.
DevCheck uses axe-core for page scans and runs automated checks related to WCAG 2 A, WCAG 2 AA, and best-practice rules.
No. DevCheck is useful for cross-functional first checks and fast regression checks, but formal audits should still include manual review and assistive technology testing.
It supports PDF structure signal checks such as tagged pages, language, links, form fields, bookmarks, and page size consistency. This is based on PDF.js parsing and is not the same as full PDF/UA certification.