- From: Jonathan Avila <jon.avila@ssbbartgroup.com>
- Date: Fri, 1 Apr 2016 23:19:00 +0000
- To: David MacDonald <david100@sympatico.ca>, "Patrick H. Lauke" <redux@splintered.co.uk>
- CC: "public-mobile-a11y-tf@w3.org" <public-mobile-a11y-tf@w3.org>
- Message-ID: <BLUPR03MB263B2D162F7BE69CA481C0E9B9A0@BLUPR03MB263.namprd03.prod.outlook.com>
Ø Touch screen and small screen accessibility? It’s potentially more than touch screens and screen size – there are other aspects of mobile devices such as vibration, geolocation, accelerometers, lack of physical keyboards, etc. that play in here. Gaming devices might have some of these as well – so they are not specific to mobile – they may be specific to handheld devices – but of course that term is not optimal as some people won’t be holding them. Jonathan Jonathan Avila Chief Accessibility Officer SSB BART Group jon.avila@ssbbartgroup.com<mailto:jon.avila@ssbbartgroup.com> 703.637.8957 (Office) Visit us online: Website<http://www.ssbbartgroup.com/> | Twitter<https://twitter.com/SSBBARTGroup> | Facebook<https://www.facebook.com/ssbbartgroup> | Linkedin<https://www.linkedin.com/company/355266?trk=tyah> | Blog<http://www.ssbbartgroup.com/blog/> Check out our Digital Accessibility Webinars!<http://www.ssbbartgroup.com/webinars/> From: David MacDonald [mailto:david100@sympatico.ca] Sent: Friday, April 01, 2016 7:14 PM To: Patrick H. Lauke Cc: public-mobile-a11y-tf@w3.org Subject: Re: Minutes of Mobile A11y TF teleconference of 31 March 2016 We're in the process of exploring what WCAG.NEXT will look like... one option is not having extensions, and just going to the next version of WCAG, which would make the problem go away. Otherwise what would you call this extension, if you could "name that child"? Touch screen and small screen accessibility? On Fri, Apr 1, 2016 at 3:49 AM, Patrick H. Lauke <redux@splintered.co.uk<mailto:redux@splintered.co.uk>> wrote: On 01/04/2016 01:05, David MacDonald wrote: Mobile seems to be the buzz these days, and the general public has not advanced past ... If we offer a course in Mobile accessibility, and another course in Pointer events accessibility, or touch events accessibility. I think the mobile a11y course will triple the attendance. Well, you wouldn't market a course just on "Touch events". And even if you wanted to, you'd call it something a bit more general such as "Making content and applications on touchscreen devices accessible". In the Microsoft Event this week the keynote the statement was "we are mobile first, meaning users should be able to access their work across all platforms and technologies, that's mobile computing, the user is mobile" But I'm fine with dumping the word mobile, if it interferes with our mission, but we should do so after consulting stakeholders. "Mobile" as a marketing buzzword is fine. "Mobile" as a categorisation for technologies/problems/recommendations which are not exclusive to smartphones/tablets is what I take issue with. That is all. P -- Patrick H. Lauke www.splintered.co.uk<http://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 Friday, 1 April 2016 23:19:29 UTC