- From: <bugzilla@jessica.w3.org>
- Date: Tue, 21 Sep 2010 20:13:29 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10657
Ian 'Hixie' Hickson <ian@hixie.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |ian@hixie.ch
Resolution| |WONTFIX
--- Comment #2 from Ian 'Hixie' Hickson <ian@hixie.ch> 2010-09-21 20:13:28 ---
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: The request seems to be based on a misunderstanding of the purpose
of ARIA, as described in comment 1.
I would recommend rephrasing this request as a problem statement, explaining it
is that needs fixing, rather than saying what the fix should be. In general
it's very hard to evaluate proposals without knowing what the problem is. In
this particular instance, for example, it's very much unclear what the problem
is: what is it that is inaccessible? What kind of Web pages would exhibit this
problem? Sample markup showing the problem would be useful; even better would
be examples of real Web pages demonstrating the problem.
HTH.
--
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, 21 September 2010 20:13:30 UTC