Accessibility

Our commitment

Our target standard is Section 508 of the Rehabilitation Act and the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. We have not yet reached full conformance, and we do not claim a conformance level below; accessibility work is ongoing and prioritized alongside functional defects.

What is in place today

• Semantic page structure: header, navigation, main, and footer landmarks, with exactly one top-level heading per page and a logical heading order.
• Labelled form controls throughout, including visually hidden labels where a visible label would be redundant.
• Visible keyboard focus styles and keyboard-operable navigation, including the marketing site menus.
• A dashboard mobile navigation drawer that is announced as a dialog, closes on the Escape key, and closes automatically on navigation.
• Light and dark themes that follow your system preference.
• Multi-factor authentication forms whose status and error messages are announced to screen readers via live regions.

Known gaps

The following issues are confirmed in the current release. We list them so you can plan around them and hold us to fixing them:

• Forms inside the dashboard beyond the member-invitation and API-key dialogs have not yet been audited for error announcement, so some may still report errors visually only.
• In the sales chat transcript, messages are distinguished as yours or the assistant's by position and colour. A screen reader reading back the log does not announce who said what.
• The screen shown when an unexpected application error occurs has no top-level (level-one) heading; its title is a level-two heading.
• No page has been tested end to end with JAWS, NVDA, or VoiceOver by a specialist. The fixes below were verified in code and by calculation, which is not the same as verifying them with the assistive technology a real user runs.

Recently fixed

These appeared on this page as known gaps and have since been remediated:

• A skip-to-content link is now the first focusable element on every page. On all standard screens — the marketing site, sign-in, registration, password reset, the dashboard, the assessor workspace, the multi-factor challenge, invitation acceptance, and the "access restricted" page, and the site-wide "page not found" and application-error fallback screens — activating it moves focus to the main content landmark.
• Sign-in, registration, invitation-acceptance, contact, and the admin dialogs now announce errors through live regions, associate them with the field that failed, and move focus to the problem on a failed submit. Success confirmations are announced too.
• Dark-mode error text now measures 6.0:1 against card surfaces and 6.5:1 against the page background, above the 4.5:1 minimum.
• The sales chat announces incoming replies, moves focus into the panel when it opens, returns focus to the launcher when it closes, and closes on the Escape key.
• The dashboard mobile navigation drawer traps keyboard focus while open and restores focus to the button that opened it. The marketing site's mobile menu is a modal menu that does the same: focus stays inside it while open, Escape closes it, and focus returns to the menu button.
• Keyboard focus indicators now measure at least 3:1 against every surface they sit on in both themes (previously about 1.9:1 on white), and card headings are exposed as real headings so they appear in screen-reader heading navigation.
• Users denied access by role now reach a real "access restricted" page with recovery links, rather than the site's generic 404.

Report an accessibility barrier

If you encounter a barrier not listed above, email [email protected] or use the contact page. Email is listed first deliberately: if the contact form itself is the barrier, you should not have to use it to report that. Include the page or feature, what you were trying to do, and the assistive technology and browser you were using. Accessibility reports are triaged with the same priority as functional defects, and we aim to acknowledge them within five business days.

Conformance assessment status

A formal third-party conformance assessment (VPAT / Accessibility Conformance Report) has not yet been completed for GovSecure AI. Once one has been performed, it will be available on request through the contact page.