W3C home > Mailing lists > Public > public-wai-evaltf@w3.org > January 2013

Aim and impact of random sampling

From: Detlev Fischer <fischer@dias.de>
Date: Thu, 24 Jan 2013 17:22:59 +0100
Message-ID: <51015FE3.1050301@dias.de>
To: EVAL TF <public-wai-evaltf@w3.org>
The assumption has been that an additional random sample will make sure 
that a tester's intitial sampling of pages has not left out pages that 
may expose problems no present in the intitial sample.

That aim in itself is laudable, but for this to work, the sampling would 
need to be

1. independent of individual tester choices (i.e., automatic) -
    which would need a definition, inside the methodology, of a
    valid approach for truly random sampling. No one has even hinted on
    a reliable way to do that - I believe there is none.
    A mere calculaton of sample size for a desired level of confidence
    would need to be based to the total number of a site's pages *and*
    page states - a number that will usually be unknown.

2. Fairly represent not just pages, but also page states.
    But crawling a site to derive a collection of URLS for
    random sampling is not doable since many states (and there URLs or
    DOM states) only come about as a result of human input.

I hope I am not coming across as a pest if I say again that in my 
opinion, we are shooting ourselves in the foot if we make random 
sampling a mandatory part of the WCAG-EM. Academics will be happy, 
practitioners working to a budget will just stay away from it.


Detlev Fischer PhD
DIAS GmbH - Daten, Informationssysteme und Analysen im Sozialen
Geschäftsführung: Thomas Lilienthal, Michael Zapp

Telefon: +49-40-43 18 75-25
Mobile: +49-157 7-170 73 84
Fax: +49-40-43 18 75-19
E-Mail: fischer@dias.de

Anschrift: Schulterblatt 36, D-20357 Hamburg
Amtsgericht Hamburg HRB 58 167
Geschäftsführer: Thomas Lilienthal, Michael Zapp
Received on Thursday, 24 January 2013 16:23:24 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:40:23 UTC