Draft, pending counsel review. This page describes how Dry Run Ready works today and may change after legal review.

Legal

Accessibility

Last updated

01Commitment and target

We design toward WCAG 2.2 Level AA for Dry Run Ready. We have not completed a formal conformance assessment, so we do not claim full conformance.

02Status

This is a self-assessment by the people who build Dry Run Ready, made during development up to October 28, 2026. No external audit has been done. What we have checked in the code and in the browser:

  • Every form field has a visible label; hints and AI notices are linked to their field with aria-describedby.
  • The AI notice on the drill page and the assistant is visible text with the note role, never a tooltip or an icon alone.
  • Keyboard focus is visible on every control (a two-pixel outline).
  • Status messages (saving, errors, dismissible alerts) use status and alert roles so screen readers announce them.
  • Readiness charts use native progress elements with text labels, and every value is also shown as text.
  • Colour contrast of the main text and controls was checked against the AA ratio in the design tokens.

03Known limitations

  • No screen-reader walkthrough of a complete drill has been recorded yet.
  • The voice drill needs a microphone and speakers. Spoken answers are saved as text in the transcript, but the live session itself has no captions.
  • Playbooks and reports print through the browser; the printed output is not a tagged PDF.
  • The nine success criteria that are new in WCAG 2.2 (focus not obscured, dragging alternatives, 24 by 24 pixel target size, consistent help placement, no redundant entry, accessible authentication) have not been checked one by one.
  • Timed drills add time pressure by design. Quick drills have no timer, and timed drills can be paused.

04Feedback

Tell us at dryrun@airworthyadvisory.com what was hard to use; we aim to reply within two business days and to provide the information in another format.