W3C home > Mailing lists > Public > public-html-a11y@w3.org > February 2010

Re: on SRT...

From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Wed, 24 Feb 2010 09:38:57 +1100
Message-ID: <2c0e02831002231438o8584e62leeb063c5d8566125@mail.gmail.com>
To: David Singer <singer@apple.com>
Cc: Matt May <mattmay@adobe.com>, HTML Accessibility Task Force <public-html-a11y@w3.org>
On Wed, Feb 24, 2010 at 3:38 AM, David Singer <singer@apple.com> wrote:
> I don't have a problem with DFXP, but I think we'll need to profile it -- it contains elements for support of (for example) 3GPP Timed Text, such as scroll-in, and also for out-of-time-order sequencing, neither of which I think we want in this case, do we?

I agree about the need for profiling. I don't mind about the scroll-in
as long as we can map the 3GPP markup to some javascript action for
the browser. But this is definitely a feature of the more complex

Most of the DFXP files I have seen so far in the wild are really simple.

For example this one from Apple:
which relates to http://www.apple.com/imac/
is basically a SRT file with a default display style. (Ignore the
metadata element which they are using and which incidentally has
non-standard attributes).

That default display style can easily be mapped onto a div and css, so
I would regard this as not very hard to implement. This markup could
be a level 0 profile.

There is also some html formatting markup inside the <p> elements,
such as <br/>, <b> and <i>, which can just be kept for HTML (obivously
needs to be well parsed and filtered so as not to create security
issues). But we could also consider that as part of level 0.

Then, level 0 provides the ability for externally provided styling and
for prettier text - a good improvement over SRT and not overly
challenging to implement I would think.

Next, we can go through DFXP and add selective features that make
sense to create a level 1,2, and maybe make level 3 the full DFXP

I would consider this as a viable way to create a path towards
introducing DFXP support in steps, which do not ask too much
implementation requirements of the browser vendors in one go. I'd be
curious what the browser vendors think about this!

Received on Tuesday, 23 February 2010 22:39:50 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:05:09 UTC