W3C home > Mailing lists > Public > public-html-a11y@w3.org > December 2011

[Bug 14107] Non-conformance of the summary attribute for the table element makes WCAG 1.0 compliance impossible

From: <bugzilla@jessica.w3.org>
Date: Sat, 10 Dec 2011 15:44:26 +0000
To: public-html-a11y@w3.org
Message-Id: <E1RZP6A-0003qQ-Bi@jessica.w3.org>

--- Comment #8 from theimp@iinet.net.au 2011-12-10 15:44:24 UTC ---
Sorry, I must have been unclear.

This bug is not "tables without @summary are inaccessible". I have plenty to
say on that subject, but this is not the forum for such discussion.

This but is not even "@summary should not be removed" - that is simply a
suggested resolution.

This bug is that, a normative section of a current W3C Recommendation,
implemented in legislation around the world, says: 
> […] in HTML, use the "summary" attribute of the TABLE element.

The current state of the spec. contradicts this directive and needs to be

If the Editor disagrees that there is a spec. contradiction, unrelated to the
merits or lack thereof regarding the summary attribute, then that is the
Editor's determination to make in respect of this spec., but I was pointing out
that regardless of any determination made in this spec., some major
stakeholders will no doubt be making their own determination in regards to the
meaning of the other mentioned spec.

Despite the assertion that removing @summary does not make pages less
accessible, keeping @summary does not make pages less accessible either, nor
does it cause any other significant problems. But removing @summary, at this
time, does cause at least this problem. Legislation is much slower-moving than
the web, even in spite of the relative slowness of some major specs.

Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Saturday, 10 December 2011 15:46:31 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:05:25 UTC