Help build the WP Accessibility Knowledge Base, the WordPress community’s 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) documentation. You can write a new page on a topic that interests you, review existing content, or report an error you notice.
- Reference: How to contribute
- Connect: Join #accessibility-docs on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/ and introduce yourself
Steps
- Explore. Check the WP A11y docs project board and wpaccessibility.org to see what exists and what’s still needed.
-
Contact first. Tell the team you’d like to work on a specific task so it can be assigned to you. Content written without contacting the leads first will not be reviewed.
-
Write. Cover a topic that interests you in your own words. Follow the page structure in the Write documentation guide, and link out to authoritative sources rather than restating them. Use AI only to translate or check your English, not to write the content.
-
Report instead (optional). Not writing a full page? Reporting an error you’ve found is a valid contribution on its own.
-
Share for review. Submit your work through the contact form, the #accessibility-docs channel, a comment on the related GitHub issue, or a pull request.
Contribution checklist
- Contacted the team and had the task assigned before writing
- Wrote about a topic that interests you, in your own words
- Followed the Write documentation page structure
- Shared your work for review through one of the listed channels
What happens next
A reviewer will read your contribution and may suggest changes before it’s published on the Knowledge Base. If you don’t hear back, follow up in #accessibility-docs.
When you’re ready, pick up another topic or settle into an area you can develop further.
Help
Stuck? Check the getting help guide, then ask in #accessibility-docs.
Further reading:
– Write documentation — page structure and the rules for writing a Knowledge Base page
– Make WordPress Accessibility — team updates and meeting notes
– Accessibility Team Handbook — how the team works and how to get involved
