Accessibility Statement

Last updated: 21 August 2026

UNFORCE is committed to making our product usable for the widest possible audience, including people with disabilities. This statement describes the accessibility status of the unforce.io website and the UNFORCE mobile + web applications.

Conformance status

We use the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA as our current target. WCAG defines requirements for designers and developers to improve accessibility for people with disabilities.

We do not currently claim WCAG conformance. Automated checks pass for the versioned landing-page matrix, but native semantics, live data-backed states, and manual screen-reader journeys still require assessment — see the known limitations below.

Measures we take

Keyboard navigation with visible focus rings on tested web journeys.
Skip-to-main-content links on versioned landing routes for screen-reader and keyboard users.
Semantic HTML with meaningful headings and landmarks.
ARIA labels on icon-only buttons, dialogs announce via role="dialog" + aria-modal.
Form fields use real <label> elements (not placeholder-only) and announce validation errors via aria-live.
Default-rule axe scans currently report zero violations across all 100 functional landing pages plus cookie-consent states in the versioned test matrix.
Motion honours prefers-reduced-motion in the tested landing and shared app components.
Shared mobile controls target platform touch-size guidance; route-specific exceptions remain part of the ongoing audit.
The app exposes Flutter semantics and supports text scaling; manual VoiceOver and TalkBack verification remains outstanding.
Six fully-translated locales: English, German, French, Spanish, Italian, Swedish.

Known limitations

The Flutter web build uses Canvas rendering; while a parallel semantic DOM tree is present for screen readers, some third-party accessibility tools still report lower coverage than on the native iOS / Android builds. We recommend the native apps when using a screen reader.
Video playback inside analyses currently lacks captions. We are planning auto-generated captions in a future release.
Charts (heatmap, shot distribution) have a text-summary fallback but no interactive screen-reader drill-down yet.

Standards we reference

WCAG 2.2 Level AA (W3C)
European Accessibility Act (EAA) — in force from 28 June 2025
US Section 508 (federal procurement)
ADA Title III (effective US web accessibility)
UK Equality Act 2010
Apple Human Interface Guidelines — Accessibility
Material Design — Accessibility

Feedback

If you encounter an accessibility barrier — or have a suggestion — please email [email protected]. We aim to respond within five business days.

If you are in the EU or UK and your complaint is not resolved, you have the right to contact your national enforcement body.

Formal assessment

This statement reflects a self-assessment refreshed by the UNFORCE engineering team on 21 August 2026. Automated axe and keyboard checks are versioned, but the VoiceOver + Safari and NVDA + Chrome checklists are not yet executed and no third-party WCAG audit has been completed.