[Bug 13532] Clarify that UAs should make user-accessible all elements that take focus or react to user input, regardless of the input method

https://www.w3.org/Bugs/Public/show_bug.cgi?id=13532

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |FIXED

--- Comment #5 from Ian 'Hixie' Hickson <ian@hixie.ch> 2012-02-16 00:06:21 UTC ---
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: Accepted
Change Description: see diff given below
Rationale: I've added some notes, but the conformance criteria were already
fine. The specs that really need some normative text is whatever specs define
the input-device-specific events like "onkeypress" or "onmousemove" — those
need to very clearly state that using such events is an accessibility problem
if more generic mechanisms aren't also provided.

-- 
Configure bugmail: https://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, 16 February 2012 00:06:39 UTC