Accessibility

We build to the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. That is the standard referenced by most US accessibility requirements, and it is a reasonable floor rather than a ceiling.

• Semantic HTML throughout, so screen readers encounter real headings, lists, and landmarks rather than generic containers.
• Visible focus indicators on every interactive element, so keyboard users can always see where they are.
• Full keyboard operability — the eligibility screener can be completed without a mouse.
• Colour contrast meeting AA ratios for body text and interface elements.
• Colour is never the only way information is conveyed; status is also carried by text and icons.
• Form controls have associated labels, and error and helper text is programmatically linked to its field.
• Reduced-motion preferences are respected; animation is suppressed when the system asks for it.
• Responsive layouts that work down to 320px and reflow rather than requiring horizontal scrolling.

The PDFs we prepare are tagged, which means a screen reader can navigate them by structure rather than reading a flat wall of text. Specifically:

• Headings, paragraphs, and the numbered paragraphs of a sworn affidavit are marked as such, so the numbering stays attached to the text it belongs to.
• Rules, box borders, and the fingerprint grid are marked as decorative, so they are skipped instead of being announced one by one.
• Every document carries its title and language, and viewers are told to announce the title rather than the filename — so you hear “Petition to Seal”, not “CE-2026-0417-final-v2.pdf”.
• Checkboxes announce whether they are selected, which matters most on the FDLE application where a single tick decides between sealing and expunction.
• Text that is visually abbreviated or set in capitals carries its full, correctly-cased form for reading aloud.

Stating these plainly is more useful than claiming conformance we have not verified. As of the last review:

• Combined packets — where several documents are merged into one file for printing — lose their tagging in the merge. Each document is also offered separately, and those individual files are fully tagged. If you use a screen reader, take the individual documents.
• We do not claim PDF/UA conformance. The documents have not been validated against a formal checker, and complex layouts such as the FDLE form's grid are tagged approximately rather than as true tables.
• Uploaded documents are your own files and cannot be made accessible by us. Where a scanned disposition is unreadable, we will read it to you.
• A full independent audit has not been commissioned. It should be, before launch.

If any part of this site prevents you from doing what you came to do, tell us and we will fix it — and in the meantime we will complete the task with you directly by phone or email so that the barrier does not cost you your relief.

support@caseeraser.com