Accessibility

Accessibility statement

Last updated July 25, 2026

Report960 is committed to making our case-review workspace usable by every officer, supervisor, and civilian analyst — including those who rely on assistive technology. This page is maintained by Report960 to describe the accessibility practices we have implemented, known limitations we are actively working to resolve, and how to request accommodations.

1. Standard we target

We design and test Report960 against the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. We also align our practices with Section 508 of the U.S. Rehabilitation Act and California Government Code § 7405 so that agency IT reviewers have a familiar baseline. This is a conformance goal, not an independent certification.

2. What we've built in

  • Keyboard-first navigation. All primary actions — uploading a report, running analysis, editing narrative text, resolving issues, exporting — are reachable without a mouse. Focus indicators are visible on every interactive element.
  • Semantic structure. Pages use a single <main> landmark, hierarchical headings, and native form controls with associated labels so screen readers can announce structure and state accurately.
  • Accessible primitives. Dialogs, menus, comboboxes, and toasts are built on Radix UI, which ships with ARIA roles, focus management, and Escape-to-close behavior.
  • Color and contrast. Text and UI colors are drawn from a design-token palette engineered to meet WCAG AA contrast ratios in both light and dark modes. Status is never conveyed by color alone — icons, labels, and text descriptions always accompany it.
  • Motion and animation. Non-essential motion is minimal, and we honor the operating system's prefers-reduced-motion setting where animations do appear.
  • Zoom and reflow. Layouts reflow cleanly up to 200% browser zoom and 400% text zoom without loss of content or functionality on standard desktop breakpoints.
  • Screen reader announcements. Live regions announce analysis progress, save state, and validation errors so non-visual users receive the same feedback as sighted users.

3. Known limitations

We disclose known gaps openly so agencies can plan accommodations:

  • Uploaded PDFs and scanned documents. Report960 preserves the text you upload, but we cannot guarantee the accessibility of source PDFs produced outside the platform. Scanned images without an OCR text layer will not be readable by screen readers until re-processed.
  • Rich-text editor. The inline narrative editor supports keyboard editing and screen readers for text content, but some advanced formatting shortcuts are still being expanded to full ATAG parity.
  • Third-party embeds. Stripe's embedded checkout is provided by Stripe; its accessibility is governed by Stripe's accessibility statement.

4. Assistive technology we test with

Report960 is tested regularly against current versions of the following combinations. Other combinations generally work, but these are the ones we treat as blocking for release:

  • VoiceOver on macOS with Safari and Chrome
  • NVDA on Windows with Firefox and Chrome
  • VoiceOver on iOS with Safari
  • TalkBack on Android with Chrome
  • Keyboard-only navigation on all supported desktop browsers

5. Requesting an accommodation

If you encounter a barrier — or need Report960 provided in an alternate format for a specific review — contact us and we will work with you and your agency to resolve it. Please include the page or feature involved, the assistive technology and browser you are using, and a description of what you expected to happen.

Accessibility contact: accessibility@report960.com
General support: support@report960.com
Mailing address: Report960, Irvine, California

We aim to acknowledge accessibility requests within two business days and to provide a substantive response, workaround, or remediation timeline within ten business days.

6. Ongoing work

Accessibility is treated as a shipping requirement, not a phase. New features are reviewed against WCAG 2.1 AA before release, and we periodically re-audit shipped surfaces as browsers and assistive technologies evolve. We welcome feedback from agencies and individual officers — it directly shapes what we ship next.

7. Formal complaints

If you are unable to resolve an accessibility concern through the channels above, you may file a complaint with the U.S. Department of Justice under the Americans with Disabilities Act, or with the California Department of Rehabilitation. Nothing on this page limits any right you have under applicable law.

This page is maintained by Report960 to describe how the product works today. It is not legal advice and does not create any warranty. Questions? Email hello@report960.com.