Re: CFC - Publication of WCAG 2.2 FPWD

+1

** katie **

*Katie Haritos-Shea*

*Principal ICT Accessibility Architect, **Board Member and W3C Advisory
Committee Rep for Knowbility *

*WCAG/Section 508/ADA/AODA/QA/FinServ/FinTech/Privacy,* *IAAP CPACC+WAS = *
*CPWA* <http://www.accessibilityassociation.org/cpwacertificants>

*Cell: **703-371-5545 <703-371-5545>** |* *ryladog@gmail.com
<ryladog@gmail.com>* *| **Oakton, VA **|* *LinkedIn Profile
<http://www.linkedin.com/in/katieharitosshea/>*

People may forget exactly what it was that you said or did, but they will
never forget how you made them feel.......

Our scars remind us of where we have been........they do not have to
dictate where we are going.




On Tue, Feb 4, 2020 at 3:05 PM Bruce Bailey <Bailey@access-board.gov> wrote:

> -1, as I am distressed that we are not addressing normative issues left
> over from 2.0:
>
>
> http://github.com/w3c/wcag/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+label%3A%22WCAG+2.2%22+label%3A%22Normative%22
>
>
>
> With regard to Willco’s middle item below, it is the first time that I
> have noticed this change, but I am a big fan actually!  When I do my own
> “Introduction to WCAG” type trainings, it is always a stumbling block to
> have “Guidelines” as the title, a major heading, and then as the middle
> tier between Principles and Success Criteria.
>
> http://www.w3.org/TR/WCAG20/#title
>
> http://www.w3.org/TR/WCAG20/#guidelines
>
> http://www.w3.org/TR/WCAG20/#text-equiv
>
>
>
>
>
> *From:* Andrew Kirkpatrick <akirkpat@adobe.com>
> *Sent:* Tuesday, February 4, 2020 2:05 PM
> *To:* Wilco Fiers <wilco.fiers@deque.com>; Alastair Campbell <
> acampbell@nomensa.com>
> *Cc:* WCAG list <w3c-wai-gl@w3.org>
> *Subject:* Re: CFC - Publication of WCAG 2.2 FPWD
>
>
>
> Wilco,
>
> For the first item, this was the change that was agreed to by the working
> group for the SC and is in the editor’s draft as a result. Whether you
> agree with this change is independent of agreeing to send the draft
> document out for public comment. If the WG gets lots of comments back that
> switching the SC from AA to A is problematic then we will consider that,
> but the change is already agreed to in the draft.
>
>
>
> For the latter item, when we published WCAG 2.1 we integrated the errata
> from WCAG 2.0 into the draft. The official language of each WCAG 2.0 and
> WCAG 2.1 SC is the version in the official recommendation, plus any errata,
> but errata create problems for people to understand the SC as some people
> don’t consider them. Many people have requested that errata be incorporated
> into later versions and that has been WG practice.
>
>
>
> Hope this helps…
>
>
>
> Thanks,
>
> AWK
>
>
>
> Andrew Kirkpatrick
>
> Head of Accessibility
>
> Adobe
>
>
>
> akirkpat@adobe.com
>
> http://twitter.com/awkawk
>
>
>
> *From: *Wilco Fiers <wilco.fiers@deque.com>
> *Date: *Tuesday, February 4, 2020 at 12:44 PM
> *To: *Alastair Campbell <acampbell@nomensa.com>
> *Cc: *WCAG <w3c-wai-gl@w3.org>
> *Subject: *Re: CFC - Publication of WCAG 2.2 FPWD
> *Resent-From: *WCAG <w3c-wai-gl@w3.org>
> *Resent-Date: *Tuesday, February 4, 2020 at 12:43 PM
>
>
>
> -1
>
> I have a few concerns with this draft:
>
> - I noticed 2.4.7 was changed from Level AA to Level A. I apologies if I
> missed the conversation on this. It's a little hard participating in this
> group without attending the calls, but I try. I've brought this up in the
> past though, and I want to repeat my concern. I do not think WCAG should
> change existing success criteria in new versions. If AG agrees a change is
> necessary, I think an errata is the right way to do this. (Please let me
> know if you'd like me to explain this further.)
>
> - The "success criterion" (and "guideline") text was removed from the
> headings. This creates a document that is no longer explicit about what
> things are success criteria. If we're removing this from the heading (which
> I'm not against), we'll need to add a definition of success criterion, or
> some normative section that says what is and what isn't a success
> criterion.
>
> - In 1.4.13 the word "Dismissable" was changed to "Dismissible". Similar
> to my first comment, a change like that should in my opinion be done in an
> errata, not in a new working draft. Otherwise it creates different
> variations of the same success criterion between different versions of WCAG.
>
>
> W
>
>
>
> On Tue, Feb 4, 2020 at 3:47 PM Alastair Campbell <acampbell@nomensa.com>
> wrote:
>
> Call For Consensus - ends Thursday 6th February at 11am Boston time.
>
>
>
> This call is to approve the publication of WCAG 2.2 as the First Public
> Working Draft.
>
>
>
> The current draft is available here:
>
> https://w3c.github.io/wcag/guidelines/22/
> <https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fw3c.github.io%2Fwcag%2Fguidelines%2F22%2F&data=02%7C01%7Cbailey%40access-board.gov%7Cff93085f2d854a0f63a108d7a9a54ae0%7Cfc6093f5e55e4f93b2cf26d0822201c9%7C0%7C0%7C637164399711972709&sdata=TDdS5jQ6%2BPbz%2BmHBzFMIlYRhKII9Jo3pcVxhA%2FvKQHQ%3D&reserved=0>
>
>
>
> The approach for WCAG 2.2 is to add only the items that have been agreed,
> and so far the Working Group has agreed to include Focus Visible (Enhanced)
> to the WCAG 2.2 working draft:
>
> https://lists.w3.org/Archives/Public/w3c-wai-gl/2020JanMar/0000.html
> <https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.w3.org%2FArchives%2FPublic%2Fw3c-wai-gl%2F2020JanMar%2F0000.html&data=02%7C01%7Cbailey%40access-board.gov%7Cff93085f2d854a0f63a108d7a9a54ae0%7Cfc6093f5e55e4f93b2cf26d0822201c9%7C0%7C0%7C637164399711982663&sdata=shcWyzUSOxXv%2FCgsqotjGjp4G0RsWuTz23OG4NMeuMo%3D&reserved=0>
>
>
>
> Future decisions / CFCs would add more to the working draft, but this CFC
> is about permission to publish this first version.
>
>
>
> 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
>
> --
>
> www.nomensa.com
> <https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.nomensa.com%2F&data=02%7C01%7Cbailey%40access-board.gov%7Cff93085f2d854a0f63a108d7a9a54ae0%7Cfc6093f5e55e4f93b2cf26d0822201c9%7C0%7C0%7C637164399711982663&sdata=xNbexTl5kN%2FyRiL4inmFN120r4SyQQe7hMHpmw69yzQ%3D&reserved=0>
> <http://www.nomensa.com/
> <https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.nomensa.com%2F&data=02%7C01%7Cbailey%40access-board.gov%7Cff93085f2d854a0f63a108d7a9a54ae0%7Cfc6093f5e55e4f93b2cf26d0822201c9%7C0%7C0%7C637164399711982663&sdata=xNbexTl5kN%2FyRiL4inmFN120r4SyQQe7hMHpmw69yzQ%3D&reserved=0>>
> / @alastc
>
>
>
>
> --
>
> *Wilco Fiers*
>
> Axe for Web product owner - Co-facilitator WCAG-ACT - Chair ACT-R
>
>