Commitment
Accessibility
Last reviewed June 2026
This archive documents how campuses communicate in emergencies. It is a resource for reading and research, not something anyone should need in the middle of one. A project about clear communication should itself be easy to use, so we treat accessibility as part of the work, not an afterthought. If something gets in your way, please tell us.
What we aim for
We target the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA as our baseline, and we test the experience the way real people use it: with a keyboard, a screen reader, and reduced-motion settings turned on.
What's built in
- Full keyboard support. Every interactive control is reachable and operable by keyboard, with a visible focus ring and a “skip to content” link.
- Semantic structure. Real landmarks (header, main, footer), meaningful headings, and ARIA live regions that announce search results and status changes.
- Respects reduced motion. If your system requests reduced motion, animations are turned off; the immersive Experience also has its own reduce-motion toggle.
- Readable contrast. Text colors meet AA contrast in both light and dark themes, and the site honors your system light/dark preference.
- Never color alone. Alert lifecycle, resolution status, and source quality are always carried by text or icons, not color by itself.
- Generous targets. Touch targets meet the 44×44px minimum, and the layout reflows cleanly from phone to desktop.
Still improving
No site is ever “done” on accessibility, and neither is this one. Some areas, like dense data tables, the immersive Experience, and very long pages, are where we focus ongoing work. We'd rather know about a barrier than assume there isn't one.
Report a problem
If any part of this site is hard to use with assistive technology, please send a note through the contact form. Tell us the page, what you were trying to do, and the tool you were using; we'll do our best to fix it quickly.