Re: CFC - WCAG 2.2 Redundant entry

+1

Gregg Vanderheiden
gregg@vanderheiden.us



> On Jun 7, 2022, at 7:49 AM, Melanie Philipp <melanie.philipp@deque.com> wrote:
> 
> +1 
> 
> Melanie Philipp, CPACC, WAS | Director, Services Methodology | 540-848-5220
> Deque Systems - Accessibility for Good
> www.deque.com <http://www.deque.com/>
> 
> On Mon, Jun 6, 2022 at 11:21 AM Alastair Campbell <acampbell@nomensa.com <mailto:acampbell@nomensa.com>> wrote:
> Call For Consensus — ends Friday June 10th at midday Boston time.
> 
>  
> 
> The Working Group has previously discussed the WCAG 2.2 SC Redundant Entry and it needs to be approved by CFC.
> 
>  
> 
> It can be previewed in the editor’s draft: 
> 
> https://w3c.github.io/wcag/understanding/redundant-entry.html <https://w3c.github.io/wcag/understanding/redundant-entry.html>
>  
> 
> The SC was last discussed Dec 3rd:
> 
> https://www.w3.org/2021/12/03-ag-minutes#t24 <https://www.w3.org/2021/12/03-ag-minutes#t24>
>  
> 
> The change history is here:
> 
> https://github.com/w3c/wcag/commits/main/guidelines/sc/22/redundant-entry.html <https://github.com/w3c/wcag/commits/main/guidelines/sc/22/redundant-entry.html>
>  
> 
> The surveys are available here:
> 
> https://www.w3.org/2002/09/wbs/35422/wcag22-redundant-entry/results <https://www.w3.org/2002/09/wbs/35422/wcag22-redundant-entry/results> and
> 
> https://www.w3.org/2002/09/wbs/35422/wcag22-redundant-entry-updates/results <https://www.w3.org/2002/09/wbs/35422/wcag22-redundant-entry-updates/results>
>  
> 
> The github issues (all closed) are listed here:
> https://github.com/w3c/wcag/issues?q=is%3Aissue+label%3A%223.3.8+Redundant+Entry%22 <https://github.com/w3c/wcag/issues?q=is%3Aissue+label%3A%223.3.8+Redundant+Entry%22>+
> 
>  
> 
> 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.
> 
>  
> 
> Kind regards,
> 
> -Alastair
> 
> -- 
> 
>  
> 
> @alastc / www.nomensa.com <http://www.nomensa.com/>
>  
>