Accessibility

Our commitment

The platform targets WCAG 2.2 AA for every customer-facing route. We test it the same way we test functionality — every release runs an automated a11y sweep, and we fix regressions before they ship. The audit also surfaces a11y findings for sites you audit, but that's separate from the platform's own conformance.

Keyboard navigation

Every interactive element is reachable by Tab and operable by Enter or Space. The focus ring is a 2px high-contrast outline that never disappears — even on hover-styled elements.

If you find a control you can't reach via keyboard, that's a bug. File it via Help → Report accessibility issue and we'll prioritise the fix.

Skip links

The first focusable element on every page is a "Skip to main content" link. It's visually hidden until focused. Pressing Tab on page load reveals it.

Screen readers

Tested against:

• VoiceOver (macOS, iOS)
• NVDA (Windows)
• TalkBack (Android)

We use semantic HTML throughout — <main>, <nav>, <article>, proper heading hierarchy. ARIA is added only where semantic HTML doesn't carry the load (live regions, complex menus, the command palette).

Live announcements

Long-running operations announce status via ARIA live regions. When an audit completes, your screen reader will read "Audit complete. Headline score 78." without you having to navigate to a banner.

Contrast

All body text meets 4.5:1 contrast against its background. Large text and UI components meet 3:1. We don't rely on colour alone — every status badge pairs a colour with text or an icon.

Motion

The "Reduce motion" preference in your OS suppresses:

• Page transition animations
• Loading-skeleton shimmer
• Hover-scale effects
• Auto-rotating empty-state illustrations

Other purposeful motion (e.g. a progress bar) stays but moves slower.

Zoom

The app reflows cleanly up to 400% zoom on a 1280-wide viewport without horizontal scroll. Browser text-only zoom is also supported.

Custom shortcuts

If a global hotkey clashes with assistive tech, disable the layer entirely at Settings → Accessibility → Keyboard shortcuts. The command palette (Cmd-K) stays available — the rest stand down.

Captions and transcripts

In-app videos (onboarding tour, feature walkthroughs) ship with closed captions and a transcript link directly underneath the player. Caption language matches the platform's locale.

Form fields

• Every input has a visible <label>. Placeholders never substitute.
• Errors announce via role="alert" and are linked to the field via aria-describedby.
• Required fields are marked both visually and with aria-required.

Known gaps

We're not currently a WCAG 2.2 AAA target. Areas where we fall short of AAA:

• Some contextual help text is below the AAA 7:1 contrast threshold (it's at AA 4.5:1).
• Sign language interpretation for video content isn't shipped.
• Pronunciation guides for technical terms aren't included in screen-reader output.

Where AAA matters to your team, let us know and we'll work toward it.

Reporting issues

Help → Report accessibility issue. The form goes directly to engineering, not first-line support. We commit to a substantive reply within two business days.