WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: yet more questions

for

From: Glenda Watson Hyatt
Date: Aug 17, 2001 11:39AM


Thanks Paul, this does help. I'm not a Javascript expert either [am
realizing I need to learn the basics], so I'm flying by the seat of my
pants, which are wearing rather thin at the moment.
I've figured out the device independent concept enough to bluff it. What's
throwing me for a loop is "logical". What does that word mean in this
context? You use "more generic". That makes sense to me.
Cheers,
Glenda
>
> In answer to your question about logical event handlers and embedded
> interfaces:
>
> Logical event handlers:
> Here is what the W3C specification says: "For scripts, specify
> logical event
> handlers rather than device-dependent event handlers. [Priority 2] "
>
> It's easiest to explain the term by first explaining what a
> device-dependent
> event handler is. The easiest examples are JavaScript commands (event
> handlers) such as onMouseover. In the case of the onMouseover
> event handler,
> the event (moving your mouse over something) triggers another event (e.g.
> switch images, show submenus, or other effects). Much of the time,
> onMouseover events are not very important (as with images that appear to
> glow when you move the mouse over them), but in other cases the events can
> be very important (as when entirely new content appears when the
> mouse moves
> over a piece of text). It would be better to not rely on a
> particular device
> (e.g. a mouse) for these important events. A programmer could use other,
> more generic event handlers, such as onSelect, which would be
> activated with
> either a keystroke or a mouse click. I'm not a JavaScript expert,
> so someone
> else may be able to further clarify which specific event handlers
> should and
> shouldn't be used.
>
>
>
> Embedded interfaces:
> The W3C spec says: "Ensure direct accessibility of embedded user
> interfaces."
>
> Things that qualify as embedded user interfaces include:
> -java applets
> -media players (Windows Media Player, RealVideo, QuickTime, etc.)
> -Flash animations/scripts
> -Shockwave scripts
> -all other plug-ins
>
> The idea here is to make sure that you use plug-ins that are built for
> accessibility. There are relatively few of them, especially when
> it comes to
> embedded plug-ins (see "To embed or not to embed" on the WebAIM site
> http://www.webaim.org/Articles/embeddedmp.php). The guideline is just
> telling us not to use inaccessible plug-ins and java applets, and not to
> create them.
>
> Hope this helps.
>
> Paul Bohman
> Technology Coordinator
> WebAIM: Web Accessibility in Mind (www.webaim.org)
> Center for Persons with Disabilities (www.cpd.usu.edu)
> Utah State University (www.usu.edu)
>
>
> ----- Original Message -----
> From: "Glenda Watson Hyatt" < <EMAIL REMOVED> >
> To: "WebAIM accessibility forum" < <EMAIL REMOVED> >
> Sent: Thursday, August 16, 2001 12:39 PM
> Subject: yet more questions
>
>
> > Can anyone explain, in simple terms, "logical" event handlers?
> >
> > And "embedded" interfaces?
> >
> > Thanks,
> > Glenda
> >
> > *********
> > Glenda Watson Hyatt
> > Soaring Eagle Communications
> > "Creating freedom and power through accessible communications"
> > E Mail: mailto: <EMAIL REMOVED>
> > Website: http://www.eaglecom.bc.ca
> > Want to know how to make your website accessible to more people?
> > Subscribe to our FREE newsletter by emailing
> > mailto: <EMAIL REMOVED>
> >
> > *********
> >
> >
> >
> >
>
>