Accessibility Statement

Our commitment

Particular Ltd is committed to making ZeroEgress accessible to all users, including people with disabilities. We aim to conform to WCAG 2.1 Level AA standards.

What is implemented

• Semantic structure: one main landmark per page, a heading outline, and a skip link ("Skip to content" on the content pages, "Skip to tool" on the app pages) as the first focusable element.
• Accessible names from visible text where possible: the Scan button is named by its label in every state (Scan, Loading model, Scanning, Wiped); option inputs are labelled by their visible labels; entity chips carry the entity text, its type and its score as their name.
• States: the encryption toggle is a switch with aria-checked; entity chips are buttons with aria-pressed (true when excluded from redaction), operable with Enter or Space, and keep focus when they re-render.
• Announcements: the status line is a polite live region; during the model download it announces at 0, 25, 50, 75 and 100 percent and at Ready rather than at every percent; after a scan, "Scan complete: N entities found, audit chain verified" (or not verified) is announced and focus moves to the Annotated Text heading; error toasts are alerts.
• Focus management: after a refused scan focus moves to the T_max select; after an emergency wipe, to the "Start a new session" button; focus rings are visible on every interactive element.
• Contrast: text and controls meet WCAG 2.1 AA (4.5:1 for text, 3:1 for large text and controls), including the button text and the small labels; decorative arrows and the redaction bars in the before-and-after example are hidden from assistive technology.
• Comparison tables: column headers carry scope="col" and row labels are row headers with scope="row"; on narrow screens the row label and the ZeroEgress column stay in view while the middle scrolls, with a hint above the table.
• Touch and text size: on touch screens and narrow viewports every control is at least 36 px tall, and no text in the app is below 12 px.
• Reduced motion: with prefers-reduced-motion set, the app pages show no animations and no transitions.
• Colour is never the only carrier of meaning: entity highlights carry a text label with their type.

Known limitations

• During a scan the page is busy for the announced time, up to about 30 seconds on a slow device: the analysis runs on the main thread by design, so assistive technology cannot interact with the page until it finishes. The expected time is shown and announced before the scan starts ("Scanning, about N seconds on this device").
• The drag-and-drop file area needs a pointer; the "Browse files" button is the equivalent for the keyboard.
• The audit chain panel lists many technical records; a screen reader user hears them in order, without a summary beyond the completion announcement.

Assistive technology

ZeroEgress has been designed to work with screen readers and keyboard-only navigation. If you encounter issues with specific assistive technology, please contact us.

Feedback

If you experience accessibility barriers while using ZeroEgress, please contact contact@zeroegress.ai. We take accessibility feedback seriously and will work to address issues promptly.