- From: Birkir Gunnarsson <birkir.gunnarsson@deque.com>
- Date: Mon, 31 Aug 2015 06:49:12 -0400
- To: Matt King <a11ythinker@gmail.com>
- Cc: Richard Schwerdtfeger <schwer@us.ibm.com>, faulkner steve <faulkner.steve@gmail.com>, public-svg-a11y@w3.org, "WAI Protocols & Formats" <public-pfwg@w3.org>, HTML A11Y TF Public <public-html-a11y@w3.org>
An additional thought: It says that the figure element should be referenced from the document text, but providing an accessible name for the figure is optional. In order to ensure usefulness and the ability of the assistive technology user to locate the figure, it needs to have an accessible name (consistent with how it is referenced in text). On 8/30/15, Matt King <a11ythinker@gmail.com> wrote: > Rich, > > > > When I first read this, I thought the word main was referring to the main > element. But then I noticed it says "main document". Later it uses the > phrase "main text". > > > > I am assuming that a figure could be used as part of an aside. Maybe it > would be worth considering some way of wording this that doesn't use "main > or clarifies what main means in this context. > > > > Matt King > > > > > > From: Richard Schwerdtfeger [mailto:schwer@us.ibm.com] > Sent: Sunday, August 30, 2015 4:44 PM > 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> > 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 > <http://rawgit.com/w3c/aria/master/aria/aria.html#dfn-assistive-technologies >> SHOULD enable users to quickly navigate to figures. Mainstream user > agents <http://rawgit.com/w3c/aria/master/aria/aria.html#dfn-user-agent> > 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 > >
Received on Monday, 31 August 2015 10:49:41 UTC