Re: Extending CFC - Publish WCAG 3.0 as FPWD

Yes. I’m good with that

This message was Sent from my iPhone. Please excuse any typographic errors.

On Nov 9, 2020, at 9:43 AM, Rachael Bradley Montgomery <rachael@accessiblecommunity.org> wrote:


Hello David,

Please take a look at pull request 212<https://github.com/w3c/silver/pull/212/files> which has removed the phrase "and more modern" from the abstract. You can see the full text at https://raw.githack.com/w3c/silver/cfc_objection_1/guidelines/index.html


Does this address your concern such that you would change your objection to a 0 or are additional changes needed?

Best regards,

Rachael

On Mon, Nov 2, 2020 at 1:52 PM David Fazio <dfazio@helixopp.com<mailto:dfazio@helixopp.com>> wrote:
I hate to be the voice of dissent, but I’m a -1 because of the following Abstract:

W3C Accessibility Guidelines 3.0 is a successor to Web Content Accessibility Guidelines 2.2<https://www.w3.org/TR/WCAG22/> [WCAG22<https://w3c.github.io/silver/guidelines/#bib-wcag22>] and previous versions, but does not deprecate<https://w3c.github.io/silver/guidelines/#dfn-deprecate> these versions. WCAG 3.0 will incorporate content from and partially extend User Agent Accessibility Guidelines 2.0<https://www.w3.org/TR/UAAG20/> [UAAG20<https://w3c.github.io/silver/guidelines/#bib-uaag20>] and Authoring Tool Accessibility Guidelines 2.0<https://www.w3.org/TR/ATAG20/>[ATAG20<https://w3c.github.io/silver/guidelines/#bib-atag20>]. While there is a lot of overlap between WCAG 2.X and WCAG 3.0, WCAG 3.0 includes additional tests and different scoring mechanisms. As a result, WCAG 3.0 is not backwards compatible with WCAG 2.X. WCAG 3.0 does not supersede WCAG 2.2 and previous versions; rather, it is an alternative and more modern set of guidelines. Once these guidelines become a W3C Recommendation, the W3C will advise developers, content creators and policy makers to use WCAG 3.0 in order to maximize future applicability of accessibility efforts. However, content that conforms to earlier versions of WCAG continue to conform to those versions.

This introduction, to me, implies that WCAG 2... is obsolete given the evolution of the web. Defendants can easily argue that courts should not hold them accountable to a standard that is no longer good enough for the current state of the web. I continue to believe that WCAG 2 should be incorporated into WCAG 3 at least as a baseline building block, and be made backwards compatible. Although, I recognize I am just 1 voice.

I would be a 0 if we removed the statement about it being a more modern set of guidelines and everything after that. That content opens too many doors to sink WCAG 2 in court, in my opinion.


David Fazio, President | [signature_777599446] <https://www.linkedin.com/in/davidpfazio/>
[A picture containing sitting    Description automatically generated]| [signature_242308129] <https://www.linkedin.com/company/helixopportunity>
P. 510.590.7363| e. dfazio@helixopp.com<mailto:dfazio@helixopp.com>| W. www.helixopp.com<http://www.helixopp.com>




From: Rachael Bradley Montgomery <rachael@accessiblecommunity.org<mailto:rachael@accessiblecommunity.org>>
Date: Friday, October 30, 2020 at 10:23 AM
To: WCAG <w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>>, Silver TF <public-silver@w3.org<mailto:public-silver@w3.org>>
Subject: Extending CFC - Publish WCAG 3.0 as FPWD
Hello,

To provide additional time for people to review the acknowledgements section<https://w3c.github.io/silver/guidelines/#acknowledgements>, we are extending the deadline for the FPWD CFC to Monday at 2pm Boston time.

The acknowledgements were originally left out of the original CFC. Michael sent them out earlier this week, but we want to provide some additional time to make sure everyone has had a chance to review the section.

Please take a few moments to read through the acknowledgements section and make sure everyone is included and names are spelled correctly.

Thank you,

Rachael

On Fri, Oct 23, 2020 at 1:38 PM Rachael Bradley Montgomery <rachael@accessiblecommunity.org<mailto:rachael@accessiblecommunity.org>> wrote:

Call For Consensus — ends Friday October 30th at 2:00 pm Boston time.



The Working Group and Silver Taskforce have discussed publishing W3C Accessibility Guidelines (WCAG) 3.0 as a First Public Working Draft (FPWD).



The document is at: https://w3c.github.io/silver/guidelines/




Call minutes:
•         1 September AGWG & Silver Meeting Minutes<https://www.w3.org/2020/09/01-ag-minutes.html>
•         15 September AGWG & Silver Meeting Minutes<https://www.w3.org/2020/09/15-ag-minutes.html>
•         6 October AGWG & Silver Meeting Minutes<https://www.w3.org/2020/10/06-ag-minutes.html>
•         20 October AGWG & Silver Meeting Minutes<https://www.w3.org/2020/10/20-ag-minutes.html#item03>

Changes are viewable through the diffs at https://github.com/w3c/silver/commits/master/guidelines/index.html




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,



Rachael

--
Rachael Montgomery, PhD
Director, Accessible Community
rachael@accessiblecommunity.org<mailto:rachael@accessiblecommunity.org>

"I will paint this day with laughter;
I will frame this night in song."
 - Og Mandino



--
Rachael Montgomery, PhD
Director, Accessible Community
rachael@accessiblecommunity.org<mailto:rachael@accessiblecommunity.org>

"I will paint this day with laughter;
I will frame this night in song."
 - Og Mandino



--
Rachael Montgomery, PhD
Director, Accessible Community
rachael@accessiblecommunity.org<mailto:rachael@accessiblecommunity.org>

"I will paint this day with laughter;
I will frame this night in song."
 - Og Mandino