- From: Andrew Kirkpatrick <akirkpat@adobe.com>
- Date: Fri, 1 Dec 2017 20:32:02 +0000
- To: WCAG <w3c-wai-gl@w3.org>
- Message-ID: <6ADF746B-B3BC-4101-B915-BA76A533E40E@adobe.com>
In the event that anyone is feeling overwhelmed by the number of CFC’s that were issued today, here’s a guide: CFC for SC changes the chairs believe consensus exists for. These include a backup CFC to provide group guidance on what to do if the CFC fails: https://www.w3.org/2002/09/wbs/35422/Identify_common_purposes_CFC/ https://www.w3.org/2002/09/wbs/35422/Device_Sensors_CFC/ https://www.w3.org/2002/09/wbs/35422/Change_of_Content_CFC/ https://www.w3.org/2002/09/wbs/35422/Content_on_Hover_or_Focus_CFC/ https://www.w3.org/2002/09/wbs/35422/Accidental_Activation_CFC/ https://www.w3.org/2002/09/wbs/35422/Timeouts_CFC/ CFC for SC that there is no consensus for within the group. These CFC will provide guidance on how to proceed with these SC: https://www.w3.org/2002/09/wbs/35422/Interruptions_minimum_CFC/ https://www.w3.org/2002/09/wbs/35422/Contextual_Information_CFC/ https://www.w3.org/2002/09/wbs/35422/Animation_from_Interactions_CFC/ https://www.w3.org/2002/09/wbs/35422/Accessible_Authentication_CFC/ Thanks, AWK Andrew Kirkpatrick Group Product Manager, Accessibility Adobe akirkpat@adobe.com http://twitter.com/awka
Received on Friday, 1 December 2017 20:32:29 UTC