Meeting minutes
Setup and Review Agenda
https://
<Jem_> https://
Jem_: Next meeting: March 4
Jem_: I will not be present at the next meeting
Jem_: Any requests for change to agenda?
jongund: Can we set aside some time to review color contrast?
Matt_King: Sure. Not during this meeting, though
Publication planning
Jem_: It's ready!
Matt_King: I saw that Remi added a lot of stuff to the branch that are not content changes
<Jem_> https://
Matt_King: I added a summary of the content changes
Matt_King: and I did a preview to make sure that those content changes are present
<Jem_> w3c/
Matt_King: There are 15 commits. Two are content, and everything else is the stuff that Remi did
Daniel: We're taking over; we just weren't sure of how things were in the past, but now we know
Daniel: Now that we're carrying over the content changes, we're doing our changes along with the content changes
Daniel: We'll be changing our process moving forward to keep these things separate in the future
Matt_King: Great. I think it's ready to go
Daniel: We'll publish what we have. What about the other things in the milestone?
Matt_King: I'll move those to a new milestone
PR 3412: Change dialog title heading elements from H2 to H1
github: w3c/
Matt_King: I took a quick look at this but didn't submit a review
Matt_King: I think we need someone to review this visually to determine whether or not we need to also make CSS changes
Jem_: I can do that
Matt_King: This impacts the headings inside the dialogs
Matt_King: e.g. the dialog for "Add Delivery Address"
Siri: Also "Verification Result"
Matt_King: And one with a heading that reads "End of the Road"
Jem_: I checked with the tag inspector and it is indeed H1
Matt_King: If I were to merge this today, do we want to add it to the release we've already prepared?
Daniel: I'm fine with that
Matt_King: I'll take another look at the actual diff before I merge it, but I'll plan to merge it
<CurtBellew> +1
Matt_King: Remember that this is not motivated by an accessibility concern. Rather, the generation logic is picking up H2 elements and inserting them into its table of contents.
Siri: Can we add a note to explain why we have made this change?
Siri: We usually don't use H1 elements like this
Matt_King: That sounds like a new issue: an issue discussing whether or not we recommend using H1 elements within the dialog pattern
Daniel: My initial impulse was to use H3 elements because those dialogs exist within specific sections
Daniel: We eventually stepped away from that justification, but I do agree that this would be good to discuss in a new issue
PR 3387: Clarify guidance for Focusability of disabled controls
github: w3c/
Matt_King: This is Adam_Page's pull request
Matt_King: I'm in the middle of reviewing it
Matt_King: I've already made a couple suggestions in the pull request. I hope they're good! It was kind of hard for me to review my own suggestions in the GitHub UI following some recent changes on that site
Matt_King: I was trying to soften up some of the language a bit more, and I have an idea for one more suggestion along those lines
Matt_King: It would be nice to get some other perspective on this pull request
Adam_Page: I've read your feedback, and I agree with all of it. I committed all the changes you suggested
Matt_King: There's a paragraph that reads, "In the APG, our examples have adopted the following" with a list of two items (the second having a bunch of sub-list items). Those two list items are worded in a definitive way. I'm thinking of aligning the wording of those list items with the wording of the text that precedes them
Jem_: I appreciate the directness of that wording
Matt_King: But the feedback is that we want to make sure the optionality is clear to readers
Adam_Page: I understand what you're getting at. There's an important rhetorical difference between "we did this" and "the reader should do this", and this change kind of mixes those two stances
Adam_Page: I'll take another pass with that in mind