This wiki has been archived and is now read-only.


From Digital Publishing Interest Group
Jump to: navigation, search

Story: I as a blind or vision impaired student need structured and rich descriptions for infographics and other information rich images I find in STEM textbooks

Descriptions for infographics and other STEM related images require more than textual descriptions. They may need HTML tables, lists and links. This is the use case for aria-describedby and longdesc.

Story: I as an author, context remixer or accessibility specialist, need to be able to easily find and download images and their associated descriptions. I need an efficient way to keep the images and their descriptions together in my file system

An advantage of longdesc and aria-describedat is that they support rich and structured descriptions as described above. However, the descriptions are not encapsulated within the image and thus may get separated, which makes it harder to share and reuse image descriptions.

Both of these stories need the <desc> element in SVG to support rich HTML markup. This markup needs to be accessible to assistive technology.
[1] http://diagramcenter.org/standards-and-practices/content-model.html
Always uses one of the predefined values PUBLISHERS-ALL, PUBLISHERS-STEM, USERS-ALL, USERS-A11Y, RETAILERS. New values will be added to this space as they are needed.
Ranking will be done as a separate activity later. For now, leave this field as 'TBD'
Optional, links to other entries in the corpus
Relevant W3C group(s)/specification(s)
Where the target WG/spec is obvious, specify it
External relevant group(s)/specification(s)
Where there are external groups/specifications that address on this problem in whole or part
Any additional info (clarifications, etc)
Submitted by
name of author of the use case
Always uses one of the values NEW | REJECTED | ACCEPTED