- From: <bugzilla@jessica.w3.org>
- Date: Thu, 01 Dec 2011 00:48:31 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13129 Ian 'Hixie' Hickson <ian@hixie.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #2 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-12-01 00:48:29 UTC --- 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: The argument here basically boils down to "the user might skip the text before the table by jumping straight to the table, and thus not understand what the table is about". Well yes. They might also skip past a paragraph and read the next one, and thus not know what the paragraph is about. At the end of the day, readers have to read the page to understand what it says, whether it's with a screen reader, reading directly from a screen, or any other mode. Authors aren't going to be adding markup to handle readers who aren't reading. What if the reader were to skip past the summary? -- 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 Thursday, 1 December 2011 00:48:39 UTC