Legal
Accessibility Statement
Our commitment to WCAG 2.1 AA, the features we've shipped, where we know we fall short, and how to report a barrier.
- Version
- v1.0
- Effective
- 2026-04-29
- Read time
- 3 min read
- Jurisdiction
- Global
1. Our commitment
CurioPilot is committed to digital accessibility for everyone — including people who use a screen reader, magnifier, switch device, voice control, or who navigate by keyboard. We aim for WCAG 2.1 Level AA conformance across the marketing site and the in-app product.
Accessibility isn’t a launch checklist for us. It’s part of shipping. New features go through an a11y review before they reach production.
2. What works today
- Keyboard navigation across every interactive element on the marketing site.
- Skip-to-main-content link, visible on focus.
- Logical heading order with semantic HTML on every page.
- Visible focus indicators on all focusable elements.
- Sufficient colour contrast in both light and dark themes.
- ARIA labels on icon-only controls (theme toggle, language switcher, mobile menu, social links).
- Resizable text up to 200% without loss of content or function.
- Reduced-motion-aware animations (Framer Motion respects
prefers-reduced-motion). - RTL support for Arabic.
3. Known limitations
We’re honest about what isn’t there yet:
- Some animated product mockups on the home and feature pages are CSS-driven; they pause for
prefers-reduced-motionbut don’t carry text-equivalents in every case. - Embedded video (when present) currently lacks transcripts; captions are provided.
- Auto-generated PDF outputs (DPA, audit-log exports) are not yet tagged for screen readers — we’re working on this.
4. Standards + technologies
- HTML5 + WAI-ARIA 1.2 for semantics.
- CSS for presentation, with no positional information conveyed by colour alone.
- JavaScript progressively enhances; core navigation works without it.
- Tested with the latest two major versions of Chrome, Edge, Safari, Firefox, plus VoiceOver (macOS / iOS) and NVDA (Windows).
5. Reporting a barrier
If you hit something that doesn’t work, please tell us. We treat accessibility bugs as P0.
- Email accessibility@moizlabs.com — we acknowledge within 1 business day, fix or scope within 5.
- Use our contact formand pick “Something else” with “a11y” in the message.
6. Assessment
This statement was last reviewed on 2026-04-29. Assessment combines automated tooling (axe-core in CI) with periodic manual evaluation against the WCAG 2.1 AA success criteria.
Changelog
- 2026-04-29v1.0 — Initial public version.