- From: Christian Vogler <christian.vogler@gallaudet.edu>
- Date: Wed, 12 Dec 2012 17:06:30 -0500
- To: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- Cc: Ian Hickson <ian@hixie.ch>, public-texttracks@w3.org, Loretta Guarino Reid <lorettaguarino@google.com>
Comments inline. On Wed, Dec 12, 2012 at 2:49 AM, Silvia Pfeiffer <silviapfeiffer1@gmail.com> wrote: >> > (2) Character color. All apparatus shall implement captioning such that >> > characters may be displayed in the 64 colors defined in CEA-708 and such >> > that users are provided with the ability to override the authored color >> > for characters and select from a palette of at least 8 colors including: >> > white, black, red, green, blue, yellow, magenta, and cyan. >> >> This we support via CSS and CSS user style sheets (the latter of which can >> be exposed as UI). It does mean that FCC-compliant WebVTT browser >> implementations will have to support CSS. I'd also like to point out that CSS support shouldn't be just about "FCC compliance." Colors and background settings have been essential in making captions work for people with vision problems, and there is also some variety as to what deaf and hard of hearing people with normal vision prefer. Moreover, positioning and font attributes are used for denoting such things as where sounds are coming from and whether someone is speaking off-screen. That's much more fundamental than trying to comply with a set of regulations. It's just good universal design practice. Christian
Received on Wednesday, 12 December 2012 22:06:55 UTC