Re: WCAG 2.2 status update

Bruce writes:

> make a go / no-go decision on making (mild-but-normative) corrections to
phrasing used by WCAG 2.0 in 2.2.

Bruce, can you provide an example?

I for one am extremely nervous about making *any* normative changes that
would have a backward impact on WCAG 2.0. However, if the envisioned
changes are ONLY 'editorial' in nature (grammer, phrasing, etc.) then the
change would be just that: editorial, with no impact on the actual
requirement / outcome. My suspicion at this time is that it would need to
be on a case-by-case review.

My $0.02

JF

On Tue, Jan 7, 2020 at 9:40 AM Bruce Bailey <Bailey@access-board.gov> wrote:

> I would very much like for us to make a go / no-go decision on making
> (mild-but-normative) corrections to phrasing used by WCAG 2.0 in 2.2.  We
> already have plenty of work for 2.2, so there is that!  But it really feels
> to me like the song says:  “If you choose not to decide, you still have
> made a choice.”
>
>
>
>
>
> *From:* Alastair Campbell <acampbell@nomensa.com>
> *Sent:* Friday, January 3, 2020 12:31 PM
> *To:* WCAG list <w3c-wai-gl@w3.org>
> *Cc:* COGA TF <public-cognitive-a11y-tf@w3.org>; LVTF - low-vision-a11y <
> public-low-vision-a11y-tf@w3.org>; public-mobile-a11y-tf@w3.org
> *Subject:* WCAG 2.2 status update
>
>
>
> Hi everyone,
>
>
>
> Welcome back after the holidays, happy new decade!
>
>
>
> I thought I would start with a quick update on the status of the various
> WCAG 2.2 SCs.
>
>
>
> I’ve included all the new SCs below, and tried to highlight which need a
> re-evaluation. They are in order of when they will appear in the agendas
> <https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FWAI%2FGL%2Fwiki%2FUpcoming_agendas&data=02%7C01%7Cbailey%40access-board.gov%7Cfddd97c3f50643c3440d08d79072d9ce%7Cfc6093f5e55e4f93b2cf26d0822201c9%7C0%7C0%7C637136695276322877&sdata=BQQGUy7wUr0ohcH%2FUDw%2Bzobao7qp%2B%2B6XalSXDBD%2B4PA%3D&reserved=0>,
> so please do start at the top!
>
>
>
> For anyone shepherding an SC, please do look at the agendas
> <https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FWAI%2FGL%2Fwiki%2FUpcoming_agendas&data=02%7C01%7Cbailey%40access-board.gov%7Cfddd97c3f50643c3440d08d79072d9ce%7Cfc6093f5e55e4f93b2cf26d0822201c9%7C0%7C0%7C637136695276322877&sdata=BQQGUy7wUr0ohcH%2FUDw%2Bzobao7qp%2B%2B6XalSXDBD%2B4PA%3D&reserved=0>
> page and let me know if you won’t be around when your one(s) comes up.
>
>
>
> *Timeline*
>
>
>
> Time is now getting short, so our short-term aim is roughly:
>
>
>
>    - *January*: Approve (or not) in principle each SC text &
>    understanding doc. We’ll be rattling through them quickly, so if you have a
>    time to work through the surveys ahead of this week, please do!
>    - *February*: For those that make it through January, we then have Feb
>    to work on at least one technique for each.
>    - *March: *Refinement and approvals, the working draft will then go
>    for a wide review in early April.
>
>
>
>
>
> *SCs for review*
>
>
>
>    - *Dragging:* Up for 1st review Jan 7th:
>    https://www.w3.org/2002/09/wbs/35422/wcag22-dragging/
>    <https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2002%2F09%2Fwbs%2F35422%2Fwcag22-dragging%2F&data=02%7C01%7Cbailey%40access-board.gov%7Cfddd97c3f50643c3440d08d79072d9ce%7Cfc6093f5e55e4f93b2cf26d0822201c9%7C0%7C0%7C637136695276322877&sdata=hZDpYeYteuiZKcQuYpk4W7CFRYD34x6bYMSxUFpXNaQ%3D&reserved=0>
>    - *Visual indicators*: Last reviewed 17th Dec:
>    https://www.w3.org/2019/12/17-ag-minutes.html#item03
>    <https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2019%2F12%2F17-ag-minutes.html%23item03&data=02%7C01%7Cbailey%40access-board.gov%7Cfddd97c3f50643c3440d08d79072d9ce%7Cfc6093f5e55e4f93b2cf26d0822201c9%7C0%7C0%7C637136695276332834&sdata=MnuZRcT%2FBqaak2ZFBWylcAPAKTqCDk4QRlOT30IIw8Y%3D&reserved=0>
>    Need to have David (author) present. Up for this Tuesday (7th),
>    overall we weren’t sure about the scope & overlap with user-agent side.
>    https://www.w3.org/2002/09/wbs/35422/Visual_indicators/
>    <https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2002%2F09%2Fwbs%2F35422%2FVisual_indicators%2F&data=02%7C01%7Cbailey%40access-board.gov%7Cfddd97c3f50643c3440d08d79072d9ce%7Cfc6093f5e55e4f93b2cf26d0822201c9%7C0%7C0%7C637136695276332834&sdata=PvALguJMXaN8gpuZJPC3b%2FevUAxUZl8%2Ftq1x%2BCWOD2c%3D&reserved=0>
>    - *Icon Description*: Has been updated after previous reviews, up for
>    the 7th Jan meeting:
>    https://www.w3.org/2002/09/wbs/35422/icon-desc-acceptance/
>    <https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2002%2F09%2Fwbs%2F35422%2Ficon-desc-acceptance%2F&data=02%7C01%7Cbailey%40access-board.gov%7Cfddd97c3f50643c3440d08d79072d9ce%7Cfc6093f5e55e4f93b2cf26d0822201c9%7C0%7C0%7C637136695276342804&sdata=%2BkXmjQR7TNxfDLfnMb02jcnjwLcOz88c36cYzJSHu9E%3D&reserved=0>
>
>    - *Accessible authentication:* Overhauled to focus on the cognitive
>    aspects after Dec 10th, all previous comments are essentially out of
>    date, please re-evaluate:
>    https://www.w3.org/2002/09/wbs/35422/accessible-auth/
>    <https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2002%2F09%2Fwbs%2F35422%2Faccessible-auth%2F&data=02%7C01%7Cbailey%40access-board.gov%7Cfddd97c3f50643c3440d08d79072d9ce%7Cfc6093f5e55e4f93b2cf26d0822201c9%7C0%7C0%7C637136695276342804&sdata=pN%2BPzvNuFNeCswLZEHSNbl8tAoa6%2FvUtMmLtTePph0Q%3D&reserved=0>
>    It needs someone to write a simple technique. (NOT implementation or
>    working example, just a short ‘how to’ explanation.)
>    - *Important controls:* Overhauled by Rachael, Bruce & MichaelG, it
>    now focuses on the visual aspect and uses a new definition of ‘prominent’.
>    All previous answers are now out of date, please re-evaluate:
>    https://www.w3.org/2002/09/wbs/35422/essential-controls/
>    <https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2002%2F09%2Fwbs%2F35422%2Fessential-controls%2F&data=02%7C01%7Cbailey%40access-board.gov%7Cfddd97c3f50643c3440d08d79072d9ce%7Cfc6093f5e55e4f93b2cf26d0822201c9%7C0%7C0%7C637136695276352755&sdata=oxodKIvOVLExoT58IicmcxKhBtIqkycskovSZ%2BO2jb8%3D&reserved=0>
>    It needs someone to write a simple technique.
>    - *Touch target spacing: *Updated by Kathy & Mobile task force to
>    enforce a minimum size+spacing. Need to establish if the approach has
>    support and then work on understanding/technique docs, please
>    re-evaluate:
>    https://www.w3.org/2002/09/wbs/35422/target-spacing/
>    <https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2002%2F09%2Fwbs%2F35422%2Ftarget-spacing%2F&data=02%7C01%7Cbailey%40access-board.gov%7Cfddd97c3f50643c3440d08d79072d9ce%7Cfc6093f5e55e4f93b2cf26d0822201c9%7C0%7C0%7C637136695276352755&sdata=uMPMLLdDr%2BRgdH7NPmf6ELCBBRBisnKnm1BtuniZ5KE%3D&reserved=0>
>    - *Information in steps:* Reviewed on Dec 3rd:
>    https://www.w3.org/2019/12/03-ag-minutes.html#item01
>    <https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2019%2F12%2F03-ag-minutes.html%23item01&data=02%7C01%7Cbailey%40access-board.gov%7Cfddd97c3f50643c3440d08d79072d9ce%7Cfc6093f5e55e4f93b2cf26d0822201c9%7C0%7C0%7C637136695276352755&sdata=LISuyuCdGSyu%2BN9xv1B8yNCz2zbMRM2sUuoy5Ms%2FI1I%3D&reserved=0>
>    Needs an update (with DavidF) to ensure the comments are addressed,
>    and down to one version for review.
>    https://www.w3.org/2002/09/wbs/35422/info-in-steps/
>    <https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2002%2F09%2Fwbs%2F35422%2Finfo-in-steps%2F&data=02%7C01%7Cbailey%40access-board.gov%7Cfddd97c3f50643c3440d08d79072d9ce%7Cfc6093f5e55e4f93b2cf26d0822201c9%7C0%7C0%7C637136695276362715&sdata=rLP7iw5Ip0QjMNB16ZDejKYDmR8QxNkwSOx6jH51dQY%3D&reserved=0>
>    - *Fixed Reference Points: *Reviewed Dec 3rd:
>    https://www.w3.org/2019/12/03-ag-minutes.html#item02
>    <https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2019%2F12%2F03-ag-minutes.html%23item02&data=02%7C01%7Cbailey%40access-board.gov%7Cfddd97c3f50643c3440d08d79072d9ce%7Cfc6093f5e55e4f93b2cf26d0822201c9%7C0%7C0%7C637136695276362715&sdata=aJ8KYbmbkakl9cJM0G1OYyq1TZRPQwNhT2OuoRSJmF8%3D&reserved=0>
>    Has since been updated to use “explicit navigation markers”, please
>    re-evaluate:
>    https://www.w3.org/2002/09/wbs/35422/page-break-nav/
>    <https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2002%2F09%2Fwbs%2F35422%2Fpage-break-nav%2F&data=02%7C01%7Cbailey%40access-board.gov%7Cfddd97c3f50643c3440d08d79072d9ce%7Cfc6093f5e55e4f93b2cf26d0822201c9%7C0%7C0%7C637136695276372678&sdata=VrOMLZjgFFRbYPacWQJBfDbr7rRPkn7eoAjMIAel%2FaE%3D&reserved=0>
>    - *Find help*: Reviewed Dec 10th:
>    https://www.w3.org/2019/12/10-ag-minutes.html#item04
>    <https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2019%2F12%2F10-ag-minutes.html%23item04&data=02%7C01%7Cbailey%40access-board.gov%7Cfddd97c3f50643c3440d08d79072d9ce%7Cfc6093f5e55e4f93b2cf26d0822201c9%7C0%7C0%7C637136695276372678&sdata=CCxhDdvtA%2F6wjVRFD8Ij%2Bn%2Bk0F9dKKhD9QCJ8Nl4dEo%3D&reserved=0>
>    Has since been updated, please re-evaluate:
>    https://www.w3.org/2002/09/wbs/35422/findable-help/
>    <https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2002%2F09%2Fwbs%2F35422%2Ffindable-help%2F&data=02%7C01%7Cbailey%40access-board.gov%7Cfddd97c3f50643c3440d08d79072d9ce%7Cfc6093f5e55e4f93b2cf26d0822201c9%7C0%7C0%7C637136695276382629&sdata=XgAd88a76Wb3pcBMIZP167hoJ4WmLKfeJdmDNnjRKgM%3D&reserved=0>
>    - *Confirmation before submission:* Reviewed Dec 10th:
>    https://www.w3.org/2019/12/10-ag-minutes.html#item03
>    <https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2019%2F12%2F10-ag-minutes.html%23item03&data=02%7C01%7Cbailey%40access-board.gov%7Cfddd97c3f50643c3440d08d79072d9ce%7Cfc6093f5e55e4f93b2cf26d0822201c9%7C0%7C0%7C637136695276382629&sdata=8nFO4xtJv5j2EEr2ajiWapTv8hveDbclgqTKR9%2BWMZo%3D&reserved=0>
>    I think it needs some updates before another review (SteveL). Previous
>    results:
>
>    https://www.w3.org/2002/09/wbs/35422/wcag22-confirm-before-submission/results
>    <https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2002%2F09%2Fwbs%2F35422%2Fwcag22-confirm-before-submission%2Fresults&data=02%7C01%7Cbailey%40access-board.gov%7Cfddd97c3f50643c3440d08d79072d9ce%7Cfc6093f5e55e4f93b2cf26d0822201c9%7C0%7C0%7C637136695276382629&sdata=kkArqadOKnXhFZLVTLeO73Kp2HIiEH%2BJsaCwsJXdY98%3D&reserved=0>
>    - *Custom interactions*, reviewed Dec 17th:
>    https://www.w3.org/2019/12/17-ag-minutes.html#item04
>    <https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2019%2F12%2F17-ag-minutes.html%23item04&data=02%7C01%7Cbailey%40access-board.gov%7Cfddd97c3f50643c3440d08d79072d9ce%7Cfc6093f5e55e4f93b2cf26d0822201c9%7C0%7C0%7C637136695276392578&sdata=5qrHS70Kg9k6MO84Eb9gqTdu4EBeRPhmINRMFO6fZqs%3D&reserved=0>
>
>    Some big questions left open about whether the interaction is the
>    problem, or the expectation of the interaction. Would really like people to collect
>    examples of a non-standard interactions (anyone, not just Jake!)
>    Survey: https://www.w3.org/2002/09/wbs/35422/Custom_interactions/
>    <https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2002%2F09%2Fwbs%2F35422%2FCustom_interactions%2F&data=02%7C01%7Cbailey%40access-board.gov%7Cfddd97c3f50643c3440d08d79072d9ce%7Cfc6093f5e55e4f93b2cf26d0822201c9%7C0%7C0%7C637136695276392578&sdata=ryuJqaLFo8cSfy1ULkDMu78OM4YSSSsatnGrOjAa4xU%3D&reserved=0>
>    - *Focus visible (enhanced):* CFC approved, will be included in the
>    working draft soon. Post-approval comments in github.
>    - *Visible labels* & *Orientation:* were thought to be possible to
>    cover with understanding/technique updates.
>
> 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%7Cfddd97c3f50643c3440d08d79072d9ce%7Cfc6093f5e55e4f93b2cf26d0822201c9%7C0%7C0%7C637136695276402543&sdata=w5BjPPQAVFe0Yj47gXuUqEc2dU3aRAxl0C%2BpSyxQsjU%3D&reserved=0>
> / @alastc
>


-- 
*​John Foliot* | Principal Accessibility Strategist | W3C AC Representative
Deque Systems - Accessibility for Good
deque.com