E-mail List Archives

Search E-mail List Archives for

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

From: Gijs Veyfeyken
Date: Tue, May 27 2014 1:47AM
Subject: VoiceOver clickable
No previous message | Next message →

Hi,

VoiceOver (version 6.0 on OSX 10.9.3) frequently announces elements as "clickable" while there is no reason to do so in the HTML.
Could anyone tell me what triggers this behaviour? I'm guessing JavaScript but I can't put my finger on it.
Live example: http://www.gelijkekansen.be/.
The telephone and fax number in the footer are announced as "clickable", same goes for everything inside the Twitter sidebar.

Thanks,

Gijs

---
Gijs Veyfeyken
AnySurfer - towards an accessible internet
http://www.anysurfer.be/en
Brussels - Belgium

From: Humbert, Joseph A
Date: Tue, May 27 2014 6:36AM
Subject: Re: VoiceOver clickable
← Previous message | Next message →

I'm guessing that it is a bug with VoiceOver. iOS and "Mobile" VoiceOver support "tel" URL scheme (https://developer.apple.com/library/ios/featuredarticles/iPhoneURLScheme_Reference/PhoneLinks/PhoneLinks.html). Based on you're the way the text is coded VoiceOver may be thinking that the text is a "mobile" telephone link.

Sincerely,
Joe

From: Gijs Veyfeyken
Date: Wed, May 28 2014 3:54AM
Subject: Re: VoiceOver clickable
← Previous message | Next message →

@Joe: the tel URL scheme is not used in the websites where I've encountered this problem and it's only supported on iOS. So that's not it.

Here's the answer from Apple's accessibility team:

> Hello,
> Thank you for your email. VO speaks “clickable” when there’s a click or other mouse event on items that are not normally associated with “clicking.”
> Items usually associated with clicking have roles like link, button, etc.
>
> To avoid it, pick an appropriate role for the element, or use event delegation on the body element.
>
> Apple Accessibility

From: Jon Avila
Date: Wed, May 28 2014 5:06AM
Subject: Re: VoiceOver clickable
← Previous message | No next message

> To avoid it, pick an appropriate role for the element, or use event delegation on the body element.

Somewhere up the chain of elements there must be an element that has a cluck event associated to it. This may be set programmatically rather than through inline. This issue is common with Windows screen readers but they have become better about filtering irrelevant or duplicate clickable events.

Jonathan

> On May 28, 2014, at 5:54 AM, Gijs Veyfeyken < = EMAIL ADDRESS REMOVED = > wrote:
>
> To avoid it, pick an appropriate role for the element, or use event delegation on the body element.