Re: Clarification on the notion of "Second Screen"?

Dear Francois:

I have CC'd the public APA email list, so that we might have a basis for
discussion during our teleconference later today. I hope that's OK!

I have two comments inline of your last email below which are relevant.
One will need further discussion, imo.

Francois Daoust writes:
> Hi Janina,
> 
> I confirm that Bluetooth headset, and speakers, are included in the
> definition of "screen" (the charter rather uses the term "presentation
> display"). In particular, the draft charter explicitly mentions Bluetooth
> and includes the following sentence: "For the purposes of this charter,
> presentation displays include wireless speakers as well".
> 

Excellent, and thanks for the clarification. One down, one to go!

> That said, I am not sure whether the group considers refreshable braille
> displays to be a possible "presentation display" as well. My limited
> understanding of refreshable braille displays is that they are meant to
> display characters, whereas the presentation displays being considered by
> the Second Screen Working Group are either those capable of rendering audio
> or video streams, or those capable of running HTML applications.
> 

So, this may be the an item for us to clarify with your group. Going
back to the days of the development of the HTML 5 specification, our
accessibility requirements clearly considered alternative renderings of
video/audio content important for conveyance to second screen devices
broadly understood. We documented these requirements in a document we
prepared to support the inclusion of markup in the HTML 5 standard, and
our additional markup was accepted into HTML 5, really with very little
controversary. The only item that was not standardized in HTML 5 was our
requirement for a programmatic association of a video transcript with
the primary video resource.

The document we prepared for HTML 5 standardization was published as a
Working Group Note by APA's predecessor Working Group, Protocols and
Formats (PFWG) under the title: "Media Accessibility User Requirements
(MAUR)" available here:

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

The two most relevant sections in this document to the current
conversation would be:

Sec. 3.8: Requirements on secondary screens and other devices

https://www.w3.org/TR/media-accessibility-reqs/#requirements-on-secondary-screens-and-other-devices

Sec. 3.5: Discovery and activation/deactivation of available alternative
content by the user

https://www.w3.org/TR/media-accessibility-reqs/#discovery-and-activation-deactivation-of-available-alternative-content-by-the-user
 
> Said differently, the APIs developed by the group may be used to stream
> audio and/or video content to a presentation display, or to establish a
> communication channel between a web application running on a controller
> device and a web application running on the presentation display. However,
> there are no provisions to stream pure text content to a presentation
> display.
> 
> Or do I misunderstand what refreshable braille displays encompass?
> 

No, your understanding is correct. Regretably, I think we need to have a
scoping conversation for the proposed API. I expect APA would strongly
oppose excluding alternative content from a W3C technology API.

Let me also note that alternative content is already being provided in
commercial settings. I hope to experience the following service myself
soon on a forthcoming trip to New York City:

https://www.galapro.com/

I sincerely hope we can find a way to accomodate accessibility support
in your proposed API. Not only Broadway theater, but educational
settings, among many other venues would benefit. And, as the above
service demonstrates, the benefits include I18N applications, not just
accessibility support.

Best,

Janina

> Thanks,
> Francois.
> 
> 
> ------ Original message ------
> From: "Janina Sajka (janina@rednote.net)" <janina@rednote.net>
> To: "Francois Daoust" <fd@w3.org>
> Cc: "Michael Cooper" <cooper@w3.org>
> Date: 07/12/2021 15:48:32
> 
> > Hi, Francois:
> > 
> > My apologies for being slow to follow up on this. Our main concern is to
> > continue to capture what we agreed some years back, perhaps 2015-2016?,
> > that "screen" should be understood to be generic, meaning that the
> > screen might be a bluetooth headset, or speaker pair, or a refreshable
> > braille display.
> > 
> > This understanding grew out of our work on media accessibility in HTML
> > 5, and we did have an exchange at some point years ago clarifying this
> > understanding. Our issue is really just that, and nothing more. We did
> > thing it worth clarifying because several years have passed, and it's
> > likely many participants in Second Screen may be newer than that old
> > exchange of understanding.
> > 
> > I will be in other meetings for the next few hours, but will get back to
> > you with more later today. Again, sorry for holding things up!
> > 
> > Janina
> > 
> > Francois Daoust writes:
> > >  Hi Janina,
> > > 
> > >  Michael noted that APA reviewed the proposed Second Screen Working Group
> > >  charter and would like a clarification about the meaning of the term "second
> > >  screen". Could you provide more detail as to what APA is wondering about?
> > > 
> > >  The proposed charter is at:
> > > https://w3c.github.io/secondscreen-charter/
> > > 
> > >  Thanks,
> > >  Francois, staff contact for the Second Screen Working Group.
> > 
> > --
> > 
> > Janina Sajka
> > https://linkedin.com/in/jsajka
> > 
> > Linux Foundation Fellow
> > Executive Chair, Accessibility Workgroup:	http://a11y.org
> > 
> > The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
> > Co-Chair, Accessible Platform Architectures	http://www.w3.org/wai/apa
> > 

-- 

Janina Sajka
(she/her/hers)
https://linkedin.com/in/jsajka

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

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Co-Chair, Accessible Platform Architectures	http://www.w3.org/wai/apa

Received on Wednesday, 8 December 2021 09:48:44 UTC