- From: <bugzilla@jessica.w3.org>
- Date: Mon, 24 Feb 2014 15:23:32 +0000
- To: public-pointer-events@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24786
Bug ID: 24786
Summary: ACTION-64: Propose a non-normative note re the
keyboard compat issue
Product: PointerEventsWG
Version: unspecified
Hardware: PC
OS: Windows NT
Status: NEW
Severity: normal
Priority: P2
Component: Pointer Events specification
Assignee: jrossi@microsoft.com
Reporter: redux@splintered.co.uk
QA Contact: public-pointer-events-bugzilla@w3.org
CC: public-pointer-events@w3.org
I'd propose adding this (admittedly wordy) NOTE to the introduction, right
after "An additional key goal is to enable multi-threaded user agents to handle
default touch actions, such as scrolling, without blocking on script
execution.", as a highlighted block:
Note:
While this specification defines a unified event model for multiple 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. Authors are encouraged, where
possible, to provide equivalent functionality for these forms of input by
including explicit keyboard event handling or responding to higher-level events
such as <code>focus</code>, <code>blur</code> and <code>click</code>. See WCAG
2.0 Guideline 2.1 for further details [link to
http://www.w3.org/TR/WCAG20/#keyboard-operation]
--
You are receiving this mail because:
You are on the CC list for the bug.
Received on Monday, 24 February 2014 15:23:33 UTC