E-mail List Archives
Re: quicktime accessibility
From: Jared Smith
Date: Jul 8, 2004 1:12PM
- Next message: pony_smith: "Re: quicktime accessibility"
- Previous message: cbsmith: "ASP.NET IE WebControls & JAWS"
- Next message in Thread: pony_smith: "Re: quicktime accessibility"
- Previous message in Thread: pony_smith: "quicktime accessibility"
- View all messages in this Thread
You are experiencing one of many discrepancies between how the media
player object interacts with different browsers. Your code is correct
- it's just that the browsers handle the media 'plugin' differently. I
typically recommend that media be opened in the stand-alone player
when possible, as the players tend to have a much broader array of
accessibility options than the embedded plugin. You can read a quick
review of stand-alone versus embedded players at
http://www.webaim.org/techniques/captions/mediaplayers/
Note that the Quicktime comparison does not indicate the missing
keyboard control that you have described.
If the stand-alone player is not an option, you might use scripting
with external buttons that could be used to control the media playback
using mouse or keyboard.
Jared Smith
WebAIM (Web Accessibility In Mind)
Center for Persons with Disabilities
Utah State University
- Next message: pony_smith: "Re: quicktime accessibility"
- Previous message: cbsmith: "ASP.NET IE WebControls & JAWS"
- Next message in Thread: pony_smith: "Re: quicktime accessibility"
- Previous message in Thread: pony_smith: "quicktime accessibility"
- View all messages in this Thread