WCAG Check

Run axe-core accessibility checks on any page, including localhost, staging and screens behind login.

Check accessibility right where you're working. WCAG Accessibility Checks helps developers, QA teams, and accessibility reviewers find accessibility issues on the pages they have open in Chrome, including localhost, staging environments, and screens behind a login. The extension uses axe-core to run automated checks directly in your browser. No account is required. WORK ALONGSIDE YOUR PAGE Results now appear in Chrome's native Side Panel instead of a small popup. Keep your findings open while interacting with the website. Review an issue, highlight the affected element, inspect its markup, and return to the page without constantly reopening the extension. WHAT YOU CAN DO • Run accessibility checks on the current page, including authenticated screens and local development environments. • Review detected issues, items requiring manual review, and passed-rule counts. • Explore findings grouped by accessibility rule and severity. • Highlight affected elements directly on the page. • Inspect CSS selectors, HTML snippets, and failure details. • Export results locally: copy a Markdown report or download structured JSON. • Switch between browser tabs without mixing their results. Previously checked pages retain their reports while the Side Panel remains open. • Select checks oriented toward WCAG-related requirements, including ADA, Section 508, EAA, EN 301 549, and AODA. • Use the dedicated DevTools panel for additional element inspection and available source hints. LOCAL BY DEFAULT A check runs only when you request it. The extension does not scan pages in the background. Local checks and exports work without registration and do not upload your results to WCAG-C. The checking engine is bundled with the extension. No remote executable code, advertising, or user-activity analytics are used. OPTIONAL WCAG-C ACCOUNT You can connect your WCAG-C account and explicitly save a local check to your workspace. A saved check may include the page URL and title, selectors, limited markup fragments, failure descriptions, optional relative source hints, and check metadata. Markup fragments can contain visible text and HTML attribute values, so review sensitive pages before saving. The extension does not read browsing history, cookies, form input values, screenshots, request headers, or full-page HTML. Authentication tokens are kept in extension session storage. WHAT AUTOMATED CHECKS CAN'T DO Automated accessibility testing identifies only some accessibility problems. Manual testing is still necessary. A local check is not a complete accessibility audit, certification, or guarantee of legal compliance. WCAG-C does not apply accessibility overlays or automatically modify your website. The checking engine uses the open-source axe-core library. WCAG-C is not affiliated with or endorsed by Deque Systems. Learn more at wcagc.com