Eitan Isaacson [:eeejay] Reporter
	Description • 10 years ago

I would expect it to behave like any other inline element. But instead it seems like it does not get an attributed action.
This manifests differently in two cases:

1. A standalone img[role=button] remains with an action count of 0. In contrast, a standalone span[role=button] gets an action 'press'.

(the more realistic problem)
2. An img[role=button] that is a descendant of a container with a click listener behaves like a LinkableAccessible, and inherits the actions of the ancestor. In the meantime, a similar ancestored span[role=button] will get an action of 'press', and the target of the DOM click event will be the span.

I think this is all due to the fact that ImageAccessible is considered a leaf and is a subclass of LinkableAccessible, while span is not.

	alexander :surkov (:asurkov)
	Comment 2 • 10 years ago

It's because LinkableAccessible never falls back into Accessible which provides ARIA support, ActionCount and ActionNameAt methods should be fixed.

	Eitan Isaacson [:eeejay] Reporter
	Comment 3 • 10 years ago

(In reply to alexander :surkov from comment #2)
> It's because LinkableAccessible never falls back into Accessible which
> provides ARIA support, ActionCount and ActionNameAt methods should be fixed.

and DoAction.

	alexander :surkov (:asurkov)
	Comment 4 • 10 years ago

DoAction seems flexible enough to work, I wouldn't swear on it though.