Fw: Action-1715: figure role and Action 1708

I am reading the minutes of the September 3, 2015 ARIA Caucus and it
indicated that I had not created proposed text for the Figure Role (I am
re-forwarding the email I had sent to the list). I did in fact do this but
I am waiting to discuss it with Steve Faulkner who was out on vacation.
Also, reading the meeting minutes I want to tell you that it the SVG
accessibility task force did not state that the content within a Figure had
to be interactive. It may however. There was quite a bit of discussion on
the figure role.

I did propose draft text for the figure role but I am waiting to discuss
this we Steve. Steve thought that he would also need a figcaption role and
I wanted to discuss that with him. The proposal is not formal until I have
had a chance to discuss it with Steve. We need to ensure that the role
satisfies use cases for both HTML and SVG.

Unlike role="img" the descendants of figure *cannot* be assumed to be
presentational.

I hope I will be able to speak with Steve before Thursday's meeting. This
week is quite full.

Cheers,

Rich


Rich Schwerdtfeger
----- Forwarded by Richard Schwerdtfeger/Austin/IBM on 09/08/2015 07:17 PM
-----

From:	Richard Schwerdtfeger/Austin/IBM@IBMUS
To:	"faulkner steve" <faulkner.steve@gmail.com>
Cc:	public-svg-a11y@w3.org, "WAI Protocols & Formats"
            <public-pfwg@w3.org>, "HTML A11Y TF Public"
            <public-html-a11y@w3.org>
Date:	08/30/2015 06:46 PM
Subject:	Action-1715: figure role



Hi Steve,

I have an action to get with you to get agreement on on a new ARIA Figure
role. We need this for SVG Accessibility as we need a mechanism to isolate
figures that could be pulled into a list of figures by assistive
technologies. Since we are doing this for ARIA and SVG  we would also like
to reuse it for HTML. Please look at the following text and let me know if
this definition would be sufficient so that HTML could use this role as the
default native host language semantics for the figure role.


figure
      A perceivable section of content which supports the main document,
      and should be easily locatable regardless of its position in the
      layout. A figure may contain a graphical document, an image, or other
      content such as code snippets or example text. A figure should be
      referenced from the main text but does not need to be displayed
      directly where it is referenced.

      A figure MAY have an associate label or caption, or an associated
      description.

      Assistive technologies SHOULD enable users to quickly navigate to
      figures. Mainstream user agents MAY enable users to quickly navigate
      to figures.



The figure role would be a subclass of role section.

Name From: Author
Accessible Name Required: False

Cheers,
Rich

      Rich Schwerdtfeger