RE: WCAG 2.x issues call, 1/26

My notes from today’s call follow.
Attendance (13):  Alastair Campbell, Bruce Bailey, Dan Bjorge, David Cox, Duff Johnson, Francis Storr, Giacomo Petri, Gundula Niemann, Lori Oakley, Mike Gifford, Patrick Lauke, Scott O’Hara, Theo Hale.
Regrets:  Mike Gower


  1.  For discussion
     *   Add two notes/clarifications to 2.1.1/2.1.3 understanding by patrickhlauke · Pull Request #1642<https://github.com/w3c/wcag/pull/1642> we discussed minor edits since last week and is Ready for approval.
     *   3.1.3 Unusual Words seems contradictory about words with "restricted" meaning · Issue #3606<https://github.com/w3c/wcag/issues/3606> discussion, status set to In progress.
     *   Add anti-aliasing note to 1.4.11 by patrickhlauke · Pull Request #3560<https://github.com/w3c/wcag/pull/3560> discussed and Ready for approval.
  2.  Drafted
     *   3.1.3 Unusual Words and neologisms/slang/made-up words · Issue #3591<https://github.com/w3c/wcag/issues/3591> discussed in conjunction with issue 3606 (above) and is In progress.
     *   Update accessible-authentication-minimum.html by bruce-usab · Pull Request #3309<https://github.com/w3c/wcag/pull/3309> Ready for approval but is not sufficient for closing 3.3.8/3.3.9: How is "authentication process" defined? · Issue #3264<https://github.com/w3c/wcag/issues/3264> which has its status reverted as To do.
     *   Remove technique H59 by patrickhlauke · Pull Request #2970<https://github.com/w3c/wcag/pull/2970> discussed and Ready for approval.
  3.  To do [skipped]
  4.  Open discussion:  Duff previewed the PDF Association work, see link below from email yesterday.

Please be encouraged to self-assign To do items and change status to In progress.

From: Bruce Bailey
Sent: Thursday, January 25, 2024 5:25 PM
To: WCAG 2.x issues list (public-wcag2-issues@w3.org) <public-wcag2-issues@w3.org>
Subject: RE: WCAG 2.x issues call, 1/26

Group, I will be watching the clock because I really do want to leave some time at the end of the call for open discussion.
In particular, I would like to spend a little time discussing recruiting additional resources.
I think a great example is the PDF Association’s forthcoming Techniques for accessible PDFs and how they propose support for findability.
Please see:  PDF techniques for accessibility: a new model<https://pdfa.org/pdf-techniques-for-accessibility-a-new-model/>.
Another example, from the U.S. federal sphere, is the ICT Testing Baseline for Web<https://ictbaseline.access-board.gov/01Keyboard/>.  Currently, that just pulls from Understanding.  The participants there will soon shift efforts to writing up new techniques.
Thanks,
Bruce

From: Bruce Bailey
Sent: Thursday, January 25, 2024 2:21 PM
To: WCAG 2.x issues list (public-wcag2-issues@w3.org<mailto:public-wcag2-issues@w3.org>) <public-wcag2-issues@w3.org<mailto:public-wcag2-issues@w3.org>>
Subject: WCAG 2.x issues call, 1/26

The WCAG 2 issues task force meets tomorrow (1/26) at our usual time (11:00am Eastern) and working on current issues<https://github.com/w3c/wcag/issues?q=is%3Aissue+is%3Aopen+label%3A%22WCAG+2.2%22+-label%3A%22Survey+-+Ready+for%22++-label%3A%22Survey+-+Added%22>.
You must be logged in for the Zoom link<https://www.w3.org/events/meetings/12f8250b-23af-4dc1-b25c-6285873846ce/20240119T110000/> and project board<https://github.com/orgs/w3c/projects/56> view.

We will be following our standing agenda:
  1.  Review ‘For discussion’ items (15 min).
  2.  Review ‘Drafted’ items (30 min), either:

  *   move back to In progress, with more work to do;
  *   move to Ready for approval, if there is general agreement the issue is sufficiently resolved; or
  *   leave in Drafted, if discussion was not concluded satisfactorily.
  3.  Review ‘To do’ (15 min).
  4.  Time permitting, items of interest to participants, including open discussions.

Regrets from Mike Gower I may be calling on assignees (if on the call) to characterize proposed file changes or to make brief notes the PRs or Issues that we discuss.

This task force process<https://github.com/w3c/wcag/wiki/WCAG-2-Task-Force-process> (among other information) is on the GitHub wiki.