Accessibility Team Meeting Notes: February 5, 2021

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 Slack channel and find the meeting’s agenda here.

Review team’s activities during WordPress 5.7 Alpha

Beta1 was released Tuesday. Let’s look back to see what went well, what didn’t go well, and what to improve on next time.

• It was agreed that working groups did help and should be used in the future.
• It is important to have one referent per working group.

Plan activities for WordPress 5.7 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.

• 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. https://wordpress.org/gutenberg/ accessibility testing. Checking the done tickets in https://github.com/WordPress/gutenberg/projects/52. General checks to make sure new features/fixed issues did not result in accessibility regressions.
• Provide pre-release accessibility testing instructions for main features in Gutenberg. Fit as much in to end to end tests as possible.
• WordPress updated color scheme checking.

#meeting-notes