[Mtgvenue] Accessibility: (was Re: comments on draft-ietf-mtgvenue-iaoc-venue-selection-process-04)

Dave Crocker <dhc@dcrocker.net> Mon, 30 January 2017 15:25 UTC

Return-Path: <dhc@dcrocker.net>
X-Original-To: mtgvenue@ietfa.amsl.com
Delivered-To: mtgvenue@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA6E7129505 for <mtgvenue@ietfa.amsl.com>; Mon, 30 Jan 2017 07:25:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.791
X-Spam-Level:
X-Spam-Status: No, score=-1.791 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=dcrocker.net
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 8CxzaYwkLZle for <mtgvenue@ietfa.amsl.com>; Mon, 30 Jan 2017 07:25:04 -0800 (PST)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F182F129504 for <mtgvenue@ietf.org>; Mon, 30 Jan 2017 07:25:03 -0800 (PST)
Received: from [192.168.1.168] (76-218-8-128.lightspeed.sntcca.sbcglobal.net [76.218.8.128]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id v0UFQRkL027367 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 30 Jan 2017 07:26:27 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1485789988; bh=iYzJyomFW+2V0iATYj+9RU04hbv63b0SKTyb/RHlCps=; h=Subject:To:References:From:Reply-To:Date:In-Reply-To:From; b=Zvr4ReIwxBrivyBZOHh9+UijeF8+rr8/hVYi2A2wjzBc/PL1e0zYA7f/9kOkbM6LD brkk2Hek0lyt9HT56KrsLbw4QwTRkAanpW4wU5vNLhL0iQc4rNQHwlsbGIiMnNVKsM xj+bvDRxOsh6CRxgM4y77juWgsdJCq9MFVnngboY=
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, Eliot Lear <lear@cisco.com>, mtgvenue@ietf.org
References: <9139334c-9c5e-814d-4299-c6f5950039b8@cs.tcd.ie> <2dcdf5d1-4e93-7476-79ba-0369e41af1c0@cisco.com> <43126aa9-5bc1-fae5-ff76-3ad288e37340@cs.tcd.ie>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <ac591a9b-f1e4-7069-f9f1-a0cb3921f108@dcrocker.net>
Date: Mon, 30 Jan 2017 07:24:44 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <43126aa9-5bc1-fae5-ff76-3ad288e37340@cs.tcd.ie>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/qxpKDjyoQAcZu2GR638054BengI>
Subject: [Mtgvenue] Accessibility: (was Re: comments on draft-ietf-mtgvenue-iaoc-venue-selection-process-04)
X-BeenThere: mtgvenue@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: "List for email discussion of the IAOC meeting venue selection process." <mtgvenue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mtgvenue>, <mailto:mtgvenue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mtgvenue/>
List-Post: <mailto:mtgvenue@ietf.org>
List-Help: <mailto:mtgvenue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mtgvenue>, <mailto:mtgvenue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Jan 2017 15:25:05 -0000

On 1/30/2017 4:40 AM, Stephen Farrell wrote:
>>> - 3.2: I don't get the distinction with "wheelchair" being
>>> mandatory and "accessible to people with disabilities"
>>> being only important. That seems like a contradiction to
>>> me. (Same in 3.4) Can you explain?
>> Funnily enough I wondered about the distinction as well, even what it
>> meant.  And so I went and asked a well known accessibility expert
>> (Andrea Saks) about this.  She pointed out that this would have to do
>> with whether elevators have braille, whether there are bedrooms are set
>> up for deaf people (doorbell lights, and such).  I'm going to hazard a
>> guess that many venues outside the US are in some way partial compliance
>> with what we Americans would call the ADA.  I'm guessing that's what
>> this is about.  A good # of UN buildings (including the ITU) have some
>> limitations along these lines, for instance.
> You may be right, but given it's confusing to both of us, that
> suggests a re-write is needed I think, but I also think that all
> criteria related to disability logically need to be at the same
> level, whether that's mandatory or important.


Is it acceptable to have a venue that requires everyone to climb a lot 
of stairs?  The answer needs to be no.

Is it acceptable to have a venue that does not have braille for its 
elevator buttons?  While it is appealing to say no, it almost certainly 
isn't practical.  Given international variability, it is likely to 
exclude even more places.

Repeat this for the very large range of very detailed, technical 
requirements that occur in any serious accessibility standard, and we 
will rapidly eliminate all but a very tiny set of venues.

'Wheelchair access' benefits far more than folk in wheelchair.  It aids 
everyone with mobility issues.  There is a universality to this benefit 
that is not matched by the many other details concerning accessibility.

That's why there two different entries in the draft, with different 
requirements levels.

d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net