E-mail List Archives

Search E-mail List Archives for

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

From: Joseph Sherman
Date: Thu, Jun 30 2016 2:11PM
Subject: clickable clickable clickable
No previous message | Next message →

I'm looking at a page with NVDA. When I use Chrome or IE it works fine. But when I use FireFox, it keeps saying "clickable clickable" etc. for every element including text. It looks like every element including <p> has an event handler for onclick from yoshki library?

Joseph

From: Jonathan Cohn
Date: Mon, Jul 04 2016 1:39PM
Subject: Re: clickable clickable clickable
← Previous message | Next message →

One of my web developers created a login page with exactly that behaviour. I don't believe we were able to resolve the issue, and it was not just NVDA but also JAWS that saw the Headers and plain text as clickable items.

I don't know if we found a specific cause of the clickable being declared.

Best wishes,

Jonathan Cohn



> On 30 Jun 2016, at 16:11, Joseph Sherman < = EMAIL ADDRESS REMOVED = > wrote:
>
> I'm looking at a page with NVDA. When I use Chrome or IE it works fine. But when I use FireFox, it keeps saying "clickable clickable" etc. for every element including text. It looks like every element including <p> has an event handler for onclick from yoshki library?
>
> Joseph
>
> > > >

From: Lucy Greco
Date: Tue, Jul 05 2016 11:53AM
Subject: Re: clickable clickable clickable
← Previous message | Next message →

i offen see pages that do this with jaws for no reason but nvda only does
this when there is a on click event

Lucia Greco
Web Accessibility Evangelist
IST - Architecture, Platforms, and Integration
University of California, Berkeley
(510) 289-6008 skype: lucia1-greco
http://webaccess.berkeley.edu
Follow me on twitter @accessaces


On Mon, Jul 4, 2016 at 12:39 PM, Jonathan Cohn < = EMAIL ADDRESS REMOVED = > wrote:

> One of my web developers created a login page with exactly that behaviour.
> I don't believe we were able to resolve the issue, and it was not just NVDA
> but also JAWS that saw the Headers and plain text as clickable items.
>
> I don't know if we found a specific cause of the clickable being declared.
>
> Best wishes,
>
> Jonathan Cohn
>
>
>
> > On 30 Jun 2016, at 16:11, Joseph Sherman < = EMAIL ADDRESS REMOVED = >
> wrote:
> >
> > I'm looking at a page with NVDA. When I use Chrome or IE it works fine.
> But when I use FireFox, it keeps saying "clickable clickable" etc. for
> every element including text. It looks like every element including <p> has
> an event handler for onclick from yoshki library?
> >
> > Joseph
> >
> > > > > > > > >
> > > > >

From: Dominic Capuano (gmail)
Date: Wed, Jul 06 2016 7:06AM
Subject: Re: clickable clickable clickable
← Previous message | No next message

Jonathon;

This sounds similar to a defect that I found with Adobe Captivate.

When you read an HTML5 page produced by Adobe Captivate using either JAWS or
NVDA you hear the word "Clickable" at the end of each line regardless of
whether the line's content is clickable.

This happens because the entire screen is clickable. All of the content is
contained within an element called "div_Slide" which has on it an "onClick"
JavaScript event. Everything on the screen, (headings, text, etc.), is
considered by any browser to be a child of div_Slide and therefore
clickable.

As an example if you click on a heading which you consider to be not
clickable you are actually clicking on div_Slide which may not or may not
actually do something.

Dominic Capuano
= EMAIL ADDRESS REMOVED =
(h)(401) 726-2551