W3C home > Mailing lists > Public > public-tt@w3.org > February 2018

Re: [webvtt] APA Comments on TimedText/WebVTT

From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Sun, 4 Feb 2018 14:28:08 +1100
Message-ID: <CAHp8n2=2QOswFsma=QNd3rE+npEx4gnzO8KEYH5APgt0BE02TA@mail.gmail.com>
To: David Singer <singer@apple.com>
Cc: John Foliot <john.foliot@deque.com>, Janina Sajka <janina@rednote.net>, Public TTWG List <public-tt@w3.org>, Accessible Platform Architectures Administration <public-apa-admin@w3.org>, W3C WAI Accessible Platform Architectures <public-apa@w3.org>
Thanks so much! I might need some direction as to what wording you'd
like to see added/changed - will follow up in the issues.
Cheers,
Silvia.

On Sun, Feb 4, 2018 at 4:24 AM, David Singer <singer@apple.com> wrote:
> Many thanks!
>
>
>> On Feb 3, 2018, at 6:39 , John Foliot <john.foliot@deque.com> wrote:
>>
>> Moved 2 of the 3 Issues to GitHub as requested:
>>       • Issue 1:  Users of magnification may have overlap issues - https://github.com/w3c/webvtt/issues/426
>>       • Issue 2: The spec should include feature explanations in plain language - https://github.com/w3c/webvtt/issues/427
>>
>> Issue 3 was closed, with thanks.
>>
>> JF
>>
>> On Fri, Feb 2, 2018 at 10:56 PM, Silvia Pfeiffer <silviapfeiffer1@gmail.com> wrote:
>> On Sat, Feb 3, 2018 at 3:13 AM, David Singer <singer@apple.com> wrote:
>> >
>> >
>> >> On Feb 2, 2018, at 6:01 , John Foliot <john.foliot@deque.com> wrote:
>> >>
>> >> Greetings David and Silvia,
>> >>
>> >> The three responses provided originated from Bugzilla Issues tracked here:
>> >> https://www.w3.org/wiki/TimedText/WebVTT_Wide_Review#Messages_sent_requesting_review_internally_to_the_W3C.2C_of_the_FPWD
>> >>
>> >> and specifically:
>> >>       • Issue 1 - Users of Magnification: https://www.w3.org/Bugs/Public/show_bug.cgi?id=28509
>> >>       • Issue 2 - The spec should include feature explanations in plain language: https://www.w3.org/Bugs/Public/show_bug.cgi?id=28510
>> >>       • Issue 3 - Captions on the audio element: https://www.w3.org/Bugs/Public/show_bug.cgi?id=28511
>> >> Silvia, I'm not seeing corresponding Issues in GitHub, so I can either a) Create new GH issues, and load them up with what I have, or b) respond to the original Bugzilla Issue (which apparently looks "live" still).
>> >>
>> >> Hoping to clear this task from my desk today, your preference here is greatly appreciated.
>> >
>> > New GH issues would seem to be needed, with forward pointers from BugZilla and back-pointers from GH
>> >
>> > BugZilla:  “Continued on GH In issue #xxx (linked)”
>> > GH: “continuation of the discussion in BugZilla at <link>”
>> >
>> > Thanks, much appreciated
>> >
>>
>>
>> Yes, I agree with this approach also: create new GH issues and link
>> them back to the BugZilla issue, then close the BugZilla issue with a
>> forward pointer to GH.
>>
>> Thanks very much for your help, John!
>>
>> Cheers,
>> Silvia.
>>
>>
>>
>> --
>> John Foliot
>> Principal Accessibility Strategist
>> Deque Systems Inc.
>> john.foliot@deque.com
>>
>> Advancing the mission of digital accessibility and inclusion
>
> David Singer
> Manager, Software Standards, Apple Inc.
>
Received on Sunday, 4 February 2018 03:29:03 UTC

This archive was generated by hypermail 2.3.1 : Sunday, 4 February 2018 03:29:04 UTC