Accessibility
This platform is built to be usable with a keyboard alone, with a screen reader, and at every required responsive width, checked continuously rather than as an afterthought.
What's tested
- Automated accessibility scans (axe-core) across every page and major workflow state, gating every change before it ships.
- Full keyboard-only workflows: search, selection, evidence review, and brief generation.
- Screen-reader-relevant structure: heading order, landmark regions, and labeled form controls.
- Responsive layouts at six required widths, from 320px mobile to 1440px desktop, with no horizontal overflow.
- Color is never the only way information is conveyed -- every percentile, badge, and status also has a text label.
Known limitations
The interactive map (Explore) is the one component with an inherent accessibility ceiling common to any map visualization -- every place it shows is also reachable through the accompanying searchable table and text-based place search, so no information is available only through the map.
Reporting an issue
If you encounter an accessibility barrier anywhere on this platform, please open an issue on GitHub describing what you were trying to do and what happened.