- From: <bugzilla@jessica.w3.org>
- Date: Sat, 10 Dec 2011 15:44:26 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=14107 --- 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 reconciled. 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 the QA contact for the bug.
Received on Saturday, 10 December 2011 15:46:31 UTC