This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
It's important to give users the ability to discover and navigate content when authoring tools are used incorrectly. The hidden attribute is a good example. Excerpt: "The **hidden **attribute must not be used to hide content that could legitimately be shown in another presentation, for example..." On occasion it will be, however, and full accessibility means the user needs some way to override this in order to deal with incorrectly rendered pages.
The HTML Accessibility Task Force intends to track these issues, per the proposal at http://lists.w3.org/Archives/Public/public-html-a11y/2010Jan/0245.html.
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: Accepted Change Description: no spec change Rationale: The rendering section already establishes that UAs can render pages however they like, including presenting everything that's hidden, the whole DOM tree, the source of scripts, or whatever else the user might want to see.
http://www.w3.org/2002/09/wbs/44061/20080513_bugs/results#xq10 We accept the response in this bug.