Steady Accessibility Statement
Our commitment
Steady is built for people who are often using it at difficult moments. Accessibility is therefore a product requirement, not a compliance checkbox. Our target is WCAG 2.2 Level AA conformance across the web app.
Current status
Steady is partially conformant with WCAG 2.2 AA: most of the interface meets the standard, but some parts do not yet. What we have in place today:
- Reduced motion: the app respects
prefers-reduced-motion; animations and transitions are disabled or minimised when set. - Semantic HTML structure, labelled form controls, and keyboard-reachable primary flows (navigation, session start/pause/end, dialogs).
- Visible focus states and calm, high-legibility typography.
- Escape-key support for pausing sessions and dismissing dialogs.
- Colour contrast targeted at AA ratios in the design system.
- A static accessibility gate in CI plus a manual AA audit (see
docs/evidence/ACCESSIBILITY_AA_MANUAL_AUDIT.md). - Text alternatives to voice: core actions (e.g. the response-prevention card) are available without audio.
Known gaps
We publish these honestly and are working through them:
- Voice-first flows and screen readers: live voice sessions announce state changes (connecting, paused, reconnecting) inconsistently to assistive technology; ARIA live-region coverage is incomplete.
- Real-time captions: the voice session shows transcript text, but it is not yet a fully synchronised caption experience for Deaf and hard-of-hearing users.
- Complex progress views: some charts/progress visualisations lack complete non-visual equivalents.
- Full keyboard audit: a small number of secondary interactions have not yet passed a complete keyboard-only pass.
- Older assistive-tech combinations (legacy browser + screen-reader pairings) are not yet part of our test matrix.
Compatibility
Steady is tested on current versions of Chrome, Safari, Firefox, and Edge, on desktop and mobile. Voice sessions require microphone access and WebRTC support.
Feedback and enforcement
If you hit an accessibility barrier:
- Email hayat@beyondelevation.com with "Accessibility" in the subject. Include the page/flow and your browser + assistive tech if possible.
- We aim to respond within 5 working days and to prioritise fixes for barriers that block core practice flows.
UK users who are not satisfied with our response may contact the Equality Advisory and Support Service (EASS).
Review cadence
This statement is reviewed at least quarterly and after any major UI release. Evidence of the latest manual audit lives in docs/evidence/ACCESSIBILITY_AA_MANUAL_AUDIT.md.