You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
linkalis edited this page Feb 22, 2015
·
18 revisions
Map Accessibility Guidelines
Make accessibility a developer-side concern.
Accessible first! Consider accessibility from the beginning—don’t hack it on at the end.
Consider diverse users (including visually impaired users, second language learners, users with cognitive disabilities, users with physical or motor limitations, etc.). For more information and resources for serving diverse users, visit the separate links along the side of this page.
Offer both route and map options. Remember that people have different ways of orienting themselves and absorbing geographic information.
Don’t have the map be your only format for data display. Supplement with a table or list.
Use simple, high-contrast color schemes. Don’t use color alone to convey information (consider patterns, line widths, etc.). Red + green = BAD!
Use smaller words and bigger text, and highly legible typefaces.
Err on the side of too few layers (3-4 per map, usually). When in doubt, leave it out!
Display layer data in a way that's appropriate for the zoom level. Hide and display geographic details as appropriate.
Link your legend to your data (for example, via interactive mouseover, clickable popup, etc). Use good symbology to make your legend as unnecessary as possible.
Make legend clearly visible & expanded by default.