These are the weekly notes for the Accessibility Team meeting that happens on Fridays. You can read the full transcript here.
Updates from the working groups
Only groups that provided updates are shown below.
General Team
@ryokuhi provided the following update:
- There are 11 tickets in the Awaiting Review queue, with only one unreviewed (probably a good candidate for closing, as it’s too generic).
- There are 5 open tickets in the 6.2 Milestone (3 which require coordination with Gutenberg, and 2 about the About Page and the dashboard banner for 6.2). 15 accessibility tickets have been committed so far in the next major release.
- There are already 12 tickets milestoned for 6.3, which we’ll start reviewing beginning next week..
Gutenberg Team (@annezazu with comments from @poena)
Mainly want to flag a few issues/PRs related to accessibility! In other news, I’m also working on a draft of improvements for 6.2 with @alexstine and @joedolson
- https://github.com/WordPress/gutenberg/issues/42373
- https://github.com/WordPress/gutenberg/issues/48054
- https://github.com/WordPress/gutenberg/pull/48204
- https://github.com/WordPress/gutenberg/pull/47241 @poena, this wasn’t labeled for a11y but seems to be. Added the label but lmk if that was incorrect.
- https://github.com/WordPress/gutenberg/pull/47898
- https://github.com/WordPress/gutenberg/issues/48015
47241 was… “Overwritten” either when the navigation block menu was added to the browse mode sidebar, or when the edit button was removed, or when the save button was added, without replacement headings. I have not been able to keep up… Its all very discouraging. I guess maybe someone saw it as pointless because the H1 ticket has not been resolved. Stefano mentioned that the last for items have been closed.
Media and Meta
@joedolson (as per Stefano) reports that we’ll start planning how to handle 6.3 tickets in the next few bug scrubs.
Open floor
@joedolson talked a bit about plans for 6.3:
One thing we need to prioritize in the next cycle is polishing the editor experience. It has a lot of technical accessibility – e.g., things that are possible to do, but it’s seriously lacking in usability with AT. We should put a lot of attention into trying to clean that up.
There are two areas I’d like to focus on:
- finishing off outstanding accessibility tickets. There are a lot of open issues, and I’d like to put pressure on those.
- Polishing the output of some of the sketchier blocks, e.g. tables.
If we, as a team, put more focus on the editor, I think we can make better progress. We just need to spend a cycle where it’s our primary focus, rather than something we get to ad the end of some bug scrubs.
Read the full discussion in the Open Floor section of the meeting’s transcript.