AccessCheck

Inspect accessibility problems in the current tab: what failed, where it is, and the real keyboard focus path.

AccessCheck audits the tab you're on and turns the result into a list of work: what to fix, where it is on the page, and what to change. HOW IT WORKS • Click the toolbar icon and the side panel opens with the verdict and what's left, for example "3 to fix" and "1 to check by hand", each problem with its own number. • The queue is split into To fix, To check by hand and Recommendations, with the most serious problems first. • The page itself shows where the problems are: each problem to fix that is on screen gets its number from the queue, on its element. Click a number to open that problem. • Open a problem and its elements are marked on the page with numbers. The panel names each one the way a person would recognize it, and "Locate on page" scrolls to it. Click a mark on the page and the panel jumps to that element. • Each problem reads in order: why it matters, where it is, what was measured, what to change with code you can copy, and whether the fix was tested. The selector, the HTML and the raw numbers sit under Details. • When a fix can be computed, such as a contrast color, AccessCheck applies it to the page for a moment, runs that rule again and puts the page back. If the rule passes, the fix is marked "Fix tested". • Fix it in your code, then press "Audit again" from anywhere in the panel. KEYBOARD "Check keyboard" presses Tab through the page for real and records every stop. The problems it finds, like focus you can't see or controls that Tab never reaches, join the same queue. Each round covers up to 200 stops and tells you what it found, and "Inspect tab order" draws the path the Tab key takes across the page. Stops where the path meets a problem carry a hatched ring in the problem's color, and the current stop names it. Chrome shows its debugging banner during the check, because real Tab presses need the debugger, and it is released as soon as the check ends. WHAT IT CHECKS • axe-core rules for WCAG 2.0, 2.1 and 2.2, levels A and AA, plus best practices • The real keyboard focus order • Target size and live regions • Items axe can't decide on its own, with steps to check them by hand • A screenshot of the visible page, kept under "About this audit" WHAT IT DOESN'T DO It isn't a compliance seal. Automated testing covers only part of WCAG, and AccessCheck says so: anything that needs a person is listed apart, and when a check couldn't run, the panel names it under "About this audit" instead of quietly passing. The mobile viewport, reduced motion, cross-origin iframes and shadow roots aren't covered by the extension. HOW IT TREATS YOUR BROWSER • No account, no sign-in, no telemetry • It only reads a tab after you click the toolbar icon on that tab • The audited page is left as it was. Any change made to test a fix is undone right away, and the marks it draws live in their own layer, never take focus from the page and are cleared when you close the panel, audit again or the tab moves to another page • Nothing is uploaded, and the audit runs entirely in your browser LANGUAGES English and Português (Brasil). The panel follows your browser's language by default, and you can change it at the bottom of the panel.