Re: Concurrent Input Mechanisms

Patrick,
I agree that this is what we are trying to address, but the question has been raised asking for specific examples. Is there a specific case of your classic example that you can point to?

Thanks,
AWK

Andrew Kirkpatrick
Group Product Manager, Accessibility
Adobe 

akirkpat@adobe.com
http://twitter.com/awkawk








On 8/3/17, 15:33, "Patrick H. Lauke" <redux@splintered.co.uk> wrote:

>On 03/08/2017 19:45, White, Jason J wrote:
>> I think Andrew’s suggested formulations are moving in the right 
>> direction so far as clarifying the idea is concerned. Obviously, 
>> restricting the available input modalities is not a good idea. On the 
>> other hand, I don’t know how Web content can fail to satisfy this, in 
>> practical terms, or how serious the accessibility issues are that result 
>> if it does. In particular, surely most of the issues lie at the user 
>> agent or operating system level.
>
>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.
>
>P
>-- 
>Patrick H. Lauke
>
>https://na01.safelinks.protection.outlook.com/?url=www.splintered.co.uk&data=02%7C01%7C%7Ce06e8fcd3cd343b6752908d4daa6b43c%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636373856991854495&sdata=GHTXVrTDQiNLwRlmcWMj%2BhCB9CbwmrKqpaGE6RaZBYg%3D&reserved=0 | https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fpatrickhlauke&data=02%7C01%7C%7Ce06e8fcd3cd343b6752908d4daa6b43c%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636373856991854495&sdata=06gZbHYcU%2BEHdvMX7xkxpIc7LseILkQlGp5dGameFSg%3D&reserved=0

>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fflickr.com%2Fphotos%2Fredux%2F&data=02%7C01%7C%7Ce06e8fcd3cd343b6752908d4daa6b43c%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636373856991854495&sdata=r2mLj7CZs3IGGK6e7nlysJ%2Fsgy0%2BkUkkWP0B9FZPQCA%3D&reserved=0 | https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fredux.deviantart.com&data=02%7C01%7C%7Ce06e8fcd3cd343b6752908d4daa6b43c%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636373856991854495&sdata=oEF9sfKBjk1%2FLO2oiudbiu%2F6XJ7EpONLOti4QJXpv8o%3D&reserved=0

>twitter: @patrick_h_lauke | skype: patrick_h_lauke
>

Received on Friday, 4 August 2017 15:32:40 UTC