Use of accessibility-ready tag for block-based themes

A few weeks ago, during 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’s meeting, @poena brought up for discussion if and how to use the accessibility-ready tag for 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.-based themes. The Team agreed to have a preliminary discussion about this topic during our next meeting, happening on Friday, September 2, 2022, 16:00 UTC.

We would like to invite contributors to 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/ and contributors of the Themes Team to join the conversation, so that we can get as much feedback as possible.

The results of the discussion will be summarized in a blog post, asking for further feedback, and, if needed, discussed during one of the weekly coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. chats.

Props in advance to @joedolson, who will be x-commenting this post.