I recently accepted the lead of the Sakai Accessibility Working Group. It’s an honour and a challenge and I’m going to make the most of it.
At Brock University we use Isaak as our learning management system, which is based on the Sakai CLE. In Ontario Canada we’re operating under the increasingly more stringent Accessibility for Ontarians with Disabilities Act (AODA) which wisely cites the various levels of the WCAG 2 as its own standards. Because of this and because its the responsible and technologically ideal way to proceed: web accessibility is important to me.
I’m a big believer that there’s a lot that can be done to improve web accessibility if more people just had a little more knowledge about the issue and the solutions and were able to apply that knowledge at the correct time.
To that end I’m coordinating conference calls about Sakai accessibility every other Thursday at 2:00 eastern (all are welcome – Add the next meeting directly to your calendar.). What we do as an accessibility working group is review general issues and trends in the Sakai CLE (sometimes there’s an OAS), set goals, offer advice, and slog through the JIRA tickets (bugs in the bug tracker) and offer to add a solution, advice or other wisdom as needed. We’re also trying to spread critical web accessibility information in the Sakai community and beyond.
Projects in the Sakai community include ongoing information sharing and canvasing (even, blogging) about the need to get more people involved, and reaching out to other upstream projects, like CKEditor and JQuery UI to both pass feedback to them and to apply their latest and greatest solutions to Sakai.
I don’t claim to be an accessibility expert, but I do understand the standards and I’ve been writing HTML so long I the two platforms I originally had to test on were a 486 Compaq and an Amiga A2000HD. More importantly, I care.