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 plans to vote for new team representatives for 2020 on Friday 8 November 2019 at 15:00 UTC.
Current accessibility team reps are @joedolson, @audrasjb, and @arush. We last set representatives on October 2018, so it’s been a year with the current reps.
Team reps are responsible for posting agendas, publishing meetings summaries, and generally leading communications inside the team. They coordinate cross-team efforts and they represent the accessibility team within the WordPress project. It’s a set of tasks that needs to happens each week. One challenge of being a team representative is that they do need to keep on top of a lot of things that are simultaneously going on.
Anyone who is an active contributor in the accessibility team can be elected as team representative.
For full information about team reps responsibility, see the related post on Make/Updates.
It’s a one-year term. We must have 2 team reps at least, to ensure duties are shared.
Existing reps are eligible to run for the election; there are no term limits. @audrasjb is still interested but wants to give priority to new people. Same for @joedolson who wants to give more time to his new core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. committer status.
Feel free to comment to ask questions. If you are interested for being an accessibility team representative, please comment this post to nominate yourself to stand for election.