So the community summit, the contributor day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. and WordCamp 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. Europe happened in Paris. And this is what we learned from all the discussions we had during that warm week in June:
Education instead of taking over
The accessibility 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 must not try to do everything themselves. Like raise and solve all accessibility trac tickets themselves. What we should do is add to the tickets how they should be solved and let other developers do the patches (or ask them to do). Hopefully this will attract more developers to do accessibility tickets. That way the developers will learn instead of handover to us. Now the team is like a proxy, everything needs to go though us, slowing the process down. What we need to accomplish is that the developers solve the issues themselves, and we just help them if needed.
Handbook
The handbook must be replaced by a list of resources, good examples and test tools, with short explanations. We don’t need to write everything ourselves, but make list of links with a short intro per subject. Focus on education and point to good info. In other words: help and educate the developers instead of fixing ourselves.
Testing and research
We need to ask more a11y 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) experts from outside the WordPress community to assist us with the testing and research. For this we can reach out to companies specialised in accessibility, ask them if they can sponsor time to do research on WP core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and featured projects.
So this defines 3 tasks for the a11y team
- Teach: Provide easy to use overview of resources for developers
- Research: Test and research current and new functionality for accessibility
- Help: Review and raise accessibility tickets and provide developers with info on how to solve the issues
This doesn’t mean we won’t be working on tickets and issues on GitHub 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/, we want to move our team focus to research, education and support.
