Crocea is for everyone.

Crocea believes the web should work for everyone. We treat accessibility not as a checkbox but as a quality standard — the same as the supplements in the bottle. We design, build, and test trycrocea.com to be usable by people with a wide range of abilities, including those who use screen readers, keyboard navigation, voice control, magnification, or other assistive technologies.

We're not perfect, and we'll never claim to be. What we commit to is: making meaningful progress, being honest about gaps, and responding quickly when you tell us something isn't working.

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA, the international accessibility standard published by the W3C. WCAG 2.2 is the basis for accessibility regulations in the US (ADA), EU (European Accessibility Act), UK, Canada, and most other major markets.

Our current conformance status: partial conformance — most of the site meets WCAG 2.2 AA, with the known exceptions listed in Section 7 below. We're working to close the gaps.

Every interactive element on the site — links, buttons, form fields, the cart, the subscription picker, the checkout — can be reached and operated using only a keyboard. Specifically:

• Tab moves forward through focusable elements; Shift+Tab moves back.
• Enter or Space activates buttons and links.
• Arrow keys navigate within menus, sliders, and the product gallery.
• Escape closes the cart drawer, modals, and dropdowns.
• A visible focus indicator shows which element currently has keyboard focus.
• A skip-to-main-content link appears at the top of every page when you press Tab from the address bar.

We test the site with the most widely used screen readers:

• NVDA (Windows, free)
• JAWS (Windows, commercial)
• VoiceOver (macOS and iOS, built in)
• TalkBack (Android, built in)

Specifically, we use semantic HTML (proper heading hierarchy, landmark regions, form labels), ARIA attributes where semantic HTML isn't sufficient, descriptive alt text on every product image, and meaningful link text (no "click here" buttons).

If you use a screen reader and something is announced unclearly, please tell us — we want to know.

Visual accessibility features built into the site:

• Color contrast — body text on background meets or exceeds the 4.5:1 contrast ratio required by WCAG AA. Headings and large text meet 3:1.
• Color is not the only cue — links are underlined, error messages include text and icons (not just red color), and form validation uses both color and text.
• Resizable text — the site remains usable when text is resized up to 200% using your browser's zoom.
• No content that flashes more than three times per second (WCAG 2.3.1).
• Reduced motion — if your operating system is set to reduce motion, animations on the site (scroll-triggered effects, ticker, image fades) are minimized or removed.

We test the site using a combination of automated tools, manual testing, and assistive-technology testing:

• Automated: Google Lighthouse, axe DevTools, WAVE — run on every major release.
• Manual: keyboard-only navigation testing, color-contrast checks on every brand asset, focus-order review on every new template.
• Assistive tech: we test critical flows (PDP, cart, checkout) with NVDA on Windows and VoiceOver on Mac/iOS before any release that touches those pages.

Automated tools catch roughly 30–50% of accessibility issues. The rest requires human judgment, which is why manual review is mandatory in our release process.

We try to be honest about what doesn't yet meet WCAG 2.2 AA. Current known gaps:

• Third-party review widgets: our customer review module is provided by a third-party app. Some review submission forms may not be fully keyboard-accessible. We're in conversation with the vendor about fixes.
• Embedded video transcripts: not every product video on the PDP has a written transcript yet. We're adding transcripts on a rolling basis — most-watched videos first.
• Some PDF documents (e.g. older Certificates of Analysis) may not be fully tagged for screen readers. We can provide an accessible version on request — see Section 11.
• Social-media embeds: Instagram or TikTok embeds on the site inherit those platforms' accessibility, which we can't control.

If you encounter any other barrier we haven't listed, please tell us — we add to this list when we learn about gaps, and we work on closing them.

If something on the site doesn't work for you, please tell us. Reports help us fix problems for everyone.

Email accessibility@trycrocea.com with:

• A description of the problem and what you were trying to do.
• The page URL where you encountered the problem.
• The browser and assistive technology you were using (if any).
• How best to reach you with a response (email, phone — whichever works).

Our commitment: we respond within 5 business days, usually the same day. We confirm receipt, investigate, and tell you what we found and what we plan to do about it.

Some content on trycrocea.com is hosted or served by third parties — embedded YouTube product demos, Instagram and TikTok widgets, the Shopify checkout, payment processors (Shop Pay, PayPal, Stripe), and our review/email/analytics tools.

We can't directly control the accessibility of these third-party services. Where we have a choice of vendor, we choose accessibility-aware partners. Where we don't, we provide alternatives (e.g. if the embedded YouTube player isn't working with your screen reader, we can email you a transcript or a direct download link).

The following are available on request, free of charge:

• The Supplement Facts panel, ingredient list, and dosage instructions as plain text or large print.
• Certificates of Analysis as accessible PDFs or read aloud over a call.
• Order confirmations, shipping notifications, and subscription emails in plain-text format (instead of HTML).
• This accessibility statement as a plain-text document.

Email accessibility@trycrocea.com to request any of the above.

This accessibility statement was last reviewed in May 2026. We review it at least every six months — and any time we make significant changes to the site. When we update the statement, we update the "Last reviewed" date at the top of the page.

Our long-term goal is full WCAG 2.2 Level AA conformance, with progress toward Level AAA on pages where it's achievable (e.g. our blog and educational content).