Re: Guidelines vs Standards (was Checkpoint 3.3)

>However, the argument that detracting from the presentation of a page in
>older browsers is more important than removing significant barriers to
users
>with disabilities being able to read the page would need to be presented,
as
>it has not yet.

Yet the whole contention and debate about Checkpoint 3.3 is that it is NOT a
situation where accessibility is being compromised for the sake of older
browsers.  Instead, the scenarios presented are accessible pages that older
browsers can read as well, yet the Guidelines condemn as non-compliant.

I am nervous about checkpoint 3.3 and a couple of other points, because the
wording seems to mandate the use of certain methods instead of outcome.
What makes me even more nervous, is when folks counter with 'well, you have
to apply common sense to them [the Guidelines].'

Forgive me for being bold, but I find common sense lacking in many instances
especially in the government workplace.  I think what is being argued for,
is guidelines that give the IT professional the ability to make their web
site accessible  yet save them from unnecessary, arbitrary protocols.

Wayne

Wayne Crotts
Network & Information Services
Institute on Human Development and Disability
     A University Affiliated Program
College of Family & Consumer Sciences
University of Georgia  30602

(706) 542-4968
(706) 542-4815 (fax)

----- Original Message -----
From: Charles McCathieNevile <charles@w3.org>
To: <webmaster@dors.sailorsite.net>
Cc: <w3c-wai-ig@w3.org>
Sent: Tuesday, July 20, 1999 6:27 PM
Subject: RE: Guidelines vs Standards (was Checkpoint 3.3)


The process which exists for requesting changes in the guidelines is to
write
to the working group at w3c-wai-gl@w3.org which is a list archived at
http://lists.w3.org/Archives/Public/w3c-wai-gl

Received on Tuesday, 20 July 1999 23:24:05 UTC