- From: Charles McCathieNevile <charles@w3.org>
- Date: Wed, 20 Oct 1999 19:17:09 -0400 (EDT)
- To: Carine Ullom <carine@ukans.edu>
- cc: "'Web Accessibility Initiative'" <w3c-wai-ig@w3.org>
You could add: browser-sniffing that rejects browsers (or suggests changing browser) reliance on javascript, java applets, shockwave, etc without accessible alternatives reliance on presentational effects (e.g. CSS, font styles, colours) to convey semantic meaning Charles McCN On Wed, 20 Oct 1999, Carine Ullom wrote: Hi, I'm conducting a poster session at a conference soon and want to list on my poster the "Top Ten Barriers to Web Site Accessibility." I have on my list so far - in no particular order (I think I got most of this from the WAI, but it's been a while ago and I'm not sure): 1) Lack of text alternatives for graphical content (e.g., images as links) 2) Misuse of HTML elements (e.g., using <H2? without <H1> in order to achieve a certain font size and text position) 3) Absence of meaningful link text (e.g., the ubiquitous "Click Here" links) 4) Absence of a formal document structure (e.g., sections, subsections, etc.) 5) Lack of consistent navigational structures Additions? Priorities? Which is the #1 barrier (or is there a #1?). TIA, Carine Ullom Software Training Specialist Academic Computing Services University of Kansas Computer Center Lawrence, KS 66045 PH: 785-864-0467 FX: 785-864-0485 e-mail: carine@ukans.edu --Charles McCathieNevile mailto:charles@w3.org phone: +1 617 258 0992 http://www.w3.org/People/Charles W3C Web Accessibility Initiative http://www.w3.org/WAI MIT/LCS - 545 Technology sq., Cambridge MA, 02139, USA
Received on Wednesday, 20 October 1999 19:17:11 UTC