This afternoon I attended a webinar titled “Exploring Web 2.0 & Accessibility.” The webinar was moderated by Tom Conway of the Center on Disability Services at the University of Hawaii at Manoa. Conway defined web 2.0 and accessibility, focusing on strategies to cater to Section 508 regulations of the U.S. Rehabilitation Act.
The definition Conway provided describes web 2.0 as “a loosely defined term for web applications that go beyond displaying individual pages of static content and allow a community of users to interact with the site and each other by adding or updating the content.” In short, web 2.0 marks a transition of the user as a consumer of the web to a producer, incorporating various new technologies such as blogs, wikis, social networking, and other web applications that enable anyone to be an “author.” Because web 2.0 is a method to empower users, it is essential that developers follow accessibility regulations set forth by Section 508. Conway simplifies accessibility to four major components:
- Enabling content to be read by a screen reader.
- Developing content to be output device independent (examples: mobile phone, tablets, etc.).
- Enabling users to navigate content without a mouse.
- Labeling and captioning images and audio.
Section 508 regulations view accessibility as a civil rights issue. Conway stressed that fact that requiring the use of an emerging technology in a classroom environment when the technology is inaccessible to an entire population of individuals is discrimination. Accommodations and modifications to the program must be made for the student to receive similar educational benefits as others in the classroom.
Finally, the webinar discussed strategies for Section 508 compliance that we can incorporate into our own institutions. The first method he discussed was to develop a written policy outlining these regulations as it specifically pertains to individual institutions. As such, an institution should develop a compliance statement, and more importantly, follow through with these statements. The second method was to develop device output independent products. Conway recommended visiting W3C Mobile and taking advantage of the WebAim WAVE Evaluator tool. The third method was to adhere to Universal Design for Learning (UDL) principles, particularly providing multiple means of representation. Conway provided a link to the Center for Applied Special Technology.
I was a little disappointed in the webinar in that it provided a very broad overview of the concept, and I was looking more for specific tools and regulations one should follow, particularly in the field of educational technology. I took interest in the last few minutes of the webinar in which Conway described three strategies for adhering to Section 508 regulations. I explored further and found the specific standards that Internet information and applications should adhere to; in my case, the content that I develop for online courses should follow these standards. Section 508 provides the following provisions that developers should consider (http://www.access-board.gov/sec508/guide/1194.22.htm):
- A text equivalent for every non-text element shall be provided (e.g., via “alt”, “longdesc”, or in element content).
- Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.
- Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup.
- Documents shall be organized so they are readable without requiring an associated style sheet.
- Redundant text links shall be provided for each active region of a server-side image map.
- Client-side image maps shall be provided instead of server-side image maps except where the regions cannot be defined with an available geometric shape.
- Row and column headers shall be identified for data tables.
- Frames shall be titled with text that facilitates frame identification and navigation.
- Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz.
- A text-only page, with equivalent information or functionality, shall be provided to make a web site comply with the provisions of these standards, when compliance cannot be accomplished in any other way. The content of the text-only page shall be updated whenever the primary page changes.
- When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by assistive technology.
- When a web page requires that an applet, plug-in or other application be present on the client system to interpret page content, the page must provide a link to a plug-in or applet that complies with §1194.21(a) through (l).
- When electronic forms are designed to be completed on-line, the form shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.
- A method shall be provided that permits users to skip repetitive navigation links.
- When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.
My previous experience has introduced me to several of these provisions, but in the future I hope to make a conscious effort to develop content that adheres to Section 508 regulations. It will be one task to develop content that is 508 compliant, but a bigger task to revisit already produced content and redesign it to meet these standards. There are a few resources on campus, but one of my future tasks will be to research tools and resources that will help me as I transition to my new environment in St. Louis.