Bluetooth issue may be related to:
 crbug.com/641772  BLuetooth pairng/connecting doesn't respond to ENTER, SPACEBAR, or SEARCH+SPACEBAR

 Issue 641772  has been merged into this issue.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/350d83a296ebac88f8d25c0a19719bf803367900

commit 350d83a296ebac88f8d25c0a19719bf803367900
Author: dtseng <dtseng@chromium.org>
Date: Tue Dec 13 06:24:09 2016

Hook up make visible action for views

- try to scroll to the view's bounding rectangle when a client requests make visible
- add switch as a checkbox (matched for that predicate)

BUG= 673048 

Review-Url: https://codereview.chromium.org/2572573002
Cr-Commit-Position: refs/heads/master@{#438082}

[modify] https://crrev.com/350d83a296ebac88f8d25c0a19719bf803367900/chrome/browser/resources/chromeos/chromevox/cvox2/background/automation_predicate.js
[modify] https://crrev.com/350d83a296ebac88f8d25c0a19719bf803367900/ui/views/accessibility/ax_view_obj_wrapper.cc

David, based on comment #5 I assume you are actively working on this issue? Can you or Laura also help clarify the priority on this too - are the fixes targeted for M-57 or do you plan to merge them back into M-56 (the material design system menu will be shipping in m-56)

Moving from P3 to P2. David, please let us know if you think it might be possible to merge to 56, or if 57 is a better bet considering the timeline here. 

Most the issues are on the views side. The change I made will only be helpful for the scrolling subissue.

Tom, can you help figure out next steps here / what are must-haves for m-56?

Tom, ping re comment #9. Is there anything left here that is a must-have in 56?

@estade, did you already make a change to announce when toggle buttons change state? If this is too large a merge we can consider punting to M57.

@dsteng is there anything left for #2, or did your change address it?

chromevox isn't working for me any more on my local build --- it doesn't show any text when I tab around (although the header bar is present and empty). Launching the web inspector on it reveals tons of errors.

A while back, I added a couple changes to make the toggle button descriptions better. See  bug 652677 . I don't know what actually triggers announcements besides changing focus, or if this works for other things like checkboxes. Back to David.

Assigning to Laura for #2 (are you still seeing visual mis-alignment for the focus highlight?).

Punting this to M57.

Friendly ping on #14.

@Laura?

Tom can you take a look?

Tested on 58.0.3007.0 (Official Build) dev (64-bit)

I think what's happening with #2 is that every time we update the list of Bluetooth devices, we lose focus and it resets to the top of the Bluetooth subpage. This means you might not be able to make it to the bottom of an especially large list, though it's also noticeable if you select an item halfway through the list, wait a couple seconds for the list to update, and then press tab.

I've noticed this too, though I'm not sure how we could get around this. I imagine this is not a md-related regression so I am removing RBS. fukino@, any thoughts? We should apply the solution, if any, to all detailed view lists (e.g., network, vpn) since they could have the same problem.

@fukino any thoughts on how we could address this?

I'm sorry I missed #20.
Let me look for how to work around the issue.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/d10bb36641de2636f34292c0e626a7202ff674bb

commit d10bb36641de2636f34292c0e626a7202ff674bb
Author: fukino <fukino@chromium.org>
Date: Fri Mar 17 02:55:48 2017

Keep focused device in Bluetooth device list when the list is refreshed.

When the Bluetooth device list is updated, child views on the scroll_content
were removed and the focused view was resed.
We should remember the focused device before remove the children, and re-focus
the device after we create the new list.

BUG= 673048 
TEST=manually tested

Review-Url: https://codereview.chromium.org/2758553002
Cr-Commit-Position: refs/heads/master@{#457666}

[modify] https://crrev.com/d10bb36641de2636f34292c0e626a7202ff674bb/ash/common/system/chromeos/bluetooth/tray_bluetooth.cc

The commit in Comment #23 fixes the issue mentioned in Comment #19.
"every time we update the list of Bluetooth devices, we lose focus and it resets to the top of the Bluetooth subpage."

The orange focus outline is still drawn in a wrong position, but it should be an independent issue with the unexpected focus reset.

@fukino: are you still working on this issue?  Is there more planned work here?

I'm sorry I have no updates after Comment #24.
As I'm not going to have cycles to work on this anytime soon, let me releasing the bug.

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

Not able to reproduce in the new UI in 70, so closing this out