- From: Andrew Kirkpatrick <akirkpat@adobe.com>
- Date: Tue, 26 Apr 2016 13:21:30 +0000
- To: Gregg Vanderheiden <gregg@raisingthefloor.org>
- CC: GLWAI Guidelines WG org <w3c-wai-gl@w3.org>
- Message-ID: <D83E7554-B493-486D-97DB-CCF370B1366B@adobe.com>
Gregg, Thanks for the suggestions. I made the changes in the first paragraph as they are editorial/grammar changes. The changes in the second paragraph are more substantial and would need to be reviewed by the WG, but we are in a Call for Consensus now, so the question for you, per the CfC, is whether you are not able to live with the proposal as it is. Thanks, AWK Andrew Kirkpatrick Group Product Manager, Accessibility and Standards Adobe akirkpat@adobe.com http://twitter.com/awkawk From: CAE-Vanderhe <gregg@raisingthefloor.org<mailto:gregg@raisingthefloor.org>> Date: Tuesday, April 26, 2016 at 00:32 To: Andrew Kirkpatrick <akirkpat@adobe.com<mailto:akirkpat@adobe.com>> Cc: WCAG <w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>> Subject: Re: CfC: Changes to Understanding 1.4.3 Suggested edits to the current text under review + <p>The minimum contrast success criterion (1.4.3) applies to text in the page, including placeholder text and text that is shown during when a pointer is hoveringed over an object or when an object is focused with the keyboard has keyboard focus. If any of these are used in a page, the text needs to provide sufficient contrast.</p> + <p>Although this Success Criterion only applies to text, similar issues occur for <phrase>content presented in charts, graphs, diagrams, and other non-text-based information. Content presented in this manner should also have good contrast to ensure that more users can access the information. Contrast of content in charts, graphs, diagrams, and other non-text-based information however is not required by this SC. (this phrase should be bolded and underlined so that the paragraph is not misunderstood. also added sentence at end to avoid confusion and discussion later. gregg On Apr 25, 2016, at 10:20 AM, Andrew Kirkpatrick <akirkpat@adobe.com<mailto:akirkpat@adobe.com>> wrote: I should have put in the link to the changes with the right “diff” view option set: https://github.com/w3c/wcag/pull/177/files?diff=split Hopefully this makes this easier… AWK From: Andrew Kirkpatrick <akirkpat@adobe.com<mailto:akirkpat@adobe.com>> Date: Monday, April 25, 2016 at 10:58 To: WCAG <w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>> Subject: CfC: Changes to Understanding 1.4.3 CALL FOR CONSENSUS – ends Wednesday April 27 at 11:00am Boston time. The WG discussed a pull request to provide specific changes to understanding 1.4.3 and agreed that the changes were acceptable. This CfC is on the changes implemented in Understanding 1.4.3 as part of the implementation of Issue 157 (https://github.com/w3c/wcag/issues/157) which was agreed to in a previous CfC. Please review the suggested changes here: https://github.com/w3c/wcag/pull/177/files 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 position, please let the group know before the CfC deadline. Thanks, AWK Andrew Kirkpatrick Group Product Manager, Accessibility and Standards Adobe akirkpat@adobe.com<mailto:akirkpat@adobe.com> http://twitter.com/awkawk
Received on Tuesday, 26 April 2016 13:22:04 UTC