W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > October to December 2015

RE: The clickable problem

From: Sean Murphy (seanmmur) <seanmmur@cisco.com>
Date: Thu, 17 Dec 2015 21:42:16 +0000
To: Jonathan Avila <jon.avila@ssbbartgroup.com>, Wayne Dick <waynedick@knowbility.org>
CC: "Patrick H. Lauke" <redux@splintered.co.uk>, "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
Message-ID: <9d46b3ca317e44408b369d7ef29c36c8@XCH-RCD-001.cisco.com>
I have seen this issue mainly in Firefox on the windows platform with Jaws for Windows and I recall NVDA. The sites I have seen it on reported elements that were not clickable. Thus I always wrote it up as an comms issue with the browser and screen reader.

Sean Murphy
-----Original Message-----
From: Jonathan Avila [mailto:jon.avila@ssbbartgroup.com] 
Sent: Friday, 18 December 2015 8:25 AM
To: Wayne Dick
Cc: Patrick H. Lauke; w3c-wai-ig@w3.org
Subject: Re: The clickable problem

This is an issue that it might be worth getting WCAG WG consensus on.  Anything that is interactive must have a role and an appropriate one.  Items that don't will fail 4.1.2.   Screen readers speaking clickable on content without roles are doing that to alert users to an action on something that may not be correctly exposing a role - compensating for bad coding.  


Sent from my iPhone

> On Dec 17, 2015, at 3:46 PM, Wayne Dick <waynedick@knowbility.org> wrote:
> I am finding the clickable problem frequently on pages that pass WCAG 2.0 at level AA.  How common is this? How do you advise clients on this issue?  Is it an AT bug? How do you code around it? We advise to limit the scope of clickable regions, but the problems seem very difficult to track down.
> Wayne
Received on Thursday, 17 December 2015 21:42:48 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 17 December 2015 21:42:48 UTC