W3C home > Mailing lists > Public > public-html@w3.org > January 2010

Re: <summary> element and Issue 32

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Sun, 24 Jan 2010 10:20:10 -0600
Message-ID: <dd0fbad1001240820j1b41de42te094b3bbb0036bb2@mail.gmail.com>
To: Laura Carlson <laura.lee.carlson@gmail.com>
Cc: Maciej Stachowiak <mjs@apple.com>, public-html <public-html@w3.org>, HTML Accessibility Task Force <public-html-a11y@w3.org>
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>

?

~TJ
Received on Sunday, 24 January 2010 16:21:02 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:17:00 GMT