There is sometimes a false violation here, in that sometimes an onclick handler is placed on parent container elements of regular
page regions, so as to track clicks for statistic gathering purposes, but the onclick has no other purpose but to do this.
So in such cases this handler is falsely being flagged as an issue when there really isn't one.
-----Original Message-----
From: Jonathan Avila [mailto:jon.avila@ssbbartgroup.com]
Sent: Thursday, December 17, 2015 1:25 PM
To: Wayne Dick <waynedick@knowbility.org>
Cc: Patrick H. Lauke <redux@splintered.co.uk>; 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.
Jon
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