Accessibility Team Meeting Notes: August 14, 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.

Review poll results for the proposed changes to the team meeting day and times

Following the discussion and voting for a new meeting day and time, the team reviewed the result of the poll. We had a tie between two options: moving to Tuesday, at 15:00 UTC, and keeping Friday, at 15:00 UTC as the meeting time.

We decided to hold another voting round in order to break the tie. Please cast your vote on the new poll.

Discussion about updating the WordPress Accessibility coding standards to WCAGWCAG WCAG is an acronym for Web Content Accessibility Guidelines. These guidelines are helping make sure the internet is accessible to all people no matter how they would need to access the internet (screen-reader, keyboard only, etc) 2.1

The team agreed that with the WCAG 2.2 draft already having been published, it was time we updated the WordPress coding standards to conform to WCAG 2.1, level AA.

We think it would be great to aim for the updated coding standards to be updated along with the upcoming 5.6 release. @sarahricker, @azhiyadev, @joedolson, and @nrqsnchz agreed to form a squad and start coordinating the work that will be needed, such as writing the requirements and creating some examples.

Advancing the Editor Interface

The team reviewed this new proposal from @itsjonq that looks to create a new foundation for the WordPress components library. The goal is to make it easier for contributors to create cohesive interfaces and conform to standards and best practices.

While still in the early stages, this proposal can have a great impact by standardizing and enforcing the accessibility of the components we use to build WordPress.