Entering the realm

VERITAS QUEST

Accessibility

What Veritas Quest does, and does not yet claim, on accessibility.

The frontend ships skip links, keyboard navigation, reduced-motion support, and stored display preferences, checked by an automated scan rather than left as an unverified claim.

What accessibility features are built in?

Skip links, focus-visible management, aria labelling across the component library, arrow-key navigation on tabs and the star chart, prefers-reduced-motion support, and a dark theme are all implemented today.

How do we check that these features keep working?

An automated axe scan runs against every screen and asserts zero critical violations, alongside a keyboard smoke test that checks for a visible focus ring and Enter-key activation, and a reduced-motion test.

Does Veritas Quest claim a WCAG conformance level?

No. We have not completed a conformance audit against a specific WCAG level or an independent third-party review, so we do not claim one.

Is there a high-contrast or forced-colors mode?

Not yet. A dark theme exists, but a dedicated high-contrast or forced-colors mode is not implemented.

How do display preferences apply without a flash of the wrong size?

Stored accessibility preferences are applied before the first React render, so text size and font choices do not shift after the page has already painted.

Who do I contact about an accessibility problem?

Use the same support entry point as any product or account question, with your school context if you have one, or email support@veritas.quest.