These are the weekly notes for the Accessibility 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 Slack 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 the meeting’s agenda here.
Updates from the working groups
Only groups that provided updates are shown below.
@azhiyadev reported that she will check out Sa11y, an accessibility tool for content creators, and that she will report back about it.
@ryokuhi reported that the Team is monitoring tickets in the Awaiting Review queue (at the time of the meeting, there were 12 of them, like two weeks before) and tickets milestoned for the 6.1 release (at the time of the meeting, 16 of them were still open and 12 of them were closed). Among the tickets closed in the two previous weeks, there is also the ticket to add functions for required fields indicator and message
As the 6.2 milestone has already been opened, the Team is now able to re-milestone tickets that won’t make it for 6.1 without need to move them to Future Release.
@joedolson reported that he only removed the ticket about redesigning the admin Image Editor from the 6.1 milestone, due to lack of time to work on it.
@ryokuhi reminded the Team that on Friday, September 2nd, part of the meeting will be dedicated to discuss the use of the
accessibility-ready tag for block Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience.-based themes. He’ll publish the post about it: @joedolson volunteered to x-post it to both the Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and the Themes Teams.
@joesimpsonjr asked if someone from the team is planning to join the Accessibility Table durign the Contributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. of WordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. US, apart from him and @joedolson.
Also, @joesimpsonjr asked how to handle the new Team Reps nomination process, where nobody nominated or accepted the nomination. After a short discussion, it was simply decided to consider the current nomination process "closed", to unpin the post from the blog and to wait until November to open a new Call for Team Reps.
@ryokuhi reminded that he won’t be able to attend the bug scrub on 26 August 2022, but that @chaion07 had volunteered to facilitate it.