Nasim Miah 5:44 pm on November 18, 2025
Tags: ,   

Accessibility Team Meeting Notes: Nov 13, 2025

On Thursday, November 13, 2025, 15:00 UTC, a team meeting started in #accessibility facilitated by Nasim Miah. You can read the full transcript or see the meeting agenda.

Biweekly Team Meeting Time Update

The bi-weekly chat meeting time has changed to alternate Thursdays at 15:00 UTC, and the meeting calendar is also updated.

Updates from working groups

Documentation:

@joedolson shared a documentation update on behalf of @rianrietveld:

  • wpaccessibility.org now has a proper search function.
  • Several documentation updates about webforms are under review and expected to be published soon.
  • The new “Debunking 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) myths” page is available here: https://wpaccessibility.org/docs/start/myths/overlays/
  • Rian is also working on implementing the new design, after which the WCAGWCAG WCAG is an acronym for Web Content Accessibility Guidelines. These guidelines are helping make sure the internet is accessible to all people no matter how they would need to access the internet (screen-reader, keyboard only, etc) https://www.w3.org/TR/WCAG21/. EM-audit can begin.

A key reminder: contributors should contact @rianrietveld before starting work on any documentation section, and should not submit PRs for issues that already have an assigned owner.
@joedolson also noted ongoing problems with PRs containing AI-written documentation, which currently does not meet quality standards.

On the topic of the accessibility profile badge, @joedolson suggested that contributors working on accessibility documentation should be eligible.

  • Nasim Miah agreed, noting it encourages consistent, quality contributions.
  • Both agreed badge criteria may need clearer standards, aligned with other teams.
  • Increased Profile Associations requests were noted; Nasim Miah also observed this trend.
  • @joedolson said smaller contributions are still considered, but must meet reasonable quality.

General

@joedolson reported that with the release of 6.9 RC1, work is now shifting toward preparing for 7.0. This week’s bug scrub focused on new tickets on TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. that were awaiting review, and most of those have been milestoned for the 7.0 release.

Next week, the focus will shift to older tickets, prioritizing ones that need attention.

In this release, 33 accessibility issues were resolved on Trac and 43 issues were resolved on GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/.

Gutenberg

@joedolson shared that all new 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/ features should continue to be tested during the Release CandidateRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. phase, and accessibility bugs should be resolved before release.
Features that didn’t make it into 6.9 — such as Tabs BlockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience., Icons Block, and Template Management are likely candidates for 7.0.

He also noted that major items requiring attention are listed in the Release Progress document:
https://make.wordpress.org/accessibility/current-release-progress/

🗓️ Next Meeting Schedule

@joedolson noted that the next meeting is currently set for November 27th, which falls during the US Thanksgiving holiday, meaning many contributors will be unable to attend. He proposed skipping the meeting or shifting it by a week.

Nasim Miah agreed, saying it makes sense to skip the November 27th meeting and resume on December 4th instead.

@joedolson confirmed he will update the calendar and ensure the change is clearly noted in the meeting minutes.

NOTE: If you’d like to have a topic added to the agenda for our next meeting, please mention it in the comments on an upcoming agenda.

Thank you, @joedolson for the pre-publish review.

#accessibility, #meeting-notes

Nasim Miah 7:37 am on November 13, 2025
Tags: ,   

Accessibility Team Meeting Agenda: Nov 13, 2025

This is the proposed agenda for the bi-weekly 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 on Thursday, Nov 13, 2025, 15:00 UTC

Updates from the working group

  • Documentation
  • General
  • 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/
  • Themes

Open floor

If you want to have a topic added to the agenda, please mention it in the comments of this post.

The Accessibility Team bug scrub is every Tuesday at 15:00 UTC, held in the #accessibility channel on the Make WordPress 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/. (registration required).

#accessibility, #agenda

Krupa Nanda 7:54 am on November 4, 2025
Tags: ,   

Accessibility Team Meeting Notes: October 30, 2025

