Closed Bug 865430 Opened 7 years ago Closed 7 years ago

Synthesized a11y mouse events are indistinguishable from physical mouse events.


(Core :: Disability Access APIs, defect)

Not set





(Reporter: eeejay, Assigned: eeejay)


(Blocks 1 open bug)



(1 file)

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 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
Attachment #741495 - Flags: review?(surkov.alexander)
Attachment #741495 - Flags: review+
Attachment #741495 - Flags: feedback?(marco.zehe)
Assignee: nobody → eitan
OS: Linux → All
Hardware: x86_64 → All
Blocks: 865452
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.
Attachment #741495 - Flags: feedback?(marco.zehe) → feedback+
Might change our mind if we later want to robot test.
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla23
You need to log in before you can comment on or make changes to this bug.