W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 2018

ReA authoring accessible tools

From: Cohn, Jonathan <jcohn@air.org>
Date: Thu, 1 Feb 2018 15:40:09 +0000
To: "accessys@smart.net" <accessys@smart.net>, "Sean Murphy (seanmmur)" <seanmmur@cisco.com>
CC: Phill Jenkins <pjenkins@us.ibm.com>, "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
Message-ID: <AE134389-ACBA-4F71-8DB3-1A88C563190F@air.org>

´╗┐On 1/31/18, 6:04 PM, "accessys@smart.net" <accessys@smart.net> wrote:

    ADA  and section 508 are user oriented.  basing things on what the user 
    can expect or "depend" on not on how it happens.  it is OS and platform 
    neutral and only says one has to be able to use it.  not "how"---
I have to disagree a little here. If a contractor is building a website that will be maintained by the contractor then the contractor can use whatever tools they want for development of the site. If however, updates will eventually be done by Government employees then Section 508 requires that those updates can be done by a person with disabilities. 
On a related note:

I found it a bit disappointing that one of the major time tracking systems used by Government contractors is nearly completely inaccessible, but since the time keeping system is internal to the contractor it is not subject to Section 508. I know several blind people who have to have co-workers enter their time for them on this system. However there seemed to be nothing tthat could be done with Section 508 regulations to try and correct this issue. The 508 rules expressly state that items that are used tby contractors and are not deliverables to the government are not subject to the accessibility rules.  


Jonathan Cohn

Received on Thursday, 1 February 2018 15:41:07 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 1 February 2018 15:41:09 UTC