QEHSScope & standard
Our target is WCAG 2.2 AA. Where a success criterion applies, we test with a combination of automated tooling (axe-core, Lighthouse, Pa11y) and manual review using keyboard, screen readers (VoiceOver, NVDA, TalkBack), and high-contrast modes.
Accessibility is considered a release blocker for marketing and product surfaces that handle sign-up, auth, and core composer flows.
Surface-by-surface
- Marketing site
- Keyboard-navigable, visible focus rings at rest, semantic landmarks, ARIA where HTML semantics fall short, responsive to 200% zoom.
- Product (app.qehsethos.com)
- All primary flows tested with keyboard, VoiceOver, and NVDA. Composer forms enforce labelled inputs, inline Zod error messaging (no placeholder-only controls), and sufficient contrast.
- Mobile apps
- Native platform accessibility APIs — Dynamic Type / Large Text support, VoiceOver + TalkBack labels on all interactive elements.
- Docs & help center
- MDX content rendered with semantic headings, descriptive link text, code blocks with language labels.
Known limitations
- Some third-party embeds (video, analytics consent banners) may have partial screen-reader coverage — we document workarounds and track fixes with the vendor.
- Interactive data visualisations include a data-table fallback, but keyboard affordances on complex chart types are still being improved.
VPAT & audits
A VPAT is produced annually and reviewed after material UI changes. We also commission an independent third-party audit once per year; the summary is included in the VPAT.
Email anil@heftyinnovations.com to request the current VPAT, report a barrier, or ask for an alternative format. We respond within 5 business days.