W3C home > Mailing lists > Public > public-html-a11y@w3.org > September 2010

[Bug 10831] Provide tablist and tab states for menu and command elements respectively

From: <bugzilla@jessica.w3.org>
Date: Thu, 30 Sep 2010 09:23:25 +0000
To: public-html-a11y@w3.org
Message-Id: <E1P1FML-0008Jl-Tb@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10831

Everett Zufelt <everett@zufelt.ca> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |TrackerRequest

--- Comment #2 from Everett Zufelt <everett@zufelt.ca> 2010-09-30 09:23:25 UTC ---
(In reply to comment #1)
> 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: A tab box is just a different overflow presentation. It's not a
> semantic distinction. Thus this really should be done in CSS (or more likely,
> XBL driven from CSS).

You couldn't be more wrong. A tablist is 100% semantic, it conveys meaning
about the purpose and role of a certain segment of the document.

-- 
Configure bugmail: http://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 Thursday, 30 September 2010 09:23:27 UTC

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