- From: Shawn Henry <shawn@w3.org>
- Date: Mon, 16 Jun 2014 11:04:35 -0500
- To: "McSorley, Jan" <jan.mcsorley@pearson.com>, Eric Eggert <ee@w3.org>, Andrew Arch <andrew.arch@gmail.com>, Helle Bjarnø <jor@servicestyrelsen.dk>
- CC: wai-eo-editors <wai-eo-editors@w3.org>
Hi Jan, Thanks for spending time on it! Here's the issue from Friday's telecon: * Andrew's comment: "Suggestion: consider adding a tip that 'alt' is primarily for screen reader users and those choosing not to display images, however as image complexity increases, cognitive load also increases and visible explanations of images are desirable." * Shawn edit suggestion: diff "visible explanations of images are desirable" -> visible textual information * Kevin: Rather than a simple tip, there might be a need for more explanation of the purpose and the usefulness of the provision of such information ... for example a complex graph in which text will include a summary of the key data points, etc * <Andrew> my example was weather forecasts - selecting city from a map vs a list of cites * <Andrew> comprehension of the presented information (rather than cognitive load) * Shawn: And rather than to use the term "cognitive load" we may discuss the fact that people process info differently and may also need onscreen text as well I think the idea that we wanted to get across is that alt is usually only used by screen reader users; however, especially with complex images, some sighted people (who would have difficulty gleaming info from the image) might need textual info for the image as well. So in some cases, it would be good to provide textual information about the image in the actual page (or linked), so that sighted people can see it, too. Minutes are at <http://www.w3.org/2014/06/13-eo-minutes> related pages: Images concepts: https://w3c.github.io/wai-tutorials/images/ Complex images: https://w3c.github.io/wai-tutorials/images/complex/ Images Tips: https://w3c.github.io/wai-tutorials/images/tips/ --- The related issue that Andrew brought up was the difficulty in understanding complex tables. <https://w3c.github.io/wai-tutorials/tables/multi-level/#split-up-multi-level-tables> says "This makes the information easier to understand by everyone and easier to code, too." and it's mentioned in <https://w3c.github.io/wai-tutorials/tables/tips/> I think the suggestion here was to explain a little more that it's hard for some (sighted) people to understand complex table structure. Andrew & Helle & Eric: Please chime in. :-) ~Shawn
Received on Monday, 16 June 2014 16:04:48 UTC