These are the weekly notes for 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 meeting that happens on Fridays. You can read the full transcript on our Slack channel and find the meeting’s agenda here.

Updates from working groups

Only working groups that provided updates are shown below.

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 on a lighter navigation block experience. Flagging this because it’s meant to explore a better user experience for the basic menus.
• PR on Adding a Dropdown block for use in Navigation. This felt like a good PR to review for the team since it’s a fairly big change to the Navigation 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. itself.
• The latest call for testing for the FSE Outreach Program on Handling a Higher Education Header. It would be lovely to get more accessibility feedback on this experience and test!

Open floor

The Accessibility team bug scrub and meeting will not happen next week. Enjoy the week off and we’ll return on September 3.