WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: The Famous Clickable Message

for

From: Don Mauck
Date: Sep 20, 2016 12:01PM


I have always seen this a lot in Firefox, so I'm not surprised that it is worse than IE11.

-----Original Message-----
From: JP Jamous [mailto: <EMAIL REMOVED> ]
Sent: Tuesday, September 20, 2016 11:47 AM
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] The Famous Clickable Message

JAWS 17 does announce it with IE11. Just make sure to keep the default settings or press Insert + Space follows by Z.

It does read it more with FireFox though.

-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of Birkir R. Gunnarsson
Sent: Tuesday, September 20, 2016 12:32 PM
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] The Famous Clickable Message

The plot thickens.
I am seeing the same result as you.
NVDA announces clickable only on the parent div (and does it for all elements that have an onclick function or event listener).
In IE nothing is announced by Jaws.



On 9/20/16, Jonathan Avila < <EMAIL REMOVED> > wrote:
>> but is not announced if there is an event listener attached to the
>> div (see test document, hopefully attached).
>
> Birkir, only because you have a role of region. If you remove your
> role region then clickable is announced from addEventListener with
> JAWS in Firefox.
>
> Jonathan
>
> Jonathan Avila
> Chief Accessibility Officer
> SSB BART Group
> <EMAIL REMOVED>
> 703.637.8957 (Office)
>
> Visit us online: Website | Twitter | Facebook | Linkedin | Blog Check
> out our Digital Accessibility Webinars!
>
>
> -----Original Message-----
> From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On
> Behalf Of Birkir R. Gunnarsson
> Sent: Tuesday, September 20, 2016 1:02 PM
> To: WebAIM Discussion List
> Subject: Re: [WebAIM] The Famous Clickable Message
>
> "clickable" is announced if there is an actual onclick event assigned
> to the div, but is not announced if there is an event listener
> attached to the div (see test document, hopefully attached).
> In the region #1 div I explicitly add an onclick event.
> In the region #2 div I add an event listener that listens for a click
> and executes a function.
> Both clicks work fine (with a screen reader you can test this by
> pressing enter on any content in the regions, the scree readers
> simulate a click event and you will get a little prompt).
> It is not keyboard accessible I know, but that's ok for the purposes
> of this example).
>
> Quick test with Jaws and Firefox has every element in div 1 announced
> as "clickable" but not in region 2.
> There are more ways to attach click events to containers I have to
> take a closer lok when I have time (which is a preciou comodity).
> Feel free go ahead and build on this example.
> This will make for a good blog for www.bats.fyi (or somewhere else).
> Cheers
> -B
>
> On 9/20/16, Jonathan Avila < <EMAIL REMOVED> > wrote:
>>> No, I used Firebug and looked at the DOM body, head and even the
>>> HTML level. None of those exist. Bootstrap is used heavily so as
>>> JavaScript in the head. Yet, I was never able to find one event
>>> handler as I copied the code from Firebug.
>>
>> JP, that is what I am saying -- if the event was added with
>> addEventListener it won't show up in the DOM tree in FireBug.
>>
>> Jonathan
>>
>> Jonathan Avila
>> Chief Accessibility Officer
>> SSB BART Group
>> <EMAIL REMOVED>
>> 703.637.8957 (Office)
>>
>> Visit us online: Website | Twitter | Facebook | Linkedin | Blog Check
>> out our Digital Accessibility Webinars!
>>
>>
>> -----Original Message-----
>> From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On
>> Behalf Of JP Jamous
>> Sent: Tuesday, September 20, 2016 12:14 PM
>> To: 'WebAIM Discussion List'
>> Subject: Re: [WebAIM] The Famous Clickable Message
>>
>> No, I used Firebug and looked at the DOM body, head and even the HTML
>> level.
>> None of those exist. Bootstrap is used heavily so as JavaScript in
>> the head.
>> Yet, I was never able to find one event handler as I copied the code
>> from Firebug.
>>
>> I even tested with NVDA and it reports the same thing using Firefox.
>> I wish this clickable nightmare can be over.
>>
>> -----Original Message-----
>> From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On
>> Behalf Of Jonathan Avila
>> Sent: Tuesday, September 20, 2016 9:59 AM
>> To: WebAIM Discussion List < <EMAIL REMOVED> >
>> Subject: Re: [WebAIM] The Famous Clickable Message
>>
>>> 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.
>>
>> Event handlers can be added programmatically through addEventListener
>> and may not appear as attributes if you are just looking at the code.
>>
>> Jonathan
>>
>> Jonathan Avila
>> Chief Accessibility Officer
>> SSB BART Group
>> <EMAIL REMOVED>
>> 703.637.8957 (Office)
>>
>> Visit us online: Website | Twitter | Facebook | Linkedin | Blog Check
>> out our Digital Accessibility Webinars!
>>
>>
>> -----Original Message-----
>> From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On
>> Behalf Of JP Jamous
>> Sent: Tuesday, September 20, 2016 10:47 AM
>> To: 'WebAIM Discussion List'
>> Subject: [WebAIM] The Famous Clickable Message
>>
>> 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
>> >> >> >> archives at http://webaim.org/discussion/archives
>> >>
>> >> >> archives at http://webaim.org/discussion/archives
>> >> >> >> archives at http://webaim.org/discussion/archives
>> >>
>
>
> --
> Work hard. Have fun. Make history.
> > > archives at http://webaim.org/discussion/archives
> >


--
Work hard. Have fun. Make history.