Re: [106attendees] Accessibility for remote participants

Jared Mauch <jared@puck.nether.net> Wed, 20 November 2019 21:46 UTC

Return-Path: <jared@puck.nether.net>
X-Original-To: 106attendees@ietfa.amsl.com
Delivered-To: 106attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68C441207FC for <106attendees@ietfa.amsl.com>; Wed, 20 Nov 2019 13:46:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zGE9kzdaBeaY for <106attendees@ietfa.amsl.com>; Wed, 20 Nov 2019 13:46:39 -0800 (PST)
Received: from puck.nether.net (puck.nether.net [204.42.254.5]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2E6EA120233 for <106attendees@ietf.org>; Wed, 20 Nov 2019 13:46:39 -0800 (PST)
Received: from dhcp-9354.meeting.ietf.org (dhcp-9354.meeting.ietf.org [31.133.147.84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by puck.nether.net (Postfix) with ESMTPSA id 77387540085; Wed, 20 Nov 2019 16:46:36 -0500 (EST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <CABZ0mu63tS3o9XMWBFcVm8ARt71KZCVZ8xXGN=sFCiEZzqdwWA@mail.gmail.com>
Date: Wed, 20 Nov 2019 16:46:34 -0500
Cc: 106attendees@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <73B864DC-958E-4C7A-8420-A5F767CA6CDE@puck.nether.net>
References: <CABZ0mu63tS3o9XMWBFcVm8ARt71KZCVZ8xXGN=sFCiEZzqdwWA@mail.gmail.com>
To: Geoff Lanotte <geofflanotte@gmail.com>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/106attendees/iJFepF9QDqRudts3229qV_oj3NA>
Subject: Re: [106attendees] Accessibility for remote participants
X-BeenThere: 106attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list of all 106 attendees for official communication <106attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/106attendees>, <mailto:106attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/106attendees/>
List-Post: <mailto:106attendees@ietf.org>
List-Help: <mailto:106attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/106attendees>, <mailto:106attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Nov 2019 21:46:40 -0000


> On Nov 20, 2019, at 4:31 PM, Geoff Lanotte <geofflanotte@gmail.com> wrote:
> 
> We have some people accessing remotely for one of the sessions that are deaf, is there any captioning (english) being provided or do we need to provide our own interpreters?


When I’ve scribed in the past, I have thought about trying to transcribe the entire conversation into the room or ether pad.

The key thing for me is that we should be ensuring the conversations are happening on-list vs rapid-fire at a microphone.  There are some well known elements that may speak at a rate that is not parsable even for native speakers let alone those who might need to translate/interpret.

While the in-person meetings are valuable, last-call and other important things remain in text format that can be translated/scraped/screen-read.

- Jared