Re: CFC - Edit to Non-text Contrast

+1
>From some interactions with designers this week, while referencing this 
proposed language this week, I think that this compromise language, while 
making things less clear cut, has the potential to help guide design 
decisions and give accessibility testers/advocats some muscle to flag 
low-contrast, important elements in a UI component.

Michael Gower
IBM Accessibility
Research

1803 Douglas Street, Victoria, BC  V8T 5C3
gowerm@ca.ibm.com
cellular: (250) 661-0098 *  fax: (250) 220-8034



From:   Andrew Kirkpatrick <akirkpat@adobe.com>
To:     WCAG <w3c-wai-gl@w3.org>
Date:   2018-05-29 10:01 AM
Subject:        CFC - Edit to Non-text Contrast



Call For Consensus — ends Thursday May 31st at 1:00pm Boston time.
 
The Working Group has discussed a change to the 1.4.11 SC text (non-text 
contrast). This issue was discussed on the May 29 call (
https://www.w3.org/2018/05/29-ag-minutes.html) and  survey (
https://www.w3.org/2002/09/wbs/35422/1_4_11_intent/results) and the 
consensus view of the Working Group is that the changes to the SC text 
accurately reflect the intent of the SC when written by the Working Group.
 
The specific changes are detailed in this pull request: 
https://github.com/w3c/wcag21/pull/945 
 
If you have concerns about this proposed consensus position that have not 
been discussed already and feel that those concerns result in you “not 
being able to live with” this decision, please let the group know before 
the CfC deadline.
 
Thanks,
AWK
 
Andrew Kirkpatrick
Group Product Manager, Accessibility
Adobe 
 
akirkpat@adobe.com
http://twitter.com/awkawk