Trust
Accessibility
A court process should not be harder because of the tools. This page says plainly what we build to, how we check it, what its limits are, and how to tell us when something is in your way.
Our commitment
People come to this platform at difficult moments, in six languages, on whatever device they have, sometimes with a screen reader, sometimes with only a keyboard, sometimes needing to leave the site instantly. Accessibility here is not a compliance checkbox — it is part of the product's honesty: a form a screen reader cannot complete is a form that does not work.
The target
Our engineering target is WCAG 2.2 Level AA, verified by automated checks on every release.
We say "target" deliberately. Conformance is a property of every page on every day, and parts of the evidence — human screen-reader sessions across assistive technologies — are still being run. This statement never claims more than the evidence ledger holds.
Scope
The statement covers the public platform at this domain in all six languages, the signed-in workspace, and the documents the platform produces (Word exports carry real heading structure and document titles; completed official court forms carry a document title and language tag on the copy you download). It does not cover the courts' own PDF layouts, third-party sites we link to, or the payment processor's hosted checkout.
How we verify — the methods actually used
Every release is gated by: token-level contrast math computed from the stylesheet source (text, control boundaries, and the focus ring measured against every background they sit on — never rounded up); an automated browser census that runs axe-core WCAG 2.2 checks over every indexable page plus the signed-in screens rendered with fixture data; keyboard-only task journeys (search, complete, and download an official form; answer a quiz; reach the quick-exit control); reflow at 400% zoom, text-spacing overrides, forced-colors, and reduced-motion checks; and a fixed accessible-structure snapshot of the core interface. A release that regresses any of these does not ship.
Manual assistive-technology sessions (NVDA, VoiceOver, iOS VoiceOver) follow a written script, and their results are recorded run by run — a task not yet run is recorded as NOT RUN, never inferred from automation.
Known limitations — stated honestly
Completed official court forms download in the court's own layout. The courts publish those PDFs without accessibility tagging, and we never redraw an official form — the questionnaire on this site is the accessible way to complete one: every field the form names, asked as labeled, keyboard-operable HTML, with your answers placed onto the court's layout at download.
Human screen-reader results exist only where a named person has run the script; the sessions still pending are listed as NOT RUN in the public evidence register. Account and payment emails are sent by our infrastructure providers in their default templates. The verbatim text of Florida law is presented exactly as the state publishes it, in English, and is marked as English so screen readers pronounce it correctly inside every language edition.
Compatibility
The platform is built to work with current versions of Chrome, Edge, Firefox, and Safari, on desktop and mobile, with keyboard-only navigation, at up to 400% zoom, in forced-colors mode, and with the operating system's reduced-motion setting honored everywhere motion exists. Right-to-left layout is native for the Hebrew edition.
A display-settings control lives in the header of every page (the circled-person symbol): text size, high contrast, reduced motion, and relaxed text spacing, saved on your device. These are first-party conveniences built on our own design system — they mirror what your browser and operating system already provide, and they are never a compliance mechanism.
What we never do
Remediation happens in our source code, at the most reusable layer. We do not install third-party scripts that claim to fix accessibility from the outside, and we treat any claim of blanket conformance — by us or by a vendor — as the red flag it is.
Tell us when something is in your way
If any part of this platform is hard or impossible for you to use, that is exactly what this form is for. It asks only what happened and where — never about your disability, and never about your case. Leaving a way to reach you is optional. We aim to respond to accessibility feedback within five business days.
Statement history
First published August 18, 2026, at the close of the platform's accessibility engineering program (phases ACC-0 through ACC-9 of the public plan). The full findings register, evidence ledger, and known-limitations record live in the repository and back every sentence on this page.