W3C home > Mailing lists > Public > public-apa@w3.org > September 2016

Re: FW: Second screen API and working group

From: John Foliot <john.foliot@deque.com>
Date: Thu, 29 Sep 2016 11:40:31 +0200
Message-ID: <CAKdCpxzqdex9wnduATBaHtZNnr7XrEe-9MctDaFA3XgXE_vSkw@mail.gmail.com>
To: Shane McCarron <shane@spec-ops.io>
Cc: Katie Haritos-Shea GMAIL <ryladog@gmail.com>, Accessible Platform Architectures Working Group <public-apa@w3.org>, Jonathan Avila <jon.avila@ssbbartgroup.com>
+1 Shane. FWIW, Kazuyuki (Kaz) Ashimura (W3C Staff Contact for the TV on
the Web IG) is really on top of the accessibility stuff for that WG.

I also added some info to the Cloud Browser TF (part of the same IG) wiki
here:
https://www.w3.org/2011/webtv/wiki/Main_Page/Cloud_Browser_TF/UseCases#accessibility

JF

On Wed, Sep 28, 2016 at 2:07 PM, Shane McCarron <shane@spec-ops.io> wrote:

> The charter has coordination with APA in it already.  However, I would
> like to see a reference to the MAUR since it specifically deals with a11y
> requirements for second screens as they relate to media access.
>
> I will submit a comment in this regard when Spec-Ops submits its review of
> the charter.
>
> [1] https://www.w3.org/TR/media-accessibility-reqs/
>
> On Tue, Sep 27, 2016 at 7:06 PM, Katie Haritos-Shea GMAIL <
> ryladog@gmail.com> wrote:
>
>> See Jonathan Avila’s email below…..
>>
>>
>>
>> ​​​​​
>>
>>
>>
>>
>>
>>
>>
>> ** katie **
>>
>>
>>
>> *Katie Haritos-Shea*
>> *Principal ICT Accessibility Architect (WCAG/Section 508/ADA/AODA)*
>>
>>
>>
>> *Cell: 703-371-5545 <703-371-5545> **|* *ryladog@gmail.com*
>> <ryladog@gmail.com> *|* *Oakton, VA **|* *LinkedIn Profile*
>> <http://www.linkedin.com/in/katieharitosshea/> *|* *Office: 703-371-5545
>> <703-371-5545> **|* *@ryladog* <https://twitter.com/Ryladog>
>>
>>
>>
>> *From:* Jonathan Avila [mailto:jon.avila@ssbbartgroup.com]
>> *Sent:* Tuesday, September 27, 2016 7:42 PM
>> *To:* WCAG <w3c-wai-gl@w3.org>
>> *Subject:* Second screen API and working group
>>
>>
>>
>> A second screen working group is being chartered.  I wanted to find out
>> if there has been any connection with this group (or community group) in
>> regards to accessibility.  Perhaps accessibility of these second screens is
>> less an issue about the API and more about the user agents – but it is
>> something we could keep on the radar.  Is there anything related to
>> accessibility that you think should be included in a charter? For example,
>> second screens can be interactive and not just passive devices.  People
>> using assistive technology such as touch screen AT interact with the device
>> with more than just the pointer location.
>>
>>
>>
>> Jonathan
>>
>>
>>
>> Jonathan Avila
>>
>> Chief Accessibility Officer
>>
>> SSB BART Group
>>
>> jon.avila@ssbbartgroup.com
>>
>> 703.637.8957 (Office)
>>
>>
>>
>> Visit us online: Website <http://www.ssbbartgroup.com/> | Twitter
>> <https://twitter.com/SSBBARTGroup> | Facebook
>> <https://www.facebook.com/ssbbartgroup> | Linkedin
>> <https://www.linkedin.com/company/355266?trk=tyah> | Blog
>> <http://www.ssbbartgroup.com/blog/>
>>
>> Check out our Digital Accessibility Webinars!
>> <http://www.ssbbartgroup.com/webinars/>
>>
>>
>>
>
>
>
> --
> Shane McCarron
> Projects Manager, Spec-Ops
>



-- 
John Foliot
Principal Accessibility Strategist
Deque Systems Inc.
john.foliot@deque.com

Advancing the mission of digital accessibility and inclusion
Received on Thursday, 29 September 2016 09:41:03 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 September 2016 09:41:04 UTC