WP A11y Docs Update September 2025  ## Metadata - Author: [[Make WordPress Accessible]] - Full Title: WP A11y Docs Update September 2025 - Category: #articles - Document Note: ```markdown --- tags: [WordPress, Accessibility, Documentation] author: [MISSING] source: Make WordPress reference: [https://make.wordpress.org/accessibility/2025/09/30/wp-a11y-docs-update-september-2025/] date created: {{date:YYYY-MM-DD}} {{time:HH:mm}} --- # 🏷️ Title: WP A11y Docs update September 2025 ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - Include links cited in or relevant to the article. ## 📝 Summary - The wpaccessibility.org Knowledge Base is ready for contributions. - GitHub issues map needed rewrites for standards and best practices. - October work includes content writing, handbook repo migration, and site fixes. - Risks: contributor quality, scope creep, and migration delays. - Bottom line: use mapped issues and contribute with clear guidelines. ## 📖 Main Content - The team copied handbook content to wpaccessibility.org with placeholders. - Contribution paths exist for GitHub and non-GitHub contributors. - Issues label pages needing review, like “Headings in the content.” - October plans assign tasks to Rian, Aminul, Joe, and Yoren. - Note: authors request minimal AI use for quality checks only. ### 🗒️ Notes ### [H1] Knowledge base opens for contributions > [!quote] [WP A11y Docs update September 2025](https://make.wordpress.org/accessibility/2025/09/30/wp-a11y-docs-update-september-2025/) by [[Make WordPress]]. Published 2025-09-30. Accessed {{date:YYYY-MM-DD}}. > “In September we made the website wpaccessibility.org ready to contribute.” Centralizes accessible docs and invites wider review. Good onramp for first issues. [view highlight](https://make.wordpress.org/accessibility/2025/09/30/wp-a11y-docs-update-september-2025/) #xref #articleseed ID:rw_371118854_0 ### [H2] PR previews simplify community review > [!quote] [WP A11y Docs update September 2025](https://make.wordpress.org/accessibility/2025/09/30/wp-a11y-docs-update-september-2025/) > “create a preview option for pull requests… without needing a local install.” Previews reduce setup burden and speed feedback loops. [view highlight](https://make.wordpress.org/accessibility/2025/09/30/wp-a11y-docs-update-september-2025/) #xref ID:rw_371118854_0b ### [H3] Non‑GitHub contribution path exists > [!quote] [WP A11y Docs update September 2025](https://make.wordpress.org/accessibility/2025/09/30/wp-a11y-docs-update-september-2025/) > “for contributors who don’t work with GitHub and just want to write or review.” Expands inclusivity; reduces tooling barriers for writers and reviewers. [view highlight](https://make.wordpress.org/accessibility/2025/09/30/wp-a11y-docs-update-september-2025/) #share ID:rw_371118854_0c ### [H4] GitHub issues label required rewrites > [!quote] [WP A11y Docs update September 2025](https://make.wordpress.org/accessibility/2025/09/30/wp-a11y-docs-update-september-2025/) > “issues on GitHub for each documentation page… labeled by topic.” Enables triage and assignment; improves contributor focus. [view highlight](https://make.wordpress.org/accessibility/2025/09/30/wp-a11y-docs-update-september-2025/) #xref ID:rw_371118854_1 ### [H5] Page alerts link to related issues > [!quote] [WP A11y Docs update September 2025](https://make.wordpress.org/accessibility/2025/09/30/wp-a11y-docs-update-september-2025/) > “page Headings… has an alert… and a link to the related GitHub issue.” Inline prompts guide updates and reduce ambiguity. [view highlight](https://make.wordpress.org/accessibility/2025/09/30/wp-a11y-docs-update-september-2025/) #xref ID:rw_371118854_1b ### [H6] Contributors should self‑author, not AI‑author > [!quote] [WP A11y Docs update September 2025](https://make.wordpress.org/accessibility/2025/09/30/wp-a11y-docs-update-september-2025/) > “Please write the content yourself and use AI only to translate or to check the quality of your English.” Sets authorship expectations; preserves accuracy and voice. [view highlight](https://make.wordpress.org/accessibility/2025/09/30/wp-a11y-docs-update-september-2025/) #addendum ID:rw_371118854_2 ### [H7] October plan assigns named owners > [!quote] [WP A11y Docs update September 2025](https://make.wordpress.org/accessibility/2025/09/30/wp-a11y-docs-update-september-2025/) > “Rian will start writing… Aminul will work on the migration… joedolson and 1fixdotio work on remaining issues…” Clear ownership enables accountability and progress tracking. [view highlight](https://make.wordpress.org/accessibility/2025/09/30/wp-a11y-docs-update-september-2025/) #share #xref ID:rw_371118854_3 ## 📚 References - [WP A11y Docs update September 2025](https://make.wordpress.org/accessibility/2025/09/30/wp-a11y-docs-update-september-2025/) - [wpaccessibility.org](https://wpaccessibility.org/) - [WordPress Accessibility Team Handbook (current)](https://make.wordpress.org/accessibility/handbook/) - [WordPress GitHub org](https://github.com/WordPress) ## 🗣️ Paraphrase - The site is open for content contributions with previews. - Issues drive page rewrites; October tasks have owners. ## 📰 Newsletter - The Accessibility Team opened wpaccessibility.org for contributions. - You can contribute via GitHub or submit text for review. - October focuses on content, migration, and site polish. - See the update and pick a labeled issue to start. - Read the update at the Make site. ## ✅ Action Items #### DevRel - Publish a contributor walk‑through video — context/update #share. - Host office hours on labeled issues — context/update. - Draft “first PR with previews” guide — context/wpaccessibility.org. - Track contributor funnel metrics — context/GitHub project. #### OSPO - Define contribution policy and review SLAs — context/update. - Document AI‑use boundaries for docs — context/update. - Align repo migration RACI — context/GitHub org. - Set governance rubric for docs changes — context/Handbook. #### Community - Run a docs sprint with topic labels — context/issues. - Pair new writers with reviewers — context/update. - Publish monthly impact report — context/project board. - Offer non‑GitHub submission form — context/update. #### WordPress - Documentation: add examples‑first patterns — context/KB pages. - Accessibility: create issues heatmap — context/issues. - Meta: ensure PR previews reliability — context/site ops. - Training: build “A11y docs style” course — context/learn. #### The WPCC - Programs: fund microgrants for A11y authors — context/update. - Projects: sponsor October writing hours — context/Rian note. - Funding experiments: milestone payouts per merged page — context/issues. ### FAIR - Policies and covenants: transparency on funding per page — context/report. - Productized governance artifacts: docs style guide template — context/KB. - Technical independence: track provenance of migrated pages — context/repo. ## 🧪 Hypotheses - PR previews increase review participation by 30%+ in one month. - Topic labels reduce average time‑to‑merge by 25%+. - Non‑GitHub path increases unique contributors by 20%+. - AI‑limited policy improves readability scores without slowing throughput. ### 📊 Methodology - A/B compare repos with and without previews; measure comments/PR. - Time series on labeled issues; compare TTM pre/post labels. - Track contributor unique IDs across channels; month‑over‑month. - Run readability audits and editorial defects per page. ### ❓ Questions - Which pages are highest priority for October? - How will migration affect existing links and SEO? - What is the review SLA per page type? - How are accessibility standards versioned in the KB? ### 🔮 Futu - Summary: This update informs you about: the Knowledge Base is ready to contribute, issues on GitHub with what needs to be worked on, the work planned for October 2025 and how you can help. - URL: https://make.wordpress.org/accessibility/2025/09/30/wp-a11y-docs-update-september-2025/ 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](https://wpaccessibility.org/) ready to contribute. All accessibility content from the [current handbook](https://make.wordpress.org/accessibility/handbook/) is copied into this website. Also new placeholder pages are made, for new content. Yoren Chang [@1fixdotio](https://profiles.wordpress.org/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](https://wpaccessibility.org/docs/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](https://wpaccessibility.org/docs/topics/). For review and rewrite of the content. Each issues is labeled by topic. For example the page [Headings in the content](https://wpaccessibility.org/docs/topics/content/headings/) now has an alert, about what needs be done with the content and a link to the [related GitHub issue](https://github.com/wpaccessibility/wp-a11y-docs/issues/106). #### How can you help? On [How to contribute](https://wpaccessibility.org/docs/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](https://github.com/orgs/wpaccessibility/projects/3). 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](https://profiles.wordpress.org/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](https://www.meetup.com/nl-NL/wordpress-amsterdam/events/307231059/) (Amsterdam) and [WPMeetup030](https://www.meetup.com/nl-NL/wordpress-meetup-utrecht/events/310887927/?eventOrigin=group_events_list) (Utrecht). You can help her by sponsoring [Rian’s time and expenses](https://github.com/sponsors/rianrietveld/). [@Aminul](https://profiles.wordpress.org/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](https://profiles.wordpress.org/joedolson/) and [@1fixdotio](https://profiles.wordpress.org/1fixdotio/) work on the remaining issues in wpaccessibility.org itself., WP A11y Docs Update September 2025, Make WordPress Accessible, 01k6nvcjwtgkws3h8ed8sve4hz.