This update informs you about:
- The Knowledge Base is ready to contribute.
- Issues on GitHub with what needs to be written or reviewed.
- The work planned for October 2025.
- How you can help.
Knowledge Base is ready to contribute
In September we made the website wpaccessibility.org ready to contribute. All accessibility content from the current handbook is copied into this website. Also new placeholder pages are made, for new content.
Yoren Chang @1fixdotio worked hard to create a preview option for pull requests for the site, so everyone can review proposed content without needing a local install. She is really amazing.
The How to contribute pages are written, also for contributors who don’t work with GitHub and just want to write or review.
GitHub issues with what needs to be written or reviewed
Rian wrote issues on GitHub for each documentation page belonging to Standards and best practice. For review and rewrite of the content. Each issues is labeled by topic.
For example the page Headings in the content now has an alert, about what needs be done with the content and a link to the related GitHub issue.
How can you help?
On How to contribute you can read the different ways to contribute to this project. If you want to help writing, pick an issue from the list of Todo issues on the projectboard Wp A11y Docs. Only contribute if you know the topic well or have good resources to share.
Note: Please write the content yourself and use AI only to translate or to check the quality of your English.
Plans for October
@rianrietveld will start writing content for the Knowledge Base, now everything is mapped out. She will also give presentations about the project at the WPMeetup020 (Amsterdam) and WPMeetup030 (Utrecht). You can help her by sponsoring Rian’s time and expenses.
@Aminul will work on the migration of the current handbook to a new Github repo accessibility-team-handbook on github.com/wordpress. Only the Accessibility Team related info will stay into that handbook.
@joedolson and @1fixdotio work on the remaining issues in wpaccessibility.org itself.