- From: ALAN SMITH <alands289@gmail.com>
- Date: Tue, 28 Jun 2016 13:44:16 -0400
- To: "Patrick H. Lauke" <redux@splintered.co.uk>, WCAG <w3c-wai-gl@w3.org>, "public-mobile-a11y-tf@w3.org" <public-mobile-a11y-tf@w3.org>
- Message-ID: <5772b770.1255810a.5f30a.7459@mx.google.com>
Patrick, Yes, the distinction of “mobile” has always been hard to define, even when we were starting out with the Mobile Accessibility Task Force, I had question does this also mean tablets, tablets with keyboards, 10inch screens, etc. Are my tablets only mobile devices if I have cellular service and when I sit down in my house and use wifi are they no longer “mobile” devices? Companies are creating “mobile” or “tablet” or “small glass/medium glass” apps. If we consider them as you state “instead qualify it more specifically as being "touchscreen accessibility", "small-screen accessibility", we find the same issues. These smaller screens often have totally different user interface and content design with a lot less clutter. So I think my premise of the differences with “desktop” (which can be touch also) designed web and smaller screen native apps and web still is valid. Alan Smith, CSTE, CQA Sent from Mail for Windows 10 From: Patrick H. Lauke Sent: Tuesday, June 28, 2016 1:19 PM To: WCAG; public-mobile-a11y-tf@w3.org Subject: Re: Conforming alternative for mobile should not be Desktop On 28/06/2016 18:05, ALAN SMITH wrote: > +1 with David’s comment. > > It says to me “mobile accessibility is not needed”. > > I had the same thoughts of this indicating we can scrap all the work of > the Mobile Accessibility task force. One of the main problems I see with this whole rhetoric is: you're still talking about "mobile vs desktop" as if those were two nicely separate, distinct silos. They're not. We need to move away from treating something as "mobile accessibility" and instead qualify it more specifically as being "touchscreen accessibility", "small-screen accessibility", etc. Already there are plenty of device in the market today (such as 2-in-1 laptops) which blur the line, but still require SCs and Guidelines that apply to new input/display/etc methods available. 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 Tuesday, 28 June 2016 17:44:47 UTC