E-mail List Archives
Re: What makes screen-readers say "clickable"?
From: Lynn Holdsworth
Date: Apr 7, 2015 9:59AM
- Next message: Cliff Tyllick: "Re: semantics for an A-Z index"
- Previous message: Steve Faulkner: "Re: What makes screen-readers say "clickable"?"
- Next message in Thread: None
- Previous message in Thread: Steve Faulkner: "Re: What makes screen-readers say "clickable"?"
- View all messages in this Thread
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 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 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
>> >> >> >> >>
> > > > >
- Next message: Cliff Tyllick: "Re: semantics for an A-Z index"
- Previous message: Steve Faulkner: "Re: What makes screen-readers say "clickable"?"
- Next message in Thread: None
- Previous message in Thread: Steve Faulkner: "Re: What makes screen-readers say "clickable"?"
- View all messages in this Thread