thanks josh, keep in mind my post is an attempt to kick off discussion and highlight issues of how to accessibility support new elements that don't have pre-defined semantics in acc APIs its not a plan set in stone. regards Stevef On 25 August 2011 07:15, Joshue O Connor <joshue.oconnor@cfit.ie> wrote: > Hi Steve, > > Just to say that I have re-read your post on the lack of a suitable role > for <figure> and <figcaption> and rather than saying right now that I > support it, I will ask the WG what they suggest is to be done to convey > the role semantics of <figure> and <figcaption> to AT via the A11y API > if Steve's reasoning isn't followed? [1] > > Cheers > > Josh > > [1] > > http://www.paciellogroup.com/blog/2011/08/html5-accessibility-chops-the-figure-and-figcaption-elements/ > -- with regards Steve Faulkner Technical Director - TPG www.paciellogroup.com | www.HTML5accessibility.com | www.twitter.com/stevefaulkner HTML5: Techniques for providing useful text alternatives - dev.w3.org/html5/alt-techniques/ Web Accessibility Toolbar - www.paciellogroup.com/resources/wat-ie-about.htmlReceived on Thursday, 25 August 2011 08:28:11 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 04:42:44 GMT