E-mail List Archives
Thread: What makes screen-readers say "clickable"?
Number of posts in this thread: 5 (In chronological order)
From: Carin Headrick
Date: Tue, Apr 07 2015 5:14AM
Subject: What makes screen-readers say "clickable"?
No previous message | Next message →
Hi. I don't know if this is readily discoverable, but I figured I'd ask.
So many times, JAWS or NVDA will come upon an element and say it's
clickable when there is nothing clickable about it. What exactly is it
picking up on? Are they both picking up on the same thing, or do they
each have their own set of criteria for saying something is clickable?
If anybody has any ideas, that would be awesome.
Thanks,
Carin
From: Lynn Holdsworth
Date: Tue, Apr 07 2015 5:33AM
Subject: Re: What makes screen-readers say "clickable"?
← Previous message | Next message →
Hi Karen,
Yes, screenreaders use different criteria for deciding which elements are clickable. VoiceOver, for example, considers an element to be clickable if it or any of its ancestors has an OnClick event handler attached.
Best, Lynn
> On 7 Apr 2015, at 12:14, Carin Headrick < = EMAIL ADDRESS REMOVED = > wrote:
>
> Hi. I don't know if this is readily discoverable, but I figured I'd ask.
>
> So many times, JAWS or NVDA will come upon an element and say it's clickable when there is nothing clickable about it. What exactly is it picking up on? Are they both picking up on the same thing, or do they each have their own set of criteria for saying something is clickable?
>
> If anybody has any ideas, that would be awesome.
>
> Thanks,
>
> Carin
> > > >
From: Moore,Michael (DARS)
Date: Tue, Apr 07 2015 5:48AM
Subject: Re: What makes screen-readers say "clickable"?
← Previous message | Next message →
The clickable ancestor leads to an interesting side effect with modern JavaScript development practices. Frequently an OnClick event handler is added to the body element so that the script will pick up a click anywhere on the page and be able to process it. Now the screen reader sees everything as clickable, which leads to a lot of extra noise.
Mike Moore
Accessibility Coordinator,
Texas Department of Assistive and Rehabilitative Services
(512) 424-4159 (Office)
(512) 574-0091 (Cell)
From: Steve Faulkner
Date: Tue, Apr 07 2015 7:23AM
Subject: Re: What makes screen-readers say "clickable"?
← Previous message | Next message →
related twitter threads may be of interest:
https://twitter.com/vick08/status/584829902190292993
https://twitter.com/vick08/status/584221768740577280
--
Regards
SteveF
HTML 5.1 <http://www.w3.org/html/wg/drafts/html/master/>;
On 7 April 2015 at 12:14, Carin Headrick < = EMAIL ADDRESS REMOVED = > wrote:
> Hi. I don't know if this is readily discoverable, but I figured I'd ask.
>
> So many times, JAWS or NVDA will come upon an element and say it's
> clickable when there is nothing clickable about it. What exactly is it
> picking up on? Are they both picking up on the same thing, or do they each
> have their own set of criteria for saying something is clickable?
>
> If anybody has any ideas, that would be awesome.
>
> Thanks,
>
> Carin
> > > > >
From: Lynn Holdsworth
Date: Tue, Apr 07 2015 9:59AM
Subject: Re: What makes screen-readers say "clickable"?
← Previous message | No next message
Thanks Steve. I've been involved in endless (sometimes rather heated)
discussions on this topic, and I can understand both sides of the
argument. I guess giving users the ability to turn off the "clickable"
announcement might strike some sort of vaguely happy medium.
Best, Lynn
On 07/04/2015, Steve Faulkner < = EMAIL ADDRESS REMOVED = > wrote:
> related twitter threads may be of interest:
>
> https://twitter.com/vick08/status/584829902190292993
> https://twitter.com/vick08/status/584221768740577280
>
> --
>
> Regards
>
> SteveF
> HTML 5.1 <http://www.w3.org/html/wg/drafts/html/master/>;
>
> On 7 April 2015 at 12:14, Carin Headrick < = EMAIL ADDRESS REMOVED = > wrote:
>
>> Hi. I don't know if this is readily discoverable, but I figured I'd ask.
>>
>> So many times, JAWS or NVDA will come upon an element and say it's
>> clickable when there is nothing clickable about it. What exactly is it
>> picking up on? Are they both picking up on the same thing, or do they each
>> have their own set of criteria for saying something is clickable?
>>
>> If anybody has any ideas, that would be awesome.
>>
>> Thanks,
>>
>> Carin
>> >> >> >> >>
> > > > >