Searchbox is here: Alt plus 4

|Go to main content|

Accessibility information page

|
 

Navigation begins here

Home (1)|
Tutorial (U)| Formats (F)| Tags (G)| Tools (L)| Resources (R)| Questions? (Q)|  

Tutorial|

1. Introduction|

2. Definitions|

3. Living with Disabilities|

4. Accessibility Basics|

5. Structure|

6. Navigation|

7. Appearance|

8. Content|

9. Data|

10. Multimedia|

11. Evaluation|

Multimedia

Sites have become more interactive as web designers and their tools have become more sophisticated. The benefit has been (sometimes) a more engaging and meaningful presentation of content and certainly greater variety. The challenge is to ensure that relevant content is communicated to those who are visually, hearing, physically or cognitively impaired, whether it is visual, sound or interactive, and in a format that is accessible.

Visuals

Visuals represent a serious challenger for those with visual impairment and must be made accessible through the addition of descriptive text and captioning that can be accessible to screen readers. MAGpie (Media Access Generator) (ncam.wgbh.org/webaccess/magpie/) allows designers to create captions, subtitles and/or describe the content in audio format. MAGpie works with QuickTime, Synchonized Multimedia Integration Language (SMIL) from the W3C, and Synchronized Accessible Media Interchange from Microsoft.

Captioning is preferable to transcripts because text that is contiguous with video provides sighted and hearing impaired users with better context. Captioning also benefits students with learning disabilities and provides clarification for students for whom English is a second language.

Sound

Sound presents a challenge to persons who are deaf or hard of hearing. Again, captioning is very useful for providing accessibility. It is also important to include descriptions of sounds and relevant activity so that hearing impaired persons can be provided adequate context.

Interactivity

Interactive content or functionality, for example, a user using a mouse to access a drop down menu, must also be available through the keyboard. This should be done in two ways: through providing alternative HTML code in case the assistive technology does not support javascript, and through tab-based commands that parallel mouse-based actions.

Alternative Code

Code example:

Drop down menu

 

Tab-based Commands

Insert list of equivalent commands

Code example:

Formats

Designers have two options for providing access to multimedia: through embeded media players or standalone players. Standalone players are currently so much more accessible from a keyboard than embedded players that they are recommended even though it results in a separate window and application opening. webAIM has provided an excellent screen reader-accessible comparison of media players. To make the transition less confusing, always inform users that the media will open in a separate window and give directions for returning to the website using their browser.

For example:

 

 

 

 
   
Bobby WorldWide Approved 508

Secondary navigation begins here

| About this site (B) | Email (E) | Site Map (3) | Comments (9) |