- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Mon, 4 Jul 2016 22:07:39 +0100
- To: "public-mobile-a11y-tf@w3.org" <public-mobile-a11y-tf@w3.org>
On 04/07/2016 21:33, Jonathan Avila wrote: > Ø Anybody, know of any "real world" accessibility issues where > something was not available to a mouse/pointer, because of some mistake > by a developer that needs correcting for accessibility reasons in WCAG? > I can't think of anything in my experience. > > > > I have seen assistive technologies such as features in screen readers > only work with the keyboard and not work correctly with the mouse. > Perhaps this is less likely on web pages – but I wonder if we need an > exception for assistive technologies? ATs may have special features > that maybe it doesn’t make sense to make accessible with the mouse or > perhaps not with the keyboard given the purpose of the AT. The proposed > Section 508 refresh has such an exception. This is the distinction we're also talking about in the other thread about keyboard - we need to separate the function of the CONTENT (web content, app, etc) from that of the UA/AT/input mechanism, I think. Otherwise we'll keep going in circles (see also gesture support etc). P -- Patrick H. Lauke www.splintered.co.uk | https://github.com/patrickhlauke http://flickr.com/photos/redux/ | http://redux.deviantart.com twitter: @patrick_h_lauke | skype: patrick_h_lauke
Received on Monday, 4 July 2016 21:08:05 UTC