These are the weekly notes for the Accessibility 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.
Meeting time change following Daylight Saving Time introduction
Meeting and bug scrub times will stay the same. Bug scrub at Friday 15:00 UTC and meeting at Friday 16:00 UTC. The day will stay the same on Friday.
Improvement of onboarding for new contributors
Here is a list of ideas that the accessibility team came up with to improve the onboarding process for new contributors to the accessibility team.
- Add information about the bi-monthly meeting for new core contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org. to the accessibility handbook
- Ease participation to tickets and issues with
needs-accessibility-feedback labels: make them more discoverable and improve how to ask for feedback from team members about them
- Add a Slackbot welcome announcement when someone joins the #accessibility channel on Slack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.
- Update the “Get involved” chapter in the accessibility handbook and make the handbook more friendly for new contributors (discussion will happen in the #accessibility-docs channel on Slack)
@annezazu informed the team that Taylor Arndt very kindly joined a Zoom meeting to share some feedback around the Full Site Editing experience when using screen readers. Here’s a quick summary of issues to be aware of (she’ll include some of these in a recap post she’s doing for the FSE Outreach Program’s second call for testing):
@annezazu also flagged the following items:
Here are a couple other issues brought up by the team.
If you have time to review/contribute to the new accessibility standards, your feedback is welcome and much appreciated.