W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > April to June 2018

RE: Question on 1.2.4 and "publicly broadcast"

From: White, Jason J <jjwhite@ets.org>
Date: Thu, 17 May 2018 18:39:32 +0000
To: John Foliot <john.foliot@deque.com>, Laura Carlson <laura.lee.carlson@gmail.com>
CC: WCAG List <w3c-wai-gl@w3.org>
Message-ID: <DM5PR07MB38680278B1D80F7D5A58B0F6AB910@DM5PR07MB3868.namprd07.prod.outlook.com>
Although not required by WCAG (perhaps it’s an issue for Silver), supporting video of sufficient quality to enable good transmission of sign languages is important in conferencing and similar WebRTC-based applications. Obviously, this isn’t entirely under the application author’s control, as I expect it can be affected by issues of network bandwidth and latency. However, if there are factors that the application can take into account, the issue would be worthy of further development.

From: John Foliot <john.foliot@deque.com>
Sent: Thursday, May 17, 2018 12:08 PM
To: Laura Carlson <laura.lee.carlson@gmail.com>
Cc: WCAG List <w3c-wai-gl@w3.org>
Subject: Re: Question on 1.2.4 and "publicly broadcast"

Hi Laura,

This starts to get murky, as ultimately what I think you are asking is "...does the 'platform' need to support captioning..."? (To which I would suggest - yes)

When it comes to two individuals engaged in direct 1-1 video conversation however, whether or not the video requires 'captions' will be dependent on the scenario: for example, I could easily imagine a "video chat" window open (say even a conference call), where the deaf person would *also* have a separate TTY device included in the mix, circumventing the need for on-screen 'captions' as we traditionally know them.

None-the-less, I would suggest (however this is but my opinion) that the creators of video communications platforms (hardware or software or both) *SHOULD* have the capacity to support HTML5 style captioning solutions (the eco-system requirement), but that when it comes to individual content the decision is significantly more nuanced and I do not think it could be regulated as a black-or-white decision.

That said, content creators who seek to provide two-way communications via video chat will still shoulder the burden of ensuring that they are not discriminating against non-hearing users, so, for example, a "help-desk" application/solution that involved videos MUST support captions when required, or provide a functional equivalent. For large organizations, this is as much a policy concern as it is a technical one I suspect.

(Not sure if this answers the question, but hope this helps).


On Thu, May 17, 2018 at 10:33 AM, Laura Carlson <laura.lee.carlson@gmail.com<mailto:laura.lee.carlson@gmail.com>> wrote:
Hello everyone,

I have received a question on 1.2.4 regarding if it is or id it isn't
applicable to content that is not "publicly broadcast" e.g. video

The understanding doc for 1.2.4 states [1], "This success criterion
was intended to apply to broadcast of synchronized media and is not
intended to require that two-way multimedia calls between two or more
individuals through web apps must be captioned regardless of the needs
of users."

If a person needs captioning in a private video chat does 1.2.4 apply?

Thank you.

Kindest Regards,

[1] https://www.w3.org/TR/UNDERSTANDING-WCAG20/media-equiv-real-time-captions.html<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FTR%2FUNDERSTANDING-WCAG20%2Fmedia-equiv-real-time-captions.html&data=02%7C01%7Cjjwhite%40ets.org%7C3d7567cff2d549c06f0608d5bc10aeba%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636621702188701411&sdata=ERIuo3Fd7dS%2F8%2BjL4S3%2FF75JpRFvFpM9gGbRfzvPhLE%3D&reserved=0>

Laura L. Carlson

John Foliot
Principal Accessibility Strategist
Deque Systems Inc.

Advancing the mission of digital accessibility and inclusion


This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.

Thank you for your compliance.

Received on Thursday, 17 May 2018 18:40:00 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 21:08:26 UTC