+ keyboard, viewport and motion checks
Every barrier measured, located on the element, and tested before it's suggested.
It's not just a report. It's 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 tested on a copy of the page.
Export as PDF or MarkdownAbout 10 to 25 seconds per page
Quick examples:
Screenshot · 1200 × 800
Select a finding and its mark lights up. Click the mark and the details open: the screenshot, the measurement and the code in one place.
No critical barriers, but 1 serious finding still makes the page harder to use for people who rely on assistive technology.
No automated level-A failures
Fails by 1.4.3 Contrast (Minimum)
Not evaluated. AccessCheck runs A and AA
This result covers the rules a tool can decide. WCAG conformance also depends on checks that no automated tool can settle on its own.
Open the page, locate the problem, test the fix
Open → Locate → Test
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 findings 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 fix as tested or as needing review.
Every automated rule, plus the checks a rules engine can't do alone
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
- MotionChecks that the page respects the visitor's reduced-motion setting
- LiveChecks the regions that announce updates 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 connected. Select a finding and its element is framed on the screenshot, under the same number as in the list. The other elements with the same problem keep a lighter frame.
Screenshot · aurora-coffee.com · 1200 × 800
Every fix is tested 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 problem no longer shows up, the fix is marked as tested. That is not a guarantee, and your real site is never touched.
Two exports for two readers: the person who decides and the person who fixes
Standing, priorities 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 fix status
Each finding with its element, measurement, suggested fix and test status, ready to paste into a ticket or a pull request.
Audit a page now and see where each barrier is
The report is ready in under half a minute and exports as PDF or Markdown.
Export 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.