E-mail List Archives

Re: bad page the passes accessibility checker (was 10.5 Separate adjacent links)

for

From: Jim Allan
Date: Mar 23, 2005 4:32PM


You might also check out Jim Thatcher's presentation on "What not to do!"
http://www.jimthatcher.com/whatnot2004/ or
www.jimthatcher.com/whatnot.htm

Jim Allan, Webmaster & Statewide Technical Support Specialist
Texas School for the Blind and Visually Impaired
1100 W. 45th St., Austin, Texas 78756
voice 512.206.9315 fax: 512.206.9264 http://www.tsbvi.edu/
"I see the Earth. It is so beautiful."--first words spoken by human in
space.
[Yuri Alekseevich Gagarin, from the Vostok 1, April 12, 1961.]

-----Original Message-----
From: norman.b.robinson [mailto: <EMAIL REMOVED> ]
Sent: Wednesday, March 23, 2005 4:09 PM
To: WebAIM Discussion List
Subject: Re: [WebAIM] 10.5 Separate adjacent links



Glenda/Terence;

Could you post an example of said web page? Do you have a
"template" you would care to share?

Regards,

Norman Robinson

-----Original Message-----
From: lists38 [mailto: <EMAIL REMOVED> ]
Sent: Tuesday, March 22, 2005 4:02 PM
To: WebAIM Discussion List
Subject: Re: [WebAIM] 10.5 Separate adjacent links



glenda wrote:

>Thank you, Terence!
>
>That is the explanation I was actually looking for -- in case the
>client asks why the site isn't Bobby-approved [even though it complies
>with Web Content Accessibility Guidelines 1.0, as far I know]. Some
>clients put so much credence into Bobby and other automated checkers,
>without fully understanding what makes a site accessible.
>
>
>
I normally create a page that does not make sense at all (bad
alternative text, wrong structure) and show that bobby deems it AAA
compliant. Then I point the clients to the plethora of "User Checks"
Bobby flags up and explain that accessibility testing is 10% tops
technical problems, the rest common sense and usability.

Another good example to show the user when is bobby complaining when an
onclick is not accompanied by an onkeypress that the onkeypress will
also be triggered by the tab key on mozilla. The workaround of course
is to apply the handler VIA javascript rather than in the HTML.

----
To subscribe or unsubscribe, visit http://www.webaim.org/discussion/

----
To subscribe or unsubscribe, visit http://www.webaim.org/discussion/