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

RE: Are Small Text buttons level 2 compliant

From: Bailey, Bruce <Bruce_Bailey@ed.gov>
Date: Tue, 26 Sep 2000 11:17:16 -0400
Message-ID: <AF196F44735ED411B93A00508BDFB1080E4297@WDCROBEXC09>
To: "'Leonard R. Kasday'" <kasday@acm.org>, "'WAI'" <w3c-wai-ig@w3.org>
Jeez Len, I thought I sometimes asked dangerous questions!
A few violators of this rule:
http://www.cast.org/bobby/ <http://www.cast.org/bobby/> 
http://www.section508.gov/ <http://www.section508.gov/> 
http://www.microsoft.com/enable/ <http://www.microsoft.com/enable/>  (but
only on their search button, the other menus are text)
http://www.trace.wisc.edu/ <http://www.trace.wisc.edu/>  (image maps)
I think you are quite correct, but that's just MHO.

-----Original Message-----
From: w3c-wai-gl-request@w3.org [mailto:w3c-wai-gl-request@w3.org]On Behalf
Of Leonard R. Kasday
Sent: Tuesday, September 26, 2000 10:20 AM
To: w3c-wai-gl@w3.org
Cc: w3c-wai-er-ig@w3.org
Subject: Are Small Text buttons level 2 compliant

To the people of WCAG,

Many sites use small buttons, menus or tabs that have text as images, e.g.

FAQs, Our Team, About Us, Consumer Products, Web Sites, Computers, Welcome,
News, How-to, Connect,

(this is a mixture from several web sites)

Do these pass the following priority 2 checkpoint? [1] 

3.1 When an appropriate markup language exists, use markup rather than
images to convey information. [Priority 2] For example, use MathML to mark
up mathematical equations, and style sheets to format text and control
layout. Also, avoid using images to represent text -- use text and style
sheets instead. 

I contend no, small image buttons/menus/tabs fail this checkpoint: since an
accessible markup exists, viz. ordinary HTML.  Plus the last sentence
explicitly says to not use images for text. 

Feasible methods exist. You can get rid of the link underline, and control
color and font with a stylesheet.  Rectangular buttons are easy.  If you
want something a bit fancier like rounded corners, it's straightforward to
piece together the text parts with slivers of images.  That's a bit of a
kluge, but in balance I think it's better than making the whole thing text,
given the importance of that checkpoint to people with low vision, who can
otherwise simply enlarge the fonts and/or change the colors.  (Loads faster

I expect some objections to this position, since a number of well known
sites in the disability area use such images, so there are clearly folks who
didn't think this was a violation.

By the way, the one place I would allow text as images are in logos, where
there are substantial reasons for making the look exact.  


This isn't an academic question for me: e.g. full WCAG is now Pennsylvania
State Policy, so we've got to know if image folkder tabs are "legal".

Leonard R. Kasday, Ph.D.        
Institute on Disabilities/UAP and Dept. of Electrical Engineering at Temple
(215) 204-2247 (voice)                 (800) 750-7428 (TTY)         
mailto:kasday@acm.org <mailto:kasday@acm.org>  

Chair, W3C Web Accessibility Initiative Evaluation and Repair Tools Group
http://www.w3.org/WAI/ER/IG/ <http://www.w3.org/WAI/ER/IG/> 

The WAVE web page accessibility evaluation assistant:
Received on Tuesday, 26 September 2000 11:17:51 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:35:57 UTC