Accessibility Team Meeting Notes: October 26, 2018

Meeting transcript on Slack

Agenda for the meeting

  1. Discuss bug scrub weekday/time
  2. Discuss and validate 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. 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). ( feedback before publishing
  3. Open floor

Bug scrub weekday/time

As the Accessibility meeting weekday/time has moved to every Fridays, 15:00 UTC, bug scrub meeting also moved to Friday, 1 hour before the meeting.

Accessibility bug scrub: Friday, 14:00 UTC
Accessibility team meeting: Friday, 15:00 UTC

Please note that both will move after Day Saving Time end in the US.

Discuss and validate Gutenberg accessibility feedback before publishing

The aim of this document is to address in an objective and professional way the accessibility issues encountered with the 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. The focus is set on the ability to author, edit, and publish posts, which is the primary purpose of WordPress.

There is 5 groups of issues:

  • Cognitive Load & Complexity
  • Inconsistent User Interface Behavior
  • Accessibility Anti-Patterns
  • Keyboard Shortcuts
  • Keyboard Navigation

The post is available on Make/Accessibility Blog:

The team tried to make this communication accessible to users with no or little accessibility expertise. If you have any question about this document, please comment it.

Open floor

The team discussed some best practices for a better accessibility in SlackSlack Slack is a Collaborative Group Chat Platform The WordPress community has its own Slack Channel at conversations:

  • Do not use threads as they are not accessible
  • Avoid large blocks of text
  • Give some time between messages
  • Consider people have different typing speed
  • Use formal beginning/end markers
  • Emojis: are they accessible?

Persons with accessibility needs are encouraged to give feedback and ask for improvements they would like to get.

Next meeting: November 2nd, 2018 15:00 UTC