- From: Katie Haritos-Shea GMAIL <ryladog@gmail.com>
- Date: Thu, 1 Dec 2016 20:54:22 -0500
- To: "'Andrew Kirkpatrick'" <akirkpat@adobe.com>, "'WCAG'" <w3c-wai-gl@w3.org>
- Message-ID: <1d3a01d24c3f$01601390$04203ab0$@gmail.com>
+1, but suggest per Patrick’s point: Support the application of the Web Content Accessibility Guidelines to mobile and touch devices, as well as 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. * katie * Katie Haritos-Shea Principal ICT Accessibility Architect (WCAG/Section 508/ADA/AODA) Cell: 703-371-5545 | <mailto:ryladog@gmail.com> ryladog@gmail.com | Oakton, VA | <http://www.linkedin.com/in/katieharitosshea/> LinkedIn Profile | Office: 703-371-5545 | <https://twitter.com/Ryladog> @ryladog From: Andrew Kirkpatrick [mailto:akirkpat@adobe.com] Sent: Thursday, December 1, 2016 6:34 PM To: WCAG <w3c-wai-gl@w3.org> Subject: Comment on change in scope for charter 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. What do people think about this as a possible change? I believe that it leaves it quite broad so we can add improvements that better support users with disabilities as well as addressing the mobile and digital publishing cases specifically. Comments? Thanks, AWK Andrew Kirkpatrick Group Product Manager, Standards and Accessibility Adobe akirkpat@adobe.com <mailto:akirkpat@adobe.com> http://twitter.com/awkawk
Received on Friday, 2 December 2016 01:55:02 UTC