Accessibility Statement

Last updated: 24 April 2026

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

Conformance status

We aim to conform with the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. WCAG defines requirements for designers and developers to improve accessibility for people with disabilities.

Our current self-assessed status: partially conformant. Some parts of the content do not yet fully conform to the accessibility standard — see the known issues below.

Measures we take

Keyboard navigation with visible focus rings on every interactive element.
Skip-to-main-content link 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.
Colour contrast verified at WCAG AA (≥4.5:1 for body text, ≥3:1 for large text and UI components).
Motion honours prefers-reduced-motion; animations on the landing use transform/opacity and can be disabled via the OS setting.
Touch targets on mobile are ≥44×44pt (Apple HIG) / 48×48dp (Material).
The app ships with a full VoiceOver/TalkBack semantic tree and supports Dynamic Type / font scaling.
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.1 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 is based on a self-assessment performed by the AceSense engineering team on 24 April 2026. A formal third-party WCAG audit is planned before EAA enforcement becomes active for private-sector digital services.