Skip to content

Accessibility

Usable by everyone who has to use it.

Vantage aims to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, which is also the standard Section 508 points to.

Updated October 5, 2026

How it is tested

Every change runs an automated accessibility check (axe-core) against the core pages, the case page, the reference and this public site, in both the light and dark themes, and the build fails on any serious or critical problem. Colour tokens are generated to clear contrast thresholds: body text 14:1 or better, muted text at least 4.5:1 on every surface it can sit on.

Automated checks find only part of what matters. Vantage has not yet had an independent accessibility audit.

Keyboard and screen readers

Everything can be reached and used from the keyboard, with a visible focus ring and a link to skip to the content. Dialogs keep focus inside them and return it when they close. Fields carry their own labels, hints and errors, and charts that matter carry a table a screen reader can read.

⌘K or Ctrl+K
Search anything, and go anywhere
N
Log what you did, from any page
G then a letter
Go to a destination (G then D for Today)
V
Switch between your command and its teams
?
Every shortcut

Seeing it your way

Light and dark themes follow your device unless you choose one. Twelve colour palettes are available under Settings, each checked for contrast. Motion is turned off when your device asks for reduced motion, and every page is laid out for a phone as well as a desk. The films on this page have captions on by default.

Known limitations

  • Some dense tables (the queue, workload by person) scroll sideways on a narrow screen rather than reflowing.
  • The films have captions but no audio description.
  • Generated PDFs are not tagged for screen readers; what they contain is always available as a page in the app.

Report a barrier

If something in Vantage is hard or impossible for you to use, tell us through the request form (no account needed) or, once signed in, from Support. Say which page, what you were trying to do, and what assistive technology you use. A barrier is treated as a defect, not a feature request.