Pillar 1 of 4
Accessibility that doesn't hide behind a green checkmark
We run the same axe-core engine that powers Deque's commercial tooling — and we tell you the truth about what automated testing can and can't find.
Why automated scanning is necessary but not sufficient
Accessibility lawsuits in the US increased every year from 2018 to 2024. The vast majority cited issues that an automated scanner would have caught: missing alt text, contrast failures, form labels, broken focus order. Catching those issues early — and continuously — is non-negotiable. But here's the part most vendors won't tell you: axe-core, the engine behind every credible automated accessibility scanner including ours, catches roughly 50–60% of WCAG issues. The rest require a human. We surface that limit clearly. If a vendor claims 100% coverage or an AAA badge from automated testing alone, walk away.
How findings reach your team
Every violation comes with the rule ID, severity, the offending DOM node's outerHTML, the CSS selector, and a short failure summary that tells your engineer what to change. We link to Deque's rule documentation so the developer doesn't have to context-switch. Findings are stored as JSON. You can export them, diff them between scans, or pipe them into a future GitHub Action that fails the build on regressions.
Score interpretation
Each violation is weighted by axe-core impact: critical = 10, serious = 5, moderate = 2, minor = 1. We subtract the total from 100 for the per-page score, floored at zero. A score of 90+ usually means a small handful of minor issues. 70–89 means a real backlog. Below 70 means the page has structural problems and needs a focused remediation pass.
Eksempler på findings
Form-elementer skal have labels
Login-formularen på /signin har et email-input uden en tilknyttet <label> og ingen aria-label. Skærmlæsere annoncerer feltet som "edit text" uden kontekst, og brugere med kognitive handicap, der bruger placeholder-tekst, mister cue’en, når de skriver.
<input type="email" placeholder="Email" class="form-input" /> Fix: tilføj <label for="email">Email</label> eller aria-label="Email".
Utilstrækkelig farvekontrast
Brødtekst på /pricing bruger #9CA3AF på #FFFFFF — en ratio på 2,84:1. WCAG 2.1 AA kræver 4,5:1 til brødtekst. Brugere med nedsat syn, ældre skærme eller solblænding vil have svært ved at læse det; nogle vil slet ikke se teksten.
Element : <p class="text-slate-400">Most popular plan</p> Foreground : #9CA3AF Background : #FFFFFF Ratio : 2.84:1 (need 4.5:1) Fix : darken to #6B7280 (5.85:1) eller større font weight 700+ ved 18.66px+ (large-text regel).
Heading-hierarki springer et niveau over
Siden /blog/post-template hopper fra <h1> direkte til <h3> og springer <h2> over. Skærmlæsere eksponerer side-struktur via heading-niveauer, og huller forvirrer brugere, der navigerer via H-key. Søgemaskine-crawlers bruger også hierarkiet til at rangere relevans for sektioner.
Sideoversigt:
H1: Article title
H3: Section heading ← skipped H2
H4: Subsection
Fix: ændr <h3> til <h2>, eller indsæt en indpakning <h2>, hvis H3’et faktisk er en undersektion.Scan dit site på 60 sekunder
25 gratis credits. Ingen kreditkort. Reelle findings på den side, du faktisk går op i.