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:51:05 +0200
Message-ID: <CAKdCpxw_cYypBTFjSe1Wn=wBfEfdbjzkFL0rgmMYf3vHZBmRYg@mail.gmail.com>
To: Janina Sajka <janina@rednote.net>
Cc: Shane McCarron <shane@spec-ops.io>, Katie Haritos-Shea GMAIL <ryladog@gmail.com>, Accessible Platform Architectures Working Group <public-apa@w3.org>, Jonathan Avila <jon.avila@ssbbartgroup.com>, David MacDonald <david@can-adapt.com>
+1 Janina.

Another thing to consider (which David MacDonald and I have chatted about
briefly) is looking to see if there is anything in the MAUR that could find
its way into either the 2.1 or 'Silver' effort going forward.

Over the course of time, I've also seen some interesting Proof-of-Concept
examples of "time adjusting" (Nigel Megitt @ BBC, although he was unable to
share the files when we chatted in Sapporo) and the popcorn.js example from
Geoff Freed at NCAM that delivers supplimental content (and also
demonstrates pausing and "time-shifting" of a different sort:
http://ncamftp.wgbh.org/rd/hgp/hgp.html). It's been on my evergreen To Do
list to continue to collect these types of examples, but...

JF

JF

On Wed, Sep 28, 2016 at 5:09 PM, Janina Sajka <janina@rednote.net> wrote:

> Thank you, Shane. I think this is an excellent suggestion and one we
> should discuss further from the perspective of leveraging the MAUR
> toward full support across relevant W3C specifications.
>
> I discussed this when I met with Wendy Selzer at TPAC. We probably also
> need to have a related conversation with Ralph Swick about how to
> accomplish this.
>
> As I explained to Wendy, we believe the MAUR is one of the stellar
> achievements for accessibility in HTML 5. We want to see follow through
> so that it doesn't simply become a great idea that went nowhere. Among
> the problems we're having in APA is understanding which W3C
> specifications implement which aspect of the overall vision in the MAUR.
> There are, in fact, multiple API specs involved. We need a global
> understanding of how these fit together. And, this global understanding
> probably needs to be prominently available somewhere as an accessible
> SVG chart.
>
> I also think we should strategize about creating cross links between the
> MAUR and the various related W3C specs that implement the vision of the
> MAUR. I firmly believe we need to help developers understand how these
> pieces are related. Perhaps, as relevant specs reach TR, we update the
> MAUR with a pointer from relevant sections, and vice versa.
>
> Lastly, APA met with EO at TPAC where I laid out my understanding of the
> need for some 10-20 minute video, hosted by W3C, where all the described
> alternative content types are utilized, and where at least 3 level
> structural navigation has been marked up. Nothing like this exists, and
> I believe tool and user agent developers need something this
> comprehensive to test against.
>
> So, I'm trying to promote a wide,cross W3C vision for implementing the
> MAUR, and I believe we need to take some time in APA to get buyin for an
> appropriate W3C wide approach on doing so.
>
> Janina
>
>
> Shane McCarron writes:
> > 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
>
> --
>
> 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
>
>
>


-- 
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:51:41 UTC

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