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

+1

sent from my phone

On Thu, Nov 16, 2023, 6:38 AM Fredrik Fischer <fredrik.fischer@myability.org>
wrote:

> +1
>
> ______________________________________________
>
> Fredrik Fischer (he/him)
> Digital Accessibility Expert
> Certified Professional in Accessibility Core Competencies
> Certified Web Accessibility Expert
> E-Mail: fredrik.fischer@myability.org
> Mobile: +43 (660) 1132553
> myAbility Social Enterprise GmbH
> Kärntner Ring 12/2b, 1010 Wien
> (Eingang über Dumbastraße 2)
> Handelsgericht Wien, FN 411924x, ATU68595601
> http://www.myability.org/ | Facebook | Instagram | LinkedIn
> Building an inclusive business world - with you.
> #DisabilityInclusion #GernePerDu
>
>
> -----Original Message-----
> From: Janina Sajka <janina@rednote.net>
> Sent: Wednesday, November 15, 2023 11:14 PM
> To: public-apa-admin@w3.org
> Subject: Call for Consensus (CfC): Comment on DAPT
>
> 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-Accessibility-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/
>
>
>
>