We want the site to work for everyone. That includes people who navigate by keyboard, people who use a screen reader, people who turn animation off, and people on small screens or slow connections. This page says what we are aiming for, what we have done, where we know we are short, and how to tell us when something is broken.

1. The standard we build to

We build to the Web Content Accessibility Guidelines (WCAG) version 2.1, Level AA. That is the standard most large publishers, broadcasters, and procurement teams already require, so it is the floor we hold ourselves to. We are tracking WCAG 2.2 and intend to meet its Level AA criteria as we touch each part of the site.

2. What we have done so far

A skip-to-main-content link at the top of every page so keyboard users can jump past the header in one tap.
Semantic headings, landmark regions (header, main, footer), and labelled navigation, so screen readers can announce the structure.
A document language attribute (lang="en") on every page.
Visible keyboard focus on every interactive element. Forms have labels for every field.
Reveal animations respect the prefers-reduced-motion setting. Turn motion off in your operating system and the entrance animations stop.
Alt text on meaningful images. Decorative bleed and gradient backgrounds are marked aria-hidden so they are not announced.
Tap targets sized for thumbs on mobile, and a sticky bottom CTA so the primary action stays reachable without a long scroll.
Colour contrast tested against WCAG AA for body text on the Aurora Black palette.

3. Where we know we are short

We have not commissioned a formal third-party audit yet. Until we do, this list is what we know from our own testing.

Some long-form headings use display weights at high contrast, but a few accent treatments on the home page sit closer to AA than AAA; we are tightening those as we redesign sections.
The atoms table interaction is keyboard-operable but the information density on small screens can be hard to navigate with magnification at very high zoom levels. A simplified view is on the roadmap.
Form error messages are visible inline but could be more descriptive. We are upgrading them as we touch each form.

We do not claim to be fully WCAG 2.1 AA conformant across every page on every browser today. We are aiming there honestly, not performatively.

4. How we test

The current state of the site has been tested by our team using a combination of: keyboard-only navigation, VoiceOver on macOS and iOS, axe DevTools and Lighthouse, browser zoom up to 200%, and the prefers-reduced-motion, prefers-color-scheme, and forced-colors media queries. A formal external audit is planned for the next major refresh of the site.

5. Tell us when something is broken

If something on the site is hard or impossible to use, please tell us. The fastest path is email to accessibility@hypercontent.ai. Include the page URL, the browser and assistive technology you are using, and what happened. We aim to acknowledge within 2 business days and to fix or come back with a plan within 10 business days, faster for blocking issues.

6. Contact

HyperContent, Inc.
PO Box 4314
Park City, UT 84060
United States
accessibility@hypercontent.ai