WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: JW Player Controls v. 2 (JQuery version)

for

From: Ken Petri
Date: Oct 4, 2012 2:44PM


Hi Marcelo,

As you know JWPC is a wrapper around JW Player. But it wraps an older,
pre-HTML5-capable version of JW Player. When we wrote JWPC 2, the plan was
to use the latest JW Player, but we gave up, as we are not Flash experts
and the architecture of JW Player changed significantly since our first
version of JWPC. We just re-used the old JW Player guts.

As you point out, we make a couple of calls that allow us to check state on
captions and audio description. In the old JW Player, this was a pretty
easy thing to do. We added a couple of listeners and callbacks to the code
and recompiled. Just couldn't figure out how to do this on the new version,
so we stuck with the old JW Player. Unfortunately, I don't have the old JW
source code we modified any more.

Also, there will be no new version of JWPC. We had a project going for a
while, but we ran into funding and staffing problems and pulled the plug.
To be honest, if I were going to tackle it again, I don't think I would use
JW Player. The JavaScript API has gotten pretty bulky. There are a couple
of good projects with accessible players out there. Forking either
Nomensa's player or the one in the WET Toolkit could be a good path, maybe.
And as far as general universal platform playability and features go, I
really like mediaelement.js. mediaelement.js is not terribly screen reader
friendly, but it's light and very nicely architected.

Best,

ken
--
Ken Petri
Program Director, OSU Web Accessibility Center



On Thu, Oct 4, 2012 at 2:56 PM, Marcelo Terreni < <EMAIL REMOVED> >wrote:

> Hi, I'm trying to build a JQuery version of the very impresive JW Player
> Controls Version 2, maybe the best accesible web video player available.
>
> I'll be using JQuery because we already use YUI and JQuery all through
> our sites and a third framework would be too much. Besides I'm trying to
> provide a better non-javascript/non-Flash suppport (that was easily
> solved, I'll send a link when everything is up and running) and change
> the controlbar's "toollbar" role (while adequate, it may make things a
> bit more difficult unnecessarily for "keyboard / non screen reader" users).
>
> As far as I'm concerned people at OSU WAC and Webhipster LTD. had to
> modify the captions / audiodescription plugins to provide some
> previously unavailable JWPlayer / JS API communication. I detected
> they've created a couple of controls for that:
>
> |togglecaptions
> captionstate
>
> |but I wasn't able use them trough jwplayer(id).getPlugin("captions").
> ¿Any clue?
>
>
> Thanks!
>
> --
> Marcelo Terreni
>
> Educ.ar S.E.
> Web: http://www.educ.ar
> Ministerio de Educación
> Ciudad Autónoma de Buenos Aires (CABA) - Argentina
>
> > > >
>
>