WebAIM - Web Accessibility In Mind

E-mail List Archives

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

for

From: Isabel Holdsworth
Date: Oct 4, 2018 4:17AM

Hi Lawrence,

IMHO it's important that anyone who is expected to carry out AT
testing with reliable results is familiar with the tools they are
testing with. It might be worth arranging some JAWS training for your
tester.

Cheers, Isabel

On 04/10/2018, Mohith BP < <EMAIL REMOVED> > wrote:
> Hi Lawrence,
>
> JAWS just reading "no clickable elements on the page" is not a real
> accessibility issue as long as the elements are structured
> appropriately and actionable with keyboard / touch.
> JAWS considers the following as actionable element:
> "/ moves the virtual cursor to the next element with an onclick handler
> JAWS only indicates the presence of the OnClick attribute for HTML
> elements that are not usually clickable. Press ENTER on the clickable
> element to perform an action or follow a link. "
>
> As you mentioned that the QA person has just begun to use JAWS try
> using Insert + F3 for elements list and ensure the elements are listed
> in one of the category such as link / form elements appropriately.
>
> Please ensure the keyboard accessibility is tested with and without
> screen reader.
> If you are building custom click / action functions ensure that the
> keypress / keydown events activate elements only for Enter & Spacebar.
>
> I am sorry for putting the random things. However, these are the few
> common issues seen on a daily basis regard to keyboard accessibility.
>
>
> Thanks & Regards,
> Mohith B. P.
>
> On 6/7/18, Lawrence Guros < <EMAIL REMOVED> > 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?
>>
>> Thanks,
>> Larry
>>
>> >> >> >> >>
> > > > >