Yes you! Don't forget your nifty TOOLBOX web 2.0 tools to meet your needs. Shelley Haven is an assistive technology consultant with an easy to read website that can serve as a basic primer when first learning about supportive web 2.0.
- Support interfaces commonly used by screen readers.
- Can be operated using only the keyboard.
- Allow the user to request more time to complete timed responses.
- Support customization of display attributes such as color, contrast, and font size.
- Support interfaces commonly used by screen magnifiers.
- Provide documentation in an accessible format.
- Support alternatives to audio information.
- Support adjustable volume control.
Accessibility is most considered in regards to those people with physical disabilities that prevent them from accessing everything on the web as it is designed to. For those somewhere on the spectrum of blindness, hearing impaired, immobility, and other challenges, assisstive technologies often intercede for them when on the web. However, the dynamic nature of the new web 2.0 tools have out-paced the capabilities of the supports. Below is a basic explanation.
New Scripts and Images Too Complex for
Current Assistive Technologies
Example: Interactive Media
The diverse interactive web 2.0 applications enrich the learning experience. However, the accessibility of these tools for those with audio, visual, dexterity, and cognitive disabilities (for example) is poor. Therefore, interactive, distance, and virtual learning environments are becoming prohibitive for the hundreds of millions of people with disabilities.
Code Not Translatable
The addition of vivid images, diverse script and font sizes, increased navigation, varied multi media, animations and data tables are usually not accompanied by html text descriptions. Referred to as incorrect coding, these items cannot be read by assistive technologies. The fundamental concept of the new codes are too varied and descriptions for images are almost nonexistent.
Code Can No Longer Mediate Content
Accessibility must be addressed through the context of design and open standards across all platforms just as the world wide web was originally developed. At that time, enabling software for those with sight and hearing impairments worked across different software and operating systems.
Uneven Interface
Websites with Ajax and other forms of Java script as well as the newer Vista operating system of Windows have all abandoned the previous translatable formats.
Example: Touch-Sensitive Screen on iPhone and iPad
The touch-sensitive flat screen that serves as thetinterface for the operating system on the iPhone and iPad is a striking design, but comes with multiple accessibility problems. There are obvious implications those with vision impairments when there are no physical markers to point to the functions.
No comments:
Post a Comment