- From: lisa.seeman <lisa.seeman@zoho.com>
- Date: Wed, 01 Feb 2017 00:44:57 +0200
- To: Thaddeus . <inclusivethinking@gmail.com>
- Cc: "public-cognitive-a11y-tf" <public-cognitive-a11y-tf@w3.org>
- Message-Id: <159f6b1ff49.c8fcac4563078.1818330836441093086@zoho.com>
Hi Folks We need to be working to include all disability groups into WCAG 2.1. I would therefore like to propose that we add the option to our surveys "include with the following to -do actions" to-do actions can include: rework to make more testable or rework to ensure backward compatibility etc It is common to have in a first working draft to-do items, and this enables us to both identify they have a problem and include them for review by the community. Let me be clear, after all the research and issue papers we can not claim that there is not enough research to enable support for learning and cognitive (like we did for 2.0). We also can not claim we support all disabilities when we do not. We must work/innovate to enable us to support them. The most we could do is say we could not reach consensus on how to make it clear/testable/ easy to do etc... which should mean that this specification is not yet finished and not that we left them out. We should only reject SC and leave them out of the draft if they are not needed to include people with disabilities. All the best Lisa Seeman LinkedIn, Twitter ---- On Tue, 31 Jan 2017 21:04:33 +0200 Thaddeus .<inclusivethinking@gmail.com> wrote ---- I feel the same. I feel like my SC are not moving forward well. I have a lot of criticism of the SC without much constructive criticism or indications of suggestions to imporove. I am trying to move the conversation away from pure criticism but it has been difficult. I also am finding that many times we are restating supporting comments that have already been stated earlier in the issue thread. Thaddeus On Jan 31, 2017 10:19 AM, "lisa.seeman" <lisa.seeman@zoho.com> wrote: I added the link to the w3c specification, that is the first Accessible authentication technique. It is in the comments of the issue. my 2 cents if these COGA SC (Such as Accessible authentication) do not go in, then WCAG 2.1 will be a joke, because we will know, when we publish, that conformant content will not include or be useable by people with cognitive disabilities. It will not be inclusive content. A basic question we need to ask is if we need wcag to enable content to be accessible to people with any cognitive disabilities, and is that an important thing. If we do, we need to find ways to include this stuff, we need to change the focus from saying no to finding solutions to make this work and include them. If we don't we are wasting our time. we may meet our deadlines but we will achieve little else . Please do not suggest moving things to AAA. It is insulting to the user groups excluded. All the best Lisa Seeman LinkedIn, Twitter
Received on Tuesday, 31 January 2017 22:45:59 UTC