E-mail List Archives
Thread: yet more questions
Number of posts in this thread: 10 (In chronological order)
From: Glenda Watson Hyatt
Date: Fri, Aug 17 2001 12:48AM
Subject: yet more questions
No previous message | Next message →
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 ADDRESS 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 ADDRESS REMOVED =
*********
From: Paul Bohman
Date: Fri, Aug 17 2001 10:36AM
Subject: Re: yet more questions
← Previous message | Next message →
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 ADDRESS REMOVED = >
To: "WebAIM accessibility forum" < = EMAIL ADDRESS 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 ADDRESS 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 ADDRESS REMOVED =
>
> *********
>
>
>
>
From: Michael Goddard
Date: Fri, Aug 17 2001 11:12AM
Subject: Re: yet more questions
← Previous message | Next message →
Paul,
Helps tons! Thank you for the information even though I did not ask the
question. Great to be learning something new.
Michael
----- Original Message -----
From: "Paul Bohman" < = EMAIL ADDRESS REMOVED = >
To: "WebAIM forum" < = EMAIL ADDRESS REMOVED = >
Sent: Friday, August 17, 2001 12:33 PM
Subject: Re: yet more questions
> 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 ADDRESS REMOVED = >
> To: "WebAIM accessibility forum" < = EMAIL ADDRESS 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 ADDRESS 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 ADDRESS REMOVED =
> >
> > *********
> >
> >
> >
> >
>
>
>
From: Glenda Watson Hyatt
Date: Fri, Aug 17 2001 11:39AM
Subject: Re: yet more questions
← Previous message | Next message →
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 ADDRESS REMOVED = >
> To: "WebAIM accessibility forum" < = EMAIL ADDRESS 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 ADDRESS 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 ADDRESS REMOVED =
> >
> > *********
> >
> >
> >
> >
>
>
From: Reidy Brown
Date: Fri, Aug 17 2001 11:47AM
Subject: Re: yet more questions
← Previous message | Next message →
Device dependent handlers will usually have an actual device name in the
event handler name, like onMouseOver or onKeyPress. An example of a
"logical" event handler would be "onSelect," or "onFocus," or "onBlur"-- in
other words, you're interested in what's happened to the element, not what
caused it to happen. You care that the element has gained or lost focus or
that it has been selected. You don't care whether someone used a mouse or a
keyboard to make it happen.
(Although in practice, many user agents (browsers) are pretty good at
translating device dependent handlers to logical handlers on the fly.)
Reidy
-------------------------------------------
Reidy Brown
Accessibility Coordinator/Sr. Software Engineer
Blackboard, Inc.
(202) 463-4860 x236
-------------------------------------------
Blackboard 5.5 Fully Implements Section 508 Accessibility Standards!
Learn more:
http://products.blackboard.com/cp/bb5/access/index.cgi
-------------------------------------------
From: Paul Bohman
Date: Fri, Aug 17 2001 11:55AM
Subject: Re: yet more questions
← Previous message | Next message →
In the context of my email, I used "more generic" to be a sort of synonym for "logical". The onSelect qualifies as a logical event handler because there are multiple ways to select something: kebyoard, mouse, etc. Event handlers such as onClick, onKeypress, or similar, are device-dependent. onSelect represents the logical action: I'm selecting it somehow, whether by keyboard, mouse, retinal scanning, puff-and-sip device or whatever else. The logical ("more generic") event is that of selecting. The device doesn't matter in this case.
A programmer may be able to give you a more technical answer, but that's the gist of it.
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 ADDRESS REMOVED = >
To: "WebAIM forum" < = EMAIL ADDRESS REMOVED = >
Sent: Friday, August 17, 2001 11:29 AM
Subject: RE: yet more questions
>
> 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 ADDRESS REMOVED = >
> > To: "WebAIM accessibility forum" < = EMAIL ADDRESS 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 ADDRESS 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 ADDRESS REMOVED =
> > >
> > > *********
> > >
> > >
> > >
> > >
> >
> >
>
>
From: Glenda Watson Hyatt
Date: Fri, Aug 17 2001 1:41PM
Subject: Re: yet more questions
← Previous message | Next message →
So, the difference between WCAG 6.4 and 9.3 is...?
>
From: Paul Bohman
Date: Fri, Aug 17 2001 2:05PM
Subject: Re: yet more questions
← Previous message | Next message →
> So, the difference between WCAG 6.4 and 9.3 is...?
6.4 For scripts and applets, ensure that event handlers are input
device-independent. [Priority 2]
9.3 For scripts, specify logical event handlers rather than device-dependent
event handlers. [Priority 2]
Looks to me like just a little bit of redundancy. Aside from the presence or
absence of the word "applets," these two checkpoints are saying essentially
the same thing.
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)
From: Glenda Watson Hyatt
Date: Fri, Aug 17 2001 3:53PM
Subject: Re: yet more questions
← Previous message | Next message →
So, I'm not missing a subtle difference or point here? Great!
>
>
> > So, the difference between WCAG 6.4 and 9.3 is...?
>
> 6.4 For scripts and applets, ensure that event handlers are input
> device-independent. [Priority 2]
>
> 9.3 For scripts, specify logical event handlers rather than
> device-dependent
> event handlers. [Priority 2]
>
> Looks to me like just a little bit of redundancy. Aside from the
> presence or
> absence of the word "applets," these two checkpoints are saying
> essentially
> the same thing.
>
> 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)
From: ccims
Date: Mon, Aug 20 2001 6:18AM
Subject: Re: yet more questions
← Previous message | No next message
I did as well. I thought it might be done manually and would take a few
days.
Suzanne
EMAIL: = EMAIL ADDRESS REMOVED =
Candace Egan
< = EMAIL ADDRESS REMOVED = To: WebAIM forum
> < = EMAIL ADDRESS REMOVED = >
Sent by: WebAIM forum cc:
< = EMAIL ADDRESS REMOVED = Subject: Re: yet more questions
d.usu.edu>
08/17/2001 04:44 PM
Please respond to
WebAIM forum
Paul,
I subscribed to the digest version of the listserv, but am still getting
individual messages.
Candace
--
Candace Lee Egan
_________________________________________
Web Manager
Phone (559) 278-5070 Fax (559) 278-2436
California State University, Fresno
5241 N. Maple MS# TA49
Fresno, CA 93740-8027
= EMAIL ADDRESS REMOVED =