865430 - Synthesized a11y mouse events are indistinguishable from physical mouse events.

Status: RESOLVED FIXED

(Core :: Disability Access APIs, defect)

Description

[Eitan Isaacson [:eeejay]]

This is a challenge in AccessFu where we need to intercept and cancel physical mouse and touch events. We need to let through mouse events that have been dispatched from nsIAccessible::doAction().

There are two options:
1. Create a new source in nsIDOMMouseEvent called MOZ_SOURCE_ACCESSIBILITY, and set mouse event sources to use it.
2. Set mouse event sources to MOZ_SOURCE_UNKNOWN. This is the convention used for scripted mouse events.

I think option 2 is good enough for now, since this is technically a scripted click.

Comment 1

[Eitan Isaacson [:eeejay]]

Attachment: Give dispatched mouse events from a11y an unkown input source.

Comment 2

[alexander :surkov (:asurkov)]

Comment on attachment 741495 [details] [diff] [review]
Give dispatched mouse events from a11y an unkown input source.

Review of attachment 741495 [details] [diff] [review]:
-----------------------------------------------------------------

So you want to ignore it in AccessFu then unknown should work, I hope core doesn't process mouse source events differently.

Marco, it'd be good to have a testing of accessible actions

Comment 3

[Marco Zehe (:MarcoZ)]

Comment on attachment 741495 [details] [diff] [review]
Give dispatched mouse events from a11y an unkown input source.

f=me. This doesn't look like it's breaking screen reader interactions. I tested clickables, links, form field focusing from a screen reader etc., and all still work as expected.

Comment 4

[David Bolter [:davidb] (NeedInfo me for attention)]

Might change our mind if we later want to robot test.

Comment 5

[Eitan Isaacson [:eeejay]]

https://hg.mozilla.org/integration/mozilla-inbound/rev/2f3ddbc27bfa

Comment 6

[Ryan VanderMeulen [:RyanVM]]

https://hg.mozilla.org/mozilla-central/rev/2f3ddbc27bfa