We'll need to think a little bit about which accessibility services on mash are implemented in chrome vs. in the window server. For example, stuff like big cursors, high contrast UI, etc. seem like window server features. I wonder if breaking the existing monolithic a11y delegate into smaller pieces would make it easier to convert.
We do have a new ui::mojom::AccessibilityManager (just for high contrast at the moment), but a lot of the existing functionality goes through ash/chrome's separate AccessibilityManager for access to profile preferences. I'm taking the approach of converting what we have, and I can make minor tweaks to that, but I'm avoiding a complex overhaul for now. Happy to discuss :)
Comment 1 by msw@chromium.org
, Oct 24 2016Labels: -Pri-3 Proj-Mustash-Mash Pri-2
Owner: msw@chromium.org
Status: Assigned (was: Untriaged)