-
Notifications
You must be signed in to change notification settings - Fork 266
2025‐01‐10
Attendance (13): Akash Shukla, Alastair Campbell, Bruce Bailey, Dan Bjorge, Filippo Zorzi, Francis Storr, Giacomo Petri, Gundal Neuman, Ken Franqueiro, Lori Oakly, Mike Gower, Patrick Lauke, Scott O'Hara, Akash Shukla
Regrets: n/a
- Welcome back, Happy New Year!
- PDF Association has published New Techniques for Accessible PDF
- We anticipate discussion on Disabled vs Read-only in near future (in context of SC 1.4.11 "except for inactive components"
- Mike and Alastair regrets next couple week
Per email
- Touch on scoping survey
- Touch on Reflow
- Then then following our standing agenda, working from the Project Board.
See discussion on Scope of WCAG 2.2 / 2.1 errata changes #4188, which does have a few down votes. There seems to be consensus about the changes (corrections) but concern with publishing errata versus versioned (e.g., 2.2.1) publication.
Chairs and staff are looking for path forward with options the different cases.
See Updated Reflow understanding doc #4055.
Covered some of the material last week, and Mike and Scott have talked between calls. Mikes goal would be to publish in the next 30 days.
Consensus from folks on call, that it's good to have a target date to work towards. Biggest bottleneck is with good illustrative images. We will want to give AGWG heads up now, as it's a long document to review.
Discussion about what to do if we don't have images for sections? Preference is to delete section, rather than some kind of "world in progress" placeholder images.
We won't be able to address every question someone could come up with. Work can continue, but Scott anxious to publish. Mike concerned for scope creep.
Gundala requests more complete treatment of large vertical viewpoints. Scott has one more comment/discussion to incorporate.
No other concerns for publishing.
4156
4125 needs closer review
3662 Mike has action item to split non-normative from changes that touch TR space.
3686 Overdue to be discussed on facilitators' call.
4104 Patrick had changes.
160
Update text-spacing.html #4125 difference between setting all version settings any per Understanding document. Alastair has suggested text in comment. Opening paragraph (intent) is wide and then second paragraph narrows to values used in SC. In context, proposed change is appropriate. Needs
1016 Suggestion for review to start with Alastair's comment. Needs review.
(2.5.8 Understanding origin of minimum "24" #4178)[https://github.com/w3c/wcag/issues/4178] -- Alastair thinks this has come up before. Bruce will look through closed issues to see if addressed. Scott recommends adding something to Understanding, since the question will come up again. Possible values to use are on a continuum.
4125 led to conversation asking if testing should be more prominent. Patrick notes that test steps won't be tech-agnostic, which is probably why they're not in the tech-agnostic-ish understanding