[Bug 24786] ACTION-64: Propose a non-normative note re the keyboard compat issue

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

--- Comment #6 from Patrick H. Lauke <redux@splintered.co.uk> ---
Ended up being a bit longer than before, but I hope I've captured Rick's
thoughts from the discussion here as well. I split it into two paras now, both
of which should be wrapped in a NOTE in the introduction, after the "An
additional key goal..." sentence, as a highlighted block:


While this specification defines a unified event model for a variety pointer
inputs, this model does not cover other forms of input such as keyboards or
keyboard-like interfaces (for instance a screenreader or similar assistive
technology running on a touchscreen-only device, which allows users sequential
navigation through focusable controls and elements). While user agents may
choose to also generate pointer events in response to these interfaces, this
scenario is not covered in this specification.

In the first instance, authors are encouraged, to provide equivalent
functionality for all forms of input by responding to high-level events such as
<code>focus</code>, <code>blur</code> and <code>click</code>. However, when
using low-level events (such as Pointer Events), authors should ensure that all
types of input are supported. In the case of keyboards and keyboard-like
interfaces, this may require the addition of explicit keyboard event handling.
See <a href="http://www.w3.org/TR/WCAG20/#keyboard-operation">WCAG 2.0
Guideline 2.1</a> for further details.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Tuesday, 4 March 2014 20:09:08 UTC