Accessibility Team Meeting Notes: November 16, 2018

Meeting transcript on Slack

Current progress on Gutenberg accessibility

The last weekly Gutenberg accessibility status update was published on November 12, 2018. Short recap:

  • 8 pull request merged
  • 19 open pull request labeled for accessibility
  • 90 remaining accessibility issues
  • 17 open pull Requests and 102 issues.

Help is needed on the remaining accessibility labeled Pull Requests.

Current progress on Gutenberg accessibility documentation

@abrightclearweb is handling Gutenberg Accessibility Documentation and it seems to be on hold.

The current document is available in Google Docs. Discussions about the document can take place on the Accessibility team Slack channel or directly by commenting the document. That’s a great way to contribute, as important as any other.

Feedback from 5.0 accessibility lead about the information message for assistive technologies users

Concerning the related Trac ticket @lonelyvegan mentioned that a shorter sentence would help. The current proposal is going to be something like “Users of assistive technology who experience usability issues with Gutenberg should use the Classic Editor” with a link to the Classic Editor plugin search page.

Please note: this task is now addressed in ticket #45178.

WCUS Contributor Day accessibility team table / The Hackathon

The team recently published a post about the accessibility table during WordCamp US contributor’s day.

The idea is to organize a hackathon to work on including some accessibility automated tests in Core Workflow. Deque System will help, as the editor of Axe-Core. The team is currently looking for core developers and committers to help, and some of them are already involved.

WP Tavern also published a post to promote the initiative. 

Next meeting

Next weekly meeting: November 23, 2018 at 16:00 UTC.