Gutenberg-focused weekly meeting: call for issues

About Us

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 shares accessibility expertise across the project to improve the accessibility of WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and resources.

WordPress targets WCAG 2.1 at level AA as the standard for development.

Learn More

For support related to WordPress & accessibility, visit the WordPress Accessibility forum.

You can also ask questions during Accessibility Team Office Hours every Wednesday at 14:00 UTC in the accessibility channel in 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/..

During the last 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 weekly meeting, it was decided that the meeting happening on Friday, September 11, 2020 at 15:00 UTC will be entirely dedicated to discussing 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/ issues.

If you want to suggest an issue or a pull request, you are invited to write it in the comments to this post before Thursday, September 10, 2020 at 21:00 UTC.

The Agenda will be published soon after and will include the issues that will be discussed during the meeting. If we won’t be able to fit all items in the agenda, we’ll consider organizing another specific meeting.

The meeting will be held, as always, 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).

Andrea Fercia 4:20 pm on September 9, 2020
In the last weeks 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 identified a series of broader issues that need to be prioritized but didn’t had the time to discuss in depth. Some of them are:

All the issues, PRs, and design related to the new Widgets screen
- too many to list here
All the issues, PRs, and design related to the new Navigation screen
- too many to list here
All the issues identified as accessibility regressions in WordPress 5.5 that still need to be addressed e.g.:
- https://github.com/WordPress/gutenberg/issues/23892
- https://github.com/WordPress/gutenberg/issues/23890
- https://github.com/WordPress/gutenberg/issues/22858 (now closed, see follow-up on sidebars below)
All the issues, PRs, and design related to existing and new sidebars:
All the issues, PRs, and design related to toolbars broken because an extraneous UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. gets rendered “on the fly” within the toolbar, e.g.:
wingo5315 4:22 pm on September 9, 2020

I’ve got a feature request for adding a link section to the Cover 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., which I (and many other people) think should be a feature: https://github.com/WordPress/gutenberg/issues/12684
- Stefano Minoia 3:30 pm on September 10, 2020
  
  Hello Calum,
  First of all, thank you for your suggestion!
  I had a look at the feature request, but it’s not clear to me if the issue is 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)-related: if you could make more clear with a comment here on or GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ why the Accessibility Team should discuss about this issue, we’ll be happy to include this item in the meeting agenda.
  I hope to see you tomorrow at the meeting, have a nice day!
Andrea Fercia 6:09 pm on September 10, 2020

I’d like to propose a couple additional things to discuss:

Search 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.: Add button, label, and widthoptions
https://github.com/WordPress/gutenberg/pull/24666

This 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/ issue, in my opinion, give too much power to users as they will be able to publish a search input with no label (at all), no placeholder, no button text (only an icon). Also, this breaks the previous agreed implementation where a properly associated label element was always present, with the option to make it visually hidden.

Mid-long term task: testing again all the Gutenberg blocks
There are still many blocks that aren’t even keyboard accessible. That means keyboard users can’t use them. It would be great to plan a thorough audit of all the blocks. At first glance it seems a huge task but it could be performed by splitting the blocks in chunks to be assigned to various contributors.

Comments are closed.

About Us

How you can help

Learn More

Share this: