These are the notes for the Make WordPress Accessibility Team meeting, that occurred Friday, February 18, 17:00 UTC. You can read the entire meeting transcript on our Slack channel and view the Meeting Agenda here. The meeting begins on time at the conclusion of the bug scrub, a welcome to new attendees with introductions, and rules for a family-friendly meeting.
Updates from working groups
- Report from General Team — @ryokuhi reported that all new tickets are being actively address as well as tickets milestoned for the next minor releases (5.9.1 and 5.9.2). The release date for the next WordPress major release has been announced. The dates that interest us the most are:
- Feature freeze on March, 29 (5 more bug-scrubs from now, with 10 tickets marked as enhancements and feature requests to be closed); and
- Beta 1 on April 12 (7 more bug-scrubs from now, with 15 tickets marked as bugs and blessed tasks to be closed).
- Report from Gutenberg Team — There has been testing (the widget screen) with a few bugs found. @ryokuhi will comment on known issues and watch for new items as they are opened; and
- Report from Documentation Team — Hauwa stated that for for sections of the Team Handbook containing code blocks a review is needed. @joedolson will review when links are provided.
Open Floor
Our weekly meeting closed with these comments:
- @estelaris is working on the redesign of the end-user documentation and wanted to follow up on an issue related to the hashtag used at the end of the headings. Comments After research he believes he has some good solutions but wanted to confirm with our team and hopes to post on Monday. Comments: Technical implementation is good and modeling on the WAI implementation would be fine. More comments promised if time permits; and
- Discussion of a request for accessibility feedback on the Gutenberg navigation block by @getdave. His comment can be viewed on the weekly agenda. Kudos to @getdave for his approach on having this item considered — “let the Gutenberg contributors do their work, then when they are ready for feedback on specific topics.”
- @joedolson mentioned getting specific testing instructions is crucial mentioning @alexstine comment about block by block vs. overall systems testing. Without knowing the internal strutures of Gutenberg blocks, Joe’s practical approach is to test a block then leave it to others to figure out the best ways to resolve the issue. @ryokuhi believes the purpose of the issue is to have a single umbrella issue to keep track of all accessibility issues with the navigation block, referenced in the general issue to track progresses of the navigation blocks.
- Reminder: some parts of the world will switch to Daylight Savings Time (DST) and we should consider revising our meeting times for next week’s meeting.