E-mail List Archives
Re: Keyboard behavior with JAWS
From: Jonathan Avila
Date: Aug 24, 2015 7:46AM
- Next message: Jonathan Avila: "Re: (off list)WebAIM-Forum Digest, Vol 125, Issue 19"
- Previous message: Jon Metz: "Re: WCAG Extensions"
- Next message in Thread: _mallory: "Re: Keyboard behavior with JAWS"
- Previous message in Thread: Léonie Watson: "Re: Keyboard behavior with JAWS"
- View all messages in this Thread
> Jaws/NVDA in browse mode activate the element's onclick event when enter is pressed with focus on that element (not the onKey events). In application/forms mode howver, the onKey events are triggered when user presses enter.
Correct, and as an FYI to new people -- for other elements (not buttons and anchors) such as divs, adding an onlick and tabindex is not enough to provide keyboard access -- an author would need an onlick and keyboard event handlers to support both the click from a screen reader in browse mode and keyboard access.
Jonathan
--
Jonathan Avila
Chief Accessibility Officer
SSB BART Group
<EMAIL REMOVED>
703-637-8957 (o)
Follow us: Facebook | Twitter | LinkedIn | Blog | Newsletter
- Next message: Jonathan Avila: "Re: (off list)WebAIM-Forum Digest, Vol 125, Issue 19"
- Previous message: Jon Metz: "Re: WCAG Extensions"
- Next message in Thread: _mallory: "Re: Keyboard behavior with JAWS"
- Previous message in Thread: Léonie Watson: "Re: Keyboard behavior with JAWS"
- View all messages in this Thread