Svg comments

From Cognitive Accessibility Task Force

add suggestions here:

  • We see a shift in emphasis between how to encode content and the content. So for Coga images are important

as is using symbols to aid understanding :

   -Use clear symbols that can easily be seen and expanded
   -Use images understood by different users
   -In left to right languages place the image to the left of the text
   Or use images to make  structure clear
   -keep linking images simple and explanatory
   -use visual grouping to enable filtering of content without overwhelming
   Or   create charts and graphics to provide additional ways to reinforce important concepts
   However, graphics should be clear and easy to identify what is going on
   The ability to “read between the lines” of a text, graphic, or lecture may seem like an exercise in “common sense,” but it may create barriers for students with autism, who may not be able to readily discern the intended relevance of graphical data.

Clear explanations may reduce undue cognitive loads for all users.

  • It is helpful for understanding to have visual content highlighted when the explanation is read. So for example, when a section of a chart is discussed, and read at the same time, the correct section of the graphic should be highlighted. If you used aria-describedby to point to text that describes the section highlighted, the associated description would be highlighted with it (Visually see associations)
  • Representing the overlap in a venn diagram when a user cannot see or understand the meaning implied in the positioning of the over between the two circles. More complex cases may have multiple overlaps with 2 or more regions overlapping. Often the overlap is communicated with colour, however this assumes knowledge of how colours can be combined (e.g. a blue circle and a yellow circle overlapped to create a green region): http://upload.wikimedia.org/wikipedia/en/0/06/Venn-diagram-AB.svg
  • The for multi-modal interaction to aid with dyscalcula or use of "numberfree" attribute.
  • Other COGA issues such as non-litral or turning off distractions and extra features. Example: It is raining cats and docs: aria-nonliteral might be "it is raining hard"
  • Do we need a simple and straightforward "alt text" that is an alternative to the regular label text for cognitive.
  • Keys for communicating what a specific color may mean, for example this diagram http://wiki.gpii.net/w/Standardization_in_GPII uses color but does not say what the color means.
  • Ability to simplify a diagram by hiding nodes to show a simplified example with annotation. For example, on this diagram: http://wiki.gpii.net/w/Standardization_in_GPII a single chain of nodes could be rendered with everything else hidden to aid comprehension.

Plumbing Potential Features:

  • Media Query feature that says to expose features of a given importance level or higher
  • Need the ability to group sections of a diagram together with a defined keyboard navigation order
  • Ability to highlight content with their associated visual descriptions
  • Ability to annotate the importance level
  • Need alternative, alternative text for people with cognitive impairments
  • We need an aria-nonliteral attribute (takes a string). See the example above. (Note: Lisa, what do you want the user agent or author to do with this. e.g. if there was a media query that stated that non-literals are used instead ... render it some how)
  • We need less icons but make them bigger. ...?
  • We need to be able to pull in information about a picture that is pulled in from somewhere else. (To Do for Lisa to expand on this)
  • Ability to tie colors to semantic meaning?