Accessibility Statement

Our standard

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, consistent with Title III of the Americans with Disabilities Act (ADA).

What we've built in

Each of these describes how the site behaves today, not what we intend to do.

• Semantic structure on every page: a navigation landmark, a main landmark and a footer landmark, one H1 per page, and headings in order.
• A “skip to main content” link that is the first thing you reach with the Tab key, with a focus ring picked to stay legible against its own dark background.
• A visible focus ring on every interactive element: a 2px solid outline offset from the element, in addition to a softer shadow ring. We never set outline: none, including on form inputs, where the design system we started from did.
• A real navigation menu on small screens, built as a native disclosure: it opens with Enter or Space, closes with Escape, and closes when you choose a link.
• A visible label bound to every form field, with hint and error text announced together with the field it belongs to.
• Expandable content (FAQs and the mobile menu) built on native disclosure elements. They are keyboard-operable without JavaScript, and the answers are in the page whether or not you open them.
• Text colours measured against the AA thresholds: 4.5:1 for body text, 3:1 for interface borders and large text. Seven defects we found in our own design system were fixed before this site shipped: focus rings too faint to see, and text colours below the floor, one of them on a form error message.
• Decorative graphics and animations hidden from assistive technology. Anything that carries information is either real text in the page or carries a written description; charts cannot be added without one.
• Respect for the “reduce motion” setting in your operating system: animations resolve immediately to their finished state rather than being cancelled part-way, and smooth scrolling is turned off.
• Layouts that reflow to a 320-pixel-wide viewport without horizontal scrolling, and to 200% browser zoom without loss of content.
• Information never conveyed by colour alone: a status colour always sits beside a word or a count.

How we check it

Every page gets four checks before it publishes: a keyboard-only pass through the skip link, the menu, every disclosure and every form; a confirmation that each interactive element shows a visible focus ring; a contrast measurement of each text colour against the background it actually sits on; and a layout pass at a 320-pixel-wide viewport. Accessibility is a practice, not a checkbox, so the checks run again whenever the design system changes underneath a page.

What we haven't done yet

We have not commissioned an independent third-party audit, and we have not tested every page with every screen reader and browser combination. This statement describes checks we ran ourselves. We would rather tell you that than imply a certification we do not hold, which is the same standard we hold our own measurement to.

Found a barrier? Tell us.

If any part of this site is difficult for you to use, email accessibility@apexdiscover.aiwith the page and the problem. We aim to respond within two business days and to fix verified barriers promptly. If you need the information on this site in another format, we'll provide it. By post:

Apex Discover LLC, 1309 Coffeen Avenue STE 1200, Sheridan, WY 82801, US.