Accessibility meeting agenda for 17 May 2019

This is the proposed agenda for the weekly 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 on Friday 17 May 2019 at 15:00.

  • WordPress 5.3: main accessibility goals.
  • Update on Automated testing (@greatislander)
  • Update on User Handbook (@karmatosed)
  • WPCampus Accessibility Audit: discussion about how to organize both 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., Accessibility and Design teams on process improvement for accessibility. For coordination purposes, this portion of the meeting will begin strictly at 10:45 am.

If you have any additional topics to propose, please comment below.

The Accessibility bug scrub is intended to be held on Friday 17 May 2019 at 14:00 and will be focused on remaining Gutenberg issues with the “Needs Accessibility Feedback” label. @afercia is unable to run the bug scrub, and we don’t currently have a plan for somebody else to lead this.

This meeting is held in the #accessibility channel in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform The WordPress community has its own Slack Channel at (requires registration).