Ready to scan
Scan target
What automated scans catch — and what they miss
Modern scanners cover roughly 60–70% of WCAG issues. The rest needs a human reviewer.
Automated · 60–70%
Caught by the scan
- Colour contrast (WCAG 1.4.3 / 1.4.11) Text vs background ratios, link underlines, focus rings.
- Alt-text presence (WCAG 1.1.1) Images missing
alt, decorative images with non-empty alt, brokenaria-labelledby. - ARIA structure (WCAG 4.1.2) Invalid roles, mismatched
aria-controls, orphaned landmarks. - Form-label binding (WCAG 3.3.2) Inputs without an associated
<label>oraria-label. - Document structure (WCAG 1.3.1 / 2.4.6) Heading-level skips, empty
<h1>, missinglangon<html>.
Manual · 30–40%
Needs a human reviewer
- Keyboard-trap detection Whether every interactive element can be reached AND escaped via Tab/Shift-Tab.
- Focus-order quality Visual order vs. DOM order, skipped sections, focus jumping to footer.
- Screen-reader legibility How NVDA / JAWS / VoiceOver actually read the page in continuous reading mode.
- Dynamic-content updates (WCAG 4.1.3) Whether
aria-liveannouncements actually fire when content changes. - Meaningful alt text Scans check presence; only humans can judge whether "Image 47.png" actually describes the image.
Why does the report open in a new tab?
QualiBooth's report viewer sends a Content-Security-Policy: frame-ancestors 'self'
response header that prevents any third-party site from embedding it
in an iframe — a sensible default for a tool that surfaces customer
URLs. Rather than work around it, we launch QualiBooth in a fresh tab
with your URL pre-filled. The page you're on stays shareable: paste
the address bar to anyone and they'll see the same primed launcher.