Legal

Accessibility Statement

Last updated: August 11, 2026

Strive Pouches is committed to making strivepouches.com usable by people of all abilities. We design and build this site to meet the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, and we are working toward auditing the site against that standard on every release.

What we've done

The storefront is built with accessibility as a baseline, not a retrofit:

  • Keyboard navigation. We work to make every interactive element on the site reachable and operable using a keyboard alone, with visible focus styles that show where you are at all times. This includes the cart action, the flavor selector, the navigation menu, and the rest of the site pages we have exercised end to end.
  • Screen reader support. The site is structured with semantic HTML, labelled form controls, descriptive link text, and ARIA where native semantics fall short. Live regions announce cart updates and form validation without stealing focus.
  • Color contrast. We aim for text that meets WCAG 2.1 AA contrast ratios against the backgrounds it appears on, including the fine-print disclaimer block in the footer. We are working through known contrast issues across the site, including on this page, and the fixes ship as we find them.
  • Responsive layout. Content reflows at 200% zoom without loss of information or functionality, and the site is usable at viewport widths down to 320px.
  • Motion. Animations honor prefers-reduced-motion for the holographic sweeps, marquee tickers, scroll-driven reveals, and the 360-degree can rotation. Visitors who have asked their device to reduce motion see those animations pause or simplify.
  • Alternative text. Product imagery carries descriptive alt text. Decorative imagery is marked as such so it is skipped by screen readers.
  • Captions and transcripts. We plan to provide captions or a transcript equivalent for any video or audio content on the site. We do not have that pipeline in place yet, and we will update this statement when it ships.

Known limitations

Despite our efforts, some content may not yet be fully accessible:

  • Third-party content. Customer-submitted product reviews may contain images or formatting we cannot fully control. Where a barrier exists, please tell us using the contact below and we will work with the original source to fix it.
  • Legacy marketing assets. Older campaign imagery, captured before the current design system, may not meet every contrast guideline. We replace legacy assets as they come up in the rotation.
  • PDF documents. If we link to a PDF (a COA, for example), it may not yet be fully tagged. A plain-language summary is available on request.
  • Conformance auditing. We do not yet run an automated WCAG audit on every release. The bullets above describe what we are doing and intend to do; the audit cadence is the work that turns intent into measured conformance.

We treat every reported barrier as a bug, not a feature request, and we aim to resolve reports within a reasonable timeframe.

Reporting an accessibility barrier

If you encounter an accessibility barrier on strivepouches.com, or if you need an alternative format (large print, plain text, audio) for any content on the site, please tell us. The fastest way is email:

info@strivepouches.com

Please include:

  • the page URL where you hit the barrier,
  • what you were trying to do,
  • the assistive technology and browser you were using (if known).

We will acknowledge your report and work with you on a fix or an alternative.

Enforcement and feedback

The Web Accessibility Initiative (WAI) develops the WCAG standards this site follows. If your feedback is not resolved to your satisfaction, you have the right to escalate to the relevant enforcement body in your jurisdiction. In the United States, complaints can typically be filed with the U.S. Department of Justice, Civil Rights Division, Disability Rights Section, or with your state attorney general's office.

Continuous improvement

Accessibility is not a one-time project. We plan to audit the site against WCAG 2.1 AA as part of our release process and against WCAG 2.2 as browser support matures. This statement is reviewed at least once a year or when the site's design changes materially.