Leslie, can you please: 

* post a screenshot of what this row looks like
* describe what the tooltip for that row is
* describe what ChromeVox reads out

?

Currently, when the user hovers over the battery icon to the right of "Nexus 6", a tooltip shows the percentage of battery remaining on the host device. (In this case, it shows "100%" because the phone is plugged in and fully charged.)

Deleted: Screenshot 2017-07-25 at 11.23.33 AM.png 49.4 KB

	Screenshot 2017-07-25 at 11.23.33 AM.png 49.4 KB View Download

The whole row is focusable but the icons and text are not, and this is what ChromeVox reads when the row is in focus.

Deleted: Screenshot 2017-07-25 at 11.24.24 AM.png 3.0 KB

	Screenshot 2017-07-25 at 11.24.24 AM.png 3.0 KB View Download

Thanks for clarifying. I think the easiest solution here would be to set the focus behavior of the battery icon view to be ACCESSIBLE_ONLY (see the FocusBehavior enum in view.h). That will make the battery icon view tab-accessible only while ChromeVox is enabled, which means that the charge percentage will be read out. The tab ordering when ChromeVox is not enabled will remain unchanged.

If I set the focus behavior to be ACCESSIBLE_ONLY it still skips over the battery icon when I'm tabbing through while ChromeVox is enabled. But if I set it it ALWAYS, then I can tab to the icon. 

Deleted: Screenshot 2017-07-27 at 6.14.24 PM.png 854 KB

	Screenshot 2017-07-27 at 6.14.24 PM.png 854 KB View Download

ACCESSIBLE_ONLY doesn't seem to have any logic associated with it-- tdanderson is following up with dtseng regarding this.

In the meantime, the CL to fix this is https://chromium-review.googlesource.com/c/592447/

dtseng@, do you have any insight into ACCESSIBLE_ONLY not working as intended and/or any suggestions of how to make an element focusable /only/ when ChromeVox is enabled?

An alternate (though more complicated) idea if this approach doesn't work out could be to try and make the accessible text and/or tooltip of the entire row be "<device name> <battery information>".

ACCESSIBLE_ONLY was only implemented for OS X (see https://codereview.chromium.org/1894383002/patch/340001/350052) 

The options now seem to be:
a) Implement ACCESSIBLE_ONLY for CrOS, or 
b) Do the workaround that Terry suggested

I think (may be wrong) FocusBehavior doesn't have anything to do with this. Probably you should be looking at things like AX_STATE_FOCUSABLE (https://cs.chromium.org/chromium/src/out/Debug/gen/ui/accessibility/ax_enums.h?sq=package:chromium&dr=CSs&l=242). Adding some people who might have more context.

Downgrading priority since this issue isn't a required fix for M61.

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.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Even though this is an old bug, and the Magic Tether UI and AX frameworks have both changed since it was filed, the underlying accessibility issue (ie low-vision users should have access to battery level information via the screen reader) should still be addressed (either fixed or verified) .