Court digital accessibility ensures that all residents can independently access legal information, complete required actions, and participate in proceedings under WCAG 2.1 AA and ADA Title II.
Access to justice is a foundational principle of democratic governance. The right to understand the legal process. The right to access public records. The right to participate in proceedings. The right to pay fines and fulfill obligations. The right to seek relief from the legal system.
When court and justice system digital services are inaccessible, these rights are not equally available to all residents. A blind defendant who cannot navigate the online case lookup system to find their hearing date. A deaf litigant who cannot access video proceedings without captions. A self-represented party with a cognitive disability who cannot understand an online court form written at a 14th-grade reading level. A resident with a motor disability who cannot complete an online fine payment because the payment portal requires mouse interaction.
These barriers exist at the intersection of disability discrimination and justice system access — a place where the consequences of exclusion are particularly severe. Missing a court date because a case lookup system was inaccessible is not a billing dispute. It is a potential warrant. Failing to complete a required online filing because the system was not keyboard accessible is not an inconvenience. It is a potential default judgment.
Courts and justice agencies operate some of the most consequential government digital services that exist. The accessibility of those services determines whether the legal system is equally available to all residents it serves — or whether disability creates a class of residents for whom justice is structurally harder to access.
This guide covers the specific digital accessibility requirements for courts, clerk of court offices, prosecutors, public defenders, law libraries, and other justice system agencies — and what the distinct characteristics of legal digital services mean for compliance obligations.
TLDR: Court Accessibility Risk Checklist
- Case lookup systems without accessible tables
- E-filing portals that break keyboard navigation
- Payment portals with inaccessible CAPTCHA
- Jury systems with inaccessible forms and date pickers
- Court PDFs without structure or reading order
- Video proceedings without accurate captions
- Legal forms written above accessible reading levels
- Vendor systems without WCAG compliance
The Legal Foundation: Courts Are Not Exempt From ADA Title II
Courts are state and local government entities fully covered by ADA Title II. The DOJ's enforcement activity against state and local courts has been consistent, substantive, and sometimes significant.
Title II of the ADA has been applied to courts in contexts including: physical courtroom accessibility, accessible communication in proceedings, sign language interpreter availability, document alternative format requirements, and — increasingly — digital service accessibility. The DOJ's 2024 final rule establishing WCAG 2.1 AA as the technical standard for Title II digital compliance applies to courts and justice agencies with the same force as any other Title II entity.
Several characteristics of court digital services make their accessibility failures particularly significant under ADA Title II:
Mandatory interaction. Unlike most government services, where a resident can choose whether to engage, court system interactions are frequently mandatory. A resident who receives a traffic citation must respond. A defendant must appear. A juror must report or formally request an exemption. A respondent in a civil case must file a response. Mandatory interactions with inaccessible digital systems create barriers that residents cannot simply opt out of.
Consequential failures. The consequences of failing to complete a court-related digital interaction are often significantly more severe than failing to complete a routine government service transaction. A missed filing deadline can result in default judgment. A missed online jury response can result in a contempt citation. A missed fine payment — if the payment portal was inaccessible — does not eliminate the fine or the penalty for non-payment.
Self-represented litigants. Courts serve a substantial and growing population of self-represented litigants — people navigating the legal system without an attorney. This population is disproportionately likely to rely on digital court services as their primary access point and is disproportionately likely to include people with limited resources, limited legal literacy, and disabilities. The self-represented litigant accessing court services online is often the person for whom accessibility matters most.
Public records obligations. Court records are public records. The public's right to access court records — case filings, dockets, judgments, orders — is a fundamental transparency principle. Inaccessible public records access systems create a two-tier system where residents without disabilities can access court records and residents with disabilities cannot.
Accessible Online Case Lookup and Docket Access Systems
Public case lookup systems — the portals that allow residents to search for case information, view docket entries, and track case status — are among the most-accessed public-facing digital services court systems operate. They are also among the most consistently inaccessible.
Common Accessibility Failures in Case Lookup Systems
Search interface accessibility. Case lookup systems typically include multiple search fields — case number, party name, filing date range, case type. These fields are frequently implemented using vendor-specific components that do not follow standard keyboard navigation patterns. Tab order through search parameter fields is often illogical. The "search" button is sometimes implemented as a non-button element that requires mouse interaction to activate.
Results table accessibility. Search results are displayed in data tables showing case number, parties, filing date, and status. These tables are almost universally implemented without proper header row designation. Screen reader users navigating the results table hear a stream of data — numbers, names, dates — with no column context to interpret what each value represents.
The accessible results table requires <th> header cells with appropriate scope attributes so that screen readers announce column context with each data cell: "Case Number: 2025-CV-001234. Plaintiff: Martinez, Rosa. Defendant: City of Springfield. Filing Date: January 15, 2025. Status: Active."
Case detail page accessibility. Clicking through to a case detail page typically shows a comprehensive docket — a chronological list of filings, hearings, orders, and other case events. Docket displays often use complex nested structures or custom display components that screen readers cannot navigate coherently.
Document download and viewing. Case documents — pleadings, orders, judgments — are almost universally available as PDFs. Most of these PDFs are court-generated documents produced by case management systems that export without accessibility structure. A docket entry that says "Order Granting Motion for Summary Judgment" links to a PDF that a screen reader cannot interpret because the document has no heading structure, no reading order, and no tag structure.
Filter and sort controls. Many case lookup systems include filter controls — filter by date range, case type, court division — implemented as custom components that are not keyboard accessible. Residents using keyboard navigation cannot apply filters and must view all results rather than the narrowed set they need.
The Accessible Case Lookup Standard
An accessible public case lookup system must:
Present the search interface as a standard accessible form with labeled fields, logical tab order, and keyboard-operable search submission.
Display search results in a properly structured HTML table with designated header rows and appropriate scope attributes.
Present case detail and docket information in a structure that screen readers can navigate coherently — with logical heading hierarchy separating docket sections, list structures for docket entries, and clear labeling of document download links.
Provide all filter and sort controls as keyboard-accessible form elements.
Link to case documents with link text that identifies the document type and date — "Order Granting Motion for Summary Judgment, filed March 15, 2025" — not "Download" or "PDF."
Accessible Online Court Filing Systems (E-Filing Systems)
E-filing systems — the portals through which attorneys and self-represented parties submit documents to the court — carry some of the most significant accessibility obligations in the court digital environment. A filing failure caused by an inaccessible e-filing system can result in missed deadlines with serious legal consequences.
The Self-Represented Litigant Problem
E-filing systems are designed primarily for attorneys who file frequently, are familiar with legal document requirements, and have technical staff supporting their practice. Self-represented litigants using these systems face a double accessibility challenge: the legal complexity of filing requirements and the technical inaccessibility of the interface.
Specific accessibility failures in e-filing systems that disproportionately affect self-represented litigants with disabilities:
Document type selection. Most e-filing systems require filers to select the appropriate document type from a lengthy hierarchical menu before uploading their document. These menus are frequently implemented as custom tree-view components that do not follow the ARIA treeitem keyboard interaction pattern — the arrow key navigation between options, the Enter key to expand nested categories, the Escape key to collapse — resulting in a menu that is navigable by mouse but not by keyboard.
PDF upload and format validation. Most e-filing systems accept only PDF documents. The file upload component, the PDF validation feedback (file size limits, page limits, format requirements), and the validation error messages must all be accessible. When a submitted PDF is rejected for technical reasons, that rejection must be communicated to screen reader users — not just displayed as a visual error state.
Electronic signature components. Many e-filing systems include an electronic signature or certification step — a checkbox or acknowledgment that the filer certifies the document's accuracy. This component must be keyboard accessible and must communicate its checked/unchecked state to screen readers.
Fee payment integration. E-filing systems frequently include a fee payment step for filing fees. The payment integration carries all standard payment portal accessibility requirements — labeled fields, keyboard operability, accessible error handling, accessible confirmation.
Filing confirmation and receipt. The confirmation that a filing was successfully submitted — including a case number, filing timestamp, and confirmation number — must be accessible and announced to screen readers. A successful filing that produces a visual confirmation that is not announced leaves screen reader users uncertain whether their filing was completed.
Courthouse Drop Box and Alternative Filing
For filers who cannot use the e-filing system due to its accessibility failures, accessible alternative filing methods must be available. This is not an invitation to keep inaccessible systems in place — it is a required interim measure while the system is being remediated. The alternative filing pathway should be documented on the e-filing portal and clearly communicated to users who encounter barriers.
Accessible Court Payment Portals (Fines and Fees)
Court fine and fee payment portals — for traffic citations, court costs, criminal fines, and civil filing fees — are among the highest-volume transactional systems courts operate. Residents frequently access these systems once, under time pressure, with financial consequences for payment failure.
Traffic citation payment portals are particularly common and particularly inaccessible. They are frequently operated by third-party vendors who serve the traffic citation processing market specifically and have minimal accessibility investment. The typical traffic citation payment portal has:
Unlabeled citation number and license plate number fields — the two primary lookup inputs — that announce nothing to screen readers on focus.
A CAPTCHA verification step that has no accessible audio alternative and no accessible bypass for users who cannot complete visual CAPTCHA challenges.
A payment method selection interface built with custom radio button components that do not follow keyboard interaction patterns.
A payment amount entry interface for partial payment options that is implemented as a custom input conditional on a radio selection — frequently requiring mouse interaction to activate.
Credit card number entry using a split field pattern (four separate four-digit inputs) that breaks keyboard navigation between segments and does not associate labels with individual fields.
A session timeout during payment processing that expires without announcement and terminates the transaction.
CAPTCHA and Accessibility
CAPTCHA systems deserve specific attention because they appear frequently in court and justice system portals — citation lookup, e-filing, record requests — and are among the most severely inaccessible components in common use.
Visual CAPTCHA systems that require recognizing distorted text or identifying objects in images are completely inaccessible to blind residents. Audio CAPTCHA alternatives are frequently unintelligible and are themselves inaccessible to deaf and hard-of-hearing residents. CAPTCHA systems that require clicking specific objects are inaccessible to residents with motor disabilities who cannot use a mouse precisely.
WCAG 1.1.1 requires that non-text content have a text alternative that serves an equivalent purpose. Most CAPTCHA implementations fail this criterion because the "equivalent purpose" — distinguishing human users from bots — cannot be achieved through a text alternative in the same way.
The accessible alternatives to CAPTCHA include: honeypot fields (hidden form fields that bots complete and humans do not see), time-based submission analysis, server-side rate limiting, and reCAPTCHA v3 which operates invisibly without user interaction. Google's reCAPTCHA v2 "I'm not a robot" checkbox has better accessibility than visual CAPTCHAs but still has documented issues with screen reader compatibility in some implementations.
For court portals that currently use visual CAPTCHA with no accessible alternative, replacing the CAPTCHA with an accessible alternative is an accessibility remediation priority.
Accessible Jury Management Systems
Jury service is a civic obligation for residents selected from voter rolls, DMV records, or other source lists. Jury management systems — the portals through which summoned jurors respond to their summons, request postponements or exemptions, and check in for jury duty — are mandatory interaction systems for the residents who receive them.
A resident with a disability who cannot use the jury management portal to request an accommodation or exemption faces a difficult choice: appear for jury duty without the accommodation they need, or risk being found in contempt for non-response. Neither outcome is acceptable.
Common Jury Portal Accessibility Failures
Juror number entry. The juror number field on jury response portals is typically the first field in the portal flow. It is frequently unlabeled or associated with a label that does not survive the portal's custom component implementation.
Response selection for postponement or exemption. The selection of a postponement request or exemption category is frequently implemented as a custom radio group with non-standard keyboard interaction. The reason for exemption — medical, financial hardship, caregiver responsibility, prior service — must be selectable by keyboard.
Supporting documentation upload. Many exemption requests require uploading supporting documentation — a physician's note, an employer letter, a prior service certificate. The document upload component must be keyboard accessible.
Date selection for postponement. Postponement requests typically require selecting a preferred date from a calendar — a date picker component that is among the most consistently inaccessible interactive elements in web applications. The jury portal date picker must accept direct text entry as an alternative to calendar interaction.
Accommodation request flow. Jurors with disabilities should be able to request accommodations — sign language interpretation, accessible seating, large print materials — through the jury portal. This flow must itself be accessible. A juror who is deaf requesting sign language interpretation should not be required to call a phone number to make that request.
Public Legal Information and Self-Help Resources
Courts serve a large population of residents who need help understanding the legal process, completing legal forms, and knowing their rights. Court self-help resources — online legal guides, interactive form assistants, law library databases — are a critical service for self-represented litigants and the general public.
Accessible Legal Form Completion Tools
Many courts offer interactive form completion tools that guide residents through completing standard legal forms — small claims complaints, protective order applications, name change petitions, eviction responses. These tools are complex multi-step workflows with significant accessibility requirements.
The specific challenges in legal form completion tools:
Conditional question flows. Many legal forms include conditional questions — if you answer "yes" to Question 3, Questions 4 and 5 appear; if you answer "no," they are skipped. These conditional questions must be implemented with accessible dynamic content patterns — the newly revealed questions must be announced to screen readers when they appear, and hidden questions must be actually hidden from the DOM (not just visually hidden) so screen readers do not navigate to them.
Legal terminology. Legal form fields frequently use legal terminology that is inaccessible to residents without legal training. Field labels like "plaintiff's domicile" or "respondent's address for service of process" do not communicate what information is being requested to a self-represented litigant without legal background. Accessible legal forms use plain-language labels with definitions available on demand.
Form instruction panels. Many legal form tools display instruction text alongside the form — guidance about what information to enter, what documents to bring to the hearing, what happens next. This instruction text must be associated with the relevant form section using ARIA and must be readable without visual spatial cues about which instruction corresponds to which form section.
Form progress and completion status. Multi-step form tools must communicate progress to screen reader users — which step they are on, how many steps remain, and what the current step requires — without relying on visual progress indicators alone.
Law Library Database Accessibility
Public law libraries and court law library databases provide access to statutes, case law, regulations, and legal reference materials. These databases — often operated by commercial legal research vendors like Westlaw, LexisNexis, or Fastcase — have varying levels of accessibility.
For court-operated law libraries that provide public access to legal research, the accessibility of the database interface is a Title II concern. A blind resident conducting pro se legal research should be able to use a court law library database with the same effectiveness as a sighted resident.
Agencies providing public access to commercial legal research databases should:
Request VPATs from the database vendors and evaluate them against WCAG 2.1 AA.
Identify the most critical functions for self-represented litigants — statute search, case citation lookup, form search — and confirm these functions are accessible.
Provide accessible alternative pathways — staff assistance with research requests — for residents who cannot use the database due to accessibility failures.
Accessible Video Proceedings and Remote Court Appearances
The rapid expansion of remote court appearances during and following the pandemic introduced video proceeding platforms as a mainstream component of court operations. The accessibility of these platforms — for both parties appearing remotely and members of the public observing proceedings — is a Title II obligation.
Caption Requirements for Video Proceedings
ADA Title II requires effective communication for participants with hearing impairments. In a physical courtroom, this is achieved through sign language interpreters and assistive listening devices. In a video proceeding, it requires captions.
Auto-generated captions from video platforms (Zoom, Microsoft Teams, Webex) are insufficient for formal court proceedings for the same reason they are insufficient for formal public meetings: accuracy rates of approximately 80 percent mean that material portions of proceedings — testimony, rulings, procedural instructions — may be misrepresented or missed. Legal proceedings require the level of accuracy achieved by CART — approximately 99 percent — because the content of proceedings is a legal record.
Courts conducting video proceedings should:
Use CART captioning for all hearings where any participant with a hearing impairment is present or requests it.
Confirm that the video proceeding platform supports CART integration before the hearing — CART providers typically join as panelists and type into the platform's caption display.
Publish captioned recordings of public proceedings where recordings are made available. Auto-captioned recordings must be reviewed and corrected before publication.
Provide participants with hearing impairments the information they need to request CART before their proceeding — this information must appear in the hearing notice and must be accessible.
Remote Appearance Platform Accessibility
For parties appearing remotely, the video platform itself must be accessible. Participants who are blind must be able to use the platform's controls — mute, camera, raise hand, chat — using keyboard navigation. Participants who rely on screen readers must receive accessible announcements of meeting events — "Jane Smith has joined the proceeding," "The judge has muted all participants."
Courts should evaluate the accessibility of any video platform before using it for mandatory court appearances. When a platform is found to have accessibility gaps, accessible alternative appearance options — phone audio participation — must be available.
Accessible Court Forms and Legal Documents
Courts produce an enormous volume of forms and legal documents: summons, complaints, orders, judgments, notices, instructions, informational brochures. Most of these are published as PDFs. Most of those PDFs are inaccessible.
The court document accessibility standard follows the same PDF accessibility requirements as any other government document — tagged structure, heading hierarchy, accessible tables, alternative text for signatures and seals used as images, correct reading order — with some additional considerations specific to legal documents.
Signature lines and certification blocks. Legal documents frequently include signature blocks with multiple underlines and labels. These are often formatted as images or as visual patterns that screen readers cannot interpret. Accessible signature blocks use properly labeled form fields (in fillable forms) or properly labeled text descriptions (in informational documents).
Official seals and court stamps. Court orders and official documents frequently include court seals, judge signatures, and court stamps. These images must have alternative text — not just "seal" or "signature" but "Superior Court of [County] official seal" and "Filed and stamped by the clerk on [date]" where the date is part of the document record.
Legal citation formatting. Judicial opinions, orders, and legal reference documents contain legal citations — case names, statute references, regulatory citations — that follow specific formatting conventions. These citations must be formatted in a way that screen readers can read coherently. Citation formats that rely on visual positioning — superscript footnote numbers, citation formatting that relies on column positioning — frequently produce garbled screen reader output.
Jury instructions. Jury instructions — the legal directions given to jurors to guide their deliberations — are publicly available documents in most jurisdictions. They are legal documents with significant reading accessibility implications. Accessible jury instructions use plain language, clear heading structure, numbered lists for sequential requirements, and reading levels that are appropriate for a jury of general community members.
The Court Accessibility Governance Program
Court accessibility governance follows the same foundational structure as any public agency program — baseline audit, risk-based prioritization, remediation, monitoring, documentation — with scope items specific to the justice system environment.
Audit scope for court digital services:
The audit scope for a court or justice agency must include: public case lookup system (table accessibility, document download, filter controls), e-filing portal (form accessibility, document upload, payment integration), fine and fee payment portal (CAPTCHA, payment form, session management), jury management portal (response form, date picker, accommodation request), court website content (form PDFs, legal guides, informational documents), and any video proceeding platforms used for mandatory appearances.
The ADA coordinator role in courts:
Courts are required under Title II to designate an ADA coordinator responsible for ensuring compliance with ADA requirements. The ADA coordinator's responsibilities should include oversight of digital accessibility — the court website, case management portals, and e-filing systems — alongside the more traditionally recognized responsibilities for physical accessibility and accommodations in proceedings.
The complaint intake process for court accessibility:
Courts must have a defined process for residents to report digital accessibility barriers. This process must be documented, the contact must be monitored, and requests for accessible alternatives must be fulfilled in a timely manner. A resident who cannot access an e-filing system must be able to request an accessible alternative before their filing deadline — not receive a response after the deadline has passed.
Vendor governance in court technology:
Courts rely heavily on specialized court technology vendors — case management system vendors, e-filing platform vendors, jury management system vendors, citation payment vendors. Many of these vendors serve the court market specifically and have limited accessibility investment. VPATs must be requested and evaluated for every court technology platform that provides public-facing digital services. Accessibility requirements must be written into vendor contracts at renewal.
Related:
How to Write Alt Text for Government Images, Charts, and Maps
How to Audit Your CMS for Accessibility
How to Train Your Government Staff on Accessibility
FAQ: ADA Accessibility for Courts and Justice Systems
Are courts required to comply with ADA Title II digital accessibility requirements?
Yes. Courts are state and local government entities fully covered by ADA Title II. The DOJ's 2024 final rule establishing WCAG 2.1 AA as the technical standard for digital accessibility applies to courts and justice agencies with the same force as any other Title II entity. The DOJ has brought enforcement actions against state and local courts for ADA violations including communication accessibility and program access failures. Digital accessibility — case lookup systems, e-filing portals, payment systems, jury management portals — is within the scope of these obligations.
What makes court digital accessibility failures more serious than other government accessibility failures?
Several factors elevate the severity of court accessibility failures. First, many court interactions are mandatory — residents cannot opt out of responding to a court summons, paying a court-ordered fine, or filing a required response in a case against them. Second, the consequences of failure are often legally significant — a missed filing deadline caused by an inaccessible e-filing system can result in default judgment, a missed jury response can result in contempt, and an inaccessible payment portal does not eliminate the fine or the penalty for non-payment. Third, courts serve a large population of self-represented litigants who rely on online systems as their primary access point to the legal process.
What are the most important accessibility requirements for online court filing systems?
E-filing systems must be fully keyboard accessible from document type selection through filing confirmation. Document upload components must be keyboard operable and must provide accessible validation feedback. Electronic signature and certification components must communicate state to screen readers. Fee payment integration must meet standard payment portal accessibility requirements. Filing confirmation must be accessible and announced to screen readers. For filers who cannot use the e-filing system due to accessibility failures, an accessible alternative filing pathway must be documented and available.
How should courts handle CAPTCHA in public portals?
Visual CAPTCHA systems are inaccessible to blind residents and to residents with certain motor disabilities. Courts using visual CAPTCHA in public-facing portals — case lookup, citation payment, e-filing — should replace CAPTCHA with accessible alternatives such as invisible reCAPTCHA v3, honeypot fields, or server-side rate limiting. Where CAPTCHA cannot be immediately replaced, an accessible bypass mechanism — such as a phone-based verification alternative — must be available. CAPTCHA accessibility failures are particularly significant in mandatory interaction systems where residents cannot opt out of completing the transaction.
What caption requirements apply to video court proceedings?
ADA Title II requires effective communication for participants with hearing impairments in court proceedings. For video proceedings, this means professional CART captioning — not auto-generated platform captions — when any participant with a hearing impairment is present or requests it. Auto-generated captions from video platforms achieve approximately 80 percent accuracy, which is insufficient for formal legal proceedings where the content is part of the legal record. Courts should confirm CART provider integration with their video platform before proceedings and include caption request instructions in hearing notices. Publicly available recordings of proceedings must be published with reviewed, accurate captions.
How should jury management portals accommodate jurors with disabilities?
Jury management portals must be fully keyboard accessible and screen reader compatible throughout the summons response flow — juror number entry, response selection, postponement date selection, exemption request, and supporting document upload. The accommodation request process — allowing jurors to request sign language interpretation, accessible seating, or other accommodations — must itself be accessible and must be available through the portal rather than requiring jurors to call a phone number. Date picker components for postponement selection must accept direct text entry as an alternative to calendar interaction, as calendar components are among the most consistently inaccessible interactive form elements.