E-mail List Archives
Thread: Jaws Issue
Number of posts in this thread: 3 (In chronological order)
From: Kakarla Meharoon
Date: Mon, Mar 05 2018 2:56AM
Subject: Jaws Issue
No previous message | Next message →
Hi All,
In JAWS everything in the page is reading as clickable on mouse hover any
solution for this.
From: Josh Schroder
Date: Mon, Mar 05 2018 8:34AM
Subject: Re: Jaws Issue
← Previous message | Next message →
My advice would be to thoroughly inspect your HTML code as well as any associated JavaScript and try to isolate the problem through trial-and-error testing.
I've seen this behavior before when JavaScript event handlers are poorly written.
Josh Schroder
Web Administrator III
Office of Strategic Communication
Texas Department of Licensing and Regulation
(512) 936-8937
From: Philip Kiff
Date: Mon, Mar 05 2018 11:44AM
Subject: Re: Jaws Issue
← Previous message | No next message
There are a handful of similar threads you can find in WebAIM list
archives when you search the word "clickable". Here are a three snippets
of responses that I thought seemed helpful:
In a thread with the subject line "screen reader announcing clickable"
around Sept 14, 2016, Brandon Keith Biggs wrote:
> [...] The clickable element means that everything inside it will be
> clickable. It
> doesn't matter if anything is attached to it, it is clickable. I'm not
> sure
> if there is any way for a screen reader to recognize if something happens
> when an element is pressed, but I doubt it. If that clickable didn't show,
> a screen reader user would never know anything in that element was
> clickable.
> The only way to get rid of this is to just wrap the part that will get a
> click in a clickable div and remove the event from higher up the tree.
In a thread with the subect line "The Famous Clickable Message" around
Sept 20, 2016, Jonathan Avila wrote:
> Event handlers can be added programmatically through addEventListener
> and may not appear as attributes if you are just looking at the code.
And lastly, in a thread with the subject line "why is everything
"clickable" in NVDA" around May 26, 2017 Patrick H Lauke replied to Tim
Harshbarger::
> On 26/05/2017 09:45, Tim Harshbarger wrote:
>> Yes, if NVDA reports everything as clickable, it is most likely
>> because there is a click event associated with the body element.
> To expand a bit on this, that's most commonly found in certain
> JavaScript frameworks that use what's called "event delegation":
> instead of attaching lots of separate click handlers throughout the
> page, these frameworks rely on clicks bubbling up to the the body, and
> then disambiguate there which element was actually clicked ... so you
> have a single click handler that deals with every interaction on the
> page, rather than a myriad of tiny click handlers everywhere.
Phil.
Philip Kiff
D4K Communications
On 2018-03-05 10:34 AM, Josh Schroder wrote:
> My advice would be to thoroughly inspect your HTML code as well as any associated JavaScript and try to isolate the problem through trial-and-error testing.
>
> I've seen this behavior before when JavaScript event handlers are poorly written.
>
> Josh Schroder
> Web Administrator III
> Office of Strategic Communication
> Texas Department of Licensing and Regulation
> (512) 936-8937
>
>