See the following JSFiddle http://jsfiddle.net/b2KDZ/1/ The example 2 should not announce clickable on the heading and the paragraph. The solution would be to suppress this behavior when the region contains naturally focusable elements and elements with appropriate ARIA roles and attributes. so this: <div> <h2>Heading</h2> <p>Text</p> <span class='fakebutton'>press</span> </div> Would announce clickable on everything, whereas these examples would not: <div> <h2>Heading</h2> <p>Text</p> <span class='fakebutton' role="button" tabindex="0">press</span> </div> <div> <h2>Heading</h2> <p>Text</p> <button>press</button> </div>
This report isn't actionable. Your examples aren't programmatically distinguishable from the anti-pattern. You're saying the span in this example shouldn't be announced as "clickable" even though this is a common problematic case: <div onclick="return delegate(event);"> <h2>Heading <span>x</span></h2> <p>Text</p> <button>press</button> </div> Our first responsibility is to our users, and the slight increase in verbosity (e.g. "clickable") when there is some ambiguous code results in a much better experience than the change you're asking for, which would make many real clickable elements undiscoverable and/or imperceivable.
Duping out to bug 133613: AX: Heuristic: Avoid exposing an element as clickable if mouse event delegation is handled on an element with any explicit ARIA role, including presentation.
*** This bug has been marked as a duplicate of bug 133613 ***