Accessibility in product work
Accessibility requirements are being added to design review, implementation, and release checks rather than treated as a one-time certification exercise.
Accessibility
Court technology should be usable by everyone it serves.
Court Nox is working toward WCAG 2.2 Level AA across public juror services and authenticated court workflows. This statement describes our current status, the work underway, and how to request help.
Our commitment
A measurable standard, not a badge.
Our product target is the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. WCAG 2.2 includes WCAG 2.1 requirements and adds criteria for focus, target size, dragging alternatives, consistent help, redundant entry, and accessible authentication.
Public-sector requirements vary by jurisdiction and procurement. We will map the applicable requirement during implementation and document what is supported, what needs remediation, and any available alternative.
Keyboard and visual access
Our review program covers keyboard operation, visible focus, logical headings, labels, contrast, zoom, reflow, and motion preferences.
Assistive technology testing
The planned test matrix includes current browser and screen-reader combinations across public juror, court staff, counsel, and kiosk workflows.
Documents and court output
Generated summons, worksheets, reports, and other court documents are included in the accessibility roadmap, not excluded from it.
Known limitations
Transparent while assessment is underway.
- Court Nox has not yet completed a comprehensive independent accessibility evaluation.
- Complex tables, jury-selection controls, document previews, signature interactions, and court-configured templates may contain barriers that have not yet been identified.
- A supported browser and assistive-technology compatibility matrix has not yet been formally published.
- Court-created content and uploaded files may vary in accessibility.
Technical information
- Technologies
- HTML, CSS, JavaScript, and WAI-ARIA where native HTML alone does not express the required interaction.
- Assessment approach
- Internal evaluation is beginning. Independent validation and a formal Accessibility Conformance Report are roadmap items.
- Review cadence
- This statement will be updated as testing establishes a supported environment matrix, confirmed limitations, and remediation status.