Special Accessibility Team Meeting Notes: January 19, 2024

This was a special meeting to discuss items key to the group moving forward, including but not exclusively: Discuss new times for the bug scrub and weekly meetings but also an 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) Vision for WordPress.

Opening/Introduction by Joe Dolson

To start this off, I’d like to make a few comments. WordPress Accessibility has, for years, worked on a catch-up schedule. Fixing historic issues in the software, then scrambling to keep up with the pace of work in the 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. and site editor.

But we haven’t had a solid long-term vision of what we want to achieve.

That may sound very simple: we want the most accessible software we can achieve. However, having concrete goals needs more than some vague abstraction.

The primary purpose of having an accessibility team – as opposed to independent accessibility contributors – is to set an overall goal. The “team” part is about coordinating efforts and having some kind of consensus.

Having a vision is about documenting our mutual goal and the process for reaching it.

You can read the full transcript of all the thoughts and discussion points here.