Skip to main content

Accessibility

Make the core workflow perceivable, operable, and understandable.

We are improving the public site toward WCAG 2.2 AA practices. This statement describes current implementation and known gaps; it is not a certification or claim that every page and third-party surface fully conforms.

Practices currently in the code and test gate

  • A global skip link and semantic page landmarks on the primary marketing shell.
  • Visible keyboard focus styles and keyboard-operable primary navigation, menus, dialogs, and forms.
  • Accessible names and state attributes on the interactive components covered by the automated component suite.
  • Reduced-motion handling in major Motion-based surfaces, plus non-WebGL fallbacks for the public storm theater.
  • Automated axe smoke tests and targeted component tests run by the repository verification script.

Known limitations

  • The map visualization is not a complete keyboard-equivalent geospatial experience; an accessible event summary and fallback list provide core record access.
  • Automated checks cover selected components and common rules. They do not establish whole-site WCAG conformance or replace testing with assistive-technology users.
  • Third-party Stripe, mapping, provider, and embedded experiences have accessibility behavior outside this repository's direct control.
  • Complex animated and canvas surfaces may still contain motion or visual density that some users find difficult despite reduced-motion paths.

Report a barrier

Email hello@ai-storms.com with the page, task, browser, device, and assistive technology if you can provide them. We will investigate and share a practical workaround or repair status when available.