- From: Laura Carlson <laura.lee.carlson@gmail.com>
- Date: Sun, 24 Jan 2010 16:37:33 -0600
- To: "Tab Atkins Jr." <jackalmage@gmail.com>
- Cc: Maciej Stachowiak <mjs@apple.com>, public-html <public-html@w3.org>, HTML Accessibility Task Force <public-html-a11y@w3.org>
Hi Tab, On 1/24/10, Tab Atkins Jr. <jackalmage@gmail.com> wrote: > On Sun, Jan 24, 2010 at 2:50 AM, Laura Carlson > <laura.lee.carlson@gmail.com> wrote: >> I am in favor of creating a <summary> element as it might be a long >> term solution for issue 32. From Al Gilman's 6 Aug 2008 email "PFWG >> WAI review of @summary for tabular data": >> >> "element content providing this info, *if linked by markup to the >> table*offers growth to even better practice" >> http://lists.w3.org/Archives/Public/public-html/2008Aug/0213.html >> >> Brainstorming long term possibilities in the Wiki: >> http://esw.w3.org/topic/HTML/SummaryForTABLE#head-1d4cc386df3edd130dd677e056ba2bf98961145a > > Would this be in opposition to using <summary> for <details>, or in > support of it, like in the following: > > <table> > <caption> > <details> > <summary>Table Summary</summary> > foo foo foo > </details> > </caption> > … > </table> I don't know. The Accessibility Task Force has not discussed <summary> and your message didn't show up on the a11y list. So I am passing it on for their information, input, and advice. Thanks. Best Regards, Laura -- Laura L. Carlson
Received on Sunday, 24 January 2010 22:38:10 UTC