Re: WCAG 2.2 status update

Hi Alastair


Here's the URL for Page Break Locators... It's been simplified and
rewritten to address previous comments. It seems to have broad support from
epub and those with previous concerns.

https://docs.google.com/document/d/12Zn0_TGcqrM-L_wb0PIFHM4AnHJ64wPsucZyRGlf2Fg/edit?usp=sharing


Cheers,
David MacDonald



*Can**Adapt* *Solutions Inc.*

Tel:  613-806-9005

LinkedIn
<http://www.linkedin.com/in/davidmacdonald100>

twitter.com/davidmacd

GitHub <https://github.com/DavidMacDonald>

www.Can-Adapt.com <http://www.can-adapt.com/>



*  Adapting the web to all users*
*            Including those with disabilities*

If you are not the intended recipient, please review our privacy policy
<http://www.davidmacd.com/disclaimer.html>


On Wed, Feb 12, 2020 at 6:20 AM Alastair Campbell <acampbell@nomensa.com>
wrote:

> Hi everyone,
>
>
>
> A quick update from this week:
>
>
>
> *SCs recently updated:*
>
>
>
>    - *Hidden controls:* Updated the SC on the call yesterday:
>    https://www.w3.org/2020/02/11-ag-minutes.html#item02
>    and the understanding is updated:
>
>    https://docs.google.com/document/d/1DPtCqWHjrhj3QZ4afsqzmWDd-zMSf39RsMqSpR2QGCg/edit#
>    Need to flesh out a technique and then hopefully a quick approval
>    soon.
>    - *Touch target spacing: *Discussed yesterday and we agreed it would
>    be best to focus the SC text on 44px, rather than having a minimum
>    area+spacing with a different value:
>    https://www.w3.org/2020/01/21-ag-minutes.html#item03
>    David has tried re-wording:
>
>    https://docs.google.com/document/d/1ejG_7yaCI2xbEPqFZCbJgqGuu_kplEMtsO-XYJVbTkg/edit
>    It might still need some work on the SC text, and does need a firmer
>    understanding doc & technique.
>    - *Visual indicators*: There has been a side conversation about
>    scoping it to similar controls as Hidden controls, i.e. controls that
>    progress a process. Given the re-scoping, it seems suitable to bring back
>    to the group:
>
>    https://docs.google.com/document/d/1WhZAbswvPHs7A3stfqM_ATsaBHPeGbHtARcmaKMck1U/edit
>    https://www.w3.org/2002/09/wbs/35422/Visual_indicators/
>
> *Up for review in the next two weeks:*
>
>    - *Information in steps:* Agreed to proceed with the SC text on the
>    28th:
>    https://www.w3.org/2020/01/28-ag-minutes.html#item02
>    Need a technique, then we can create PR to integrate.
>    - *Fixed Reference Points: *Reviewed Jan 28th:
>    https://www.w3.org/2020/01/28-ag-minutes.html#item04
>    It seemed that making it more specific to page numbers from a paper
>    publication would be more appropriate, if that is updated quickly it
>    could be re-reviewed.
>    - *Dragging:* Was reviewed Jan 7th, and since then some examples have
>    been found & put forward, so it does appear to be feasible. There are still
>    comments from the review that need updating in the doc.
>    https://www.w3.org/2002/09/wbs/35422/wcag22-dragging/
>    - *Confirmation before submission:* Reviewed Dec 10th:
>    https://www.w3.org/2019/12/10-ag-minutes.html#item03
>    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
>    - *Custom interactions*, reviewed Dec 17th:
>    https://www.w3.org/2019/12/17-ag-minutes.html#item04
>    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!). some have been collected, but
>    only one ‘failing’ example at the moment.
>
>    https://docs.google.com/document/d/13QWLthBoEU6xuJQ4UrYOwuvJp0a42Z70JRjAsjtv1m4/edit#
>
>
>
> *SCs that hit problems, not scheduling for re-review:*
>
>    - *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.
>
> *SCs approved:*
>
>    - *Accessible authentication:* Approved on a call, need a review of
>    the PR and CFC:
>    https://github.com/w3c/wcag/pull/1037
>    - *Focus visible (enhanced):* CFC approved, will be included in the
>    working draft soon. Post-approval comments in github.
>
> Kind regards,
>
>
>
> -Alastair
>
> --
>
> www.nomensa.com / @alastc
>