Meeting transcript on Slack
Current progress on Gutenberg 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/ accessibility 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) / WP 5.0 RC1
WordPress 5.0 RC1 is now available for tests.
The blog post introduced an accessibility related ticket about allowing low privileged users to use ARIA attributes.
Basically these ones are now allowed in the post content:
aria-describedby
aria-details
aria-label
aria-labelledby
aria-hidden
Concerning Gutenberg and WordPress 5.0 timeframe
The release candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. is out and from there the timeline for release will be determined. Unless it is a blocker, new tickets or issues will be milestoned in 4.6 for Gutenberg plugin 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/ or can be cost-based plugin from a third-party and in 5.0.1 for WordPress Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress..
Current progress on Gutenberg accessibility documentation
The current document is available in Google Docs.
@abrightclearweb is looking for comments from the accessibility team.
@dryanpress to help moving this document to developers and users docs.
Feedback on the Notice for assistive technologies users to include in WordPress 5.0 About page
The initial ticket was #45270 and the issue was finally addressed in ticket #45178.
The current wording is “Note to users of assistive technology Assistive technology is an umbrella term that includes assistive, adaptive, and rehabilitative devices for people with disabilities 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 needed to accomplish such tasks.
https://en.wikipedia.org/wiki/Assistive_technology: if you experience usability issues with the block 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, we recommend you continue to use the Classic Editor.” followed by a link to the WP Admin plugin install page (only visible if the user can install plugins).
At this time, there is no confirmation if the Classic Editor plugin is going to be bundled with WordPress 5.0 or not.
WCAG WCAG is an acronym for Web Content Accessibility Guidelines. These guidelines are helping make sure the internet is accessible to all people no matter how they would need to access the internet (screen-reader, keyboard only, etc) https://www.w3.org/TR/WCAG21/. success criteria: should the team refer to WCAG criteria in issues?
Decision: WCAG criteria can be referenced in issues or tickets but they are not mandatory. The accessibility team is not going to make a policy on it.
Update about the WordCamp 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. US Contributor 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/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. accessibility team table / The Hackathon
(related: previous blog post)
People involved in this initiative will get in touch next week with Deque System to organize the hackathon.
Open floor
There’s some inconsistency in the screen-reader-text documentation in the handbook: specifically position: absolute uses !important. It will be removed from the handbook.
@afercia to create a ticket about icon-only controls in WordPress Admin.
Next meeting
Next weekly meeting: November 30, 2018 at 16:00 UTC
