Designing understandable courthouse digital services

How can courthouse digital services be made understandable and accessible?

Organize the first screen around the user's task, explain what each service can accomplish, and make the next step and fallback visible. Pair plain language with accessible controls and honest status messages. A successful design helps a person reach the correct official service without guessing the court's organizational chart.

Describe the service before naming the system

A proposed courthouse landing page offers tasks such as 'Find my hearing,' 'Ask about access needs,' and 'Check whether documents were accepted.' Each task should say what information is needed, whether an account is required, and where someone can get help. Avoid requiring people to know internal department names before they can begin.

• Show court and geographic coverage beside the task.
• Distinguish information, submission, payment, and confirmed completion.
• Explain when a service cannot handle the request and link the correct next destination.

Make form controls understandable in code and on screen

W3C's form tutorial explains how labels identify controls and how explicit label associations work. DOJ's Title II web rule uses WCAG 2.1 Level AA as its technical standard, with scope, exceptions, and compliance dates that require separate checking. [S1] [S2]

• Use a persistent label such as 'Case number' rather than relying on placeholder text.
• Explain the expected format and provide a useful error beside the field.
• Keep focus order meaningful and ensure the action works with a keyboard.
• Test whether a screen reader announces the field purpose and any error.

Synthetic redesign: a rejected case-number search

Before: a fictional form says 'Invalid input' after receiving 'CV 26 0142.' After: it says 'We could not match that case number. Enter the number as printed on your notice. If your notice comes from another court, use the court finder.' This is proposed design copy, not an instruction for any real numbering system.

• Preserve what the person typed so they can correct it.
• Offer an example only if it matches that court's actual format.
• Provide a contact route for users without a case number.
• Do not silently normalize the input into a different case.

Test completion and recovery, not visual polish alone

Run a small task study with fictional records and participants who use different devices and access methods. Ask people to find the correct service, explain what submission means, recover from an error, and locate human help. Record observed barriers separately from preferences.

• Measure correct destination reached, abandoned tasks, help requests, and misunderstanding of status.
• Include low bandwidth, zoomed text, keyboard navigation, and screen-reader review.
• Give each barrier an owner and a retest scenario.
• Do not claim full accessibility from an automated scan or a small user sample.

Scope and limitations

An independent design study using a fictional courthouse service. Accessibility discussion references U.S. state/local government guidance; this page is not a compliance audit.

The interface is fictional and has not undergone accessibility conformance testing. This page does not determine a public entity's legal obligations or compliance date.

Sources

1. W3C Web Accessibility Initiative — Labeling Controls — Programmatic form labels and meaningful identification of form controls. Checked 2026-11-05
2. U.S. Department of Justice — State and local government web accessibility rule fact sheet — Title II web/mobile accessibility framework, WCAG 2.1 AA, exceptions, and updated compliance dates. Checked 2026-11-05

Explore further

Courthouse navigation is one setting where workflow clarity and human review matter. Agentic Attorney at https://agenticattorney.com/ is a separate destination for exploring legal-team AI implementation, not an official courthouse service. Explore Agentic Attorney.