Accessibility
Accessibility at REYS
We want everyone to be able to learn about, choose, and order REYS — regardless of how they use the web.
What we aim for
REYS is built and reviewed against the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. We're a small team, so we don't get every detail perfect on day one — but accessibility is part of how we build, not a checklist we hand off.
What our site supports today
Keyboard navigation. Every interactive element — menus, gallery thumbnails, cart, Subscribe & Save toggle, checkout — is reachable and usable with a keyboard alone.
Skip-to-content link. A visible link appears when you tab through the page, letting screen reader and keyboard users bypass the header and jump straight to the main content.
Visible focus indicators. A distinct outline shows which element is currently focused.
Semantic structure. Headings, lists, and landmarks are coded with proper HTML so assistive technologies can navigate the page in the right order.
Alternative text. Every meaningful image — clinical demonstrations, ingredient cards, lifestyle photography — carries descriptive alt text.
Reduced motion. If your operating system has "Reduce Motion" enabled, our marquees, animations, and transitions are disabled automatically.
Color contrast. We use color combinations and contrast levels that aim to meet or exceed WCAG AA across body text and interactive elements.
Assistive technology support. The site is reviewed with screen readers (VoiceOver, NVDA), keyboard-only navigation, and standard browser zoom up to 200%.
What's outside our control
Some third-party tools we rely on — payment processors, subscription management portals, analytics, and customer support widgets — render their own interfaces that we don't fully control. We choose partners with reasonable accessibility practices, but their standards may differ from ours. If you hit a barrier inside a third-party tool, please let us know and we'll work with that partner or give you an alternative path to complete what you needed.
If you hit a barrier
We want to know. Email and include:
The page or feature you were trying to use
A short description of what didn't work
The browser and assistive technology you were using, if known
We aim to respond as quickly as we're able with either a fix, a workaround, or a way to complete your request directly (by phone or email).
Ongoing work
This isn't a one-time audit. We run accessibility checks before every release and welcome community feedback. If you have suggestions, we want to hear them.
Last updated: May 2026