There's rapidly growing interest and activity in Open Source Education
and this is a great opportunity use student energy for solving
accessibility problems as well as ensuring students get real world
knowledge and experience.
The Mozilla Foundation have started worked on an Open Education
Program that builds on the proven work of David Humphrey at Seneca.
Core accessibility development work has a very long learning curve so
is unlikely to be a good candidate but testing core or other areas
should be good candidates.
In addition to Mozilla and Seneca a growing number of groups are
working in this space including the National University of Singapore
and OSS Watch (www.oss-watch.ac.uk) while Project:Possibility
(www.projectpossibility.org) are specifically working with
accessibility at USC and UCLA. So now is the time to make sure
accessibility is given due representation from the start.
Besides the core a11y, which is really a biggie to digest in a short
time, there are many areas that are related to accessibility in various
forms which would certainly be great for students to work on and see the
results in the product soon.
I'm especially thinking of keyboard navigation/control availability
issues like this Firefox Places Organizer bug:
<https://bugzilla.mozilla.org/show_bug.cgi?id=414750> - When performing
a Search in Places Organizer, inaccessible buttons appear (no tab order)
or the various theming/zoom display issues that we have floating around
in Bugzilla and which someone with both programming and artwork/graphics
skills/interests could look at.
I certainly look forward to nominating a few of these and help mentor
students implement these!
> there are many areas that are related to accessibility in various forms
> which would certainly be great for students to work on and see the results
> in the product soon.
For the ProjectPossibility SS12 weekend code-a-thon it would be great
to find things that have a really short learning curve. Perhaps small
feature ideas rather than 'fix it' bugs. Plus the right mentor.
On 21.02.2009 13:11, Steve Lee wrote:
> For the ProjectPossibility SS12 weekend code-a-thon it would be great
> to find things that have a really short learning curve. Perhaps small
> feature ideas rather than 'fix it' bugs. Plus the right mentor.
Hmm I do not know if we actually have many enhancement/feature requests
that are small. The problem with accessibility is that it tends to get a
bigger project really fast usually. :-(