Skip to content
HunterPass

Accessibility

Accessibility Statement

What we have built in, what is verified by the build rather than by good intentions, and what we know is not finished.

Last updated · August 2026

The target

WCAG 2.2 Level AA. We are not claiming full conformance — a site this new making that claim would be asserting something it has not tested properly. What follows is specific about what is verified and what is not.

Verified by the build

  • Color contrast. Every documented color pairing in the design system is checked against its WCAG target by an automated test that fails the build if a pairing regresses. This is not a manual audit that goes stale — it runs on every commit.
  • Design tokens. Color values are defined once and mirrored across CSS, TypeScript, and JSON, with a test that fails if they drift apart. Contrast cannot silently break by someone editing one of the three.

Built in

  • Reduced motion. Every animation on the site — scroll reveals, the hero video, parallax, and menu transitions — honours prefers-reduced-motion. The hero video hides itself and shows a still rather than relying on a script that could fail.
  • Keyboard operation. All navigation, menus, and forms are keyboard-operable. The mega menu and mobile navigation are built on accessible primitives with focus trapping, focus restoration, and Escape handling rather than hand-rolled equivalents.
  • Visible focus. A brand-colored focus ring is applied globally to every interactive element, with an offset so it is visible against any surface.
  • Skip link. A skip-to-content link is the first focusable element on every page.
  • Semantic structure. One h1 per page, headings in order, landmarks used properly, and tables with real header cells and captions rather than styled divs.
  • Disclosure without JavaScript. FAQ accordions use native disclosure elements, so they work with JavaScript disabled and their answers are always available to assistive technology.
  • Text scaling and reflow. Layouts are fluid, type scales with the viewport, and wide tables scroll inside their own container rather than forcing the page sideways.

Known gaps

Being specific is more useful than being reassuring.

  • We have not yet completed a full assistive-technology pass with screen readers across every page.
  • Generated photography currently carries decorative alt text where a richer description would serve better on content-bearing images.
  • The product application at its own subdomain has not shipped, so nothing here speaks to its accessibility yet. It will be held to the same standard.

Tell us

If something on this site blocks you, we want to hear about it specifically — the page, what you were trying to do, and what happened. Email hello@hunter-pass.com. A concrete report gets fixed; a general complaint gets filed.