RE: FW: Second screen API and working group

Good idea Shane. I am hoping when the PAUR is done we can do the same for those specs that have payment implications….;-)

 

​​​​​

 

 

 

* 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: Shane McCarron [mailto:shane@spec-ops.io] 
Sent: Wednesday, September 28, 2016 8:08 AM
To: Katie Haritos-Shea GMAIL <ryladog@gmail.com>
Cc: Accessible Platform Architectures Working Group <public-apa@w3.org>; jon.avila@ssbbartgroup.com
Subject: Re: FW: Second screen API and working group

 

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 <mailto: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 <tel:703-371-5545>  |  <mailto:ryladog@gmail.com> ryladog@gmail.com | Oakton, VA |  <http://www.linkedin.com/in/katieharitosshea/> LinkedIn Profile | Office: 703-371-5545 <tel:703-371-5545>  |  <https://twitter.com/Ryladog> @ryladog

 

From: Jonathan Avila [mailto:jon.avila@ssbbartgroup.com <mailto:jon.avila@ssbbartgroup.com> ] 
Sent: Tuesday, September 27, 2016 7:42 PM
To: WCAG <w3c-wai-gl@w3.org <mailto: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 <tel: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!

 





 

-- 

Shane McCarron

Projects Manager, Spec-Ops