W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > January to March 2002

Re: Checkpoint 4.4 Review

From: <goliver@accease.com>
Date: Mon, 18 Feb 2002 01:57:25 -0800 (PST)
To: GV@TRACE.WISC.EDU
Cc: w3c-wai-gl@w3.org
Message-Id: <20020218015726.23121.c000-h004.c000.wm@mail.accease.com.criticalpath.net>
Me between the *'s
<snip>

1 – I think the checkpoint could be worded more
straightforwardly.    Perhaps

Checkpoint 4.4 --  Ensure that content is usable with
default user agent settings and no plug-ins. 

*The wording doesn't work for me, it's too loose +
difficulty of defining 'default'*


Checkpoint 4.4   Ensure that all content is readable
and all function (other than artistic) is preserved
when stylistic and scripting technologies are not
supported or are turned off.   

*This is closer for me, but think it needs some
tweaking. For example, see Jim Thatcher's page [1] on
Scripts and Applets and Section 508.
I would agree with his analysis of a fly-over menu 

'If content is exposed with the onMouseOver event for a
link, then for your site to meet the Section 508
requirement for scripts, that content must be available
elsewhere, preferable prominently displayed on the page
that is opened by that link.'

To me this is accessible.

The functionality is not preserved (it can't be) but
there is 'equivalent availability'.

So I would prefer something like

*Ensure that all content remains available when
stylistic and scripting technologies are not supported
or are turned off.*


Cheers 
Graham

[1] - http://www.jimthatcher.com/webcoursea.htm

AccEase Ltd : Making on-line information accessible
Phone : +64 9 846 6995
Email : goliver@accease.com
Received on Monday, 18 February 2002 04:57:57 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:18 GMT