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

RE: mouse example in "Introduction to Web Accessibilty document"

From: Shawn Lawton Henry <shawn@w3.org>
Date: Fri, 16 Jul 2004 22:45:21 -0500
To: "'EOWG'" <w3c-wai-eo@w3.org>
Message-ID: <000101c46bb0$7c764b80$d4837544@SLHenry>

Per the comments below, I am inclined to keep the example as simple as
possible - rather than going for specificity and range. Open for
discussion - rewrite coming soon...

> On Behalf Of Libby Cohen
> 
> Here's a suggestion for rewording the "mouse" example in the
> Introduction to Web Accessibility document: For example, some 
> individuals are not able to use a typical computer input 
> device, such as a mouse. Web accessibility ensures that the 
> Web can be used with other types of input devices, such as 
> onscreen keyboards, switches, and pointers.

> On Behalf Of Andrew.Arch@visionaustralia.org.au
>
>  Web accessibility focuses on designing [pages and
> applications] so that people with disabilities can use the  
> Web effectively. For example, some people cannot use a mouse  
> [while others cannot see the screen and its graphics]. Web  
> accessibility ensures that the Web can be used with only a  
> keyboard and does not require a mouse, [and information is  
> contained solely in images]. [An accessible site is also  
> likely to be more usable on mobile devices than inaccessible sites??]
>
> And just to note that I like the term "functional
> limitations" as can include  the elderly, injured, and PWD

Right - _we_ all know that, but will the novice reader? I think the
novice reader is much more likely to not have a clue what is meant by
"functional limitations" and not only lose that it encompasses those you
mention, but miss the basic meaning as well.
Received on Friday, 16 July 2004 23:45:28 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:55:52 UTC