On Thursday, October 30, 2025, 15:00 UTC, a team meeting started in #accessibility facilitated by @krupajnanda. You can read the full transcript or see the meeting agenda.

Updates from working groups

Documentation Updates

  • Publishing of new documentation on wpaccessibility.org has started.
  • Three new topics are now available:
    1. Frontend code: Accessible name
    2. Web forms: Input field and form label
    3. Web forms: Input field and description
  • Site maintenance: 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) of wpaccessibility.org will be fixed by Joe and audited soon.
  • Outreach: @rianrietveld presented the project at WordPress Meetups in Amsterdam and Utrecht. Next presentation scheduled for November 27 at WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Netherlands.

How others can help:

  • Read and share feedback on the new content at wpaccessibility.org.
  • Pages about web forms need examples of how plugins handle accessibility.
    • Contributors from WordPress form plugins are invited to share input via the contact page.
  • Extended update available at WP A11y Docs update October 2025.
  • Volunteers are needed to review new documentation and take ownership of unresolved issues.

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/ Updates

  • WordPress 6.9:
    • Most changes have been merged into coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..
    • Some remaining bug fixes will be backported.
    • Notable updates are still in progress for the Notes feature.
    • Joe will begin preparing the Accessibility Improvements List in the next couple of weeks for clearer tracking.

Themes Updates

  • @joedolson connected with @alh0319 to coordinate on finalizing the updated accessibility-ready guidelines.
  • Work is planned for late November, with the goal of having updates ready for broader review in December or January.
  • A special meeting with the Themes team will be scheduled once the guidelines are ready.

NOTE: If you’d like to have a topic added to the agenda for our next meeting, please mention it in the comments on an upcoming agenda.

#accessibility, #meeting-notes

Krupa Nanda 7:34 am on October 30, 2025
Tags: ,   

Accessibility Team Meeting Agenda: Oct 30, 2025

This is the proposed agenda for the bi-weekly 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 on Thursday, October 30, 2025, 15:00 UTC

Updates from the working group

  • Design
  • Documentation
  • General
  • 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/
  • Media
  • 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.
  • Themes

Open floor

If you want to have a topic added to the agenda, please mention it in the comments of this post.

The Accessibility Team bug scrub is every Tuesday at 15:00 UTC, held in the #accessibility channel on the Make WordPress 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/. (registration required).

#accessibility, #agenda

Rian Rietveld 9:36 am on October 29, 2025
Tags:   

WP A11y Docs update October 2025

This update informs you about:

  • publishing of new documentation has started;
  • 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) of wpaccessibility.org itself;
  • presentations at WP Meetups about the project;
  • how you can help.

Accessibility information for web forms

We started publishing documentation in the section Standards and best practice.

Three topics are now published:

For the pages about web forms we need examples of how WP plugins handle this (or don’t handle this).

Accessibility of wpaccessibility.org

@joedolson is working on making the search option at the top of each page, fully accessible. We hope to finish that soon. After that Level Level will perform an official WCAG EM audit. Because we need to practice what we preach.

Making noise

Rian gave two presentations at the WP Meetups, in Amsterdam and Utrecht about the project; This resulted in more readers and reviewers of new documentation and also possibly one more sponsor. The next talk will be November 27 ’25 at WordCamp Netherlands.

How can you help?

Read new content and let us know what you think. We write for you! Can you understand it, is it helpful, do you need more or different examples. New content doesn’t starts with the alert “This content needs to be reviewed and expanded”.

For the pages about web forms we need examples of how plugins handle accessibility. Do you use or work for one of the major WordPress Form plugins and want to help? Please contact us, we need your expertise.

Plans for november 2025

  • Continue to write the documentation about web forms.
  • Make sure wpaccessibility.org is WCAGWCAG WCAG is an acronym for Web Content Accessibility Guidelines. These guidelines are helping make sure the internet is accessible to all people no matter how they would need to access the internet (screen-reader, keyboard only, etc) https://www.w3.org/TR/WCAG21/. 2.2 AA accessible.

#wp-a11y-docs

Nasim Miah 3:30 pm on October 21, 2025
Tags: ,   

