Accessibility

Accessibility Statement

A web that works for more people is a better web. Here’s where we are and how to tell us when we miss.

Last updated: April 30, 2026

Our commitment

ProjectThunder is committed to making projectthunder.com usable by as many people as possible, including people with disabilities. We measure our work against the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. We treat accessibility as part of quality, not a separate checkbox at the end.

What we’ve done

  • Semantic structure. Pages use proper landmarks (header, main, footer, nav), heading levels in order, and lists where they belong — so screen readers can navigate the way they expect.
  • Keyboard navigation. We test interactive elements — links, buttons, form fields, tabs, the mobile-menu toggle — for keyboard reachability, and we expose a “Skip to main content” link at the top of each page. We’re working through a full axe-core + manual keyboard pass before claiming complete coverage.
  • Color contrast. Body text meets at least 4.5:1 against background; large display text meets at least 3:1.
  • Alt text and ARIA. Meaningful images get descriptive alt text; decorative SVGs are marked aria-hidden; tab controls and the menu toggle expose ARIA states (aria-expanded, aria-controls, aria-current).
  • Forms. Every form input has a visible label and associated <label> element. Errors are reported in plain language; we use HTML5 validation patterns where the browser can help.
  • Reduced motion. The page-hero parallax and the Tesla-coil scan loader respect prefers-reduced-motion for users who’ve asked the OS to scale animations back.
  • Responsive layout. Pages reflow cleanly from 320 px wide up through ultrawide, and content remains readable at 200% browser zoom without horizontal scrolling.

Where we know we still have work to do

Honesty is part of accessibility. Items we are still improving:

  • Video. The hero video on the scan page does not yet have closed captions or a transcript. It is decorative and contains no narration, but we’ll add a transcript link.
  • Tab focus styles. Some custom UI elements use the browser default focus ring; we’re moving everything to a consistent, high-contrast focus outline.
  • Third-party content. Embedded players (Vimeo) and external sites we link to are governed by their own accessibility practices; we cannot guarantee them.

Tools we use

We test with a combination of:

  • axe-core and Lighthouse during development.
  • Keyboard-only walkthroughs of interactive flows during release reviews.
  • Screen-reader spot checks with VoiceOver (macOS) and NVDA (Windows).
  • Color-contrast verification at design and review stages.

Tell us when something is broken

If you can’t use part of the site because of an accessibility issue, please write us. We will respond within five business days.

Helpful detail to include: the page URL, the action you were trying to take, the assistive technology and browser you were using (if any), and what happened.

Conformance status

This site is partially conformant with WCAG 2.2 Level AA. "Partially conformant" means that some content does not yet fully conform to the standard. We track the gaps above and remediate them as part of normal maintenance.

Formal complaints

If you have raised an accessibility concern with us and are not satisfied with our response, you have the right to escalate to your local accessibility regulator. In the United States, this includes the U.S. Department of Justice (Title III of the ADA).