- From: Andrew Kirkpatrick <akirkpat@adobe.com>
- Date: Thu, 25 Jan 2018 16:34:34 +0000
- To: lisa.seeman <lisa.seeman@zoho.com>, "W3c-Wai-Gl-Request@W3. Org" <w3c-wai-gl@w3.org>
- CC: public-cognitive-a11y-tf <public-cognitive-a11y-tf@w3.org>, Janina Sajka <janina@rednote.net>
- Message-ID: <30953C1F-41BD-442F-A633-B2853050D491@adobe.com>
Lisa, Thanks for raising this on the list. I have a few thoughts on this that I think are worth considering. This language has been part of WCAG since WCAG 2.0, this is not new language in the abstract. I do not believe that WCAG 2.0 fully addresses accessibility concerns for any group of users with disabilities, including people that with cognitive disabilities, and the same is true for WCAG 2.1. I am concerned that we aren’t possibly setting up the expectation that WCAG 2.1 is somehow taking steps backwards in accessibility. If the language changes to say “begins to address learning disabilities and cognitive limitations at conformance level AAA” it may lead people to that conclusion, and indicate that there is nothing in the AA success criteria that benefits this group of users. Does the COGA TF believe that there is nothing at all in WCAG 2.0 that provides benefits? The text that is proposed to be changed is editorial. We could change it now, but to be clear, we can also change it during the CR period. What I would like to propose is that the Working Group have a discussion about how this text could be changed when we have more than two hours to make that change. Since this was just discussed on the COGA call this morning (https://www.w3.org/2018/01/25-coga-minutes.html) it is definitely a late-arriving change request, and one that can be addressed during CR. Can we commit to having the Working Group have a collective discussion about this language and arrive at consensus language early in the CR period? Thanks, AWK Andrew Kirkpatrick Group Product Manager, Accessibility Adobe akirkpat@adobe.com http://twitter.com/awkawk From: "lisa.seeman@zoho.com" <lisa.seeman@zoho.com> Date: Thursday, January 25, 2018 at 10:44 To: WCAG <w3c-wai-gl@w3.org> Subject: making the draft for CR accurate Resent-From: WCAG <w3c-wai-gl@w3.org> Resent-Date: Thursday, January 25, 2018 at 10:43 I think the draft for CR has to change the introduction: from Following these guidelines will make content accessible to a wider range of people with disabilities, including blindness and low vision, deafness and hearing loss, learning disabilities, cognitive limitations, limited movement, speech disabilities, photosensitivity, and combinations of these. These guidelines address accessibility of web content on desktops, laptops, tablets, and mobile devices. Following these guidelines will also often make your Web content more usable to users in general. to Following these guidelines will make content accessible to a wider range of people with disabilities, including blindness and low vision, deafness and hearing loss, limited movement, speech disabilities, photosensitivity, and combinations of these. These guidelines address accessibility of web content on desktops, laptops, tablets, and mobile devices and begins to address learning disabilities and cognitive limitations at conformance level AAA, I am not sure if consider low vision to be addressed or "begins to addressed" All the best Lisa Seeman LinkedIn<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fil.linkedin.com%2Fin%2Flisaseeman%2F&data=02%7C01%7Cakirkpat%40adobe.com%7C5e0aa0123fd84199723e08d5640a76a7%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636524918465112191&sdata=dNUnFC87oYq%2BSeakcaAAxu0QxfEjE%2BCdodGYVTmaZLo%3D&reserved=0>, Twitter<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftwitter.com%2FSeemanLisa&data=02%7C01%7Cakirkpat%40adobe.com%7C5e0aa0123fd84199723e08d5640a76a7%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636524918465112191&sdata=YbFr1AxwaSfG%2BqrXmKpZkXWjItdVB0zcSorhLmDXom4%3D&reserved=0>
Received on Thursday, 25 January 2018 16:35:00 UTC