AllyProof Accessibility Statement

AllyProof is committed to ensuring digital accessibility for people with disabilities. We are continually improving the user experience for everyone and applying the relevant accessibility standards. Because we sell accessibility scanning as our product, our own site must be exemplary — and we treat that as a non-negotiable engineering constraint, not a marketing slogan.

Conformance status

The Web Content Accessibility Guidelines (WCAG) defines requirements for designers and developers to improve accessibility for people with disabilities. It defines three levels of conformance: Level A, Level AA, and Level AAA. allyproof.com is tested against WCAG 2.2 Level AA using automated multi-engine scanning plus targeted manual review. Our latest automated scan found no covered failure patterns, but that result alone does not establish full WCAG conformance.

How we measure ourselves

• Every push to main triggers an axe-core scan against allyproof.com in CI. A regression blocks the deploy.
• Three scanning engines run continuously: axe-core (zero false-positive), HTML_CodeSniffer (~200 rules), and APCA (WCAG 3.0 contrast preview).
• Color tokens are designed in OKLch with mandatory contrast checks at definition time. Brand accent green was darkened explicitly to meet WCAG 2.2 AA against white surfaces.
• Visible skip-to-content link, semantic landmarks, ARIA where native HTML semantics fall short, and a keyboard-trap-free command menu (Ctrl+K).
• Every interactive component is built on Base-UI primitives that enforce focus management, ARIA states, and keyboard handling by default — not bolted on after the fact.

Known limitations

Automated scanning detects common WCAG failure patterns; it cannot establish conformance, and a scan without findings has only ruled out the failure patterns its rules cover. Criteria that require manual evaluation (meaningful sequence, cognitive load, plain-language equivalents, and certain interactive patterns) are reviewed by humans before release. If you encounter a barrier we have not yet addressed, please let us know — we treat accessibility bug reports as production incidents.

Compatibility

allyproof.com is designed to be compatible with current versions of major browsers (Chrome, Firefox, Safari, Edge) and the following assistive technologies: NVDA, JAWS, VoiceOver (macOS and iOS), TalkBack (Android), and Windows Narrator.

Feedback

We welcome your feedback on the accessibility of AllyProof. Please let us know if you encounter accessibility barriers:

• accessibility@allyproof.com

We aim to respond to accessibility feedback within 2 business days.

Assessment & approval

This statement was prepared using the AllyProof platform itself and reviewed by the engineering team. It is regenerated against the current scan data on every deploy. This statement was last reviewed on 01.09.26.