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 on the new workflow keyword on TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/.

Since WordPress 5.8 is nearing release, this has lost a bit of momentum. After 5.8 is out, let’s circle back to this and get the new keyword added. The latest proposal is linked here. A poll will be created to decide the final keyword.

Tracking accessibility MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. tickets

At this current time, there is no straight forward or easy way to check accessibility tickets on Meta Trac. Since there is no focus tracking on Meta Trac, this is not an option to add an accessibility focus. One proposal is a "needs-accessibility" workflow keyword. This would likely be the quickest and easiest to implement.

How to improve tracking of accessibility issues in 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/

Did not have enough time for this agenda item today.

Open floor

Nothing was brought up for Open floor today.