Perceivable → Text Alternatives → MAP-1
Map Content Text Alternative
WCAG Requirement
Interactive maps that convey geographic information must provide a text-based alternative — such as a data table, downloadable dataset, or text summary — that gives users equivalent access to the spatial data without requiring visual interpretation of the map.
Experience Builder Notes
EB apps rarely include data tables alongside maps. The Table widget can display the same feature layer data that the Map widget shows. Add a Table widget configured to the same data source and place it in an accessible location (e.g., a collapsible panel or tab).
Map & GIS Considerations
This is the single most impactful accessibility requirement for any GIS application. A map without a text alternative is like an image without alt text — it completely excludes users who cannot see or interpret the visual display. The alternative does not need to replicate every visual detail, but must convey the same information and enable the same decisions. For EB apps, the Table widget is the simplest implementation — configure it with the same data source as the Map widget.
Sufficient Techniques
- ✓Add a Table widget displaying the same data as the map
- ✓Provide a 'Download data' link for the underlying feature layer
- ✓Include a text summary describing key spatial patterns
- ✓Use the List widget as an alternative view of map features
Common Failures in EB Apps
- ✗Map is the only way to access the geographic data
- ✗No table, list, or text equivalent provided
- ✗Data download requires GIS software to open
This is an AuditEB map-specific criterion informed by WCAG principles. View references
Have questions about MAP-1?
Ask our AI assistant about this criterion, remediation strategies, or how it applies to your EB app.
Ask About MAP-1