Re: Request for joint meeting during TPAC

I'd like to confirm 11AM on Tuesday also works for ARIA. Given that CSS 
typically has much larger rooms, we're assuming we'll come to you rather 
than the other way around. But we can sort that out.

--joanie

On 8/22/19 10:48 AM, Janina Sajka wrote:
> Hi Rossen, All:
> 
> Just a quick in process response to acknowledge that 11AM on Tuesday
> works for APA, and we should expect confirmation (or alternative) from
> ARIA later today following their teleconference.
> 
> Janina
> 
> Rossen Atanassov writes:
>> Hi Janina et al.,
>>
>> We should certainly spend an hour in a joint meeting and go over the 
>> agenda items provided.
>>
>> Would Tuesday 11:00am - noon work for you all? If not, Tuesday after 
>> lunch would be good for us as well but I'm not 100% what the lunch 
>> times are yet.
>>
>> Best,
>> Rossen
>>
>> On 8/20/19, 3:54 PM, "Janina Sajka" <janina@rednote.net> wrote:
>>
>> Dear Rossen, Alan, All:
>>
>> This is a request for a joint meeting with CSS, ARIA and APA on behalf
>> of our joint CSS-Accessibility Task Force during the upcoming TPAC in
>> Fukuoka.
>>
>> Noting that both CSS and ARIA are scheduled to meet Monday and Tuesday
>> of TPAC, I propose we find a mutually agreeable hour during those two 
>> days.
>> Suggestions welcome.
>>
>> Noting that we have a good list of open issues on our
>> github<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fcsswg-drafts%2Fissues%2F&amp;data=02%7C01%7CRossen.Atanassov%40microsoft.com%7Ccfa33decd4ed4bdf001008d725c15e9e%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637019384767648165&amp;sdata=nd%2FF08WymaXYasOAsQRKx4Nss6LcD1lADR9HvhhGyeA%3D&amp;reserved=0>, 
>> please consider the
>> following agenda for this joint meeting as a starting point. Let's
>> refine as needed on this email thread.
>>
>> ***Initial Suggested Agenda***
>>
>> 1.) Controlling Animations
>>
>> COMMENT: A reliable mechanism to block, or allow stepping through
>> animations has been on the accessibility wish list for a long time.
>> Whenever we examine a particular specification which includes some
>> animation specificity, it transpires that that particular spec may not
>> be the appropriate place to globally control animation. We would request
>> CSS commit to telling us in what specification such control should
>> reside by some date certain, though we don't necessarily expect that by
>> this TPAC!
>>
>> 2.) Aural Transformation and Control
>>
>> COMMENT: We have two subtopics here which beg the global
>> question: Does CSS see itself defining and managing aural presentations?
>>
>> a.) Text Transforms and
>> TTS<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fcsswg-drafts%2Fissues%2F3775&amp;data=02%7C01%7CRossen.Atanassov%40microsoft.com%7Ccfa33decd4ed4bdf001008d725c15e9e%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637019384767648165&amp;sdata=KVAgmP9dRbm2Nv%2FdIThjJfGADjvC7nLQrJJkMiUR%2Fic%3D&amp;reserved=0>
>>
>> b.) Controlling Correct TTS Pronunciation
>> Gap 
>> Analysis<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fw3c.github.io%2Fpronunciation%2Fgap-analysis%2F&amp;data=02%7C01%7CRossen.Atanassov%40microsoft.com%7Ccfa33decd4ed4bdf001008d725c15e9e%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637019384767648165&amp;sdata=Xgsmk1d%2FpN4vejS6XB5iawU%2FeL2Y0CTrDSgzG2NZYbo%3D&amp;reserved=0>
>> which considers whether CSS-Speech might meet the TF's
>> requirements.
>>
>> 3.) Is it time to create a CSS-AAM?
>>
>> Additional topics and comments welcome via this github page:
>>
>> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fcss-aam%2Fissues%2F3%23issuecomment-522012668&amp;data=02%7C01%7CRossen.Atanassov%40microsoft.com%7Ccfa33decd4ed4bdf001008d725c15e9e%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637019384767648165&amp;sdata=34j2gAxZEA%2FLY3Gp3OkJtt4HGhCuO4mw68JMjgBnFNM%3D&amp;reserved=0
>>
>> Best,
>>
>> Janina Sajka, Chair
>> Accessible Platform Architectures (APA)
>>
>> -- 
>>
>> Janina Sajka
>>
>> Linux Foundation Fellow
>> Executive Chair, Accessibility Workgroup: 
>> https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fa11y.org&amp;data=02%7C01%7CRossen.Atanassov%40microsoft.com%7Ccfa33decd4ed4bdf001008d725c15e9e%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637019384767648165&amp;sdata=AljnlYb21MyLAr4SP%2BLsTucEY43JEJWzzcno4GL42Ws%3D&amp;reserved=0
>>
>> The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
>> Chair, Accessible Platform Architectures 
>> https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.w3.org%2Fwai%2Fapa&amp;data=02%7C01%7CRossen.Atanassov%40microsoft.com%7Ccfa33decd4ed4bdf001008d725c15e9e%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637019384767648165&amp;sdata=73TpUBGAwyN%2BEl6Jt0V%2Fi%2FM%2FK483J409%2FR%2BmGQSaJG4%3D&amp;reserved=0
>>
>>
>>
> 

Received on Thursday, 22 August 2019 17:20:44 UTC