WCAG Labels

@rcuisnier -

Could you please provide an explicit list of improvements in the JW Player that you would like to see?

Not meaning to hijack the thread, but definitely need more accessibility features built in or easily implemented. Folks at OSU (http://wac.osu.edu/examples/jwpc/)have an older version that doesn't support html5, but has almost all the needed functionality built-in (keyboard controls, tab order, labels, etc.) At least in the government space this kind of functionality is critical and would certainly expand jwplayer's use.

Note: The UK has an "accessible" player, but it is 100% flash-based (http://blog.ouseful.info/2011/02/06/the-most-accessible-media-player-on-the-web/). It has great functionality, but limits usage to those devices that can use Flash.

@Steve -

Again, could you provide a list of specific features you'd like to see in the JW Player?

Taken primarily from the features in the OSU version, but the bottom line is full, section 508 compliance without needing additional plugins.

• Accessible to screen reader and keyboard: All controls are accessible via the keyboard alone, and buttons and controls are announced by the screen reader.
• Labels for controls (on, off, on mouse over)
• Captions and audio description built in.
• Full complement of shortcut keys
• Keyboard-accessible full-screen mode
• Jump increments determined by movie length
• Volume increments screen reader accessible
• Maintain a proper heading order: These non-visible headings are there so that screen reader users can easily find information about the movie and the movie controls. Web page authors can specify the level of the first heading, so that the page heading outline is maintained.

Others feel free to add to the list.

Forgot to add all functionality in both Flash and html5

That's perfects suggestions.
Could it be added to the future roadmap ?
Maybe for the 6.0 versions ?

Was this sufficient information?

Additional request would be to support the SAMI format for Closed Captioning

The Label Accessiweb FR doesn't validate this version of JW Player.
http://www.braillenet.org/accessibilite/cellule/label.htm

This would be great to ensure the support of WCAG :
http://www.longtailvideo.com/support/jw-player/22/making-video-accessible

@SteveW, rcuisinier -

Thanks for your feedback. I've created a ticket to address accessibility in the player using the points you've brought up. You can keep track of our progress here:

http://developer.longtailvideo.com/trac/ticket/1576

One feature to remember is the ability to activate the controls without first having to use the mouse to click on the video.

The example video you provide on http://www.longtailvideo.com/support/jw-player/22/making-video-accessible

provides keyboard controls but only after i have clicked on the video with my mouse.

This means that if I am only using a keyboard i have no way of accessing the video.

This seems to be a common problem with embedded players. As someone previously mentioned, Govts around the world are moving to WCAG 2.o having a player that meets these requirements will be an essential requirement for any new government site.I imagine this presents a good business case for making these improvements

@Gremlyn -

The ability to do this in Flash mode is heavily dependent on the browser implementation. For example, the following page does allow keyboard input when the user tabs over the player, but the functionality only works properly in Firefox:

http://developer.longtailvideo.com/player/trunk/fl5/js/test/examples/tabbing.html

As things transition to HTML5, the player will be more accessible via the keyboard.