Event Title: Innovation with Accessibility Policy Institute
Date: Monday, July 26th, 2011
Location: Michael E. Moritz College of Law
I attended this all day event in which speakers from educational, legal, and non-profit sector discussed “procuring, developing and implementing innovative enterprise & learning technologies with ADA requirements” with a particular focus on the web. As a dilettante in web development and interface design, I found this to be a useful session. I see accessibility is a close cousin of what’s known in web coding circles as “markup validation” (essentially a spell check for the language used to code websites). Making sure one’s site is validated improves accessibility, though it doesn’t solve all problems. As an administrator of web content who typically stays on top of validation, I haven’t always considered accessibility explicitly.
But what does it mean to be accessible? Daniel Goldstein, a legal expert and champion for accessibility, roughly stated that it means everybody should have “equivalent ease of access” to information. For instance, this means that a screen reader should be able to accurately represent information through text-to-speech or other means for those who are unable to view or read something in its native format. A typical restrictive practice are scanned texts that faculty might post for his or her class. If it’s purely an image, a screen reader would not be able to interpret it in any meaningful way. The National Federation of the Blink provides a list of accessible practices for the web, but some include:
- Links — Sufficient information is provided for the user to determine the purpose of the link (e.g., link text can be read by the screen access software to tell the user what the link will do).
- Charts — Screen access software can extract meaningful information from charts (e.g., a text description of information conveyed via a pie chart is easily available).
- Check Boxes and Radio Buttons — Text information about the purpose of checkboxes and radio buttons is easily available to screen access software, enabling the blind computer user to know what is being checked or unchecked.2
One of the overarching themes was that obstacles toward accessibility typically does not lie in the technology—it’s with the culture and administration. Faculty and decision-makers do not always have a clear understanding of why it’s necessary (even though it’s the law regardless of the make up of your class) and making it happen on a large university campus is difficult. However, Jonathan Lazar of Towson University in Maryland gave an overview of how it might be accomplished as well as an arsenal of selling points–some of which were in response to barriers that current disability service workers encounter when trying to build consensus. Here’s a small sampling:
- Do a campus audit and actually test technologies (instead of just asking) being used and bring it to the attention of top administration. It’s not just about disability services.
- Remind faculty that it’s not about restricting academic freedom. It’s about increasing access to information.
- Create incentives and penalties as well as a clear timeline for training and implementation.
- Provide clear language in RFPs and software contracts to require accessible features.
This was just a brief overview, but it had me thinking about a lot of other aspects of the university campus that accessibility could feed into. One of the recommendations given was that accessibility be lumped as a part of a larger solution or into a more widely accepted practice like universal design.
Thinking a little loftier but worth thinking about, I can see that there might be implications here for other things, such as faculty training. Providing accessible materials for students requires technical skills. The burden cannot be on disability services. It needs to happen at the point of creation. If accessibility training is a mandatory practice, there is an opportunity to create a learning course that also incorporates pedagogical instruction and a more unified campus.
What other impacts could a push towards a more accessible campus have?
Recent Comments