A couple years ago the mustash team in WAT ported the a11y autoclick feature to work as an out-of-process mojo app. It's similar to the way the keyboard shortcut viewer app works. It runs in its own process, opens a views::Widget to draw a circle around the cursor, and calls a one-off mojo API in our window service code to inject a click.
The idea was to demonstrate that a11y features could be a separate app. However, we never shipped this, as it was dependent on window service APIs that were only available when ash ran fully out-of-process.
We've recently shipped enough of the window service APIs that the autoclick app *could* be shipped. However, it isn't a priority for the mustash team -- we've got our hands full with keyboard shortcut viewer, out-of-process ash, and other stuff.
The autoclick code in ash is now kind of awkward -- it's split into multiple components, regular ash + mojo app + common code. It would be simpler to just keep the regular ash version and unfork it. If the a11y team in the future wanted to ship an a11y app they could copy the structure of either the tap_visualizer app or the keyboard shortcut viewer app, which the mustash team is supporting.
Comment 1 by jamescook@chromium.org
, Aug 21