W3C home > Mailing lists > Public > whatwg@whatwg.org > April 2010

[whatwg] Introduction of media accessibility features

From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Sun, 11 Apr 2010 22:14:09 +1000
Message-ID: <v2w2c0e02831004110514w98e258a5od6af857ce143f624@mail.gmail.com>
Hi Rob,

On Sun, Apr 11, 2010 at 4:18 PM, Robert O'Callahan <robert at ocallahan.org> wrote:
> It would be helpful if the "role" values were defined.

Both proposals contain a list of roles - were you asking for a
registering mechanism or something? I'm confused.


>> If the text is rendered on top of the video, rendering engines must ensure
>> that the rendered text does not collide with other elements rendered on top
>> of the video, e.g. controls.
>
> This needs to be clarified. Authors can position arbitrary content over the
> video, and presumably the browser is not supposed to ensure rendered text
> doesn't collide with such content. I presume what you meant is simply that
> rendered text must not collide with browser built-in UI. Although I'm not
> sure how that can be ensured when arbitrary styling of the rendered text is
> supported.

Yes, the idea was for browser built-in default UI controls. There is
indeed not much you can do if the Web Developer does something stupid
or the user moves the areas on top of each other.

The main issue is to keep the area that captions or subtitles are
rendered into and the area that controls are rendered into separately,
since you will always want to have access to both if both are
activated.

Cheers,
Silvia.
Received on Sunday, 11 April 2010 05:14:09 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:22 UTC