WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: The Famous Clickable Message

for

From: JP Jamous
Date: Sep 20, 2016 10:16AM

Aaron,

I did search for the word Click since the markup was too long. I did find a few, but I was too busy to investigate those.

Thank you for this warning as I am not familiar with JQuery. I will check this out much deeper this weekend.

-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of Aaron Cannon
Sent: Tuesday, September 20, 2016 9:54 AM
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] The Famous Clickable Message

How did you verify that no elements in the DOM have onclick or similar? If you only browsed the attributes on the elements, you could have missed one or more.

For instance, if you do something like the following with jQuery:

$(body).click(clickHandlerFunction);

That will add a click handler to the body tag, but won't place an onclick attribute on the body element in the DOM inspector. At least this is how it was when I last checked a few years ago.

Other events that respond to clicks are the mousedown and mouseup events, so technically they could be picked up by a screen reader as well, but I'm not sure if they are.

Aaron

On 9/20/16, JP Jamous < <EMAIL REMOVED> > wrote:
> Okay folks,
>
>
>
> This has gotten me stumped here. I have the whole DOM of multiple
> pages and neither one has onclick or onmouseover. Yet, JAWS 17 is
> announcing Clickable after static text.
>
>
>
> What other DOM elements could make JAWS or NVDA announce Clickable
> besides the above?
>
> > > archives at http://webaim.org/discussion/archives
> >