Working Groups

If you want to help out, these are the groups you can join:

CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Core

The core working group will find 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). ( issues, write and discuss tickets on core trac and write code patches for WordPress core. Contact: Andrea Fercia (@afercia)

Top ↑

Documentation Documentation

The documentation working group will write documentation about accessibility in our Handbook and on other relevant places on The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. Contact: Sami Keijonen (@samikeijonen)

Top ↑

Theme team Theme team

The Theme team will review themes for the repo labeled with the accessibility-ready tag and the new core themes. Contact: Joe Dolson (@joedolson)

Top ↑

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. Meta

The Meta team will find accessibility issues, write and discuss tickets on meta trac and code patches for the website and Joe Dolson (@joedolson)

Top ↑

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. themes WordCamp themes

The WordCamp themes working group will review of the WordCamp themes and help with fixing the accessibility. Contact: David Kennedy (@davidakennedy)

Last updated: