New issue
Advanced search Search tips

Issue 648752 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner: ----
Closed: Aug 14
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocking:
issue 557399



Sign in to add a comment

Login UI - Need unified Accessibility Manager

Project Member Reported by jonr...@chromium.org, Sep 20 2016

Issue description

The CoreOobeHandler provides accessibility support via chrome/browser/chromeos/accessibility/accessibility_manager.h
 which has direct ties to the ash::Shell.

When running in mash there is no shell instance.

Alternative work has been done with services/ui/ws/accessibility_manager.h

For login on mash we need to determine the best way to unify these, or get them communicating so that login can support accessibility.

 
Labels: Proj-Mustash
Components: Internals>MUS
Project Member

Comment 3 by sheriffbot@chromium.org, Oct 5 2017

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Components: -Internals>MUS Internals>Services>WindowService
Components: -MUS
Status: Fixed (was: Untriaged)
AccessibilityManager has been mostly ported to mash. We have separate bugs for the remaining items.

Sign in to add a comment