Semantic HTML, no `<div>` buttons
Every interactive element is a button or anchor. Headings follow a single h1 then nested h2/h3 — no skipped levels. Page structure uses landmark elements (<header>, <nav>, <main>, <footer>).
Accessibility statement
Our site is the product. Of course it's accessible.
We sell an accessibility scanner. Everything we ship runs through our own scanner before deploy. If our site fails an axe-core rule, we fix it before the build merges. This page documents the measures we take, the score we hold ourselves to, and the limitations we know about.
axe-core score
100/ 100
Across all marketing pages, build-blocking
Last audit
Continuous via CI · pa11y-ci gate
Conformance target
WCAG 2.2 AA
+ Manual review checklist run pre-launch
Honest framing
We hold ourselves to the same disclaimer we put on every customer report: automated tools detect approximately 25–57% of accessibility violations. We pair the axe-core gate with a manual checklist run before every public release. We are not certified. We will not claim "fully accessible" — and we apologise in advance for any access barrier you encounter. accessibility@scan-access.com and we will fix it.
Measures we take
The structural choices that make violations hard to introduce.
Visible focus rings, never disabled
All focusable elements show a 2px brand-blue ring with 2px offset, ≥ 3:1 contrast against any adjacent surface. We never set outline:none without an equivalent indicator.
Color independence, color-contrast checked
Every status (pass/warn/risk) pairs an icon with a color label, satisfying WCAG 1.4.1. Body text ≥ 4.5:1, large text ≥ 3:1, UI components ≥ 3:1, all verified by axe-core in CI.
Honors `prefers-reduced-motion`
All animations and transitions collapse to ≤1ms when the OS reports reduced-motion preference. No autoplay video. No parallax effects.
Skip-to-content link is the first focusable
Press Tab on any page; the first thing you see is the skip-to-content link, visible at top-left, brand-styled, that jumps directly to <main>.
Forms with real labels, errors announced
Every input has a visible <label>. Errors are linked via aria-describedby and announced via role='alert' so screen readers receive them on submit.
Known limitations
Where the site is not yet what we want it to be.
Customer logos in the peer-logos section are decorative SVG icons — they will be replaced with real customer logos and named case studies in Q3 2026, with permission.
We do not yet ship a public VPAT (Voluntary Product Accessibility Template). The first VPAT is scheduled for publication alongside the SOC 2 Type I report (target Q3 2026).
User-uploaded content (logos in white-label PDFs, custom agency notes) is not auto-checked for alt text or contrast — agencies are responsible for the assets they upload.
Some marketing copy makes deliberate use of stylised tracking and balanced text-wrapping; we have audited these for screen-reader output, but if you encounter rendering issues please report them at accessibility@scan-access.com.
Report a barrier
Found something inaccessible? Tell us.
We commit to acknowledging accessibility reports within 2 business days and shipping a fix or workaround within 10 business days.
accessibility@scan-access.com