In the previous blog post I discussed the guidelines I suggested we follow with regard to web accessibility. Although that discussion remains open, and I encourage more feedback, I think it would make sense not to get too hung up on that conversation.
Today, I would like to discuss the various action items this task force needs to accomplish and the timeframe in which they can be accomplished, and then begin dividing up the work.
Here are the major action items I think would make sense for this task force to undertake, with the proposed name of the leader for that action item, proposed start date, and a few sub-items to give a little more information on the work involved with each part. It should be noted, the â€œleaderâ€ just means who will head up a particular subsection of this effort. For example, I donâ€™t expect Cory to rewrite the style guide herself, but I would hope that she could take responsibility for that part of the task force to get the guide rewritten.
- Style Guide Revisions (Cory Lampert) â€“ Start Date: January
- Formalize coding standards everyone has to follow
- Require Alt Tags
- No â€œClick hereâ€ links, etcâ€¦
- Automated Accessibility Testing (Brian Egan) â€“ Start Date: January
- Choose the tool(s) (AChecker/CynthiaSays/Lift/etc)
- Create a plan to check all current pages with AChecker and our determined guidelines
- Build Accessibility into the Drupal Publishing workflow
- Use an editor with Achecker built in
- Generate lists of updated/modified pages that need testing
- Live Accessibility Testing (Alexis & Michael) â€“ Start Date: January, testing begins when new CML site is finished
- Establish Working relationship with DRC
- Identify Tests that need to be run
- Which browsers need checking?
- Which pages are most important at first?
- Establish testing standards / methods of testing
- Who will run tests?
- How will they be scheduled?
- How often will they occur?
- Work with DRC to find students who can help us perform live tests
- Possibly coordinate incentives
- Web Developers Training (Kee) â€“ Start Date: January
- Create Screencasts / Presentations for Web Dev Meetings
- Common Accessibility Pitfalls
- Working with the automated accessibility checker in Drupal
- Modify / Add to our website (Brian Egan) â€“ Start Date: January
- Accessibility Feedback Form, something like: http://library.buffalo.edu/libraries/aboutus/policies-use/accessibility.php
Ok, Iâ€™ve been kind enough to put some of your names on these items (youâ€™re welcome! =P), but that was just my best guess as to who would be interested in leading each particular section. In addition to leaders, we need a volunteers to help with each section, particularly the Live Testing. If you have an interest in helping out with one of these sections, please let us know in the comments!