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

RE: Resolutions on Changes to REQUIREMENTS DOC

From: Lee Roberts <leeroberts@roserockdesign.com>
Date: Mon, 28 Jan 2002 06:55:53 -0600
To: <GV@TRACE.WISC.EDU>, "GLWAI Guidelines WG \(GL - WAI Guidelines WG\)" <w3c-wai-gl@w3.org>
Message-ID: <NFBBJHFEOLAGEICMIMBPAEIKCBAA.leeroberts@roserockdesign.com>
Just curious here.

Gregg
"S1 - Serving content in different forms in order to meet different user
needs or preferences is an acceptable way to comply with the guidelines,
--  as long as equivalents for all of the information are provided in
the different forms, and it is all available from the same URI.
(Accessible, findable links to alternate form(s) is allowed.) (Server
side solutions are acceptable - as specified.)"

Many times I've heard the argument that the blind or deaf can have someone
translate the information for them. Still it comes from the same URI. I
realize this avoids the standards we are attempting to provide. However, how
do we defeat this rationalization of the uneducated?

Thanks,
Lee

-----Original Message-----
From: w3c-wai-gl-request@w3.org [mailto:w3c-wai-gl-request@w3.org]On
Behalf Of Gregg Vanderheiden
Sent: Monday, January 28, 2002 12:19 AM
To: GLWAI Guidelines WG (GL - WAI Guidelines WG)
Subject: Resolutions on Changes to REQUIREMENTS DOC



Here is a quick summary of the changes to be made to the Requirements
Doc based on last weeks Working Session.

Each change is separated by dashed lines for clarity


--------------------------------------
In section 2 the statement
'Each requirement must be easily verifiable'
will be changed to:

Each requirement must be verifiable

----------------------------------------

Change
"WCAG 2.0 will clearly identify the target audience of each
requirement."
to:

WCAG 2.0 will clearly identify who will benefit from each requirement"

--------------------------------------

Combine A-1, A-2, and A-3 into one item that reads:

A -1  The working group acknowledges that accessibility to everyone is
not possible.  Our target is to make things as accessible to as many
people as possible given then need to have practical techniques and
criteria.  We will expend our best effort to identify techniques,
criteria and examples that would cover the greatest range possible.

--------------------------------------

In Section 2
"Sample Site"
is changed to
Sample content

--------------------------------------

Remove [N3]    Replace it with a placeholder that states:
N3 --  [Deleted during consolidation.]

---------------------------------

Tune up S1 so that it is clearer what is meant.  It would now read:

S1 - Serving content in different forms in order to meet different user
needs or preferences is an acceptable way to comply with the guidelines,
--  as long as equivalents for all of the information are provided in
the different forms, and it is all available from the same URI.
(Accessible, findable links to alternate form(s) is allowed.) (Server
side solutions are acceptable - as specified.)

--------------------------------------


If anyone has any concerns with these please let us know.   Else we will
be posting after this Thursday's session.


Thanks

Gregg




-- ------------------------------
Gregg C Vanderheiden Ph.D.
Professor - Human Factors
Dept of Ind. Engr. - U of Wis.
Director - Trace R & D Center
Gv@trace.wisc.edu <mailto:Gv@trace.wisc.edu>, <http://trace.wisc.edu/>
FAX 608/262-8848
For a list of our listserves send "lists" to listproc@trace.wisc.edu
<mailto:listproc@trace.wisc.edu>
Received on Monday, 28 January 2002 09:50:20 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:18 GMT