This site should work if you use a screen reader, navigate by keyboard, need large text, or have low vision. If something doesn't work for you, email us and we'll fix it — and in the meantime we'll get you the information another way.
Our commitment
People using this site are often under stress, sometimes on an old phone, sometimes reading in a second language, sometimes with a disability. Accessibility isn't a compliance exercise for us; it's a condition of the site being any use at all. We design for that.
The standard we follow
We aim to meet Web Content Accessibility Guidelines (WCAG) 2.2, Level AA, published by the W3C. We also design toward the Section 508 standards and the plain-language principles in the Plain Writing Act, though as a private company we are not directly subject to either.
Conformance status
Partially conformant with WCAG 2.2 Level AA. "Partially conformant" means most of the site meets the standard but some content does not yet. We would rather say that honestly than claim full conformance we haven't verified.
What we've done
- Keyboard. Every interactive element is reachable and operable by keyboard, with a visible focus indicator that meets contrast requirements. No keyboard traps.
- Screen readers. Semantic HTML throughout, one
h1per page and a logical heading order, labels tied to every form field, and descriptive text alternatives for every chart and diagram. - Charts. Every visualization carries a text description conveying the same information, and the key figures also appear as text in the surrounding paragraphs. No information is available only as a graphic.
- Colour. Body text meets a contrast ratio of at least 4.5:1 and large text at least 3:1. Colour is never the only way we convey meaning — status is always accompanied by a word, and chart segments are labelled with numbers in the legend.
- Zoom and reflow. The site works at 200% zoom and reflows to a 320px viewport without horizontal scrolling.
- Motion. We honour
prefers-reduced-motionand disable transitions for anyone who has asked their system to reduce animation. Nothing auto-plays, flashes, or moves without user action. - Timing. No time limits on reading or completing forms.
- Errors. Form errors are described in text, tied to the field programmatically, and explain how to fix the problem.
Language and plain writing
Accessibility includes being understandable. We write short sentences, avoid idioms that don't translate, define legal and immigration terms the first time we use them, and explain every statistic in words as well as numbers. The site is available in English and Spanish, and the Spanish version is written by a human translator rather than generated automatically. If a page reads as confusing or condescending, that's a bug — please report it.
Tested with
- NVDA with Firefox and Chrome on Windows
- VoiceOver with Safari on macOS and iOS
- TalkBack with Chrome on Android
- Keyboard-only navigation across all browsers
- Browser zoom to 400% and OS-level text scaling
- Windows High Contrast Mode and forced-colors mode
Tell us about a problem
If you hit a barrier, please tell us. You do not need to know the technical term for what went wrong — "I can't read the chart with my screen reader" is a perfect bug report.
You can also email info@uscasestatus.com or write to Texas, USA.
We acknowledge every report within 2 business days and aim to resolve or provide a workaround within 10 business days. If a fix will take longer, we will tell you why and give you a date.
Alternative ways to get the information
If any part of the site is unusable for you, email info@uscasestatus.com with your receipt number and we will send the same information as plain text or in another format you can use, at no charge. You should never have to fight the interface to find out about your own case.
Review schedule
We review this statement and re-test the site at least every six months, and after any significant redesign.