- From: Shelley Powers <shelleyp@burningbird.net>
- Date: Mon, 07 Jun 2010 14:51:19 -0500
- To: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
- CC: Steven Faulkner <faulkner.steve@gmail.com>, Bruce Lawson <brucel@opera.com>, Laura Carlson <laura.lee.carlson@gmail.com>, HTML WG <public-html@w3.org>, HTML Accessibility Task Force <public-html-a11y@w3.org>
Leif Halvard Silli wrote: > Also note that if we do > > <figure role="img"> > <img src="image" role="presentation" > > <summary>Description</summary> > </figure> > > then <figure>, just like the WAI-ARIA example, groups *two* elements - > <summary> and <img>. > Just a clarification before people get confused: It's figcaption, not summary. The summary element is in details. Shelley > PS: We really *must* define <figure> so that it - in general - is > unnecessary to use aria-labelledby for designating the caption. Just as > for the <caption> of <table>, it should be self evident what <figure>'s > caption element is captioning. > I believe this was the intent for UAs: that figcaption be treated like table caption, except figcaption allows markup. > And this begs the question: What role does <table>'s <caption> element > have? The best match I could find was the abstract role "sectionhead": > [1] > > ]] > A structure that labels or summarizes the topic of its related section. > ]] > > [1] http://www.w3.org/TR/wai-aria/roles#sectionhead > > Leif > > Shelley
Received on Monday, 7 June 2010 19:52:33 UTC