Meeting minutes
Canceling next week's meeting
Matt: I have conflicts. Next meeting would be on the 28th
Publication planning
Matt: We did complete publication in December, thank you for people who reviewed
… We got three changes, we didn't get to the high contrast practice
… I created a milestone for February, we have to set a date
… I want to make sure we get comfortable enough for the contrast guidance
… I am proposing the 25, last Tuesday
Daniel: Good from our perspective
Jon: There is asynch issue, I made some updates to dark light and I don't see they aree updated in the preview
… I'll be around the rest of the meetings this month
Matt: I am going to adjust the milestone to the 25. Right now there are two things: for some we will be adding some stuff
… There are WIP things, so we'll end up with four or five
PR 3194 - Grid and table properties practice editorial fix
Matt: This needs a reviewer. A first time contributor submitted it, seems legit
… In the grid and tables property example there's is a misplaced attribute that should be inside the tag
Adam: Glad to do that
Matt: Will assign you, Adam
PR 2991 - Practice Page for Supporting High Contrast
Matt: Jon, you made a lot of commits last week of December
… But the preview isn't building
Jon: I also made some more changes last week and they're not coming through either
Matt: Looks like you addressed all of Adam's feedback and Adam approved
Matt: Some of the checks are failing, maybe this is affecting the build
Matt: Last change you made, all checks passed.
Matt: I know there is some kind of trick to get the other repo to re-build,
Mike: I can bring this to Howard's attention
Matt: Howard can take care of this
Matt: Also, there was editorial work that I wanted to do but I didn't get done, maybe I should complete this before having people look at this again
Jon: Changes just updated the light dark to use the light dark function
Matt: I just wanted to be as stable as possible. We did have other people who were assigned but didn't get to it yet
… Let's aim for getting all the changes in there before the next meeting so that we can trigger another review round afterwards
Mike: Howard may be able to join us
Issue 3174 - Multi-thumb slider hover ring
Matt: Could anyone take this on with a PR? Howard made an analysis and it seems pretty straightforward
arigilmore: I can assign myself
Issue 3211 - Labeling tablist
Matt: Related to feedback from Mike Gower
… Apparently both the tab list pattern and the naming guidance table are requiring a name on a tab list
… When we wrote this we thought it was a good idea, but now we've discovered situations where it may be redundant and end up degrading the experience for screen reader users
… Is the group willing to change this? Should we recommend it or make it discretionary?
… In this particular case, if there is a visual label, we are requiring an aria-labeledby association
… In our example, the lack of association would be problematic
… The question is how frequently the case is for tabs that don't have a visual label and should not have a aria label
… I proposed a couple of conditions at the end of the issue
… Mike has created a PR, haven'tlooked at the wording yet
… I am feeling like this could be either way but I am leaning towards recommended
Siri: Tab list should have labels if there is no previous heading. Should it be required when there is no heading?
Jon: If the ARIA spec does not require it we can't require it
Matt: We could
Jon: If there is a visible label, 100% recommended. And also that people clarify what labels mean
<Matt_King> guidance that naming is unnecessary when both 1) there is no visible text that can serve as a useful name , and 2) individual tab names are sufficiently meaningful.
Matt: For example, when tabs are used for navigational purposes, I'd still name the tab list
Jon: The above text seems an improvement on what we have
Adam: Agree
Matt: We may have a PR for review by the next meeting, either by Mike or by myself
2991 preview generation
Howard: I addressed it. Some work was done in the preview generator repo last year, and this should prevent this issue from happening again
<jongund> https://
Skipto
Jon: There is a work on a new extension that includes a feature that provides sequential access to headings and landmarks, if anyone has time I'd appreciate any feedback
Jon: You can run this on any browser, which give you shortcuts similar to the navigation features some screen readers have
… It also implements some of the UAAG
Matt: It'd be helpful if people in this group help Jon before we circulate this further
Live regions guidance
Matt: I refactored that, there is a PR available waiting for volunteers to continue the work
Jon: I can take it up after the work on contrast is finished
Matt: We also have to redesign how the landmark pages are, they don't follow the rest of APG