Policy

Accessibility statement

PainMap treats accessibility as part of the product: visualizations need table equivalents, maps need search paths, and dynamic updates need programmatic status messages.

  • The place search is intended as the keyboard and screen-reader equivalent to the map.
  • Charts and rankings include table equivalents for inspection and reuse.
  • Loading, selection, and search-result updates use live status regions where practical.
  • The site respects reduced-motion preferences for non-essential transitions.