Accessibility

We build to WCAG 2.2 Level AA as our engineering target, keep a crosswalk to WCAG 2.1 AA (the U.S. Department of Justice standard) and to Section 508 for firms that procure with it, and we say only what has been checked. This page describes the named release and the documented scope evaluated with the listed methods — it is not a claim of legal compliance.

The production release of 16 August 2026: every public page in all seven languages, the sign-in, role-check, working-session and feedback flows, dialogs and search, the signed-in components (matter workspace, vault, ledger, beneficiaries, firm console, attorney desk) through a fixture harness, printed letters and packets, e-mail notifications, and the Word and Outlook add-in panes.

• Automated accessibility scans (axe-core, WCAG 2.0/2.1/2.2 A and AA rules) run on public pages and the seven-language matrix. Results are release evidence and critical or serious findings are intended to block promotion; current evidence and known limitations are published separately.
• Keyboard-only automation of the essential journeys — sign-in, the role check, the feedback form, the checkout hand-off, dialogs and search — with focus order, focus return and announcements checked.
• Zoom and reflow at the 400% equivalent, text-spacing overrides, forced-colours (high contrast) and reduced-motion checks.
• Source-level guards that fail the build if a form control loses its label, a colour pair drops below the contrast floor, a dialog stops managing focus, or this statement over-claims.
• Screen-reader task sessions (NVDA and Narrator on Windows) are scheduled against a published script; until they are recorded here they are described as not yet run — never as passed. VoiceOver has not been run.

• Full keyboard navigation with a visible focus ring on every control; dialogs, menus and search are keyboard-complete, and the attorney desk's list shortcuts are optional.
• Every form control has a persistent visible label; required fields and errors are announced to screen readers and connected to the field they belong to.
• Dialogs keep keyboard focus while open and return it when they close; the skip link lands on the page content; nothing hides behind sticky bars.
• Single-key shortcuts are off unless you turn them on, so dictated speech never triggers an action.
• Accessibility settings in every header (the accessibility symbol) — text size up to 150 %, roomier spacing, a high-contrast palette, reduced motion, always-underlined links and a sans-serif option — built into the site, saved on your device, no third-party script.
• Touch targets meet the 44px comfort floor across the portal, measured on a real 360px phone viewport in our test suite.
• Read-this-aloud on the trustee's guidance and lessons, using the best voice the device offers.
• Seven languages — English, Spanish, French, Haitian Creole, Russian, Hebrew, Ukrainian — with full right-to-left layout for Hebrew.
• Calm by design: no autoplaying sound, no flashing, no urgency animations on grief-adjacent surfaces.
• Every release runs automated accessibility audits (score floor 95/100) on the seven most-visited public pages including this one, and an accessibility scan of every public page in English plus a rotating sample of the localized pages; the full matrix of every public page in every language and the signed-in components run every night. A failing result blocks the release.

Every page carries an Accessibility settings control — the accessibility symbol in the header (a person with open arms inside a circle): text size, spacing, contrast, motion, link underlines and heading font. It is built into the site itself — no third-party overlay script — applies at once, and is saved on your device only. Your browser's zoom and your device's own accessibility settings keep working alongside it. The same control is here:

We audit our own product against WCAG 2.2 AA and publish what we find. What is still in progress, in the order it will land:

• Screen-reader sessions — NVDA and Narrator on Windows against our published task script, with each result recorded here; VoiceOver when Apple hardware is available.
• Testing with disabled users — screen reader, magnification, keyboard or switch, and cognitive access needs — on the role check and the checkout journey, with findings published in our register.
• Native-speaker review of the six translations, language by language, so the in-product “machine-translated” note can come down.
• An independent evaluation each year and a quarterly refresh of the conformance report and of this statement.

• Screen-reader sessions (NVDA and VoiceOver) have not yet been run on every journey; until they are, we describe them as not run rather than passed.
• Non-English translations are machine-generated pending native-speaker review; those screens say so in-product until each language is cleared.
• Browser-printed binders and packets depend on the browser's PDF tagging. Workspace PDFs preserve the supported Unicode corpus but are not tagged; the saved account view and semantic Word download are the more accessible alternatives.
• Payment happens on Square's hosted checkout page. We keep the hand-off and the return accessible; the hosted page itself is Square's and is covered by Square's own accessibility statement.
• Video captions are English-only for now; transcripts accompany every video.
• Automated audits do not catch everything. Some assistive-technology combinations may hit rough edges we have not found yet.

Designed for current Chrome, Edge, Firefox and Safari on desktop, Safari on iOS and Chrome on Android, with NVDA, Narrator, VoiceOver and TalkBack. Older combinations may not provide the same experience — tell us and we will provide an alternative format.

Square provides the hosted checkout page; Supabase delivers sign-in e-mails (the link lands on our own page). We test the integrated experience rather than relying on vendor statements, and we list any material limitation above.

A conformance report in the VPAT® 2.5 (International) layout — WCAG 2.2, WCAG 2.1/2.0 and Revised Section 508, with the evidence behind each row — is published in English and refreshed quarterly; the current evidence edition is a release candidate dated 31 August 2026 and has not been activated in production.

Read the conformance report (English)

First published July 2026 · corrected and rebuilt from the evidence ledger 16 August 2026 · Phase 7 evidence candidate refreshed 31 August 2026 without production activation · reviewed quarterly · owner: TrusteeClear's founder.

If anything here is difficult to use with your setup, use the form below. It reaches a person directly (it does not depend on email), and fixes are prioritized by how badly they block a task.