- From: Steven Faulkner <faulkner.steve@gmail.com>
- Date: Mon, 7 Jun 2010 16:19:11 +0100
- To: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
- Cc: Bruce Lawson <brucel@opera.com>, Laura Carlson <laura.lee.carlson@gmail.com>, Shelley Powers <shelleyp@burningbird.net>, HTML WG <public-html@w3.org>, HTML Accessibility Task Force <public-html-a11y@w3.org>
> Again, Steve, you did not answer one of my questions previously: what > is the default ARIA role for <figure> *itself*? leif try reading what i wrote in my original email on this thread: # <figure> should be mapped to accessibility APIs as a grouping element like <p> or <div> in other words role="group" regards stevef On 7 June 2010 16:10, Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> wrote: > Steven Faulkner, Mon, 7 Jun 2010 15:19:09 +0100: >> hi bruce, >> >>> <figure> >>> <img src=ceo.jpg alt=""> >>> <figcaption>Brian Slick, CEO of Blammo Corp, leveraging a >>> synergy</figcaption> >>> </figure> >>> >>> seems entirely accessible (?) >> >> the issue i see with this is that using alt="" says the image can be >> safely ignored. A caption is a label for something so the presence of >> the image needs to be exposed. > > This is no different from the WAI-ARIA example - WAI-ARIA does not > think it has to "be exposed": > > <div role="img" aria-labelledby="caption"> > <img src="example.png" role="presentation" alt=""> > <p id="caption">A visible text caption labeling the image.</p> > </div> > >> when <figcaption> is supported in browsers the mapping will be >> provided so that: >> >> <figure><img src=ceo.jpg alt="Brian Slick, CEO of Blammo Corp, >> leveraging a synergy"></figure> >> >> and >> >> <figure> >> <img src=ceo.jpg> >> <figcaption>Brian Slick, CEO of Blammo Corp, leveraging a >> synergy</figcaption> >> </figure> >> >> will both provide the accessible name as "Brian Slick, CEO of Blammo >> Corp, leveraging a synergy" > > > The proper solution to Bruce's example ought to be be this: > > <figure role="img" > > <img src=ceo.jpg alt=""> > <summary>Brian Slick, CEO of Blammo Corp, leveraging a > synergy</sumamry> > </figure> > > Yes, there are some backward compatibility issues. We have to discuss > how we can be *both* backward compatible *and* HTML5 compatible. > -- > leif halvard silli > -- with regards Steve Faulkner Technical Director - TPG Europe Director - Web Accessibility Tools Consortium www.paciellogroup.com | www.wat-c.org Web Accessibility Toolbar - http://www.paciellogroup.com/resources/wat-ie-about.html
Received on Monday, 7 June 2010 15:20:07 UTC