Accessibility Statement

A field tech in the rain on a 5-inch screen with one glove off has the same right to a usable app as anyone else. This is what we've built so far, what we haven't, and how to tell us when we get it wrong.

01Commitment

Claver aims to meet WCAG 2.1 Level AA across goclaver.com and app.goclaver.com. We test against AA, not the looser A. We also follow Section 508 (U.S.), the ADA, AODA (Ontario), and EN 301 549 (EU). We don't yet claim full conformance. This page is honest about that.

02What's working today

Keyboard-only navigation through every primary flow (jobs, quotes, customers, dispatch).
Visible focus rings (2px amber) on every interactive element. We don't override the browser default unless we improve it.
Forms have programmatically associated labels, error messages tied to the field via aria-describedby, and inline validation that doesn't depend on color alone.
Color contrast ratios meet AA on text and AAA on body copy. Our amber-on-navy combination is checked at 7.1:1.
Native HTML semantics for headings, buttons, links, and landmarks. Custom widgets carry the right ARIA roles and states.
Status changes (toast notifications, save confirmations) are announced via role="status".
Modals trap focus and restore it on close.
prefers-reduced-motion turns off non-essential animations.
Light + dark mode with manual override; we don't force you to live in either.
Tap targets are at least 44 × 44 pt on mobile.
Tested in NVDA + Chrome, JAWS + Edge, VoiceOver + Safari (macOS & iOS), and TalkBack + Chrome (Android).

03What we haven't fixed yet

The dispatch board's drag-and-drop has a keyboard alternative (arrow-key reassignment) but the live region announcing the change isn't yet exhaustive. Tracking A11Y-014.
The Leaflet-based map view exposes pin clusters via mouse only. Keyboard equivalents are in the May release. Tracking A11Y-021.
Some third-party widgets (Stripe Connect onboarding, Mapbox autocomplete) follow vendor patterns we can't fully control. We track their progress and apply patches when they ship.

04Found a barrier?

Email [email protected] with the page URL, what you tried, what happened, and (if relevant) the assistive technology and version. We acknowledge within 1 business day and resolve, or schedule, within 10. We do not require an ADA complaint to act.

05Formal complaints

If we don't resolve your concern, you can file with the U.S. Department of Justice ADA division at ada.gov, or your state's accessibility regulator.

06How we test

Automated: axe-core in CI on every PR. Pa11y on the marketing site. Lighthouse accessibility > 95 required to ship.
Manual: keyboard-only walkthrough on every release of changed pages.
External: scheduled annual audit by a third-party WCAG auditor (next: 2026 Q3).