- From: <bugzilla@jessica.w3.org>
- Date: Tue, 07 Sep 2010 17:51:49 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10484
Ian 'Hixie' Hickson <ian@hixie.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |ian@hixie.ch
Resolution| |WONTFIX
--- Comment #1 from Ian 'Hixie' Hickson <ian@hixie.ch> 2010-09-07 17:51:48 ---
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: For <figcaption> and <caption>: ARIA doesn't have a clear role that
fits here, so having a default seems bad — it would be better to let the UA
map things to the accessibility APIs directly, following platform conventions.
On the other hand, there are lots of roles that might fit in various
circumstances, so we don't want to disallow roles. Hence the situation in the
spec now.
I would rather leave magic like defaulting roles based on other roles to the
ARIA spec editors. It doesn't seem like something that would be HTML-specific.
If ARIA could be simplified, the place to do that is the ARIA spec, not the
HTML spec.
--
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 Tuesday, 7 September 2010 17:51:51 UTC