Accessibility Team Meeting Notes: October 16, 2025

On Thursday, October 16, 2025, 15:00 UTC, a team meeting started in #accessibility facilitated by @muddassirnasim. You can read the full transcript or see the meeting agenda.

Biweekly Team Meeting Time Update

The bi-weekly chat meeting time has changed to alternate Thursdays at 15:00 UTC, and the meeting calendar is also updated.

Bug Scrub Schedule for WordPress 6.9

Updates from working groups

Design

No Update

Documentation: @rianrietveld reported that Work on the WP Knowledge Base

  • Rian started with (re)writing content about accessible web forms. @GaryJones and @Annelies Verhelst help with reviews. Nothing published yet, all in review at the moment.
  • Vyshnavi Kurapati works on improving the search functionality of the website
  • Jeffrey Lauwers will look at the design of the website, to give it a more professional and usable look and feel.

MigrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. handbook: @aialvi works on the migration of the current handbook to a new GithubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ repo 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-handbook on github.com/wordpress.

General

@joedolson We’re under a week from betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1. There are now 14 tickets in the milestone, three of which need to be completed before beta 1. 28 tickets have been completed. The three tickets remaining in the milestone are plausible, assuming I can find the time to get through them all.

Gutenberg

@joedolson reported that, the icons blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. has been removed from 6.9, but the Accordion block has been stabilized and Block Comments (now Notes) is in the process of being stabilized. Both of these have been reviewed extensively, but don’t hesitate to keep re-checking. The Tabs Block is still undetermined, but will need additional accessibility review.

Media

@joedolson reported that There’s been good progress on #63895, but could really use more stock photo examples to test. Contact @saj1ad to provide images. (An update from Sajjad would be helpful here regarding whether he’s received any samples yet.)

Themes

@joedolson noted that looking towards having updates on accessibility-ready after WP Accessibility Day. @joedolson will follow up with @alh0319 to move this forward.

NOTE: If you’d like to have a topic added to the agenda for our next meeting, please mention it in the comments on an upcoming agenda.

Thank you, @joedolson for the pre-publish review.

#accessibility, #meeting-notes

Nasim Miah 1:07 pm on October 16, 2025
Tags: ,   

Accessibility Team Meeting Agenda: Oct 16, 2025

This is the proposed agenda for the bi-weekly 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 on Thursday, October 16, 2025, 15:00 UTC

Updates from the working group

  • Design
  • Documentation
  • General
  • 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/
  • Media
  • 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.
  • Themes

Open floor

If you want to have a topic added to the agenda, please mention it in the comments of this post.

The Accessibility Team bug scrub is every Tuesday at 15:00 UTC, held in the #accessibility channel on the Make WordPress 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/. (registration required).

#accessibility, #agenda

Nasim Miah 1:56 pm on October 4, 2025
Tags: ,   

Accessibility Team Meeting Notes: October 02, 2025

On Thursday, October 2, 2025 at 11:00 PM GMT+8, a team meeting started in #accessibility facilitated by @muddassirnasim. You can read the full transcript or see the meeting agenda.

Biweekly Team Meeting Time Update

The bi-weekly chat meeting time has changed to alternate Thursdays at 15:00 UTC, and the meeting calendar is also updated.

Bug Scrub Schedule for WordPress 6.9

The bug scrub schedule for WordPress 6.9 has been prepared for its upcoming release.

Updates from working groups

Design

@joedolson reported that the admin redesign is officially no longer part of the 6.9 roadmap, so it will not be an immediate concern. This outcome was largely expected.

There will also not be a new default theme in this release cycle, which means design needs are relatively light.

Documentation

@rianrietveld reported that the WP Knowledge Base is now ready for contributions 🎉. All 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) content from the current handbook has been copied into wpaccessibility.org, and placeholder pages have been created for new content. The How to contribute pages are finished, including information for contributors who don’t work with GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/. A tracking issue is available with details on what still needs to be written.

