Accessibility Team Meeting Notes: July 31, 2020

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.

This week we decided to continue the discussion around 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. focus outlines that started during the accessibility bug scrub right before our team meeting.

Rather than try to summarize it, I encourage those interested to follow the discussion in Slack.

We agreed to revisit this topic and discuss possible proposed solutions during our next extra bug scrub planned for Tuesday, August 4, 2020, at 15:00 UTC.

We also agreed to revisit the agenda items planned for today’s meeting during our meeting next week.

#meeting-notes-2