Accessibility
Accessibility Statement
Supreme Court Case Tracker is designed to make public court information easier to follow. Accessibility is part of the launch bar, not a post-launch extra, and this statement describes the current target, known limitations, and feedback path.
Current target
The current target is conformance with WCAG 2.2 AA for the primary user journey: homepage, case list, case detail, feed surfaces, and policy pages. Accessibility checks are expected to remain part of design review, testing, and release validation.
What we are doing now
- Semantic HTML and keyboard-accessible navigation across core layouts and case browsing surfaces.
- Color contrast and focus states intended to support WCAG 2.2 AA-level reading and interaction patterns.
- Screen-reader-friendly labels for navigation, search, filters, and data-rich case detail sections where practical.
- Responsive layouts that remain usable on mobile, tablet, and desktop widths without requiring horizontal scrolling for the main experience.
Known limitations
- Third-party source documents and PDFs may not be fully accessible, because they are hosted by external providers outside this project’s control.
- AI-generated summaries and dynamically changing analysis blocks may occasionally need additional labeling refinement as features evolve.
- Launch-period regressions are possible when upstream data or document structures change quickly during major opinion releases.
Feedback
If you encounter an accessibility barrier, include the page URL, the assistive technology or browser you were using, and a short description of the problem when you report it.
The preferred contact path is the project repository issue tracker or the maintainer contact channel published with the project. We treat reports affecting the core case-browsing flow as launch-bar issues.