Every barrier measured, located on the element, and tested before it's suggested.
This is not another report. It is a visual inspector: paste a web address and every finding comes tied to the element that caused it, with the contrast ratio, the selector and a fix we test on a copy of the page.
No account, no extension, no change to the audited siteExport as PDF or MarkdownAbout 10 to 25 seconds per page
Quick examples:
Nota conformance seal. It measures what automated tools can prove, and marks the rest for a human to review.
Text below the minimum contrast
Select a finding and its marker lights up. Click the marker and the details open: the screenshot, the measurement and the code in one place.
No critical blockers, but 1 serious finding still makes the page harder to use for people who rely on assistive technology.
If you fix these, the score rises to
4 manual-review items sit outside the score. Each line is the score after fixing that severity on its own. The score is non-linear, so fixing more than one recovers less than the lines added together.
No automated level-A failures
Fails by 1.4.3 Contrast (Minimum)
Not evaluated. AccessCheck runs A and AA
The score is an internal priority measure. WCAG conformance also depends on checks no automated tool decides alone.
One page, opened, located and verified
Open → Locate → Verify
Opened in a real browser
We open the page in a real browser, let it finish loading, then run the axe-core accessibility tests on it. This works even on sites with strict security rules (CSP).
Every finding is measured and tied to an element
Contrast ratio, selector, code snippet and position on the screenshot. Repeated issues are grouped, so one fix can cover several elements at once.
Each fix is tested before we suggest it
We apply the change to a copy of the page, run the check again, then mark the result as verified or needs review.
Every automated check, plus the passes a tool can't run on its own
checked automatically
- 1.4.3Text contrast against a computed background
- 1.1.1Text alternatives for images and icons
- 4.1.2Accessible name for fields, buttons and ARIA controls
- 1.3.1Heading order and structural relationships
- 2.4.4Ambiguous or unlabeled link purpose
- 2.5.8Minimum target size
- 3.1.1Declared page language
- 1.4.4Viewport that does not block zoom
the static DOM
- KeyboardTabs through the page to check focus order, keyboard traps and focus you can't see
- ContextChecks the page again at mobile size and after opening menus and expandable sections
- VisionSimulates color blindness (deuteranopia, protanopia, tritanopia), low vision and grayscale
- MotionChecks that the page respects the visitor's reduced-motion setting
- LiveWatches for updates announced to screen readers (live regions)
- ReviewLists what a person still needs to check, with the steps to confirm it
See the barrier on the element that caused it
Element, selector, measurement and diagnosis stay in one chain. Select a finding and its marker fills in. The located element is labeled with the ratio, and the others keep a dashed outline, so you can tell them apart without relying on color.
Text below the minimum contrast
The white text on the light-green button disappears for people with low vision, or for anyone in bright sunlight. And this is the checkout button.
Tested in a sandbox copy. aurora-coffee.com was not altered.
Every fix is proved on a copy, so your site is never touched
We apply the change to a copy of the page, run the check again, then undo it. If the issue stops showing up, we mark the fix as verified. It is never a guarantee, and it never touches your real site.
Two exports for two readers: the person who decides and the person who fixes
Score, ruler and impact in plain language
Summary, severity levels and each finding's impact on people. Ready to send to a client or a product team, with no engineering context required.
Selector, snippet and verification status
A severity table and a prioritized list, ready to paste into a ticket or a pull request, with the verified fixes already marked.
Audit again later and see exactly what moved
A page that passes today can fail after the next deploy. Every audit you run signed in is saved, and the next one is compared rule by rule against it — not just a new number, but which barriers cleared and which came back.
- 1.4.3Text contrast against a computed background
- 1.3.1Heading order and structural relationships
- 1.1.1Text alternatives for images and icons
History is saved when you sign in with GitHub or Google. Everything else on this page — the audit, the fixes and the exports — works without an account.
Audit a page now and see where each barrier is
No account, no extension, no change to your site. The report is ready in under half a minute and exports as PDF or Markdown.
No account, no extension, no change to the audited siteExport as PDF or MarkdownAbout 10 to 25 seconds per page
Quick examples:
We can only audit public pages. Private or internal addresses will be refused.