Accessibility Team meeting notes for January 24 2020

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). ( team meeting that happens on Fridays. You can read the full transcript on our Slack channel and find the meeting’s agenda here.

Update on 5.4 TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub. tickets

@audrasjb has organized a schedule to run additional bug scrubs in preparation for the 5.4 release. Last week we were at 40 accessibility focused tickets still open in the milestone, and today we are at 36 open tickets.

We were all reminded that BetaBeta 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 is planned for February 11, 2020, and it is our deadline for committing patches into coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..

The next bug scrub is planned for Tuesday, January 28 at 17:00 UTC.

Update on the last WPAD planning meeting

Last week we held out third planning meeting for the WordPress Accessibility Day in the #accessibility-events channel in Slack. The team reports that the event organization is taking shape, and we’re considering September 26, 2020, as our intended date.

We’ve considered other WordPress events and mayor global holidays to define this date. That being said, we’d like to let it sit for a couple more weeks in case we’ve missed an important event or holiday.

Big thanks to @joedolson and everyone else who’s volunteered for the organizing team.

Please head over to the #accessibility-events channel in Slack to find out when then next planning meeting will be.

Follow up of the GutenbergGutenberg 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. blockBlock 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. focus project

Work is underway, and the next steps are converting the team’s observations into actionable GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. issues in the Gutenberg repository.

Help with testing the navigation block

The design team has asked for our help with performing accessibility testing on the navigation block in the editor. @nrqsnchz will coordinate a document where those available to help can add their feedback and observations.