Overview

24Squad aims to make this site usable by everyone, including people with disabilities. We target WCAG 2.2 Level AA conformance across every public page. This page documents what we do, what we measure, and how to report issues.

Conformance standard

We follow the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. The WCAG 2.2 AA standard defines approximately 50 success criteria across four principles: perceivable, operable, understandable, robust.

Our current conformance status is partial AA. We meet the vast majority of Level AA criteria on every page; specific gaps (mostly in PDF documents and a small number of embedded videos) are tracked in the audit log.

What we do

Semantic HTML for structure — every page uses real <header>, <nav>, <main>, <article>, <aside>, <footer> landmarks.
Sufficient color contrast in both light and dark themes — every text token passes WCAG AA contrast (4.5:1 for body, 3:1 for large text). Tokens are defined in src/styles/global.css.
Keyboard-navigable menus and forms — every interactive element has a visible :focus-visible ring; tab order matches reading order; modals trap focus and restore on close.
Descriptive alt text for images — every <img> has an alt attribute that is either descriptive or explicitly empty for decorative images. The scripts/check-page-content-leak.mjs build gate fails if any image renders without alt text.
Reduced-motion support via prefers-reduced-motion: reduce — every animation, transition, and parallax effect is suppressed when the user has requested reduced motion.
Skip-to-content link as the first focusable element on every page.
Captions and transcripts for every video, with the caption file link exposed in the player UI.
Form labels — every <input> has an associated <label>; error messages are programmatically linked via aria-describedby.

How we test

Automated: axe-core runs against the preview server on every PR via the scripts/seo-audit.mjs integration. Critical and serious violations block merge.
Manual: keyboard-only navigation, screen reader walkthrough (NVDA on Windows, VoiceOver on macOS), and zoom-to-200% on every major template. Performed by the team on every quarterly release.
User feedback: the contact form exposes an [email protected] inbox. Issues are tracked in the repository.

Known issues

We currently have no open critical or serious accessibility issues on the public site. We are actively working on:

Caption quality for the older video library (transcripts exist but captions are auto-generated).
High-contrast mode refinement for the dark theme.

Feedback

If you encounter an accessibility issue, please email [email protected] with the page URL, a short description, and (if possible) the assistive technology you were using. We commit to:

Acknowledge your report within 2 business days.
Triage and respond with a fix timeline within 5 business days.
Credit you in the next public audit update if you request it.

This page was reviewed by Renish Mithani on 19 July 2026 and is reviewed quarterly.

Accessibility