The age of video on the Web is here! Both content creators and users have high expectations and you may become caught in the middle. Learn how to create an accessible media interface that will allow your institution to deliver high quality Flash video with closed captioning, convey a consistent design across your Web presence, and remain easy to maintain even after your “small” project is unexpectedly scaled to include hundreds of videos.

• 2008 Presentation slides
• 2008 Overview handout

Downloads to get you started:

• Download:
  • Version 1.0 (basic, a good place to start)
  • Version 1.1 (recently used in production)
  • Version 1.2 (adds full screen, link to transcript)
    
• Examples:
  • View the basic and production versions
  • dfxp.xml caption file
  • smil.xml file

Other Resources:

• Creating Captions
  • NCAM/Media Access Generator (MAGpie)
• ActionScript3 Documentation:
  • Using the FLVPlayback component
  • FLVPlayback component details
  • FLVPlaybacCaptioning component details
    
  • UILoader component details
  • Using a SMIL file
  • Handling events
• Community MX
  • Flash Video: Why the Other Players Don’t Get It By Robert Reinhardt
  • The Working with SMIL Series by Robert Reinhardt (You will need to be a member)
• GoToAndPlay.Net
  • Learn about the trouble we had with our streaming provider (and how it was fixed)
• SWFObject
  • Javascript Flash Player detection and embed script

Rick Ellis -Washington State

Much better! “Our job is to support mountain climbers”, he begins, a huge slide of Mt. Rainier behind him. Mt climbers? Yes, in a way I can see his metaphor. Getting resources on the web can often seem like a daunting task for our faculty and staff. We are the Sherpas to aid them and choose the tools to make sure that their message reaches all students.

Slowly, Rick begins to talk about the history of accessibility and describes what he refers to as the 1.0 and 2.0 versions of web accessibility. At the start, HTML was created only to convey the structure of the content, not the presentation. This was the only way to ensure that any single page could be displayed on different devices, browsers and screen readers. Then the browser wars messed that all up…