maps

# Maps Accessibility Skill > **Canonical source**: `examples/MAPS_ACCESSIBILITY_BEST_PRACTICES.md` in `mgifford/ACCESSIBILITY.md` > This skill is derived from that file. When in doubt, the example is authoritative. Apply these rules when implementing or reviewing any static or interactive map. **Only load this skill if the project contains maps.** --- ## Core Mandate No single text description works for every map. Start with the map's purpose and the tasks it supports, then provide accessible content and controls that preserve that purpose for people who cannot see, distinguish, point at, drag, zoom, or interpret the visual map. Keep the map and its structured alternative synchronized from the same data source. --- ## Severity Scale (this skill) | Level | Meaning | |---|---| | **Critical** | Essential location data has no accessible alternative | | **Serious** | Interactive map unreachable by keyboard; `role="application"` misused | | **Moderate** | Skip link missing; colour independence gap; popup focus not managed | | **Minor** | Missing `prefers-reduced-motion` for animations; legend incomplete | --- ## Classify the Map's Purpose First | Map purpose | Essential task | Common accessible presentation | |---|---|---| | Simple locator | Where one place is and how to reach it | Concise alt, address, landmark, directions, contact info | | Location directory | Find and compare services | Searchable list/table with names, addresses, distances, categories | | Route/wayfi...