W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > April to June 2003

Re: Javascript

From: Jonathan Chetwynd <j.chetwynd@btinternet.com>
Date: Fri, 2 May 2003 06:41:54 +0100
Cc: Isofarro <w3evangelism@faqportal.uklinux.net>, Angela Hilton <angela.hilton@umist.ac.uk>, w3c-wai-ig@w3.org
To: James Craig <work@cookiecrook.com>
Message-Id: <C8002249-7C60-11D7-9714-0003939B5AD0@btinternet.com>

James
rather than using skipnav, why not place the content links earlier than 
the nav links for each page? skipnav may work for screen readers, but 
how about people with physical impairments.
jonathan

On Thursday, May 1, 2003, at 07:36 PM, James Craig wrote:

>
> Isofarro wrote:
>
>> I think the trick with making DHTML accessible is to avoid 
>> onmouseover and
>> onmouseout - this is where things quickly become inaccessible.
>
> I've been working on some accessible DHTML menus that do use 
> onmouseover and onmouseout. Not finished yet, but my experiments so 
> far are here:
>
> http://www.cookiecrook.com/bugtests/menus/menus.htm
> http://www.cookiecrook.com/bugtests/menus/demo.htm
> http://www.cookiecrook.com/bugtests/menus/demo2.htm
>
> Unordered list, keyboard access via [tab], etc. Degrades well in 
> non-DOM or partial DOM browsers. Of course, the final will have to be 
> combined with a "skip nav" link, but these are just experiments.
>
> Also of note, for accessibility, if the user has JS turned off but CSS 
> on, they only receive access to the top-level links. Fortunately, the 
> site these are for provides redundant links in the page content for 
> each of the sub section. Users will not have the exact same 
> experience, but it will be a comparable, accessible, experience.
>
> Any comments on the accessibility of these? I'm curious.
>
> Thanks,
> James Craig
>
>
> -- 
> http://www.cookiecrook.com/
>
Received on Friday, 2 May 2003 01:39:03 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 July 2011 18:14:09 GMT