Re: leaving SC out of the draft - this is an issue that must get consensus

I'm with Lisa on this AAA gets ignored.

Kind regards,

Neil Milliken
Head of Accessibility & Digital Inclusion
M: 07812325386<tel:07812325386>


On 7 Feb 2017, at 21:29, lisa.seeman <<>> wrote:

Hi Rachel

I dont think putting them as AAA will make anyone look at them., certainly not tool developers.

All the best

Lisa Seeman

LinkedIn<>, Twitter<>

---- On Tue, 07 Feb 2017 21:53:55 +0200 Bradley Montgomery<<>> wrote ----

I understand the point made today that we will have criteria at varying stages of completeness.  Some likely should not make it into the working draft but my understanding of AAA criteria was that they were intended to include SC that may be stretch goals based on current technology or techniques. Can we look at using AAA when the criteria are sound but we do not have clear technology to support them? Making them AAA would ensure that techniques get reviewed and discussed as part of the working draft and if we are able to answer outstanding questions we could move them up to AA  as part of the draft process.



From: lisa.seeman [<>]
Sent: Tuesday, February 7, 2017 2:17 PM
To: W3c-Wai-Gl-Request@W3. Org <<>>
Subject: leaving SC out of the draft - this is an issue that must get consensus

Hi Folks
Andrew said on the call today that  SC that do not meet all the acceptance criteria left out of this draft . This is an issue that must get consensus. It should not be a decision the chairs and staff contact make by themselves.

My 2 cents is no. This is not ok.

It is essential that SC that address a user need such that, some users can not use content that does not conform, are in the draft for 2.1 at the end of the month. Even if they  do not have full consensus, and we may have identified issues with them. These issues can be identified as an editors note next to any relevant SC.

If we do not publish them we are making it significantly less likely that we will be able to include them into WCAG 2.1 when we get to CR. This means that people with disabilities that WCAG have not yet addressed, we will continue to not address. That is horrible and in my opinion, unacceptable . Further it is a step that shows that we have not made reasonable effort to include low vision and cognitive.

Let's explain with an example. A typical issue is testability - and a lack of testing tools. Often the tools are there, just not in use in the accessibility testing industry. For example, there a open sources natural language processing tools, and there are tools that test against word list (VOA have one for restricted languages, translation etc). If the simple lange criteria are included then the tool owners can get working making a user interface that is useable for our industry, and when we get to CR people will find this a testable SC.

Did you know Voice of America had such a tool for their simple language news  broadcast  when wcag 2.0 came out? They were talking about using it for accessibility, but because it ended up just being level AAA and using common words was not even a requirement there - they did not bother. No tools no SC. No SC no tools.

With this draft we have an opportunity to encourage our industry to look for new tools, look for new solutions and learn about new disabilities. They may need to install something new on there laptop. So be it.

 All the best

Lisa Seeman

LinkedIn<>, Twitter<>

Atos, Atos Consulting, Worldline and Canopy The Open Cloud Company are trading names used by the Atos group. The following trading entities are registered in England and Wales: Atos IT Services UK Limited (registered number 01245534), Atos Consulting Limited (registered number 04312380), Atos Worldline UK Limited (registered number 08514184) and Canopy The Open Cloud Company Limited (registration number 08011902). The registered office for each is at 4 Triton Square, Regent’s Place, London, NW1 3HG.The VAT No. for each is: GB232327983.

This e-mail and the documents attached are confidential and intended solely for the addressee, and may contain confidential or privileged information. If you receive this e-mail in error, you are not authorised to copy, disclose, use or retain it. Please notify the sender immediately and delete this email from your systems. As emails may be intercepted, amended or lost, they are not secure. Atos therefore can accept no liability for any errors or their content. Although Atos endeavours to maintain a virus-free network, we do not warrant that this transmission is virus-free and can accept no liability for any damages resulting from any virus transmitted. The risks are deemed to be accepted by everyone who communicates with Atos by email.

Received on Wednesday, 8 February 2017 20:07:09 UTC