- From: <bugzilla@wiggum.w3.org>
- Date: Fri, 08 Jan 2010 14:56:45 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8449 Shelley Powers <shelleyp@burningbird.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |TrackerRequest --- Comment #6 from Shelley Powers <shelleyp@burningbird.net> 2010-01-08 14:56:44 --- (In reply to comment #5) > EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are > satisfied with this response, please change the state of this bug to CLOSED. If > you have additional information and would like the editor to reconsider, please > reopen this bug. If you would like to escalate the issue to the full HTML > Working Group, please add the TrackerRequest keyword to this bug, and suggest > title and text for the tracker issue; or you may create a tracker issue > yourself, if you are able to do so. For more details, see this document: > http://dev.w3.org/html5/decision-policy/decision-policy.html > > Status: Rejected > Change Description: no spec change > Rationale: Given how bad the current situation is regarding authors providing > explanatory text for tables, I think we should given them as much information > as possible, in as many places as possible. We do AT users a disservice if we > pretend that their needs aren't important enough to include advice on how to > best serve them in the spec. > More text will not make tables any clearer, or ensure people use the element in the proper way. What's needed is a good, clean, succinct example, with a clear explanation of each element of the table, including the summary attribute. A good explanation of how to use summary properly would do wonders for the table's accessibility. A meandering description of how people can use anything _but_ summary, is only going to cause conflict with previous versions of the markup, with existing screenreader implementations, and runs counter to the expressed interest and wishes of every accessibility person on the HTML WG team -- and beyond. The section needs re-written, but such is best left for a change proposal. I want this one escalated to an issue. Use the original title and comment as the body of the issue. Thanks. -- Configure bugmail: http://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 Friday, 8 January 2010 14:56:46 UTC