- From: Joanmarie Diggs <jdiggs@igalia.com>
- Date: Wed, 14 Oct 2015 17:59:42 -0400
- To: Fred Esch <fesch@us.ibm.com>
- Cc: public-pfwg@w3.org
Hi Fred. I've made this change and also added the text you provided for the new 'graphical document' glossary entry: https://rawgit.com/w3c/aria/action-1714/aria/aria.html#figure Thanks! --joanie On 10/08/2015 02:46 PM, Fred Esch wrote: > Joanie, > > > > I would move the first sentence of the last paragraph to be the second > sentence of the first paragraph. Like this: > > figure (role) > A perceivable _section_ > <https://rawgit.com/w3c/aria/action-1714/aria/aria.html#section> of > content that typically contains a graphical document, images, code > snippets, or example text. The parts of a figure *may* be user-navigable. > > > Authors *should* provide a reference to the figure from the main text, > but the figure need not be displayed at the same location as the > referencing element. Authors *may* reference text serving as a caption > using _aria-describedby_ > <https://rawgit.com/w3c/aria/action-1714/aria/aria.html#aria-describedby> and > text serving as a label using _aria-labelledby_ > <https://rawgit.com/w3c/aria/action-1714/aria/aria.html#aria-labelledby>. > > In addition, assistive technologies > <https://rawgit.com/w3c/aria/action-1714/aria/aria.html#dfn-assistive-technologies> *should* enable > users to quickly navigate to figures. Mainstream user agents > <https://rawgit.com/w3c/aria/action-1714/aria/aria.html#dfn-user-agent> *may* enable > users to quickly navigate to figures. > > Now the first paragraph states what a figure is and implicitly states > how it is different from an img role and calls out a significant > feature. The second paragraph is author guidance. The third paragraph is > hopeful guidance for user agents. > > Regards, > > Fred Esch > Accessibility Focal, Watson Solutions > AARB Complex Visualization Working Group Chair > W3C SVG Accessibility Task Force > IBM Watson > Fred > > > > Inactive hide details for Joanmarie Diggs ---10/08/2015 02:24:54 > PM---I've attempted to incorporate everyone's feedback here: hJoanmarie > Diggs ---10/08/2015 02:24:54 PM---I've attempted to incorporate > everyone's feedback here: https://rawgit.com/w3c/aria/action-1714/aria > > From: Joanmarie Diggs <jdiggs@igalia.com> > To: public-pfwg@w3.org > Date: 10/08/2015 02:24 PM > Subject: Re: Action-1708, Action-1709: Proposal for a Figure Role > > ------------------------------------------------------------------------ > > > > I've attempted to incorporate everyone's feedback here: > https://rawgit.com/w3c/aria/action-1714/aria/aria.html#figure > > --joanie > > On 10/06/2015 10:20 PM, Richard Schwerdtfeger wrote: >> *I reviewed this with with Steve Faulkner. It may require some >> wordsmithing but we are good to go. Steve is also ok with not having >> a caption role. * >> >> >> *figure * >> * A perceivable section of content which supports the main >> document, and should be easily perceivable regardless of its >> position in the layout that can contain a graphical document, an >> image or other content such as code snippets or example text.* >> >> *Authors SHOULD provide a reference to the figure from the main >> text, but the figure need not be displayed at the same location as >> the referencing element." >> >> A figure MAY have an associated description representing a caption >> and may have an associated label.**_ >> >> _**_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.* >> >> *Is abstract: False* >> *Superclass Role: section* >> *Subclass Roles:* >> *Inherited States and Properties: (inherits from section)* >> *Name From: author* >> *Accessible Name Required: False* >> >> >> >> Rich Schwerdtfeger > > > >
Received on Wednesday, 14 October 2015 22:01:19 UTC