RE: Concurrent Input Mechanisms

> -----Original Message-----
> From: Patrick H. Lauke []
> Classic example: a page sniffs to see if Touch Events are present, and if so only
> hooks up touch event listeners (rather than traditional mouse, keyboard, generic
> `click` handlers, etc).
> This falls apart on devices like laptops/desktops with both touchscreen AND
> traditional keyboard/mouse (e.g. Surface), and in situations where a nominally
> touch-only device like a phone or tablet has a paired keyboard and/or mouse.
> The impact is that users are forced to just use the touchscreen. The fact that the
> keyboard in these situations doesn't work can be filed as a failure of 2.1.1, but
> forcing mouse users to use touchscreen falls between the cracks of current
> WCAG at the moment. This would hopefully fill that gap.

[Jason] I think this is a good case, and if it and other such examples (with their accessibility drawbacks) are documented, they can constitute a rationale for the proposal.


This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.

Thank you for your compliance.


Received on Thursday, 3 August 2017 19:39:42 UTC