W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > July to September 2001

Re: More: Disability Type Analysis of WCAG 2.0 and Section 508

From: Tyler Kendall <tyler_kendall@ncsu.edu>
Date: Fri, 24 Aug 2001 09:11:37 -0400
Message-ID: <3B865289.C899591F@ncsu.edu>
To: Kynn Bartlett <kynn@reef.com>
CC: w3c-wai-ig@w3.org
Kynn,

Thanks for bringing this up (and for your comprehensive data breakdown).

It does seem that the Section 508 guidelines are targeted especially
towards access for users with visual disabilities.  A clear sign of this
is the Access Board's guide to Section 508 -
http://www.access-board.gov/sec508/guide/1194.22.htm - which in most
places equates accessibility with accessibility for screen reader
users.  

For example, see the Scripts section -
http://www.access-board.gov/sec508/guide/1194.22.htm#(l) - which gives
advice contrary to the WCAG's HTML Techniques recommendations -
http://www.w3.org/TR/WCAG10-HTML-TECHS/#directly-accessible-scripts -
regarding event handling.

Best,
    --tyler

Kynn Bartlett wrote:

> Section 508 seems to have mostly adopted the requirements for visual
> disabilities from WCAG "single-A", but falls behind on cognitive
> limtations.  This is mostly attributable to the fact that WCAG 1.0's
> "use clearest and simplest language" checkpoint which does not have an
> equivalent in 508.  Some progress seems to have been made for low dexterity
> but that is a bit misleading since keyboard access is not explicitly
> required in 508.

--
Tyler Kendall
Web Accessibility Specialist
North Carolina State University
Voice: 919-513-4087
Fax: 919-513-1893
Email: tyler_kendall@ncsu.edu
Received on Friday, 24 August 2001 09:14:14 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 July 2011 18:13:56 GMT