Re: WCAG 2.2 status update

Alastair,
Refer:  Understanding Accessible Authentication: It needs  an editorial  fix.
https://raw.githack.com/w3c/wcag/3e05c24b9f1ef2d3538aa3ee8c14f1ca841c916b/understanding/22/accessible-authentication.html

All headings following the 'Intent' reference 'Focus Visible' instead
of 'accessible authentication'.
Thanks,
Sailesh




On 3/27/20, Alastair Campbell <acampbell@nomensa.com> wrote:
> Hi everyone,
>
> This is hopefully the final status update for the WCAG 2.2 as pre-approved
> drafts, after this we’ll be dealing with CFCs and github comments.
>
> We have two which appear to be pretty much ready but we need approval, up on
> Tuesday:
>
>
>   *   Touch target spacing: We updated that in the meeting on Wednesday, but
> the Mobile TF suggested some updates:
> https://docs.google.com/document/d/1sszSUKB8t3VuRzxHtOjLfQZjNYCw-xr_EbuMwW7WiGc/edit#heading=h.7sa7n7yr2ykk
>
>   *   Visual Indicators (to progress): Has been updated, re-review needed:
> https://docs.google.com/document/d/1WhZAbswvPHs7A3stfqM_ATsaBHPeGbHtARcmaKMck1U/edit<https://docs.google.com/document/d/1WhZAbswvPHs7A3stfqM_ATsaBHPeGbHtARcmaKMck1U/edit#heading=h.y476ttrsa0b5>
>
> We have a few which are approved from an SC point of view, pending updates
> to the understanding/technique documents:
>
>
>   *   Hidden controls: Approved (in meeting) SC:
> https://www.w3.org/2020/02/11-ag-minutes.html#item02
> New technique to approve.
>   *   Find help: Approved (in meeting) the SC:
> https://www.w3.org/2020/03/17-ag-minutes.html#item05
> Needs a fleshed out technique.
>   *   Fixed Reference Points: Approved (in meeting) the SC:
> https://www.w3.org/2020/03/25-ag-minutes.html#item04
> Has an updated technique.
>   *   Error correction (Processes): Approved (in meeting) the SC:
> https://www.w3.org/2020/03/25-ag-minutes.html#item03
> Needs a fleshed out technique.
> Please do review the above and comment in the documents if you have
> editorial suggestions.
>
> We are creating pull requests prior to CFC for:
>
>
>   *   Information in steps
> Note – we approved a definition for “steps” that will be applied to this SC
> as well.
>   *   Dragging
> SCs that hit problems:
>
>   *   Icon Description: Was reviewed on the 7th Jan:
> https://www.w3.org/2020/01/07-ag-minutes.html#item06
> There does not seem to be a good way of achieving this on touch-screen
> devices, in a way that doesn’t make the interaction worse in some
> circumstances.
>   *   Visible labels & Orientation: were thought to be possible to cover
> with understanding/technique updates.
>   *   Custom interactions: It is really difficult to define what a ‘custom
> interaction’ actually is. A lot of the problematic ones are ‘standard
> interactions’ (e.g. swipe gesture) but with an unexpected result. This is
> deferred, more research needed.
> https://www.w3.org/2020/03/24-ag-minutes.html#item01
>
> SCs approved:
>
>   *   Accessible authentication: CFCed and ready to merge:
> https://github.com/w3c/wcag/pull/1037
>   *   Focus visible (enhanced): Part of FPWD.
> Kind regards,
>
> -Alastair
> --
> www.nomensa.com<http://www.nomensa.com/> / @alastc
>


-- 
Sailesh Panchang
Principal Accessibility Consultant
Deque Systems Inc
381 Elden Street, Suite 2000, Herndon, VA 20170
Mobile: 571-344-1765

Received on Tuesday, 31 March 2020 14:24:44 UTC