Re: DHTML and accessibility

by Barry Johnson <b_w_j(at)yahoo.com>

 Date:  Wed, 23 Apr 2003 10:13:36 -0700 (PDT)
 To:  Dominique Clawson <Dominique.Clawson(at)colorado.edu>
 Cc:  aware-techniques(at)hwg.org
 In-Reply-To:  colorado
  todo: View Thread, Original
Dominique,

Congratulations on wanting to make a plan and for
wanting to inculde axccessible features in it.

You should use the <noscript> option any time you use
a JavaScript for those that have scripts turned off or
whose browsers do not support Scripts.

You should also provide alternative content --- i.e.
have the main item on the menu click through to a page
that lists all of the links on the sub menu. This also
helps with some problems associated with cross browser
issues, not all browsers like the rollover menus. It
also helps to have the menu come up next to the
rollover item. a lot of people have problems getting
into the menu if they have to move the mouse too far.

Barry Johnson
508 compliance coordinator
BAE Systems, FAA Division

--- Dominique Clawson <Dominique.Clawson(at)colorado.edu>
wrote:
> Hello:
> 
> My question is: how does a reader read a submenu
> that's triggered from
> JavaScript and is located on another layer?
> 
> This also brings me to the following question: are
> layers readable by a
> screen reader.  I use Dreamweaver and use a lot of
> layers but I don't
> convert them to tables.
> W3C discourages the use of tables and favors instead
> the positioning of
> elements with CSS.
> 
> I'm getting ready to redesign our site completely
> (Yippee!!!). I have a plan
> to have a PLAN, instead of cleaning up later. (-:
> 
> Thanks for your thoughts and comments,
> 
> Dominique
> 

HWG: hwg-basics mailing list archives, maintained by Webmasters @ IWA