-
Notifications
You must be signed in to change notification settings - Fork 290
2025‐06‐13
Attendance (9): Alastair Campbell, Bruce Bailey, Ken Franqueiro, Giacomo Petri, Filippo Zorzi, Francis Storr, Gunduala Neuman, Mike Gower, Patrick Lauke
Regrets: Lori Oakley, Dan Bjorge, Steve Faulkner, Scott O'Hara
- WCAG 2 Issues (feedback due by 20 June) are first item on the agenda for the Tuesday AGWG call. Items are listed below but were not addressed on the call as a set.
- Per agenda email, some updates from Ken and then using our standing agenda.
Use of GitHub for generating WCAG, WAI, and W3C pages continues to mature, especially with respect to the current material. WCAG 2.1, 2.2, and supporting content published to W3.org/WAI are now fully managed via GitHub and our repo. The older content, namely WCAG 2.0 and TR-path 2.0 specific content, is copied into the GitHub repo and contains a fair amount of legacy coding from the previous publication system. Adding to the cruft is that the build process did not catch files deleted from the gh-pages working branch. In addition to the PR items following, Ken is doing other cleanup chores so there are fewer spurious files and directories, and that will be improving over time.
- Clean out unused Techniques and Understanding pages/images from gh-pages branch #4437 includes a description of this sort of maintenance.
Ken has added some automated tests to flag certain errors, such as uploading a video. The new tests have customized error, for example listing the directory which should be used for videos.
There are also a few older Technical Reports which are in our repo but not under development by AGWG.
If your PR generates a failure that seems spurious and is preventing merging, please ping Ken or Kevin, as only admins can bypass these new warnings.
For more details, please see:
Ken solicited feedback on a warning banner that preview builds are not finalized guidance.
- Mike has been working on Add new errata to both 2.1 and 2.2 #4370 which is not controversial and something we have discussed before.
- PR 4370 is now the clean set of errata that are actually new, as opposed to previously approved errata that was accidentally missed.
- Before this new errata could go to CFC, W3C first needed to republish 2.1 errata which omitted a few items. See Update errata/21.html for previous publications #4424.
Ken also has confirmation that very trivial edits, such as closing a tag, can be directly merged at the discretion of the TF. This is very sensible, as these sort of syntax corrections are invisible and have no effect on the page.
-
Briefly discussed Editorial: "Web" to "web", "Success criteria" to "success criteria" #4428 is nominally straightforward enough, but is an intimidatingly large number of files. It also mixes in a few TR path documents which we will want to split out to a separate PR. Mike also wants to double check with EO as there is some nuance around Web being shortened form of World Wide Web.
- From style guide for web capitalization (updated March 2025 to match W3C-wide style):
- web - lowercase when used by itself, including as an adjective (such as "web accessibility", "web page", "web application") and a noun ("making the web accessible"),
- Web - capitalize in proper names and titles such as Web Content Accessibility Guidelines, World Wide Web Consortium, Web Consortium, World Wide Web.
- Stays in For Discussion for now.
- From style guide for web capitalization (updated March 2025 to match W3C-wide style):
-
Briefly discussed Tweak understanding for 1.2.3 and 1.2.5 #1790 which we covered last week. We should be able to close after Friday after related PRs are merged. Stays in For Discussion for now.
-
Discussed Update abbreviation.html #4440 and noted that the visual ambiguity introduced by the color formatting (circa 2.1 publication) is consistent with WCAG 2.0 source code. It might be prudent to wait until WCAG2ICT is republished, as their TF work has surfaced other long-standing idiosyncrasies. Stays in For Discussion for now.
- Discussed Add note about logo/logotypes contrast to 1.4.3, 1.4.6, and 1.4.11 understanding #4402 which Patrick has tweak to add example of border as one way to give UIC 3:1 contrast. Patrick also got some feedback on referencing defined terms versus emphasis. Suggestion made to reuse example from logotype section.
- We discussed yellow-on-white (as part of logo) as with M in McDonalds (see bottom of page, not a link but for sake of the argument, assume it is). It is essential (from a business branding perspective) that the yellow background of footer exactly match the yellow in logo. With this example, if the logo were a button, would a thin dark border on rounded square wreck aesthetics?
Bruce noted question raised on listserv regarding SC 1.3.5 Identify Input Purpose. There was consensus that online discourse was resolved, sufficiently discoverable, and didn't warrant an update to Understanding.
Francis shared that he working on some status messages techniques. He noted that Patrick's excellent Why aren’t my live regions working article didn't test the marquee role. As one of the “potential future techniques” for the marquee role, Francis built a prototype. As far as Francis can tell, there’s no support for it, but maybe not, and regardless welcomes feedback.
These were not directly addressed during this call. Feedback from AGWG is due June 20th. The following outlines the updates proposed and implemented by the WCAG 2 Task Force, providing a two-week window for Working Group members to review non-normative WCAG 2 updates, and consists of changes in several categories.
Changes that do not meaningfully alter informative language in a normative document.
None this cycle.
Changes that meaningfully add or alter existing non-normative guidance.
Audio description failure technique #4390
Small improvements to language intended to clarify existing guidance.
Suggested additional note for focus-not-obscured (AAA) #4403
Response-only items for which we are not going to create a PR.
Concern for use of "must" in notes. #4432
These are trivial editorial corrections such as typos and broken links.
Restore SCR21, marked as obsolete #4411