Educause 2006 - Accessibility Roundtable
Educause 2006
Dallas, Texas
Accessibility Roundtable
How is accessibility defined? Standards vs. Is it functionally usable?
Bring in real users.
Vendors don’t understand how assistive technology works.
Current Issues of group:
-How to raise awareness in university management.
-Captioning.
-Student Resources must be usable, not just compliant.
-Consortiums to support vendors with feedback (this has been done with Elluminate and BlackBoard).
Keep accessibility in mind while you’re building it.
BB received a white paper of complaints from a GROUP of universities. This gave the paper and complaints lots of credibility and it worked its way into the hands of those who could make changes.
Athenpro.org = higher-ed consortium to discuss accessibility.
Most problems: XHTML must be well formed – 90%, content of alt tags, color issues.
Steps to accessibility
1- use a validator, even though they only only measure 20% of web accessibility. (Some use “lift” as the code validator)
2- Perform a manual general check
3- Do a more specific, detailed check.
Add requirements to RFPs.
Are you accessible? Vs. Are you compliant?
It isn’t about disabilities – its about different learning styles and multiple approaches. (Think “I’ll teach more students, better!”) It’s the right thing to do.
It would be nice to have awards for accessibility – help the “cool” factor. Faculty culture “What’s in it for me?”
Connect.educause.edu
Google:
Lift – a tool - http://www.usablenet.com/
webct accessibility interest group
Freedom Scientific – University of Illinois
Dallas, Texas
Accessibility Roundtable
How is accessibility defined? Standards vs. Is it functionally usable?
Bring in real users.
Vendors don’t understand how assistive technology works.
Current Issues of group:
-How to raise awareness in university management.
-Captioning.
-Student Resources must be usable, not just compliant.
-Consortiums to support vendors with feedback (this has been done with Elluminate and BlackBoard).
Keep accessibility in mind while you’re building it.
BB received a white paper of complaints from a GROUP of universities. This gave the paper and complaints lots of credibility and it worked its way into the hands of those who could make changes.
Athenpro.org = higher-ed consortium to discuss accessibility.
Most problems: XHTML must be well formed – 90%, content of alt tags, color issues.
Steps to accessibility
1- use a validator, even though they only only measure 20% of web accessibility. (Some use “lift” as the code validator)
2- Perform a manual general check
3- Do a more specific, detailed check.
Add requirements to RFPs.
Are you accessible? Vs. Are you compliant?
It isn’t about disabilities – its about different learning styles and multiple approaches. (Think “I’ll teach more students, better!”) It’s the right thing to do.
It would be nice to have awards for accessibility – help the “cool” factor. Faculty culture “What’s in it for me?”
Connect.educause.edu
Google:
Lift – a tool - http://www.usablenet.com/
webct accessibility interest group
Freedom Scientific – University of Illinois