- From: <bugzilla@jessica.w3.org>
- Date: Thu, 13 Sep 2012 18:57:22 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18245
steve faulkner <faulkner.steve@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |faulkner.steve@gmail.com
--- Comment #3 from steve faulkner <faulkner.steve@gmail.com> 2012-09-13 18:57:21 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
> Rationale: Tabs are a presentational effect that can (and in a number of cases
> is) be done in such a way as to be AT friendly. If standardised this could be
> better handled through CSS.
Hi Robin, claiming it is a presentational effect appears to be at odds with
every accessibility API which provide distinct roles to identify the semantic
structures of tabs [1](tab, tablist, tabpanels) which are implemented across
OS's and platforms. They are provided because almost all UI languages have tab
widgets. tabs are not merely presentational they are UI controls and have a
role and states and properties that cannot be handled by CSS.
[1] http://www.w3.org/WAI/PF/aria-implementation/#mapping_role
--
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 Thursday, 13 September 2012 18:57:29 UTC