W3C home > Mailing lists > Public > public-wai-evaltf@w3.org > September 2011

RE: scope of "methodology"

From: Léonie Watson <lwatson@nomensa.com>
Date: Thu, 22 Sep 2011 10:23:38 +0100
To: Shadi Abou-Zahra <shadi@w3.org>, Eric Velleman <E.Velleman@bartimeus.nl>, Eval TF <public-wai-evaltf@w3.org>
Message-ID: <D4219A0ECCAE794C9ED7DC6F5A4C0CD537B37D0FCC@jupiter.intranet.nomensa.com>
	The scope looks good. I wonder if the definition of a website needs to include associated assets? I'm thinking Flash, PDF etc.


Nomensa - humanising technology

Léonie Watson, Director of Accessibility & Web Development

tel: +44 (0)117 929 7333
twitter: @we_are_Nomensa @LeonieWatson
-----Original Message-----
From: public-wai-evaltf-request@w3.org [mailto:public-wai-evaltf-request@w3.org] On Behalf Of Shadi Abou-Zahra
Sent: 22 September 2011 09:50
To: Eric Velleman; Eval TF
Subject: scope of "methodology"

Hi Eric, All,

In relation to agenda item #e, here is one attempt to outline and scope the "methodology". One definition for "methodology" could be:

- Process to assess the conformance of entire websites to a particular level of WCAG 2.0.

We would then also need to define "website"; here is a proposal for it:

- A coherent collection of one or more related web pages that together 
provide common use or functionality. It includes static websites, 
dynamically generated websites (aka CMS-driven), and web applications 
(aka client-side scripting).


Shadi Abou-Zahra - http://www.w3.org/People/shadi/
Activity Lead, W3C/WAI International Program Office
Evaluation and Repair Tools Working Group (ERT WG)
Research and Development Working Group (RDWG)
Received on Thursday, 22 September 2011 09:24:20 UTC

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