Rian will write the web form documentation herself, as she has permission to use materials written for the Dutch government. Level Level, a Dutch WordPress agency specializing in accessibility, will conduct an official WCAGWCAG WCAG is an acronym for Web Content Accessibility Guidelines. These guidelines are helping make sure the internet is accessible to all people no matter how they would need to access the internet (screen-reader, keyboard only, etc) https://www.w3.org/TR/WCAG21/.-EM audit on wpaccessibility.org at the beginning of November, with the goal of having all accessibility issues fixed by then. Contributors are encouraged to pick tasks from the projectboard Wp A11y Docs, but should only contribute on topics they know well, as AI is not yet reliable in accessibility.

For October, @rianrietveld will start writing content on web forms. @aialvi will work on migrating the current handbook to a new GitHub repository on github.com/wordpress. @joedolson and @1fixdotio will focus on the remaining issues in the website itself.

General

@joedolson reported that we are just under three weeks away from betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 of WordPress 6.9. There are 19 tickets still in the milestone, including five enhancements/features that need to be committed before beta. So far, 25 tickets have been completed for this milestone.

All enhancement and feature tickets were scrubbed on Tuesday and are in good shape, with most looking plausible to complete. However, a few are at risk. Ticket #48655 has had only minimal progress with some initial research, and ticket #49876 has seen no recent involvement from its contributor, meaning significant work is still needed.

Overall, the milestone is in good shape despite these concerns.

Gutenberg

@joedolson reported that several major features are in progress that are important for accessibility, including the Icons blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience., Tab block, Accordion block, and Block Commenting. He has reviewed the Icons block, Accordion block, and Block Commenting, but has not yet had time to review the Tabs block.

Feedback on the Accordion block and Block Commenting is in good shape. However, the Icons block has been shifting directions frequently, and accessibility feedback has not yet been addressed. Joe plans to review the Tabs block this week and will revisit the Icons block to confirm whether his earlier feedback is still relevant after the changes.

There may be additional issues, but these are the main updates at this stage.

Media

@joedolson reported that testing on ticket #63895 is in progress, but more image sources are needed to ensure thorough results. In particular, images from major stock photo sites such as Shutterstock, Adobe Stock, Getty Images, iStock, and Alamy would be helpful. Contributors who have access to new images from these sources are encouraged to share them with @saj1ad, who is collecting them.

This ticket is not currently set for the 6.9 milestone but could be included if these issues are addressed in time.

Themes

@joedolson noted that @amberhinds is working on the theme accessibility ready guide. However, with WP Accessibility Day happening in less than two weeks, it is unlikely that there will be updates on this work until November.

@joedolson also mentioned that it may be difficult for him to attend the next meeting, since Accessibility Day will be ending just as the meeting begins.

NOTE: If you’d like to have a topic added to the agenda for our next meeting, please mention it in the comments on an upcoming agenda.

Thank you, @krupajnanda for the pre-publish review.

#accessibility, #meeting-notes

Nasim Miah 12:01 pm on October 2, 2025
Tags: ,   

Accessibility Team Meeting Agenda: Oct 02, 2025

This is the proposed agenda for the weekly 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 on Thursday, October 02, 2025, 15:00 UTC

  • Bug Scrub Schedule for WordPress 6.9

Updates from the working group

  • Design
  • Documentation
  • General
  • 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/
  • Media
  • 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.
  • Themes

Open floor

If you want to have a topic added to the agenda, please mention it in the comments of this post.

The Accessibility Team bug scrub is every Tuesday at 15:00 UTC, held in the #accessibility channel on the Make WordPress 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/. (registration required).

#accessibility, #agenda

Rian Rietveld 6:16 am on September 30, 2025
Tags: , ,   

WP A11y Docs update September 2025

This update informs you about:

  • The Knowledge Base is ready to contribute.
  • Issues on GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ 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 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) 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 installLocal Install A local install of WordPress is a way to create a staging environment by installing a LAMP or LEMP stack on your local computer.. 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 migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. 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.

#accessibility, #make-wordpress-org-updates, #wp-a11y-docs