WordPress constantly evolves and improves. It is never “done.” The same is true of WordPress 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). Changes in design, user experience, and code need to be evaluated. The community needs continuing educational support in accessibility.
Accessibility Team tasks:
- Provides support in the forums.
- Meets in the WordPress Slack #accessibility channel.
- Helps with the discussion of possible solutions.
- Contributes documentation to the:
- Develops and maintains an accessibility standard for themes.
- Distributes design pattern code examples on GitHub.
- Performs tests and audits.
- Gives presentations at WordCamps and Meetups.
- Writes tickets and patches on the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. tracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/..
- Extends WordPress with plugins.
- Reviews themes for the WordPress.orgWordPress.org 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. https://wordpress.org/ repo.