WebAIM - Web Accessibility In Mind

E-mail List Archives

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

for

From: Laken Hafner
Date: Jun 7, 2018 1:19PM

In addition to what Steve pointed out, JAWS also takes into account focusable elements too. When you say that you have "buttons," are they native HTML buttons? If they're created with something like a div that has click events, JAWS probably won't detect that, nor will any keyboard-only user be able to use that page unless it has a tabindex attribute. Quickest way to check is to see if you can use the button and get to it by using your keyboard's TAB key only, without touching your mouse.

--
  Laken Hafner

On Thu, Jun 7, 2018, at 2:19 PM, Steve Green wrote:
> 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
>
> > > at http://webaim.org/discussion/archives
> > > > >