Accessibility Team Meeting Notes: June 17, 2022

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). ( Team meeting that happens on Fridays. You can read the full transcript on our SlackSlack Slack is a Collaborative Group Chat Platform The WordPress community has its own Slack Channel at channel and find the meeting’s agenda here.

Team contributions to the Developer Resources blog

@bph joined our meeting to get in touch with our Team Reps regarding how we might be involved (editorial board) in a new blog project for the The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. website. A follow up should be out next week or so. Discussion points included:

  • The time this extra activity would stretch the team reps may drain resources needed here.
  • This could be a good opportunity to bring content added to our team’s documentation to a broader public.
  • @Hauwa Abashira offered to coordinate efforts between Learn and Accessibility; and
  • If you have other questions or if you want to be part of this effort, contact Birgit via Direct Message.

Pull Request about accessibility enhancements to Writing Flow in Gutenberg

@alexstine reported that this is a big improvement for blocks that are not single fields such as paragraph, heading, list, etc. There are 2 major adjustments. Kudos to Alex for this massive achievement.

No team updates or Open Floor items Due to the length of the discussion and updates a brief period was set aside here. Next week, bug scrub.