# Accessibility at STRIPPIES We're working toward making gostrippies.com usable by everyone, including people who use screen readers, keyboard navigation, screen magnification, voice control, or who need reduced motion and high contrast. This page describes the standard we're targeting, what we've done so far, where we know we still have work to do, and how to reach us if something doesn't work for you. The standard we're working toward We are targeting Web Content Accessibility Guidelines (WCAG) 2.1, Level AA — the standard cited most often in US accessibility law and the one most established assistive technologies are tested against. WCAG 2.1 AA is a checklist of about 50 specific success criteria covering how content is structured, how interactive elements work, how text contrast is measured, and how the site behaves when someone has reduced motion or uses a keyboard instead of a mouse. We do not claim full conformance today. We are working toward it, in public, with each new release. What we've done so far In May 2026 we ran a full WCAG 2.1 AA audit on the surfaces a paid-traffic or organic visitor lands on first — the homepage, our landing pages, and our product pages. We then shipped a same-day fix pass on the highest-priority issues. The changes include: Replacing <div> click targets with semantic <button> and <a> elements so screen reader users can find and operate them. Adding :focus-visible styles to every interactive element so keyboard users can see where they are on the page. Adding hidden text labels to form inputs that previously only had placeholder text. Marking decorative icons and emoji as aria-hidden so screen readers skip them instead of reading them as words. Adding descriptive title attributes to embedded third-party widgets. Honoring the prefers-reduced-motion setting site-wide — animated glitch effects, typing animations, and auto-dismissing overlays all respect that preference. If your operating system is set to reduce motion, our site does too. Increasing the contrast on muted and inactive text so it passes the 4.5:1 ratio WCAG requires for body text. What we're still working on We're being honest about what's open: The PIP interactive terminal at /pages/pip-terminal uses a custom chat input and streaming output that needs its own targeted audit. It's on the queue. The /all-your-vibes page uses a custom template that doesn't inherit our standard accessibility settings. It's getting its own pass next. The blog and content pages were not part of the May 2026 audit. They go next after the two surfaces above. Third-party widgets (review widgets, chat, analytics) are partially outside our direct control. We work with vendors when their components block accessibility but we cannot always fix them at the source. We will update this page when each of these moves from open to shipped. If something doesn't work for you If a page, button, form, or any other part of the site doesn't work the way you need it to, please tell us. We take every report seriously and we will respond. Email: support@gostrippies.com Subject line: Accessibility — [what doesn't work] Include the page URL, what assistive technology or setting you're using (screen reader, keyboard only, reduced motion, browser zoom, etc.), and what happened. We aim to respond within two business days and to ship a fix as quickly as we can. What we test against We test our site on: macOS with VoiceOver, Safari and Chrome iOS with VoiceOver, Safari Windows with NVDA and JAWS, Firefox and Chrome Android with TalkBack, Chrome Keyboard-only navigation across all of the above Browser zoom at 200% The OS-level reduce-motion setting If you use a setup not in this list and you hit a barrier, please tell us — we want to know. A note on accessibility overlays We do not use accessibility-overlay widgets (sometimes called "AI accessibility tools" that promise one-line installs to make a site compliant). The accessibility community, screen reader user groups, and established disability-rights organizations have consistently said these products make assistive-technology user experience worse, not better, and they do not address the structural issues in the underlying code. We agree, and we are not going to use them. We're doing the work in the code instead. Last updated: May 12, 2026. ## Browse other STRIPPIES pages - [Homepage](/?view=md) - [FAQ](/pages/faq?view=md) - [First-order landing](/pages/first-order?view=md) - [Ingredients & science](/pages/ingredients?view=md) - [All products](/collections/all?view=md) - [Blog](/blogs/news?view=md) ## Source Canonical HTML: . Last rendered: 2026-07-27T10:43:12Z. For more STRIPPIES context, see the curated `/llms.txt` at .