-
Notifications
You must be signed in to change notification settings - Fork 487
2026–06–05
Kenneth G. Franqueiro edited this page Jun 5, 2026
·
1 revision
Attendance (12): Bruce Bailey, Lori Oakley, Filippo Zorzi, Francis Storr, Adam Page, Giacomo Petri, Baldino Morelli, Patrick H. Lauke, Ken Franqueiro, Steve Faulkner, Scott O'Hara, Jonny James
Regrets: Gundula Niemann
- Noting there have been a few comments so far on #5113 and #5133; will look in more detail next week
-
#5090: Add C40 (two-color focus) as sufficient for 1.4.11 Non-text contrast, make sufficient techniques for 1.4.11 situationally specific
- Also clarifies context under which C40 and several other techniques are sufficient
- Bruce suggested adding preceding sentence before procedure in G174, to be consistent with others
- Giacomo: This doesn't quite close #2575; I commented in 2022 that it is still possible to fail if the inner/outer borders happen to coincide with control and page background colors, respectively.
- Patrick: #5090 specifically tackles the part where it wasn't added
- Giacomo: Concerned this will spread an existing mistake under 2.4.7 also to 1.4.11
- Giacomo: Might be worth adding another note to clarify this situation
- Patrick: Let's open that as a separate issue to keep this PR focused
- Moved to Ready for approval
-
#5065: Expand 1.4.5 Images of Text benefits
- Benefits previously named who benefits but not how/why
- Some discussion over suggested edits on first bullet point
- Adam: This also makes the text machine-readable and thereby accessible to assistive technology; it can be wrapped in semantics. Seems weird that this was completely absent from benefits list
- Patrick: Somewhat of a parallel one; might be good as an additional note in a separate PR
- Bruce: Might also be worth a future note about cognitive benefits?
- Moved to Ready for approval
-
#4558: Total rewrite of example for SCR27
- Probably needs more rigorous testing first, leaving for a future meeting
-
#1159: Clarify whether SC 1.3.1 requires grouped links to be in a list structure
- Moved to Ready for approval
-
#5135: Add a non-normative explanation of "proper name" to 3.1.2 Language of Parts understanding
- The normative attempt did not go over well (perhaps unsurprisingly)
- There's already been some discussion on this PR as well
- Lori: What counts as a "product"?
- Further clarification by TF to correlate product to brand name
- Moved to Ready for approval
-
#5131: Add "also" to note about flashing content in 2.2.2 Pause, Stop, Hide understanding
- Clarifies that this is "in addition to", not "instead of"
- Also reorders 2.3.1 and 2.3.2 mentions to be in increasing numerical order (and A before AAA)
-
#5130: Add "also" to Note 1 for 2.2.2 Pause, Stop, Hide
- Akin to #5131 but for note within normative SC
- Bruce: Adding "also" seems less necessary here
- Adam: Possibly due to the significant difference in how this note is phrased compared to the informative one
- Giacomo: Question RE 4.1.3 that might warrant an issue?
- RE a multi-step process with a button being disabled upon submission, and displays a "Loading..." message, then becomes re-enabled and label reverts within 1 second
- Patrick: 4.1.3 is for things that happen elsewhere on the page; this is fine on 4.1.3 as screen readers will announce it
- Giacomo: NVDA does not announce the change of label; maybe this is an issue with NVDA
- Giacomo: Given that the control is disabled... the normative wording mentions "receiving focus"
- Adam: I've always interpreted "without receiving focus" as meaning "without needing to receive focus", i.e. the status message has to be deliverable without requiring the author to move focus to the thing
- Patrick: As opposed to e.g. a toast
- Giacomo: To me, announcing the disabled button seems more confusing than not announcing anything
- Patrick: I suspect screen reader users may have gotten accustomed to hearing this pattern