- From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- Date: Fri, 8 Mar 2013 19:37:25 +1100
- To: public-texttracks@w3.org
- Cc: Loretta Guarino Reid <lorettaguarino@google.com>, Victor Cărbune <victor.carbune@gmail.com>
- Message-ID: <CAHp8n2=ZM8R196v0zJaOLOpkT+UBJxD7fH2E_9YHje6U+KYkSA@mail.gmail.com>
Update on the region spec: I have just fixed two issues with the spec: 1. The spec stated percentages to be double, but only parsed integer percentages. It now specifies them as real numbers and also throws IndexSizeError when not within 0-100%. 2. Added a removeRegion(region) function to TextTrackRegion to close https://www.w3.org/Bugs/Public/show_bug.cgi?id=21191 Cheers, Silvia. On Fri, Feb 15, 2013 at 7:47 AM, Silvia Pfeiffer <silviapfeiffer1@gmail.com>wrote: > For those browsers interested in implementing a rollup captions feature > and other FCC requirements, there is now a concrete extension specification > for WebVTT: > https://dvcs.w3.org/hg/text-tracks/raw-file/default/608toVTT/region.html > > Regards, > Silvia. > > > On Thu, Dec 13, 2012 at 9:06 AM, Christian Vogler < > christian.vogler@gallaudet.edu> wrote: > >> 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 Friday, 8 March 2013 08:38:17 UTC