-
Notifications
You must be signed in to change notification settings - Fork 335
2025‐08‐01
Attendance (10): Bruce Bailey, Dan Bjorge, Steve Faulkner, Ken Franqueiro, Mike Gower, Patrick Lauke, Lori Oakley, Adam Page, Giacomo Petri, Francis Storr
Regrets: Alastair Campbell, Gundula Niemann,
- Reminder that WCAG 2 proposed changes (feedback due by 4 August) was on the agenda at the Tuesday AGWG call.
- WCAG2ICT editors draft anticipated for CFC soon. Please be on the lookout, and reserve some time for that. It has benefited from our TF work on Understanding documents for several SC. Publishing is to support EN 301 549 update. AAA SC and some other work still underway.
- Our usual standing agenda, per email.
Discussed Tweak language around modal dialogs #4381 and comment in discussion thread that the APG does not exactly align with Understanding. Adam offered to circle back to ARIA WG. There was not a request for us to change the PR. Returned to Sent for WG Approval.
Discussed Use "color vision deficiency" instead of "colorblindness" #4472 replacement made in six places. Shawna provided cite to EO wiki style guide around term "color blindness" and gave her +1. Returned to Sent for WG Approval.
Quickly discussed Correct link in pause-stop-hide.html #4456 fixing a minor bug. It was included with last batch Sent for WG Approval but has not attracted many thumbs up. Kept in Sent for WG Approval.
Quickly discussed Add a "don't clear form fields on a submission error" example to 3.3.7 #4372 and good minor edit made during call. Kept in Sent for WG Approval.
Mike raised 1.4.11 Non-text contrast understanding doc references placeholder as a passing technique, despite it being a transient state #4413 which warrants some consideration. When is low contrast placeholder text permitted? Does Understanding permit "redundant" information having low contrast? Similar to tension between LV needs and visually conveying that a field is inactive. Francis noted there is a new CSS property for text caret inside form fields, so we probably want an updated technique to use that. Giacomo raised floating labels as interesting since they can have good contrast. Dan concurs CSS property as not being sufficient technique. Also, this issue is about when an input field does not have focus.
Discussed Reimplement associated techniques as data #4509 Ken working on a way to automate "related links" Prompted wcag.json is a mess #4393. TF members encouraged to review changes to techniques pages and weigh in if anything seems like it might be going too far. Discussed why implementing as Front Matter was not a sufficient approach. Concern raised that change log for a particular Understanding document will not reflect new or revised association. Ken will add pros/cons of three different possible approaches. Staying in Drafted to provide TF additional time to review.
Discussed Add missing meta charset and remove editors stylesheet at build time #4513 which supersedes add meta charset to all techniques #4506 which Ken spotted only after Francis started his PR. Ken's approach makes correction in the build process (rather than patching 500+ file). Closed 4506 in deference to 4513. In the future, if any TF member notes wide scale defect, please ping Ken. During call, Ken double checked that Language of Parts informative docs were included. Moved to Ready for Approval.
Briefly discussed discussed Remove links to too old Editor's Draft in Understanding SC 4.1.2 #4261 and Accessible Name reference in particular. Current editors draft actively being worked on. Ken will check 1.2 is best version to reference. Moved to Read for Approval.
Discussed G224: fix two typos and a broken link #4512 which fixes a few typos in G224. Moved to Ready for Approval.
Discussed Update F3 #1035 which proposes to update F3 by removing the word "important" in particular. Dan noted that there are ways to associate text alternatives with CSS - but not CSS background. Concern remains for wording. We considered changing "important" to "not decorative" to more closely tract to normative phrasing, but that approach has similar difficulty. Giacomo pointed out that repetitive links are still important (at least one of them). Currently response only. Not a problem for a failure to be stricter than requirement. Item for WCAG3 task. Mike will tweak response. Kept in Drafted.
Discussed Technique ARIA14: Replacing “invisible label” with “accessible name” #4482 which we also discussed a couple weeks back. Change fixes one earlier problem, but now introduces new implication that ARIA label can be used arbitrarily. Giacomo suggested citation to ARIA spec with regard to what cannot be labeled. Patrick will double check. Needs another review then Ready for approval.
Discussed Minimum bounding box and line wrapping - unclear definition #3376 to which a few more visuals illustration for target have been added. Dan and Mike are still discussing exception for inline links via email. The general idea it that hypertext is exempted. Stays in Drafted.