Accessibility at trustbox

Federal staff, providers and the public all use trustbox, so it has to work for everyone, including people who use a keyboard, a screen reader, magnification or other assistive technology.

Our goal

We use the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA as a target for improving trustbox.dev, the admin app our customers use, the trust centers we host and their availability pages, the FedRAMP Trust Center Index, and the emails we send.

Where we are

We use automated browser checks and practical keyboard and visual checks to find and fix accessibility barriers. Formal WCAG and Section 508 conformance has not been assessed. These checks do not establish conformance, and known limitations and unverified areas remain:

• Sign-in time limits. For security, a signed-in session ends after 30 minutes without activity. Two minutes before, the page warns you and a "Stay signed in" button extends it. A sign-in also lasts at most 8 hours, which can't be extended: the page warns you 5 minutes before and offers a new sign-in in another tab, after which what you typed on the page can still be sent. The warnings need JavaScript.
• Screen readers. We check names, roles and states in the browser's accessibility tree, but we haven't yet tested with NVDA or VoiceOver. Announcements of errors and status messages are unverified until we do.
• High-contrast modes. We haven't yet checked the pages in Windows high-contrast mode.
• A few pages not yet checked at narrow widths. The payment result pages and the pages for resuming sign-up or unsubscribing from email haven't been checked at 320 pixels or with increased text spacing.

Some content isn't ours. Payment pages are run by our payment provider. The documents a provider publishes on its trust center are that provider's, and their accessibility is the provider's responsibility.

How we test

• Our automated test suite uses axe-core in Chromium on the page types in its test set, in light and dark themes at 1280 and 320 pixels wide, plus checks of skip links, text spacing and browser accessibility-tree information. It does not cover every page or every accessibility requirement.
• Our October 31, 2026 testing record describes a headless Chromium sweep of 61 page types, plus directory and availability-page templates, with keyboard, layout and source checks. It led to fixes for skip links, focus, contrast, text spacing and narrow layouts. Resized viewports were used rather than browser zoom; real screen readers, Windows high-contrast mode and other browsers were not tested.

Formal assessment

A formal accessibility assessment and an Accessibility Conformance Report (ACR) are deferred. An assessed ACR is not available. We continue practical testing and fixes without treating them as certification or a conformance report.

Tell us about a barrier

If something on trustbox is hard to use with your browser, keyboard or assistive technology, or you need information in another format, email support@trustbox.dev. Tell us the page and what happened. We reply within one business day, and the same business day for outages and agency access problems.

Last reviewed October 31, 2026.