Title: Accessibility Team Meeting Notes: November 16, 2018 Author: Jb Audras Published: November 20, 2018 --- [ ](https://profiles.wordpress.org/audrasjb/) [Jb Audras](https://profiles.wordpress.org/audrasjb/) 9:20 pm _on_ November 20, 2018   # Accessibility Team Meeting Notes: November 16, 2018 [Meeting transcript on Slack](https://wordpress.slack.com/archives/C02RP4X03/p1542384066721200) ## Current progress on 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/](https://wordpress.org/gutenberg/)󠁿 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) The last [weekly Gutenberg accessibility status update](https://make.wordpress.org/accessibility/2018/11/12/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](https://github.com/WordPress/gutenberg/pulls?q=is%3Aopen+is%3Apr+label%3AAccessibility). ## Current progress on Gutenberg accessibility documentation [@abrightclearweb](https://profiles.wordpress.org/abrightclearweb/) is handling Gutenberg Accessibility Documentation and it seems to be on hold. The current document is [available in Google Docs](https://docs.google.com/document/d/1pjYlOhkMu4NqcsNhKzJ_KTz2Z-yacMuX8UySslJp6oQ/edit#). Discussions about the document can take place on the Accessibility team SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/) 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](https://core.trac.wordpress.org/ticket/45270) [@lonelyvegan](https://profiles.wordpress.org/lonelyvegan/) mentioned that a shorter sentence would help. The current proposal is going to be something like “Users of assistive technologyAssistive technology **Assistive technology** is an [umbrella term](https://en.wikipedia.org/wiki/Umbrella_term) that includes assistive, adaptive, and rehabilitative devices for [people with disabilities](https://en.wikipedia.org/wiki/Disability) and also includes the process used in selecting, locating, and using them. Assistive technology promotes greater independence by enabling people to perform tasks that they were formerly unable to accomplish, or had great difficulty accomplishing, by providing enhancements to, or changing methods of interacting with, the [technology](https://en.wikipedia.org/wiki/Technology) needed to accomplish such tasks. [https://en.wikipedia.org/wiki/Assistive_technology](https://en.wikipedia.org/wiki/Assistive_technology) who experience usability issues with Gutenberg should use the Classic Editor” with a link to the Classic Editor pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. search page. Please note: this task is now addressed in [ticket #45178](https://core.trac.wordpress.org/ticket/45178). ## WCUS Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of 󠀁[https://make.wordpress.org/](https://make.wordpress.org/)󠁿 There are many teams that people can participate in, each with a different focus. 󠀁[https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/](https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/)󠁿 accessibility team table / The Hackathon The team recently [published a post](https://make.wordpress.org/accessibility/2018/11/15/hackathon-automated-accessibility-testing-with-deque-on-the-wcus-contributor-day/) about the accessibility table during WordCampWordCamp WordCamps are casual, locally- organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. [Learn more](https://central.wordcamp.org/about/). US contributor’s day. The idea is to organize a hackathon to work on including some accessibility automated tests in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. 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 ](https://wptavern.com/wordpress-accessibility-team-to-host-hackathon-with-deque-systems-at-wordcamp-us-2018) to promote the initiative.  ## Next meeting Next weekly meeting: [November 23, 2018 at 16:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20181123T1600). ### Share this: * [ Threads ](https://make.wordpress.org/accessibility/2018/11/20/accessibility-team-meeting-notes-november-16-2018/?share=threads) * [ Mastodon ](https://make.wordpress.org/accessibility/2018/11/20/accessibility-team-meeting-notes-november-16-2018/?share=mastodon) * [ Bluesky ](https://make.wordpress.org/accessibility/2018/11/20/accessibility-team-meeting-notes-november-16-2018/?share=bluesky) * [ LinkedIn ](https://make.wordpress.org/accessibility/2018/11/20/accessibility-team-meeting-notes-november-16-2018/?share=linkedin) * [ X ](https://make.wordpress.org/accessibility/2018/11/20/accessibility-team-meeting-notes-november-16-2018/?share=x) * [ Facebook ](https://make.wordpress.org/accessibility/2018/11/20/accessibility-team-meeting-notes-november-16-2018/?share=facebook) 1. Pingback: [Gutenberg, accessibility, and compromise - Gutenberg Times](https://gutenbergtimes.com/gutenberg-accessibility-and-compromise/) Comments are closed. # Post navigation [← Accessibility team meeting agenda: November 16th](https://make.wordpress.org/accessibility/2018/11/16/accessibility-team-meeting-agenda-november-16th/) [Accessibility team meeting agenda: November 23th →](https://make.wordpress.org/accessibility/2018/11/23/accessibility-team-meeting-agenda-november-23th/)