Meeting minutes
Agenda and Next Meeting
<Matt_King> Next meeting: April 4
Status of Site Updates
Review updates to first AT support table - pull request #2569
<Github> w3c/
github: w3c/
Matt_King: Victory! AT support tables for Button and Toggle Button are merged
Matt_King: Unfortunately, they aren't visible in the preview of the "main"branch
Alex_Flenniken: The link that you shared with me is an outdated deployment
Alex_Flenniken: here's the link to the active deployment https://
Matt_King: Ah, there it is. This is good news!
Matt_King: So our plan is that we will ask Shawn to do the publication to production on April 11
Matt_King: In the mean time, there's a lot that needs to go on to prepare for that launch
Matt_King: I'm having meetings with Apple and Vispero, preparing a blog post (hopefully getting a quote from Vispero and/or Apple), add support tables to the link, Alert, and Radio Button with Active Descendent example pages (I'll make a pull request for that soon)
Matt_King: Once we have all that lined up and receive a "Green light" from all of our stakeholders, we'll proceed with a **launch** on April 11 and and an **announcement** on April 13
Matt_King: I don't think we'll be deploying to production between then and now
About page ready for review - pull request 2558
github: w3c/
Matt_King: Just before this meeting, I added a link to the Netlify preview
Matt_King: https://
Andrea: At first glance, this looks good, visually
Matt_King: Among other things, we want to make sure reflow works correctly and that color contrast is acceptable.
Matt_King: The one thing that's different here is that we didn't use a "card" view for the "About" page. That was intentional (because we're not going to come up with graphics for each section)
Alex_Flenniken: That's right, Isaac Durazo didn't create icons or other graphics for each of these
Matt_King: Yeah, that's fine. We don't want to have to commit to distinct graphics for each of these things. Maybe we can in the future, if we want to spice it up...
Matt_King: I wonder if we want to use some generic icons in the future--if that would help. But I don't know what our visual library is like
Matt_King: if that all looks good to you, Andrea, then if you can submit a "GitHub Review" in the GitHub interface, that would be great
(the group worked through a confusing part of the GitHub.com user interface for code review)
Pull request reviews
PR 2625 - Tablist Examples: Improve support for magnification by jongund
github: w3c/
Matt_King: jongund isn't here today, but I'd like to assign some folks to review, if possible
Andrea: I can help out!
Andrea: I can do visual review and accessibility review
Matt_King: This is a really narrowly-scoped set of changes to CSS
Matt_King: I don't know if there's much of a code review to be done here
Alex_Flenniken: I can do the code review
(Matt_King updates the review checklist)
(Matt_King adds Andrea's account to the GitHub Team named "aria contributors" in order to authorize review)
Matt_King: I think that's all we can do for pull requests without jongund present
Date picker date selection issue
Matt_King: I'd like jongund to be present for this discussion, so let's defer this agenda item for next week
New Issue Action Planning
Button example's sample buttons lack visual focus indication
github: w3c/
Matt_King: This seems like a stunning find. Stunning in the sense that I can't believe we would have overlooked it
MarkMcCarthy: If I tab to the buttons, then I see nothing
Matt_King: How is that possible? We put "outline" to "none" and then did nothing...?
Matt_King: This seems like a pretty major oversight
Matt_King: I'm assuming we're overriding the default browser styling for focus
Alex_Flenniken: the issue seems to be happening between the APG and the WAI ARIA Practices repository
Matt_King: I expect there may be some styling in the template that is somewhat generic
Matt_King: I'll assign the issue to Carmen Cañas at Bocoup, then she can take of delegating this to someone at Bocoup
Matt_King: Looks like I can't do that right now. After this meeting, I will add Carmen's GitHub handle to the "aria contributors" GitHub Team and then assign this issue to her
<CurtBellew> It looks like there's no outline color set on those particular buttons. So I suspect outline color is inherited from somewhere else.
"HTML Source Code" for some examples is hard to visually parse
github: w3c/
(MarkMcCarthy explains the problem)
Matt_King: I agree that certain tags should be rendered inline with the surrounding text
MarkMcCarthy: This behavior is consistent across Chrome and Firefox in Windows and also on Safari in macOS
MarkMcCarthy: I don't think this particularly egregious in many places. It's perhaps ironically most noticible in the simpler examples. But in any case, I think we can put this in the backlog.
Matt_King: It feels a little agressive to call this a bug. I'm going to label it as an "Enhancement"
"About This Example" text is not always aligned properly
github: w3c/
Matt_King: Does this happen on every single example page?
MarkMcCarthy: No. It doesn't happen on Alert or Slider. It might just be the Button
MarkMcCarthy: It may depend on how much text precedes the list
Matt_King: It does have some of the smallest amount of text
Andrea: I see it, as well
Howard_Edwards: I see it, as well
Andrea: I'm seeing a negative value for a CSS margin which looks suspicious to me.
Alex_Flenniken: That margin comes from the template
MarkMcCarthy: But that doesn't appear to be the cause in and of itself
Howard_Edwards: It looks like the content above has been implicitly pushing down the list so that the bullets clear the graphic
<MarkMcCarthy> jugglinmike: not to suggest a structural change for a presentational problem, but if we wrapped the icon and intro text in a block level element, it may make it even easier to flow everything correctly
Matt_King: This feels like kind of a minor issue. Its coded as "bug" and "site design" right now
MarkMcCarthy: This is a little distracting, but not a big deal. I think we can keep it in the backlog as "low priority"
Matt_King: Okay, then we'll do that