Accessibility approach in development · No conformance claim
This page describes what must be prepared and checked before launch. It is not a binding policy or set of terms.
We design for keyboard use, assistive technology, and multiple screen sizes, but must test the built site before claiming any conformance level.
Images and audio
Meaningful images need descriptions, audio must not autoplay, and the player should convey connected, paused, and error states. Motion settings should respect reduced-motion preferences.
Testing before standards claims
Test core pages and states with keyboard, screen reader, zoom, contrast, and mobile displays before claiming WCAG conformance or certification.
Information to confirm
- Test listening and shopping flows when active
- Record issues and fixes
Report a barrier
An accessibility reporting channel will be published once there is a real case owner and follow-up process.
View contact status ↗Before publishing an operative version, we must add the operator, effective date, real contact channel and workable processes, then review them against applicable law.
Back to Help Center