Open frastlin opened 3 months ago
Here are passing non-visual map examples, let me know if you'd like some examples of failing maps as well:
Although this level of text description is rare, let’s try and hit all the elements of spatial knowledge for a few states:
Here is an Audiom map of COVID Cases over the U.S. showing interactive alternate text. Here is a video showing the Audiom interactive alternate text usage.
Here is a video requiring headphones showing a campus map with interactive alternate text as well.
If we are solely limiting discussion to what we should required in alt text for maps, below are several thoughts:
Alt text should follow the guiding principle for any image: If I removed the map and just had the information in the document and the alt text, would all the critical information being communicated by that map still be fully available? What critical information would I lose if I couldn’t perceive the map? If there is information loss without the image, there may be more work to do to ensure that the map is accessible to everyone.
Where possible, an additional text alternative for all data and information is provided
Where a text alternative to full describe map content and context is not possible, include, if possible, an alternative means to access content such as a POC, link to google map, or other interactive means that will provide an accessible alternative
We also had a suggestion to split out minimum requirements based on the type of map. Some types of maps (in more plain language) are:
Hello, The above response seems to reiterate the current best practice presented by places like the state of Minnesota. Current best practice is not systematic, quantitative, rigorous, reproducible, or evidence based. The current best practice is harmful to people depending on the alternate text for viewing maps because it is not an “equivalent” access to the content. Blind people are calling for these practices to be updated to something that can allow for professional blind cartographers to exist which the current best practice does not allow. The proposed test is quantitative, rigorous, reproducible, systematic, and based on decades of research in the cartographic community.
Maps can be categorized into thematic or referential, but the one thing they all have in common are geometries. There are thousands of other types of maps than those listed above, including utility, service outage, emergency exit, oceanographic, Steller, fictional, multivariate, time-sequenced, etc. and it’s important to have guidance that encompasses all map types. Having separate rules for each type of map would make the rules too lengthy. All maps convey geometries, so I'm arguing that geometries should be the foundation for any accessible map. There needs to be clear guidance for conveying geometries in alternate text, and that’s what this proposed test provides.
There seems to be two underlying misguided assumptions in the current best practice: (1) alt-text is severely limited in what spatial content it can convey; and (2) Spatial content is inherently visual. The interactive alt-text method presented by maps like this Eclipse map shows it’s possible to convey detailed landmark, route, and survey knowledge. This includes distance, direction, shape, size, orientation, and the general layout of all points, polygons, and lines on a map. This data can be conveyed at the same fidelity as the visual map. It only takes a few minutes to generate this level of detail from a geojson file. Not only is it possible to convey this level of detail, but it’s fast and easy. This method of interactive alt-text is just one way to convey this information, I’m sure there are numerous other ways to convey this level of detail as well. There’s nothing visual about geojson. If a fraction of effort was put into text representation of geometries as is put into the visual representation of geometries, I’m sure there would be a number of easy ways to convey this information. As it stands, we have both the interactive alt-text method above, and the long-form alt-text described in post two.
The blind and low vision community is unhappy with the current alternate text practices for representing maps. Only conveying “summaries”, “critical information”, “author’s intention”, and “Where possible”, is keeping blind people from independently participating in professions requiring the use of digital geographic maps. The “minimum requirements” of the alt text need to be at the level so the alternate text user can use the map for the “equivalent purpose” as their sighted counterparts. This does require a paradigm shift away from only considering alternate text created by hand and static alt-text. On July 7, 2024, the National Federation of the Blind passed a resolution calling for maps to convey the level of detail outlined in this issue. This resolution represents the voice of over 50,000 blind people. Over 50,000 blind people are saying the current method of alt-text on maps is inadequate.
The authors of the WCAG were clear that the alternative text representation needs to show an “equivalent purpose” to the visual representation. This means that blind people should be able to answer any question a sighted person can answer about a map. Using this interactive alt-text eclipse map, or systematic long-form alt-text as described in comment two, blind people can.
I just wanted to add a comment about this statement (from the original post at the top of this thread):
For thematic maps showing more than 3 categories of colors, it’s physically impossible to comply with [SC 1.4.11] as written. Recommended compliance criteria should be as high of contrast as possible color scheme, coupled with patterns to distinguish between the values.
So, I helped write SC 1.4.11, and there is a creative way to solve this contrast problem. I call it the oreo method, or the outline method. Instead of having map items touch each other directly, you can outline each item with one of the following:
The outline can be white, or black or pick whatever color works best for your color scheme. When things get super complex, you can even go with what I call the "oreo outline"...which is a triple line outline...where the online is a black outline (black cookie) surrounded by a white outline ( white frosting), surrounded by a 2nd black outline (2nd black cookie). With the oreo cookie technique...you can distinguish any item at 3 to 1...because you controlled the background. If black doesn't work as the cookie layer...you could flip it to white cookie, black frosting, white cookie.
Overview
Currently, digital geographic maps are evaluated using section 6. Images, but digital geographic maps are too complicated to be combined under images without explicit evaluation criteria. Digital geographic maps are complex multicomponent elements that require an entire evaluation of their own, above the general website evaluation. In particular, WCAG 1.1:Non-text content requires a more nuanced definition. Having requirements specific to digital geographic maps will reduce ambiguity of what to evaluate on geographic maps, and ensure evaluation criteria are clear and consistent across results so that the section 508 standards are applied correctly to this complex component.
An Accessibility Conformance Report was done on the top 11 digital map tools, and the below criteria are the most common failures.
Section 1.1.1:Non-Text Content Applied to Maps
Section 1.1.1:Non-Text Content states: “All non-text content that is presented to the user has a text alternative that serves the equivalent purpose”. The problem is that “equivalent purpose” is somewhat ambiguous and is often misinterpreted. In academic literature the framework of landmark, route, and survey knowledge acquisition is used, and that is what I propose be the refined framework for section 1.1.1:Non-Text Content applied to digital geographic maps.
Traditionally, the practice of making maps accessible is to step back and look at the “point” of the map. Is the alternative that’s presented conveying the primary objective of the map? This practice can be observed by blog posts written by prominent digital accessibility experts and documentation by government agencies: https://www.tpgi.com/accessible-digital-map-experiences/ https://mn.gov/mnit/about-mnit/accessibility/maps/static.jsp https://github.com/DEFRA/design-standards/blob/master/Maps.md
This practice is not compliant with section 1.1.1, as following this method only has the “main purpose” conveyed when the criteria states “equivalent purpose”. If the “main purpose” of a university campus map is to show roads on campus, it does not help the map user needing to manage garbage cans on campus. A visual campus map would have garbage cans, but since they’re not the “main purpose”, the map user accessing the text alternative would not be able to use the map for the “equivalent purpose” that the original map could have been used for. Using the survey knowledge framework would facilitate this “equivalent purpose” though.
Siegel et al. published a seminal work in 1975, titled “The development of spatial representations of large-scale environments” defining the framework of landmark, route, and survey knowledge for evaluating spatial knowledge acquisition from geographic maps. This framework has subsequently been used in numerous studies across maps in visual, auditory, and tactile modalities including: https://cartographicperspectives.org/index.php/journal/article/view/cp75-ishikawa-takahashi/html https://www.tandfonline.com/doi/full/10.1080/13875868.2021.1969401?casa_tok https://www.sciencedirect.com/science/article/pii/S0272494407000734 https://icad2022.icad.org/wp-content/uploads/2022/06/ICAD2022_27.pdf https://www.frontiersin.org/articles/10.3389/fnhum.2014.00223/full https://www.sciencedirect.com/science/article/pii/S0272494406000594
This framework is rigorous, quantifiable, and easy to use.
Definitions and criteria to evaluate each element of landmark, route, and survey knowledge:
Using this framework of spatial knowledge allows a quantitative evaluation of the spatial information in a map. Additionally, there needs to be full access to the numeric or other information that may be overlayed on the geographic features. If a text alternative is missing any of these elements, it does not serve the “equivalent purpose” of a map, and is not section 508 compliant.
Section 1.4.11:Non-text Contrast Applied to Maps
1.4.11:Non-text Contrast states: “The visual presentation of the following have a contrast ratio of at least 3:1 against adjacent color(s): User Interface Components; Visual information required to identify user interface components and states, except for inactive components or where the appearance of the component is determined by the user agent and not modified by the author; Graphical Objects; Parts of graphics required to understand the content, except when a particular presentation of graphics is essential to the information being conveyed.” Unfortunately, for thematic maps showing more than 3 categories of colors, it’s physically impossible to comply with this criteria as written. Recommended compliance criteria should be as high of contrast as possible color scheme, coupled with patterns to distinguish between the values. The pattern criteria works for colorblind users, and the high contrast colors work for low-vision users.
Section 2.1.1 Keyboard Applied to a Map
Section 2.1.1 Keyboard states: “All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints.” This includes keyboard accessibility for all features (e.g., points, polygons, and lines) on the map. For map creation tools, drawing with the mouse or touchscreen may be dependent on a path of the user’s movement, but it’s possible to place points and vertices with the keyboard.
Proposed Content for Section 508 ICT Testing Baseline: 25. Geographic Maps
Accessibility Requirements
Test Method Rationale
Limitations, Assumptions, Exceptions
25.A Test Procedure for Maps
Baseline Test ID: 25.A-Maps
Identify Content
Identify a collection of points, polygons, and lines and possible associated controls that comprise a map, whether it’s an image, interactive, in a document, and or in an iFrame.
Test Instructions
Test Results
If any of the above checks fail, then Baseline Test 25.A- Maps fails.
Advisory: Tips for streamlined test processes
WCAG 2.2 Techniques
The following sufficient techniques and/or common failures were considered when developing this test procedure for this baseline requirement: