Our commitment

Accessibility.

We aim for WCAG 2.2 AA conformance across the site. Below is what we deliver, what we are still working on, and how to flag a gap. We update this list quarterly.

Last updated April 2026

What we are aiming for.

We design and build to WCAG 2.2 Level AA. We test every release with keyboard-only navigation, with VoiceOver on macOS and iOS, and with the reduced-motion preference enabled. The site should be operable, perceivable, understandable and robust — across the rotation of devices people actually use.

We have not certified this through a third-party audit yet. We will when the next release lands; the audit and the report will live here.

  • Keyboard navigation

    Every interactive element is reachable with Tab. Focus is always visible. Esc closes drawers. Enter or Space activates.

    Conforms

  • Color contrast (4.5:1 body, 3:1 UI)

    Body type sits at 4.7:1 against the bone surface. The graphite mode is held at 4.6:1. Form borders meet the 3:1 component minimum.

    Conforms

  • Reduced motion

    Every animation we wrote respects prefers-reduced-motion: animations stop or shorten to a fade.

    Conforms

  • Screen reader semantics

    Headings step from H1 to H2 to H3 with no skips. Forms have programmatic labels. Live regions announce cart updates and filter results.

    Conforms

  • Image alt text

    Primary product images now fall back to product titles when supplier filenames are missing or unusable. We are still auditing the full media library for richer descriptive alt text.

    Conforms

  • 200% browser zoom

    Core templates are being tested for reflow at desktop and mobile breakpoints. Any horizontal overflow found in QA is treated as a launch blocker.

    Conforms

  • Video captions

    Lookbook videos auto-play muted with captions on by default. Movement Library demo videos do not yet have captions — we are recording them this quarter.

    In progress

  • Linked PDF accessibility

    The press kit PDF is not yet tagged for screen readers. We rebuild it the next time we update the kit (target: June 2026).

    Known gap

  • Third-party iframes (Shop Pay, Klarna)

    We do not control the accessibility of payment provider iframes. Both vendors publish their own VPAT reports — if either is the blocker for you, write to us and we will route the alternative.

    Note

Feedback

How to flag a gap.

Email access@shop8am.com with the URL of the page where you hit the barrier, the device and assistive tech you are using, and what you expected to happen. A real human responds, fixes the gap or — if the fix takes longer — explains why and gives you a date.