WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: JAWS / says "No clickable elements on page"

for

From: Tim Harshbarger
Date: Jun 7, 2018 1:34PM

When is JAWS giving you the "no clickable elements" message. Are you using the / (slash) hot key in virtual cursor mode?

If you are testing with JAWS you will want to use other keys to navigate and use the page. I think the only time I have ever used that keystroke myself is I need to find a page element that isn't one of the HTML 5 interactive elements (like links) or an element provided with an aria role and a tabindex. Basically a situation where someone attached a click event to an element and didn't do any of the other things that would make it accessible.

Thanks,
Tim



-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of Steve Green
Sent: Thursday, June 7, 2018 1:19 PM
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: [EXTERNAL] Re: [WebAIM] JAWS / says "No clickable elements on page"

This sounds like a massive accessibility issue, and not only for screen reader users. JAWS considers clickable elements to be links, buttons and elements with onClick event handlers - I don't think there's anything else.

I have encountered many websites where JAWS does not recognise one or more of the links or buttons, but never a website where it didn't recognise any. In the case of links, the cause is often the absence of an "href" attribute, which would also break keyboard navigability. In that case, adding href="javascript:void()" or href="#" usually fixes the issue.

Steve Green
Managing Director
Test Partners Ltd


-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of Lawrence Guros
Sent: 07 June 2018 18:35
To: <EMAIL REMOVED>
Subject: [WebAIM] JAWS / says "No clickable elements on page"

JAWS / says "No clickable element on page" - Does anyone know what JAWS considers a clickable element? There are many buttons, etc on the page.
We do use Knockout, so I think most of the event listeners are probably (speculating here) done with javascript element.addEventListener and not by having a click="someFunction()" in the DOM. Is that the issue? (but not under our control).

Is this an accessibility issue?

Thanks,
Larry