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

Re: a11y TF CfC on resolution to support "Media Text Associations" change proposal for HTML issue 9

From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Mon, 5 Apr 2010 22:36:45 +1000
Message-ID: <n2g2c0e02831004050536v7546d54cz4481b7a7cf4b515e@mail.gmail.com>
To: Sean Hayes <Sean.Hayes@microsoft.com>
Cc: "public-html-a11y@w3.org" <public-html-a11y@w3.org>
Hi Sean,

On Mon, Apr 5, 2010 at 9:37 PM, Sean Hayes <Sean.Hayes@microsoft.com> wrote:
>  I said " and any other format that has no formal timing model "; clearly smilText does come with its own model. It's possible that there are text formats that would not map to TTML, especially complex ones, but they probably would come under the above too. What I was really after was the myriad of simple formats which for the most part do map to TTML. In addition, we really only need to talk about this for formats which are mentioned in the spec. But if you want to replicate the necessary rules in the HTML spec, I'm OK with that; I just think it will be less efficient as you will need to explain your terms. Even TTML for the most part defers to SMIL.

I believe there is only this one rule really, since we don't have to
deal with the full complexity of the SMIL timing model.

> Yes "container" would have to exclude any control area, including dynamic ones, I've done that trick with Silverlight too.

Cool, happy with that.

> I was assuming extent="media" would be an illegal/inappropriate value for <audio>, rather than not having the attribute apply in case we come up with other values in the future. But as I'd like to make media the default perhaps we could state something like: "if the media has no intrinsic size, then specifying the 'media' value for @extent results in the same area as 'container'".

Sounds good.

Received on Monday, 5 April 2010 12:37:38 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:55:34 UTC