W3C home > Mailing lists > Public > w3c-wai-eo@w3.org > October to December 2004

RE: Comments-Selecting and Using Web Accessibility Evaluation Tools

From: Shadi Abou-Zahra <shadi@w3.org>
Date: Fri, 15 Oct 2004 18:21:42 +0200
To: "'Sailesh Panchang'" <sailesh.panchang@deque.com>, "'EOWG'" <w3c-wai-eo@w3.org>
Message-ID: <007401c4b2d3$0ed462a0$6466a8c0@K2>

Hi Sailesh,

Thank you for raising. It gets quite tricky with these multiple
negations, here an example:

Testing Web content for checkpoint 1.1:
  * Tool result: Pass (positive result)
  * Real result: Fail (actually, there is an error)

This means the tool would report a false positive by not identifying an
existing error. Or, as you define, report a positive result (Pass) in a
subject (Checkpoint 1.1) that doesn't have the necessary attributes
(actually failed).



-----Original Message-----
From: w3c-wai-eo-request@w3.org [mailto:w3c-wai-eo-request@w3.org] On
Behalf Of Sailesh Panchang
Sent: Friday, October 15, 2004 17:33
Subject: Comments-Selecting and Using Web Accessibility Evaluation Tools

I think the definitions are reversed for false positive / negative:

“False positives (not identifying existing errors) and false negatives
(incorrectly reporting errors).”

False positive= A positive test result in a subject that does not
possess the attribute for which the test is being conducted. 

This means an error is reported when none exists.


Sailesh Panchang
Senior Accessibility Engineer 
Deque Systems,11180  Sunrise Valley Drive, 
4th Floor, Reston VA 20191
Tel: 703-225-0380 Extension 105 
E-mail: sailesh.panchang@deque.com
Fax: 703-225-0387
* Look up <http://www.deque.com> *

Received on Friday, 15 October 2004 16:21:41 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:29:36 UTC