Accessibility Statement
We want Myrivo and storefronts built on Myrivo to be usable by as many people as possible, including people using assistive technology, keyboard navigation, and reduced-motion settings.
What we are doing now
We actively review customer-facing storefronts and shared dashboard surfaces for keyboard access, form semantics, motion preferences, and clear navigation landmarks. Accessibility work is part of our ongoing product roadmap.
- storefront browse-to-buy and product discovery
- cart and checkout completion
- customer account and order lookup
- dashboard navigation and store management
- privacy, legal, and consent workflows
Need help or found a barrier?
If you run into an accessibility issue, use the report form below or email hello@myrivo.app. Please include the page or feature you were using, what assistive technology or browser setup you rely on, and what happened.
How we review releases
We use a release checklist for shared shells, motion-heavy surfaces, forms, and changed customer journeys before shipping major updates.
- verify skip-link and main-content focus flow on shared shells
- verify keyboard access and visible focus on changed controls
- verify reduced-motion behavior on animated or skeleton-heavy surfaces
- verify form labels, descriptions, and error messaging on changed forms
- verify chart and dashboard modules keep a readable fallback when visual cues are limited
Current evidence model
We keep an internal evidence matrix for the highest-risk flows so support, product, and engineering can see how a flow is reviewed today without overstating formal conformance.
| Flow | Evidence we keep | Primary owner |
|---|---|---|
| storefront browse-to-buy and product discovery |
| Engineering + QA |
| cart and checkout completion |
| Engineering + Support |
| customer account and order lookup |
| Engineering + Support |
| dashboard navigation and store management |
| Engineering + Product |
| privacy, legal, and consent workflows |
| Engineering + Support |
Conformance note
We are improving accessibility continuously and maintaining release evidence for key flows, but we are not making a formal WCAG conformance claim right now.
We treat the following as high-priority issues: checkout completion is blocked with keyboard or assistive technology; authentication or account access is blocked; store-management tasks are blocked for keyboard-only users; critical legal or privacy choices cannot be completed accessibly.