Accessibility Team Meeting Notes: October 7, 2022

These are the weekly notes for the AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Team meeting that happens on Fridays. You can read the full transcript on our SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel and find the meeting’s agenda here.

Gutenberg

@joedolson reported that the main update on all things is that we’re moving rapidly towards release candidateRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. on WP 6.1. @sabernhardt is working on developer notes for 6.1 changes.

Media

Joe reported that Media has started working on milestoning issues for 6.2. There’s a large backlog of issues (over 600), so we’re focused on finding simple fixes that have simply dropped off everybody’s radar.

On a more general note @alexstine asked if there anyone who wants to join these working groups or get more information?

Meta

@joedolson has provided extensive feedback on the Learn catalog and on the new Audio downloads section of openverse. The Learn changes I requested have already been fixed; I don’t have an update on the Audio downloads.

@zackkrida mentioned the Openverse side created a bunch of discrete GitHub issues from your suggestions but have yet to start work.

Open Floor

Joe made a general request that when we request working group updates, that the point person for each working group is specifically @ references in the request. Also, the point people are all listed in the Accessibility Handbook.

@sabernhardt shared that if you want to follow the dev note progress, there was an issue for the general Accessibility improvements dev note and the overall TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. ticket is #56723. @annezazu has requested help.

** Thanks to everyone who attended, including first-timers interested in contributing to the accessibility of WordPress. We’ll see you for the next weekly bug scrub.