Accessibility Team Meeting Agenda: January 18th

This is the proposed agenda 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 on Friday 18 January 2019 at 16:00

  1. Update on WP Campus 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/ audit
  2. Update on automated testing projects
  3. Future release(s) goals and discuss triage/milestoning to help a maximum of accessibility focused tickets to land in 5.1.x or 5.2
  4. 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. Editor updates and planning
  5. Individual availability for the incoming months
  6. Open floor

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

Accessibility Bug scrub will happen on Friday 18 January 2019 at 15:00

This meeting is held in the #accessibility channel in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. (requires registration).