WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: The Famous Clickable Message

for

From: Birkir R. Gunnarsson
Date: Sep 20, 2016 11:01AM

"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!
>
>
>