- From: <bugzilla@jessica.w3.org>
- Date: Tue, 07 Sep 2010 20:04:47 +0000
- To: public-html-a11y@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10479
steve faulkner <faulkner.steve@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|WONTFIX |
--- Comment #7 from steve faulkner <faulkner.steve@gmail.com> 2010-09-07 20:04:46 ---
(In reply to comment #6)
> 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: If you changed the role of a <details> element, the user could no
> longer expand the <details> element to get to its contents. That would be a net
> loss of accessibility. If you have a group of radio buttons inside a <details>
> and you need to wrap them with role=radiogroup, then you should use an element
> for that group; <details> is not it.
The following does not make sense, please explain why:
> If you changed the role of a <details> element, the user could no
> longer expand the <details> element to get to its contents.
--
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 Tuesday, 7 September 2010 20:04:49 UTC