- From: Kynn Bartlett <kynn-edapta@idyllmtn.com>
- Date: Thu, 27 Dec 2001 16:25:49 -0800
- To: Scott Luebking <phoenixl@sonic.net>, w3c-wai-gl@w3.org
At 3:42 PM -0800 12/27/01, Scott Luebking wrote:
>Hi,
>
>I'm preparing some answers to some questions from some CHI-WEB people.
>Is there a definition of what an accessible web page is? (This might
>also be helpful for any future testing.)
A page is considered accessible if it can be used by users with
disabilities. It's not a very rigorous definition, but it's the
one in WCAG 1:
<blockquote cite="http://www.w3.org/TR/WCAG/#accessible"
xml:space="preserve">
Accessible
Content is accessible when it may be used by someone with a disability.
</blockquote>
There are obviously serious problems with this definition.
WCAG 2.0 draft does not attempt to define accessible, but instead
refers to accessible web sites and, by implication, kinda defines
accessibility:
<blockquote cite="http://www.w3.org/TR/WCAG20/#intro-purpose">
This document outlines design principles for creating accessible Web
sites. When these principles are ignored, individuals with
disabilities may not be able to access the content at all, or they
may be able to do so only with great difficulty. When these
principles are employed, they also make Web content accessible to a
variety of Web-enabled devices, such as phones, handheld devices,
kiosks, network appliances, etc. By making content accessible to a
variety of devices, the content is now accessible to people in a
variety of situations.
</blockquote>
Hope this helps.
--
Kynn Bartlett <kynn@idyllmtn.com> http://kynn.com
Chief Technologist, Idyll Mountain http://idyllmtn.com
Web Accessibility Expert-for-hire http://kynn.com/resume
January Web Accessibility eCourse http://kynn.com/+d201
Received on Thursday, 27 December 2001 19:27:43 UTC