Ways to Organise the Accessibility Initiative
Since the news that some WordPress teams are to be merged, I’ve been thinking (a lot) about this group might move forward. First off, I need to say that I do understand why it might be necessary to merge some groups. Too much fragmentation is as bad as an overly centralised system when trying to manage/coordinate work whilst also ensuring a constant trickle of new blood.
But I don’t think merging is the answer for this group. Accessibility is too over-arching an area to work well if we try to split it down into separate groups. We’re likely to lose impetus with over-dilution, Plus we will loose the opportunity to attract assistive technology users who could, longer term, become a panel of expert testers. We actively need an ongoing dialogue between technical developers and non-technical users to help wordpress.org develop effective accessible solutions.
So I feel that we need to stay as a separate group but with direct links into the other groups – possibly via designated lead developers.
If that’s possible, then we’ll also need to work hard to coordinate and communicate the changes that are taking place — both in terms of what we’ve achieved and to highlight work in other groups where we might be able to contribute. To that end, I’m going to see if I can pull in feeds from some of the other groups to see if will help us to highlight areas where we need to get involved.
If you’re already involved in discussions in other groups or in Trac, then please let us know what you are doing via a status update here. If you do not have posting privileges here, let me know and I’ll sort that out for you.
In the meantime, if anyone has any other ideas of how we can ficus our efforts more effectively, then please chime in.