Re: RE:What shall we do about evaluation tools

I am in favor of numbers 3, 5, and 6.

Tools to help do the assessments should be easily understood and usable by
all.  They should make it clear what the accessibility features are, and how
they can be easily implemented.  We need to keep things simple for people
who are not sophisticated web page designers and builders.  With the low
barrier to entry many sites will be put up for small businesses.  For both
their benefit and the benefit of the users who need accessible web sites we
must be sure that these sites can be accessible.  If we raise the barrier of
entry too high for the small web sites, then we destroy the web.

Automated and Semi-automated correction tool can help correct errors and if
properly designed they can help the uninitiated to make their sites
accessible.

These are my thoughts...I repeat again that we must keep things simple.

Sincerely,

Mike Burks
-----Original Message-----
From: David Clark <dmclark@cast.org>
To: Kasday, Leonard R (Len), ALTEC <kasday@att.com>
Cc: w3c-wai-rc@w3.org <w3c-wai-rc@w3.org>
Date: Monday, March 16, 1998 8:44 AM
Subject: RE:What shall we do about evaluation tools


         Reply to:   RE:What shall we do about evaluation tools
My vote would be a combination of 1 & 4.  I think that an automatic checker
is more appealing to the "nonconverted", and quantitative feedback  is much
more tangible.

David Clark
CAST, Inc.
On 3/14/98, Kasday, Leonard R (Len), ALTEC wrote:
>Subject: What sorts of activities shall we do with respect to tools.
>
>We need to decide on the specific things we will do as a group.  One
>general area is that of tools (like Bobby) that evaluate accessibilty.
>
>Which if any of the following shall we deal with?
>
> 1. accessibility tests that can be done in a purely automatic manner
> 2. tests that require human judgment
> 3. tools to help the humans do those judgments
> 4. an algorithm for an overall score
> 5. automated repair of access problems
> 6. semi-automated repair of access problems
> 7. Other, viz. (fill in the blank)
>
>And what sort of involvement should that be?  For example, >
>a. write a specification
>b. collect data needed for evaluation, e.g. capabilities of current
>browser/screenreaders
>c. develop tools
>d. provide master page that forwards to one or more tools
>e. serve as clearinghouse for tools (and what does clearinghouse >mean)
>f. Other, viz. (fill in the blank).
>
>Len
>
>============================================================
>=
>kasday@att.com         phone 732 949 2693
>
>Leonard R. Kasday
>Room 1J-316A
>AT&T Laboratories
>101 Crawfords Corner Rd.
>Holmdel NJ 07733
>
>>
>
>
>
>RFC822 header
>-----------------------------------
>From w3c-wai-rc-request@w3.org Sat Mar 14 16:17:35 1998
>Received: by CASTSERVER1.cast.org from localhost
>    (router,QMProSrv V2.5); Sat, 14 Mar 1998 16:17:35 -0500
>Received: by CASTSERVER1.cast.org from www19.w3.org
>    (18.29.0.19::mail daemon; unverified,QMProSrv V2.5); Sat, 14 Mar 1998
>16:17:34 -0500
>Received: by www19.w3.org (8.8.5/8.6.12) id QAA16733; Sat, 14 Mar >1998
16:13:09 -0500 (EST)
>Resent-Date: Sat, 14 Mar 1998 16:13:09 -0500 (EST)
>Resent-Message-Id: <199803142113.QAA16733@www19.w3.org>
>X-Authentication-Warning: www10.w3.org: Host cagw2.att.com >[192.128.52.90]
claimed to be att.com
>Message-ID: <c=US%a=_%p=ATT%l=NJC240PO04-980314211404Z-
>4026@njb140bh3.EMS.ATT.COM>
>From: "Kasday, Leonard R (Len), ALTEC" <kasday@att.com>
>To: "'wai rc group post'" <w3c-wai-rc@w3.org>
>Date: Sat, 14 Mar 1998 16:14:04 -0500
>X-Mailer:  Microsoft Exchange Server Internet Mail Connector Version
>4.0.995.52
>MIME-Version: 1.0
>Content-Type: text/plain; charset="us-ascii"
>Content-Transfer-Encoding: 7bit
>Subject: What shall we do about evaluation tools
>Resent-From: w3c-wai-rc@w3.org
>X-Mailing-List: <w3c-wai-rc@w3.org> archive/latest/13
>X-Loop: w3c-wai-rc@w3.org
>Sender: w3c-wai-rc-request@w3.org
>Resent-Sender: w3c-wai-rc-request@w3.org
>Precedence: list
>Status: RO
>
>

Received on Monday, 16 March 1998 11:28:17 UTC