Script Week is meant to be usable by every coach on a staff, including coaches who use a keyboard instead of a mouse, a screen reader, large text, or a high-contrast display. This page says what is built, what is not built yet, and how to tell us about a barrier. It describes the product as it is, not as we hope it will be.
Our target is WCAG 2.1 Level AA. We do not claim full conformance today, and we have not had a third-party audit. The sections below are exact about where we stand.
What is built
- Color contrast — text and controls in both the light and dark themes meet the AA ratios (4.5:1 for text, 3:1 for control boundaries and marks). The contrast table is checked by an automated test on every change, so a color cannot drift below the line without the build failing.
- Dark mode and large text — the app follows your operating system's light or dark setting, or a choice you make in the header. Text is set in relative units, so browser zoom and your system text size are respected, and pages are built to reflow to a phone width rather than assume a wide screen.
- Keyboard — every page has a skip link to the main content, every button and form control is reachable in tab order with a visible focus ring, and menus and dialogs close with Escape.
- Screen readers — pages use real headings, landmarks and labelled form controls; the current page is marked in the navigation; confirmations and errors are announced through live regions; the play designer's field is exposed as a labelled image whose description reads the whole play: the formation and concept, how many players and routes it holds, and each route in words ("X: 15 yards downfield, breaking right").
- Reduced motion — if your device asks for reduced motion, every animation and transition in the app is turned off.
- Print — call sheets, wristbands and play cards print in high-contrast black on white regardless of the on-screen theme, and the printed output is the product for most coaches.
- No time limits — no task in the coach app has a timer, and the player app's quizzes are untimed.
What is not built yet
The play designer is a drawing surface, and most of it now works without a pointer. A list beside the field names every shape ("QB", "Route from X", "Text: Cover 2"); arrow keys move through it and Enter selects, and the inspector panel then edits every property of the selected shape. With a shape selected, the arrow keys move it one yard on the field (Shift: five), and each move is undoable. The toolbar's Add menu places a new player or a route from the selected player, and the inspector has fields and buttons for each point of a route. The one act that still needs a mouse, trackpad or touch screen is drawing a freehand route; a route placed from the keyboard starts as a straight stub and is shaped point by point in the inspector. That is the gap left, and we say so here until it is closed.
Video walkthroughs recorded by a coach do not carry captions. Recording is a coach's own screen and voice, and we do not generate transcripts.
For districts and athletic departments
If your purchasing process asks for an accessibility conformance report (a VPAT or ACR), write to us and we will prepare one against the current product. We would rather send you an exact document with a short list of exceptions than a template with every box ticked.
Tell us about a barrier
If something in Script Week is hard or impossible for you to use, write to support@scriptweek.com. Tell us the page, what you were trying to do, and the browser and assistive technology you were using. A report like that goes to the front of the queue — it is a bug, not a feature request — and we will tell you what we changed.