Re: Call for Consensus (CfC): Comment on DAPT

+1

*Dr.  Keith Newton *(Call me "Dr. Keith")
Executive Leader and Strategic a11y in Digital Accessibility Experience
614-654-4116 <%28614%29%20654-4116> |
https://www.linkedin.com/in/dr-keith-newton  | newtonsgroove2@gmail.com


On Thu, Nov 30, 2023 at 10:41 AM Mark Miller <mmiller@tpgi.com> wrote:

> +1
>
> Mark Miller
> Sales Director
>
>
>
> TPG Interactive
> www.tpgi.com
>
> A Vispero Company
> https://vispero.com/
> M: (603) 810-8235
>
>
>
>
> ARC
> Certified Administrator 2022
> TPGi.com
>
>
>
>
> -----Original Message-----
> From: Janina Sajka <janina@rednote.net>
> Sent: Thursday, November 23, 2023 9:49 AM
> To: Keith Newton <newtonsgroove2@gmail.com>
> Cc: public-apa-admin@w3.org
> Subject: Re: Call for Consensus (CfC): Comment on DAPT
>
> CAUTION:EXTERNAL EMAIL SENDER!
>
>
> Dear All:
>
> I'm responding publically to this comment because it's posted on a formal
> APA Call for Consensus (CfC). It is actually about a different topic in APA
> and appears to have simply been posted on the wrong email thread. It is
> irrelevant to the current CfC.
>
> Janina
>
> Keith Newton writes:
> > Matt and Janina, here are a few general considerations for accessibility:
> > A rapid reduction of service due to load could cause the following:
> >
> > Reduced Responsiveness for Assistive Technologies: If the API causes a
> > website to reduce its resource usage under high CPU pressure, this
> > might lead to slower response times or reduced functionality,
> > negatively impacting users of assistive technologies like screen
> > readers or voice recognition software.
> >
> > Insufficient Notification: If changes in compute pressure lead to
> > alterations in content or functionality without proper notification,
> > it could confuse or disorient users, especially those with cognitive
> > disabilities.
> >
> > Loss of Accessibility Features: In an attempt to lower CPU usage, if a
> > website disables certain features or content, it might inadvertently
> > remove accessibility enhancements (like high-contrast modes or
> > text-to-speech functionality), making the site less accessible for
> > users with visual or auditory impairments.
> >
> > Visual Disturbances: Rapid changes in content or layout in response to
> > compute pressure changes could cause issues for users with
> > photosensitive epilepsy or other visual processing disorders.
> >
> > When I have time to create use cases and align them with WCAG
> > guidelines, I’ll add them to the thread
> >
> > *Dr.  Keith Newton *(Call me "Dr. Keith") Executive Leader and
> > Strategic a11y in Digital Accessibility Experience
> > 614-654-4116 <%28614%29%20654-4116> |
> > https://www.linkedin.com/in/dr-keith-newton  |
> > newtonsgroove2@gmail.com
> >
> >
> > On Tue, Nov 21, 2023 at 5:45 PM Janina Sajka <janina@rednote.net> wrote:
> >
> > > +1
> > >
> > > Janina Sajka writes:
> > > > Colleagues:
> > > >
> > > > This is a Call for Consensus (CfC) to the Accessible Platform
> > > Architectures (APA) Working Group testing for agreement on a formal
> > > comment to the Timed Text Working Group regarding their Dubbing and
> > > Audio description Profiles of TTML2 (https://www.w3.org/TR/dapt/).
> > > APA's input was requested as part of our role in performing
> > > horizontal review of accessibility concerns in W3C specifications.
> > > >
> > > > APA's background discussion on this review can be seen in the
> > > > APA's
> > > teleconference minutes at :
> > > >
> > > > https://www.w3.org/2023/11/15-apa-minutes.html#t07
> > > >
> > > > The Timed Text WG has thoughtfully provided a summary of their
> > > accessibility guidance both in the Introduction of their
> > > specification referenced above, but also at:
> > > >
> > > >
> > > https://github.com/w3c/dapt/wiki/Considerations-for-the-Accessibilit
> > > y-review
> > > >
> > > > Please note that we are seeking the change of emphasis suggested
> > > > below in a future Working Draft, not necessarily this current one.
> > > > We see no reason to block publication of the current WD. In fact
> > > > we are very appreciative of this well written specification and of
> > > > its clear and helpful examples.
> > > >
> > > > *** Draft Comment***
> > > >
> > > > APA appreciates the thorough support for accessibility concerns in
> > > > the DAPT Working Draft. We have only one comment. The document notes
> that:
> > > >
> > > > "The audio mixing can occur prior to distribution of the media, or
> > > > in
> > > the client player. If the audio description script is delivered to
> > > the player, the text can be used to provide an alternative
> > > rendering, for example on a Braille display, or using the user's
> configured screen reader."
> > > >
> > > > APA appreciates the need to support audio mixing prior to
> > > > distribution,
> > > but would prefer that this be left to the user agent whenever
> > > possible.  We would like to encourage content creators to embed
> > > alternative media in .mp4 or .mkv type containers to facilitate
> > > greater flexibility of meeting individual user needs. Therefore we
> > > would request a simple indication of preference for mixing in the
> > > user agent. We would further generalize this preference across all
> forms of alternative media content.
> > > >
> > > > *** Action to Take ***
> > > >
> > > > This CfC is now open for objection, comment, as well as statements
> > > > of
> > > support via email. Silence will be interpreted as support, though
> > > messages of support are certainly welcome.
> > > >
> > > > If you object to this proposed action, or have comments concerning
> > > > this
> > > proposal, please respond by replying on list to this message no
> > > later than
> > > 23:59 (Midnight) Boston Time, Wednesday 22 November.
> > > >
> > > > NOTE: This Call for Consensus is being conducted in accordance
> > > > with the
> > > APA Decision Policy published at:
> > > http://www.w3.org/WAI/APA/decision-policy
> > > >
> > > >
> > > --------------------------------------------------------------------
> > > -----------
> > > >
> > > > Janina Sajka (she/her/hers)
> > > > Accessibility Consultant https://linkedin.com/in/jsajka
> > > >
> > > > The World Wide Web Consortium (W3C), Web Accessibility Initiative
> (WAI)
> > > > Co-Chair, Accessible Platform Architectures
> http://www.w3.org/wai/apa
> > > >
> > > > Linux Foundation Fellow
> > > > https://www.linuxfoundation.org/board-of-directors-2/
> > > >
> > >
> > > --
> > >
> > > Janina Sajka (she/her/hers)
> > > Accessibility Consultant https://linkedin.com/in/jsajka
> > >
> > > The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
> > > Co-Chair, Accessible Platform Architectures
> http://www.w3.org/wai/apa
> > >
> > > Linux Foundation Fellow
> > > https://www.linuxfoundation.org/board-of-directors-2/
> > >
> > >
> > >
>
> --
>
> Janina Sajka (she/her/hers)
> Accessibility Consultant https://linkedin.com/in/jsajka
>
> The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
> Co-Chair, Accessible Platform Architectures     http://www.w3.org/wai/apa
>
> Linux Foundation Fellow
> https://www.linuxfoundation.org/board-of-directors-2/
>
>
>