- From: Steve Faulkner <faulkner.steve@gmail.com>
- Date: Thu, 17 Sep 2015 09:57:46 +0100
- To: Richard Schwerdtfeger <schwer@us.ibm.com>
- Cc: Joseph Scheuhammer <clown@alum.mit.edu>, "WAI Protocols & Formats" <public-pfwg@w3.org>, LĂ©onie Watson <lwatson@paciellogroup.com>
- Message-ID: <CA+ri+VktbVYvtvJnvCeacqhcr1-ya7HNtixmQdejjoVZMRuJHw@mail.gmail.com>
Hi Rich, cc leonie May be useful to have as an agenda item on an ARIA call, so we can discuss? I know Leonie has some thoughts on figure/figcaption, If that is possible will makes sure I can attend call. -- Regards SteveF Current Standards Work @W3C <http://www.paciellogroup.com/blog/2015/03/current-standards-work-at-w3c/> On 16 September 2015 at 22:29, Richard Schwerdtfeger <schwer@us.ibm.com> wrote: > > I have provided an update to the proposed figure role. However, before > we formalize this I need to cover other issues that Steve Faulkner and I > discussed regarding its use for <figure>. Steve mentioned that <figcaption> > defaults a label relationship with <figure>. In actuality it is actually > used as a description. At times however the label for the figure may be > embedded in it. Am example is below: > https://search.yahoo.com/yhs/search?p=figure+and+figcaption+element&ei=UTF-8&hspart=mozilla&hsimp=yhs-001 > > At other times it can appear like a label: > http://www.w3.org/wiki/HTML/Elements/figcaption > > We differentiate label and descriptions as one being short and the > other being long. Steve would like for us to have a figcaption role but > what I think we really need to do is state that Figures must have both a > visible label and a description. In HTML the description can be implied. I > would like to discuss this with the group and also see whether Steve things > that we should require an aria-labelledby on the <figure> element or at > least an aria-label. I can see where the implied description could be > adequate and we might just want to have an aria-label on it. > > We need to resolve this before this becomes a formal proposal. > > > > figure > > A perceivable section of content which supports the main document, > and should be easily perceivable regardless of its position in the layout. > A figure might 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 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. > > > > > Rich Schwerdtfeger >
Received on Thursday, 17 September 2015 08:58:54 UTC