Legal

Accessibility

Last updated: August 16, 2026

Rouzey wants rouzey.com to work for everyone, including people who use assistive technology. Our goal is conformance with the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA, and we treat accessibility as part of building the site, not an afterthought.

What we've built in

Semantic HTML with a logical heading structure, native buttons and form controls, and labels on every input.
Full keyboard operability — every interactive element can be reached and used with a keyboard, with clearly visible focus indicators and a "skip to main content" link.
Screen-reader support: expandable sections announce their state, decorative graphics are hidden from assistive technology, and meaningful images carry text alternatives.
Text colors chosen to meet WCAG AA contrast requirements against their backgrounds.
Respect for your system's reduced-motion setting — when it's on, animations and moving content on the site are turned off.
A responsive layout that works at small screen sizes and remains usable when text is zoomed to 200%.

How we check

Before we publish changes, we review them with keyboard-only navigation and automated accessibility checks, and we fix what we find. As a small team we may miss things — when we do, we want to know.

Third-party content

Some parts of our service run on outside providers — for example our email signup platform and, in the future, checkout and customer support tools. We don't control their code, but we take accessibility into account when choosing providers and raise issues with them when we find any.

Known limitations

We're not aware of significant barriers on this site today. If we discover any — or you do — we'll list them here while we fix them.

Tell us what's not working

If any part of this site is difficult for you to use, we genuinely want to hear about it. Email hello@rouzey.com with "Accessibility" in the subject line and a description of the problem and, if you can, the page and the assistive technology you were using. We aim to respond within 5 business days and to fix confirmed barriers promptly.

Accessibility is ongoing work, and this page will be updated as the site evolves.

Template notice for the site owner (delete before publishing): set up the contact mailbox, and re-run an accessibility check (keyboard pass + a free tool like Lighthouse or axe) whenever you add new sections, embeds, or the checkout — then update the "Known limitations" section honestly if anything is pending.