E-mail List Archives

Search E-mail List Archives for

Number of posts in this thread: 14 (In chronological order)

From: JP Jamous
Date: Tue, Sep 20 2016 8:47AM
Subject: The Famous Clickable Message
No previous message | Next 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?

From: Aaron Cannon
Date: Tue, Sep 20 2016 8:53AM
Subject: Re: The Famous Clickable Message
← Previous message | Next 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 ADDRESS 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?
>
> > > > >

From: Jonathan Avila
Date: Tue, Sep 20 2016 8:58AM
Subject: Re: The Famous Clickable Message
← Previous message | Next 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 ADDRESS 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 ADDRESS 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?

From: JP Jamous
Date: Tue, Sep 20 2016 10:14AM
Subject: Re: The Famous Clickable Message
← Previous message | Next 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 ADDRESS REMOVED = ] On Behalf Of Jonathan Avila
Sent: Tuesday, September 20, 2016 9:59 AM
To: WebAIM Discussion List < = EMAIL ADDRESS 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 ADDRESS 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 ADDRESS 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?

From: JP Jamous
Date: Tue, Sep 20 2016 10:16AM
Subject: Re: The Famous Clickable Message
← Previous message | Next message →

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 ADDRESS REMOVED = ] On Behalf Of Aaron Cannon
Sent: Tuesday, September 20, 2016 9:54 AM
To: WebAIM Discussion List < = EMAIL ADDRESS 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 ADDRESS 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
> >

From: Don Mauck
Date: Tue, Sep 20 2016 10:35AM
Subject: Re: The Famous Clickable Message
← Previous message | Next message →

I'm curious, does this mostly happen in Firefox?

-----Original Message-----
From: JP Jamous [mailto: = EMAIL ADDRESS REMOVED = ]
Sent: Tuesday, September 20, 2016 8:47 AM
To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
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?

From: Jonathan Avila
Date: Tue, Sep 20 2016 10:48AM
Subject: Re: The Famous Clickable Message
← Previous message | Next 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.

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 ADDRESS 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 ADDRESS 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 ADDRESS REMOVED = ] On Behalf Of Jonathan Avila
Sent: Tuesday, September 20, 2016 9:59 AM
To: WebAIM Discussion List < = EMAIL ADDRESS 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 ADDRESS 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 ADDRESS 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?

From: Birkir R. Gunnarsson
Date: Tue, Sep 20 2016 11:01AM
Subject: Re: The Famous Clickable Message
← Previous message | Next 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 ADDRESS 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 ADDRESS 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 ADDRESS 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 ADDRESS REMOVED = ] On Behalf
> Of Jonathan Avila
> Sent: Tuesday, September 20, 2016 9:59 AM
> To: WebAIM Discussion List < = EMAIL ADDRESS 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 ADDRESS 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 ADDRESS 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?
>
> > > http://webaim.org/discussion/archives
> > > > http://webaim.org/discussion/archives
> >
> > > http://webaim.org/discussion/archives
> > > > > >


--
Work hard. Have fun. Make history.

From: Jonathan Avila
Date: Tue, Sep 20 2016 11:08AM
Subject: Re: The Famous Clickable Message
← Previous message | Next message →

> 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 ADDRESS 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 ADDRESS 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 ADDRESS 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 ADDRESS 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 ADDRESS 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 ADDRESS REMOVED = ] On
> Behalf Of Jonathan Avila
> Sent: Tuesday, September 20, 2016 9:59 AM
> To: WebAIM Discussion List < = EMAIL ADDRESS 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 ADDRESS 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 ADDRESS 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.

From: Birkir R. Gunnarsson
Date: Tue, Sep 20 2016 11:31AM
Subject: Re: The Famous Clickable Message
← Previous message | Next 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 ADDRESS 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 ADDRESS 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 ADDRESS 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 ADDRESS 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 ADDRESS 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 ADDRESS 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 ADDRESS REMOVED = ] On
>> Behalf Of Jonathan Avila
>> Sent: Tuesday, September 20, 2016 9:59 AM
>> To: WebAIM Discussion List < = EMAIL ADDRESS 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 ADDRESS 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 ADDRESS 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.
> > > > >


--
Work hard. Have fun. Make history.

From: JP Jamous
Date: Tue, Sep 20 2016 11:46AM
Subject: Re: The Famous Clickable Message
← Previous message | Next 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 ADDRESS REMOVED = ] On Behalf Of Birkir R. Gunnarsson
Sent: Tuesday, September 20, 2016 12:32 PM
To: WebAIM Discussion List < = EMAIL ADDRESS 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 ADDRESS 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 ADDRESS 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 ADDRESS 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 ADDRESS 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 ADDRESS 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 ADDRESS 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 ADDRESS REMOVED = ] On
>> Behalf Of Jonathan Avila
>> Sent: Tuesday, September 20, 2016 9:59 AM
>> To: WebAIM Discussion List < = EMAIL ADDRESS 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 ADDRESS 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 ADDRESS 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.

From: JP Jamous
Date: Tue, Sep 20 2016 11:48AM
Subject: Re: The Famous Clickable Message
← Previous message | Next message →

Oh got you. I thought you meant opening the markup with Notepad or some other editor.

-----Original Message-----
From: WebAIM-Forum [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Jonathan Avila
Sent: Tuesday, September 20, 2016 11:49 AM
To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
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.

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 ADDRESS 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 ADDRESS 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 ADDRESS REMOVED = ] On Behalf Of Jonathan Avila
Sent: Tuesday, September 20, 2016 9:59 AM
To: WebAIM Discussion List < = EMAIL ADDRESS 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 ADDRESS 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 ADDRESS 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?

From: JP Jamous
Date: Tue, Sep 20 2016 11:49AM
Subject: Re: The Famous Clickable Message
← Previous message | Next message →

Nope. It is present in IE11 as well.

-----Original Message-----
From: WebAIM-Forum [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Don Mauck
Sent: Tuesday, September 20, 2016 11:36 AM
To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
Subject: Re: [WebAIM] The Famous Clickable Message

I'm curious, does this mostly happen in Firefox?

-----Original Message-----
From: JP Jamous [mailto: = EMAIL ADDRESS REMOVED = ]
Sent: Tuesday, September 20, 2016 8:47 AM
To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
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?

From: Don Mauck
Date: Tue, Sep 20 2016 12:01PM
Subject: Re: The Famous Clickable Message
← Previous message | No next message

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 ADDRESS REMOVED = ]
Sent: Tuesday, September 20, 2016 11:47 AM
To: WebAIM Discussion List < = EMAIL ADDRESS 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 ADDRESS REMOVED = ] On Behalf Of Birkir R. Gunnarsson
Sent: Tuesday, September 20, 2016 12:32 PM
To: WebAIM Discussion List < = EMAIL ADDRESS 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 ADDRESS 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 ADDRESS 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 ADDRESS 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 ADDRESS 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 ADDRESS 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 ADDRESS 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 ADDRESS REMOVED = ] On
>> Behalf Of Jonathan Avila
>> Sent: Tuesday, September 20, 2016 9:59 AM
>> To: WebAIM Discussion List < = EMAIL ADDRESS 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 ADDRESS 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 ADDRESS 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.