Forum OpenACS Q&A: Accessibility Tutorial
I uploaded the slides I used during the tutorial: http://www.openacs.org/storage/index?folder_id=2478679
Since we haven't had time to see all of it, we'll organize online sessions to finish it. I'll inform in this forum about when and how.
look forward to see it.
In the slides I've uploaded last week, there's a reference to a test server. This server is no longer available for testing. Any dotLRN installation from HEAD can be used instead, the slides are based on the HEAD version.
I uploaded the pdf file with all the articles of the conference in the same place: https://openacs.org/storage/?folder_id=2478679
Lots of great reading for those of us that couldn't make it.
I count about 8 developers that will attend from Guatemala.
If you need a online conferencing system we can use the webex service at Galileo.
Thanks for reminding this :)
I had no specific plan so far since WCAG 2.0 is out and wanted to update the tutorial to the new guidelines first. But this may take a while and WCAG 1.0 is a subset so it's not that necessary to upgrade for a first tutorial.
Nevertheless I won't be available before end of january. Would that be OK for you?
I have been very busy lately since the beginning of the year and couldn't find a moment for the tutorial.
The initial plan was to update the current materials according to WCAG 2.0 and then to have the online tutorial. I think we can skip the first step and have the tutorial using the materials as they are.
Please, contact me by email or aim so we can arrange a date.
We will use Webex, so if it is first time you use it in your computer, I recommend start connecting 30 mins earlier.
How long it will last? not sure, I think Emma has 2 hours.
The whole tutorial will be recorded and published for future reference.
There are about 10 more seats available in webex for the session. So if there is a group of people I recommend to join together in a room so more can see it live.
If you are interested in attending, please contact mailto:email@example.com for reserving you seat and to get the information about how to connect. Also, if you have technical questions, please ask to that email. During the conference won't be solved any webex questions, so we don't waste time on it, so be early! We'll start on time!
Yo need the Webex ARF Player plugin (Windows and Mac only)
Thanks to Emma for the Tutorial !
You are welcome, it's been a pleasure
I'm sorry about the technical problems we had at the beginning, delaying the tutorial.
Let me insist that despite the tutorial lasted 2.5 hours, it covers only part of the accessibility issues to be considered when creating/reviewing/evaluating a website.
I think it would be interesting to have a one-day workshop on usability and accessibility at the next OpenACS/.LRN conference.
Thank you Rocael and Galileo team for the organization of the tutorial and your support.
We have uploaded the scripts mentioned in the accesibility tutorial here: https://openacs.org/storage/?folder_id=2478679
They use standard unix tools (sed, grep,...) to test some items of the WCAG 1.0 Checklist, priority 1 and 2.
It's possible to add exceptions, for each test and globals, in the exceptions directory. They will be evaluated as grep patterns, so regular expressions are ok, as well as simple expressions like filenames.
The script has a verbose option (-v), which shows a large description of each test being passed and the URL of the checklist item.
Usage: $ ./waitest [-v] priority directory
Example: $ ./waitest 1 /web/openacs/packages/
* Performing checks for Web Content Accesibility guidelines 1.0, priority 1
I have tested them in a Debian GNU/Linux box, results may be different on other Unixes with different grep/sed/... versions.
Adding new tests or editing existing ones is really easy:
1- Add the test description on waitest-descriptions.
2- Replace the dummy test on waitest-functions file with the new one.
3- Uncomment the test on waitest file.
Future: OpenACS integration, upgrade to WCAG 2.0, new tests, database interaction...
Hope you like it :)