W3C home > Mailing lists > Public > public-html@w3.org > January 2010

Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)

From: James Craig <jcraig@apple.com>
Date: Fri, 22 Jan 2010 15:13:02 -0800
Cc: public-canvas-api <public-canvas-api@w3.org>, HTML WG <public-html@w3.org>
Message-Id: <E81F59A0-9EC0-41B2-96D2-FCDE4AC488CD@apple.com>
To: Ian Hickson <ian@hixie.ch>
(I'm pretty sure this came from Ian. The threading was a little broken in the last reply)

Ian Hickson <ian@hixie.ch> wrote: 

> I'm not sure how to phrase what I said more clearly. To clarify, if I may: "click" is a mouse gesture, "hit enter" is a keyboard gesture.

This is not always true. 'mousedown' and 'mouseup' are certainly mouse gestures, and the combination results in a 'click' event, but clicks can be fired by other input devices. For example, in most modern browsers, 'pressing enter' on a link will fire a 'click' event on the focused element. Likewise, most screen readers have a concept of a 'default action' for any UI element. This is sometimes triggered by a key combination that is not Enter (VO uses Ctrl+Opt+Space) and is not a mousedown/mouseup combo, yet it still results in a 'click' event.

> These are different input devices with different resulting DOM events. Click events are targetted based on the coordinates of the mouse cursor. Keyboard events are targetted based on the current focus.

Mouse events *are* targeted based on the coordinates of the mouse, and click events *can* be, but only when triggered by a mouse or another input device mimicking the combination of mousedown/mouseup events.
Received on Friday, 22 January 2010 23:13:36 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:17:00 GMT