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 channel and find the meeting’s agenda here.
Review of 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/ issues marked as accessibility regressions
The first part of the meeting was dedicated to reviewing Gutenberg issues marked as accessibility regressions; it was a continuation of the bug scrub that had started an hour before. In the end, the team analyzed eleven issues and discussed which of them were considered as must-have to be included in WordPress 5.5.
The complete discussion about Gutenberg accessibility regressions (including items addressed during the bug-scrub) is in the #accessibility channel 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/..
Planning of an extra pre-alpha triage session
Following the discussion we had two weeks ago about how to better address accessibility bugs in WordPress core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and issues in Gutenberg, the team agreed on organizing an extra bug-scrub after WordPress 5.5 Release Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. 1. The scope of the additional triage is to identify easier and self-contained tickets and issues to mark as
The team agreed to separate the Friday bug-scrub from the extra once-per-release triage: half of it will be focused on WordPress Core tickets and the other to Gutenberg issues.
The suggested time for this extra bug-scrub is Tuesday, August 4th, 2020 at 15:00 UTC, but the team will choose the final date and time and the bug-gardener in charge of conducting the triage during next weekly meeting. If we can’t get through all tickets and issues in a single meeting, a follow-up will be planned.
Updates on WordPress Accessibility Day organization
Organization of WordPress Accessibility Day, the 24-hour event about WordPress and accessibility starting on Friday, October 2nd, 2020, is in progress, but the organizing team asked for some help.
They are looking for people to volunteer as Emcees, moderators, and monitors during the event, and a specific call for volunteers will go live in the next few days.
If someone wants to participate to a greater extent, please join the #accessibility-events channel, where discussion about the event is ongoing and a weekly meeting happens every Wednesday at 16:30 UTC.