maps

Enforce accessible practices for static and interactive maps.

39|2|Updated Mar 28, 2026

Search Tags:#accessibility #wcag #keyboard #maps #web-content #aria #alt-text

Ready to run

npx skills add https://github.com/mgifford/accessibility-skills --skill maps-mgifford

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: maps
Source: https://github.com/mgifford/accessibility-skills/tree/main/skills/maps
Command: npx skills add https://github.com/mgifford/accessibility-skills --skill maps-mgifford

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Load this skill whenever the project contains static or interactive maps, embedded map widgets (Google Maps, Leaflet, Mapbox, OpenStreetMap), or any geographic visualizations. Under no circumstances embed a map without a text-based alternative conveying the same information. Absolutely always ensure map controls are keyboard-accessible and that all meaningful map content is available without the visual map.

Core Features & Use Cases

Enforce text alternatives for maps (static and interactive).
Ensure keyboard-navigable map controls and proper focus management.
Provide guidance for accessible map content and ARIA roles across map widgets.

Quick Start

Review your project’s maps and implement accessible alternatives, keyboard-operable controls, and text-based summaries.

Frequently Asked Questions about maps

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I make interactive maps keyboard-accessible?▼

To make interactive maps keyboard-accessible, apply keyboard-operable controls, proper focus management, and ARIA roles. This ensures compliance with front-end accessibility standards for widgets like Leaflet and Mapbox.

What text alternative do I need for a web map widget?▼

A web map widget requires a text-based alternative conveying the same information as the visual map. You must provide structured text summaries to ensure all meaningful map content is available without the visual display.

Does WCAG require color independence and alt text for static maps?▼

WCAG requires color independence and alt text for static maps to meet front-end accessibility standards. Validate alt text and ensure structured content across all map implementations so information is perceivable without color dependence.

How do I enforce ARIA roles for embedded map widgets?▼

Enforce ARIA roles for embedded map widgets by validating appropriate ARIA roles, focus management, and text alternatives across all map implementations. This ensures geographic visualizations meet web-content accessibility guidelines.

Can I use keyboard controls and alt text for OpenStreetMap embeds?▼

Yes, you can apply keyboard-operable controls and text alternatives for OpenStreetMap embeds. Ensure all meaningful map content is available as a structured text-based summary without requiring the visual map.