These are the 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 every other Friday. You can read the full transcript on our Slack channel and find the meeting’s agenda here.
Revision of meeting and bug-scrub times
In view of the switch to Daylight Saving Times in various parts of the Northern Hemisphere, the team agreed to keep the current starting time for bug-scrubs (16:00 UTC) and meetings (17:00 UTC) until the end of March. Beginning with 1 April 2022, weekly bug-scrubs will be held every Friday at 15:00 UTC and meetings will happen on the first and third Friday of each month at 16:00 UTC.
Team involvement during 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. Europe
Members of the organizing team of WordCamp Europe reached out to the team to discuss how the accessibility team could be involved in the activities of WordCamp Europe, especially during 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/. happening on 2 June 2022. @ryokuhi plans to attend and already made himself available to facilitate work at the accessibility table.
On the other side, it’ll be very difficult for the accessibility team to facilitate also a second accessibility table dedicated to the Accessibility WP Theme Auditor, as suggested: the people who were coordinating the project at the time are no more active in the accessibility team and the team size has shrunken since last WordCamp Europe. As such, the team agreed to focus on a single accessibility table.
If someone else is attending WordCamp Europe, and if they are available and willing to contribute to the activities of the accessibility table during the Contributor Day, they can reach out to @ryokuhi on 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/. either directly or in the #accessibility channel.
Updates for the working groups
Only groups that provided updates are shown below.
@azhiyadev reported before the meeting that there are no updates from the group.
The group continues to monitor tickets in the Awaiting Review queue, to avoid them piling up.
There are 2 tickets milestoned for 5.9.2, which the group is monitoring.
There are 9 enhancement or feature request tickets milestoned for 6.0, with two more weeks to get them committed.
There are 15 bug tickets milestoned for 6.0, with four more weeks to get them committed.
Gutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/
Before the meeting, @getdave shared a Pull Request about converting classic menus in block ones that will probably benefit from some feedback from the team.
@isabel_brison left a comment to the meeting agenda (apologies for not mentioning it during the meeting), asking for feedback on an issue about keyboard shortcuts and the best alternatives to the current 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. editor setup. List View is crucial to accessible navigation of the editor content, so it would be good to ensure that the shortcut to open it works across all screen readers. In order to include this feature in the 6.0 release, it should be ready before Beta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1, which leaves not too much time to work on it.
@joedolson reported that work is in progress; as the features the group is working on are quite complicated, it isn’t easy at the moment to predict what will make it in the release. A couple of easy fixes should be done in about a week.
@joedolson reported that he’s working to identify some better workflows for testing Gutenberg blocks. Given that the accessibility of Full Site Editing themes is highly dependent on the output of blocks, this is extremely important to assess if such themes are accessibility-ready.
No topic was raised during open floor.