- From: <alands289@gmail.com>
- Date: Fri, 2 Dec 2016 08:15:00 -0500
- To: "Patrick H. Lauke" <redux@splintered.co.uk>, "w3c-wai-gl@w3.org" <w3c-wai-gl@w3.org>
- Message-ID: <584173d7.5322c80a.ee567.2b8c@mx.google.com>
Another point to remember that I brought up at the start of the Mobile Task Force is the original industry complaint we were hearing from mobile app developers and industry leading mobile app companies was that WCAG is for web content and that mobile apps were not web content. It was the content that was the original focus. The devices themselves introduce the concepts of screen size, target size, touch interfaces, motion, vibration, stylus, and other human computer interaction methods that were not covered as well. These are found on mobile and the newer 2 in 1 laptops/tablets/hybrids. We still have not address wearable devices which can also have some or all of the same content on yet one more new device that has developed within the industry. Alan Sent from Mail for Windows 10 From: Patrick H. Lauke Sent: Thursday, December 1, 2016 6:45 PM To: w3c-wai-gl@w3.org Subject: Re: Comment on change in scope for charter On 02/12/2016 00:33, Andrew Kirkpatrick wrote: > WCAG’ers, > > Concerns were expressed that the charter scope should be clarified: > > 1. While addressing the requirements of digital publishing is believed > to already be covered by the charter a commenter would like to see > explicit mention. > 2. A concern was raised that the scope appears to limit the areas in > which updates can be made. > > The bullet in question: > Support the application of the Web Content Accessibility Guidelines to > mobile and touch devices through the development of Normative updates to > WCAG 2.0, as well as adding improvements to better support users with > low vision and cognitive, language, and learning impairments. > > I propose changing the scope bullet to the following: > Support the application of the Web Content Accessibility Guidelines to > mobile use cases and digital publications through the development of a > recommendation-track update to WCAG 2.0, as well as adding improvements > to better support users with disabilities including low vision and > cognitive, language, and learning impairments. This change makes the mistake of boiling down "mobile and touch devices" to just "mobile use cases"...which completely misses the point that touch devices are not just mobile (see for instance two-in-one laptop/tablet hybrids, desktops with touchscreens). If anything, I'd expand that bit instead to "mobile devices, a wider range of inputs such as touchscreens and and stylus digitizers, and digital publications..." or similar. 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 Friday, 2 December 2016 13:15:42 UTC