These are the bi-weekly notes for the Accessibility Team meeting that happens on Fridays. You can read the full transcript here or see the full meeting schedule.
Updates from the working groups
NOTE: Only groups that provided updates are shown below.
Team Updates
- @joedolson share news of significant updates on learn.wordpress.org and a call for testing.
- Joe also mentioned that @Amber Hinds and the contributors at WCEH spent some time on theme accessibility-ready documentation.
- WordPress 6.6 is released. Also, bug scrubs have been continuing; I’ve now got about 30 tickets milestoned for 6.7, so Joe will be getting started on those soon. @afercia has been getting a number of tasks done in Gutenberg, as well.
- @joedolson ran the bug scrub this week on Gutenberg issues, and @jeryj made a PR for one of the open issues that we wanted to have available to test conceptually. Here: is the link to the Github PR. This automatically opens the sidebar panel for block settings when a block is selected. Currently, the block sidebar stays in whatever mode you’ve selected, which requires you to switch modes if you want to configure blocks. This PR would change that so that the block sidebar auto-switches to be active when you select a block. We want to test this to see whether it makes an easier flow; it might be an improvement, but we’re not really sure. I’m going to try and set up a test environment that can be shared so that I can ask some people to try it out. When I (Joe) do, I’ll post on Make WordPress Accessible.
Work is starting on Twenty Twenty Five, so that’s the biggest new thing. But the progress on the accessibility-ready tag is also moving forward; continuing work as I mentioned earlier, but also some tickets with movement to add information about the accessibility-ready tag in user facing environments in the theme directory.
- #7714: Add informational section on the theme single for themes with Accessibility Ready tag describing what that means
- #7713: Add banner on the themes archive when a search is done for accessibility ready to add context on what this designation means
These two items would really help in letting people know what exactly the accessibility-ready tag means.
- @antpb is working on experimentation for the next generation media library; we discussed it on Wednesday. Nothing else to report there. It’s still in very early stages, but we talked about some long-term goals that we want to think about, so that the media library can be built in a way that would support those features. Things like an in-browser captioning environment, etc.
Meta Working Group:
Meta is giving feedback to @elblakeo31, who is getting his process refined, on the following update:
- We need feedback on a color contrast issue I posted here: https://github.com/WordPress/wporg-main-2022/issues/472
- Also need feedback on a heading order ticket I posted here: https://github.com/WordPress/wporg-main-2022/issues/473
- Fixing those issues should resolve the WordPress DotOrg issues
- Next, we’ll be scanning learn.wordpress.org
- #472 Insufficient Color Contrast on Links, Headings, and Paragaphs WordPress/wporg-main-2022 | Jul 15th | Added by GitHub
- #473 Invalid Heading Orders WordPress/wporg-main-2022 | Jul 15th | Added by GitHub
Also, FYI- Looks like there’s a comment on the Alt issue here: https://github.com/WordPress/wporg-main-2022/issues/462#issuecomment-2214176587.
The hardest part is the timing; the scans of the old design are mostly being ignored, because (rightly) they’re going to be redesigned soon.
@joesimpsonjr will follow up with @nhrob and @rcreators regarding expressed interest in assuming the Team Rep roles and asked Joe for thoughts on procedure and preparing for a vote to make it official. He suggested posting a post for a Call for Team Reps, documenting what is seen as responsibilities to pass on as well. You can use this as a reference https://make.wordpress.org/updates/team-reps/.
NOTE: If you’d like to have a topic added to the agenda for our next meeting, please mention it in the comments on an upcoming agenda.