RE: ARIA roles for graphics

From: chaals@yandex-team.ru [mailto:chaals@yandex-team.ru] 
Sent: 26 May 2015 00:19

Some quick feedback…

 

21.05.2015, 11:38, "Léonie Watson" <lwatson@paciellogroup.com <mailto:lwatson@paciellogroup.com> >:

From: Amelia Bellamy-Royds [mailto:amelia.bellamy.royds@gmail.com <mailto:amelia.bellamy.royds@gmail.com> ] 
Sent: 21 May 2015 03:44

The following roles I think would cover most basic graphics.  In combination with proper use of other ARIA attributes (such as labelled by and flow to) they could greatly enhance the ability to describe infographics and labelled diagrams.

* graphic

* Complex visual content with a meaningful structure to it.  The component parts may be interactive.
* A large graphic can contain component graphics so long as they still meet the criteria.
* This would be the default role for <svg> and <g> elements that meet the criteria for inclusion in the accessibility tree.
* The fallback role would either be group or region depending on how significant the graphic is.

LJW: Conceptually this makes sense, but I think it might be difficult to distinguish between an image and a graphic in a practical sense. Throwing some alternative name suggestions out there… “datachart”, “infographic”, “structuredimg”, or “compleximg”?

 

CMN: compoundImage? Trying to think through examples:

 

 - A shape that has one interactive child.

 - A diamond - binary decision in a flowchart, which has 3 bits of text, one inbound arc and two outbound arcs

 - A cartoon frame, which has several characters, a caption, and a couple of speech bubbles in it

 - A cartoon strip, part of a series of strips that together make a single narrative

 - A 22-node static graph of a social network

 - A skeumorphic user interface for video editing software

 

+1 to compoundImage.

 

Léonie.