Let's Make Maps Widely Accessible
summary
A prototype pulls an NYC DOT Excel of ~200 APS locations and plots them with the Google Maps JavaScript API; the default SDK leaves markers unreachable by keyboard, so clustering reduces interactive targets to clusters reduced to ~10 keyboard stops, a synchronized data table shows nearest signals by distance, ARIA roles and tabindex + onfocus/onblur reveal tooltips, access keys and switch-access controls provide alternate input, street‑view images plus cognitive image descriptions are explored, and a Google issue (91 stars) raises priority for platform fixes.
AI-written summary · about
chapters (27)
- 0:00Introduction
- 4:10GIS Technologies
- 5:45First Exposure
- 6:12New York City
- 6:30Accessible Pedestrian Signal
- 7:32Accessible crosswalks
- 7:56Accessing the data
- 8:46Visualizing the data
- 9:25Building on your own
- 9:50Demo
- 13:37Documentation
- 15:01ArcGIS
- 15:31OpenStreetMap
- 16:05Map Accessibility
- 17:19Clusters
- 20:30Data Table
- 22:26View Data
- 28:06Visual Controls
- 29:34Google Maps
- 29:47HFF
- 30:17North Carolina
- 30:39New York
- 30:57Google
- 32:41Call to Action
- 35:07ESRI
- 38:02Questions
- 40:39Challenges
related talks
12mBuilding Accessible Maps and Navigation
22mA Journey Towards More Accessible Maps
15mBuilding Accessible Maps and Navigation
16mAdvanced Map Techniques (en)
32mBetter Accessibility with JavaScript
49mSaving the world with JavaScript: A Data Visualization story
01h 34mBuild a Web Map with Open Source Tools
12m"Look! A Map"