WebAIM - Web Accessibility In Mind

E-mail List Archives

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

for

From: Lawrence Guros
Date: Jun 8, 2018 1:14PM

OK, here is an HTML example button created with our Knockout based
single page infrastructure. This is back to Client-Server technology,
with the client written in Javascript and javascript based technologies.

In many cases, we do not have direct access to modifying the HTML directly.

We do have accessibility toolbars build into a browser that test many
things, including color contrast, HTML, alt-text, aria-labels, ids...
Keyboard testing showed only a few issues that were fixed, so we can
access anything in the page from the keyboard, including popups and the
like.

I should also state, that our test person is just starting out in JAWS,
and I am not sure if he was in "Virtual Cursor Mode". I have asked. He
is able to navigate the page using tabs in JAWS. (We are only doing the
screenreader testing with JAWS). I am pretty much a neophyte with screen
readers, just a developer that wants to make sure it is done right.

I will check if there is a page on the open internet that can be
accessed for free.

Here is a sample of a button that was grabbed from Chrome. I would
expect the "click" data-binding would result in a javascript
element.addEventListener() to catch the click. In Chrome, there are
click event listeners listed, but not as attributes. Looks like JQuery
may be involved, as there are some event handlers in some Jquery
attributes.  Will have to dig more.

<button id="hamburgerButton" class="emaas-appheader-hamburger-button
emaas-appheader-toolbar-button oj-button-jqui oj-button oj-component
oj-enabled oj-default oj-button-half-chrome oj-button-icon-only
oj-component-initnode" data-bind="ojComponent: {component:'ojButton',
display:'icons', chroming: 'half',
                                label: hamburgerBtnLabel, disabled:
!renderHamburgerMenu,
                                icons: {start: 'fa-icon-font fa-bars'}},
                    click: renderHamburgerMenu ? toggleHamburgerMenu :
null, attr: {title: hamburgerBtnLabel}" role="button" tabindex="0"
aria-labelledby="ui-id-1" title="OMC Navigation"><div
class="oj-button-label"><span class="oj-button-icon oj-start
fa-icon-font fa-bars"></span><span class="oj-button-text
oj-helper-hidden-accessible" id="ui-id-1">OMC
Navigation</span></div></button>

Thanks for the responses!
Larry

Subject:
Re: [WebAIM] JAWS / says "No clickable elements on page"

From:
"Patrick H. Lauke" < <EMAIL REMOVED> >
Date:
6/7/2018 3:23 PM

To:
<EMAIL REMOVED>


On 07/06/2018 18:35, Lawrence Guros wrote:
> 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?

For reference: without providing a reduced test case, a live URL, or
even just an extract of the markup/DOM, it's always difficult to
diagnose this sort of thing.

Also...just JAWS? Which browser? Have you tried other browser/AT
combinations? Do they all report things the way you expect, and it's
only JAWS that's misbehaving?

P
--
Patrick H. Lauke

twitter: @patrick_h_lauke | skype: patrick_h_lauke


Re: [WebAIM] JAWS / says "No clickable elements on page".eml

Subject:
Re: [WebAIM] JAWS / says "No clickable elements on page"
From:
Tim Harshbarger < <EMAIL REMOVED> >
Date:
6/7/2018 3:34 PM

To:
WebAIM Discussion List < <EMAIL REMOVED> >


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