WebAIM - Web Accessibility In Mind

E-mail List Archives

Thread: why is everything "clickable" in NVDA

for

Number of posts in this thread: 10 (In chronological order)

From: Angela French
Date: Thu, May 25 2017 10:49AM
Subject: why is everything "clickable" in NVDA
No previous message | Next message →

Hello,
I am an NVDA newbie. I am trying to evaluate a web application where I work. Why is it that NVDA (using Chrome) says "clickable" in front of everything it reads whether it is an actionable item (such as a link) or not? It's driving me crazy.



Angela French
Internet/Intranet Specialist
Washington State Board for Community and Technical Colleges
360-704-4316
= EMAIL ADDRESS REMOVED = <mailto: = EMAIL ADDRESS REMOVED = >
www.sbctc.edu<;http://www.sbctc.edu/>;

From: Jeremy Echols
Date: Thu, May 25 2017 1:27PM
Subject: Re: why is everything "clickable" in NVDA
← Previous message | Next message →

I can't speak to your setup of course, but when I've used it with Firefox I have had a fair amount of success.

Can you share the site you're testing? It may be that things are mislabeled (role="button" and similar issues).

From: Beranek, Nicholas
Date: Thu, May 25 2017 1:36PM
Subject: Re: why is everything "clickable" in NVDA
← Previous message | Next message →

I've noticed the accessible state being revealed as 'clickable- when there is an 'on click- JavaScript event handler on the BODY element. You may also have an element relying on device-dependent handlers such as a mouse click to operate the control without having the proper accessible role associated with the control.

--
Nick Beranek
Digital Accessibility Team

On 5/25/17, 3:27 PM, "WebAIM-Forum on behalf of Jeremy Echols" < = EMAIL ADDRESS REMOVED = on behalf of = EMAIL ADDRESS REMOVED = > wrote:

I can't speak to your setup of course, but when I've used it with Firefox I have had a fair amount of success.

Can you share the site you're testing? It may be that things are mislabeled (role="button" and similar issues).

From: Angela French
Date: Thu, May 25 2017 2:05PM
Subject: Re: why is everything "clickable" in NVDA
← Previous message | Next message →

It is an internal application so I can't share the URL. I will try other browsers and see if I get a different set of results.

Angela

From: Jeremy Echols
Date: Thu, May 25 2017 2:52PM
Subject: Re: why is everything "clickable" in NVDA
← Previous message | Next message →

Hmm... is there any way to save a sample page's HTML, or is there sensitive information (or other barriers to sharing it)?

I wouldn't mind giving my setup a shot if you're at liberty to share.

From: Tim Harshbarger
Date: Fri, May 26 2017 2:45AM
Subject: Re: why is everything "clickable" in NVDA
← Previous message | Next message →

Yes, if NVDA reports everything as clickable, it is most likely because there is a click event associated with the body element.

I know that both JAWS and NVDA will report that items are clickable. I suspect that is intended to help on web pages where developers attach click events to divs and spans. Unfortunately, there are pages where the click event is attached to the body element which ends up causing NVDA to report it on every element.

You can tell NVDA to stop reporting that information. In Document Formatting (under Preferences,) there is a checkbox labelled clickable. If you uncheck that checkbox NVDA won't report that information anymore.

When I am using NVDA for personal use (not to test web pages), I typically turn off that feature since I don't think it really helps all that much and hearing "clickable" along with every element on the page makes it a bit harder to listen to the page since I have to constantly mentally filter out that information.

From: Patrick H. Lauke
Date: Fri, May 26 2017 3:06AM
Subject: Re: why is everything "clickable" in NVDA
← Previous message | Next message →

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.

P
--
Patrick H. Lauke

www.splintered.co.uk | https://github.com/patrickhlauke
http://flickr.com/photos/redux/ | http://redux.deviantart.com
twitter: @patrick_h_lauke | skype: patrick_h_lauke

From: Jonathan C. Cohn
Date: Fri, May 26 2017 5:02AM
Subject: Re: why is everything "clickable" in NVDA
← Previous message | Next message →

Oh, and I believe NBDA has an open bug on this. One just needs to find an appropriate heuristic for when to announce.

Best wishes,

Jonathan Cohn

> On May 26, 2017, at 5:06 AM, Patrick H. Lauke < = EMAIL ADDRESS REMOVED = > wrote:
>
>> 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.
>
> P
> --
> Patrick H. Lauke
>
> www.splintered.co.uk | https://github.com/patrickhlauke
> http://flickr.com/photos/redux/ | http://redux.deviantart.com
> twitter: @patrick_h_lauke | skype: patrick_h_lauke
> > > >

From: Joy Relton
Date: Fri, May 26 2017 7:06AM
Subject: Re: why is everything "clickable" in NVDA
← Previous message | Next message →

"heuristic" Great description of a more level headed approach to problems. I also like the information about unchecking the box in the settings. Often, although not always, there is a similar solution. I hadn't seen this word used before, so I learned something new today. Thank you Jonathan.

From: Angela French
Date: Fri, May 26 2017 9:58AM
Subject: Re: why is everything "clickable" in NVDA
← Previous message | No next message

Thanks for all the helpful replies. The first element in our create account form is "username". Upon exit from that element we run a check to see if that username is available. There is javascript involved in this functionality and that is what is causing the clickable . Not sure what we can do about that, but at least I know how to turn off the reading of it when I listed.

Angela French
SBCTC.edu