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

Re: FW: Second screen API and working group

From: Janina Sajka <janina@rednote.net>
Date: Wed, 28 Sep 2016 10:37:44 -0400
To: Katie Haritos-Shea GMAIL <ryladog@gmail.com>
Cc: public-apa@w3.org, Jonathan Avila <jon.avila@ssbbartgroup.com>
Message-ID: <20160928143744.GJ1665@opera.rednote.net>
Hi, Jonathan,

Katie forwarded your note to APA, so I'm responding to let you know that
we've worked with Second Screen over the years. We were initially
concerned that the various use cases discussed in the Media
Accessibility User Requirements (MAUR) [1] were addressed and supported
by Second Screen. They asked us also for additional use cases and
requirements which were provided--though I'd have to do a little digging
to point you to that communication as some time has passed since. Those
interactions occured when the HTML Accessibility Task Force was still
active.

I do intend we'll ask for APA coordination via their charter, now that
they're moving to become a Working Group. I doubt that will be
controversial. I'm also confident they'd appreciate your participation,
if you're so inclined.

Janina

[1] http://www.w3.org/TR/media-accessibility-reqs/

Katie Haritos-Shea writes:
> See Jonathan Avila’s email below…..
> 
>  
> 
> ​​​​​
> 
>  
> 
>  
> 
>  
> 
> * katie *
> 
>  
> 
> Katie Haritos-Shea 
> Principal ICT Accessibility Architect (WCAG/Section 508/ADA/AODA)
> 
>  
> 
> Cell: 703-371-5545 |  <mailto:ryladog@gmail.com> ryladog@gmail.com | Oakton, VA |  <http://www.linkedin.com/in/katieharitosshea/> LinkedIn Profile | Office: 703-371-5545 |  <https://twitter.com/Ryladog> @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 <mailto:jon.avila@ssbbartgroup.com> 
> 
> 703.637.8957 (Office)
> 
>  
> 
> Visit us online:  <http://www.ssbbartgroup.com/> Website |  <https://twitter.com/SSBBARTGroup> Twitter |  <https://www.facebook.com/ssbbartgroup> Facebook |  <https://www.linkedin.com/company/355266?trk=tyah> Linkedin |  <http://www.ssbbartgroup.com/blog/> Blog
> 
>  <http://www.ssbbartgroup.com/webinars/> Check out our Digital Accessibility Webinars!
> 
>  
> 

-- 

Janina Sajka,	Phone:	+1.443.300.2200
			sip:janina@asterisk.rednote.net
		Email:	janina@rednote.net

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:	http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair, Accessible Platform Architectures	http://www.w3.org/wai/apa
Received on Wednesday, 28 September 2016 14:38:14 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 28 September 2016 14:38:15 UTC