I assigned this to Steven to fix the navigation first.

(I'd suggest sorting the list of networks and continuing navigation from 'approximately the same' position on list refresh, but it might me even more complicate.)

But the problems with ChromeVoX may be separate, or dependent on the cr-network-list changes, so Dominic, please look into this yourself ASAP.

I don't know what the best way to address this is.

The auto refresh feature is fairly important, especially for OOBE, but I can see how this would be challenging from an accessibility perspective.

+jennschen@ - who is the best person to help tackle this from a UX/accessibility perspective?

Is this a requirement for 58? Whatever we come up with is unlikely to be trivial to implement.

lpalmaro@ is probably the best person to provide accessibility feedback and what is and isn't blocking from that perspective. 

Is this a regression (i.e. did we have this before) and is this blocking 58?

I ask because I have a CL up that makes a first pass improvement to a11y for network settings in  issue 699289 , but it's not trivial and it is currently schedule for 59.

That won't fully address this, it just provides the name of a selected network, not the 'connecting' state. We need to figure out what we want to do both focus-wise and chromevox-wise when a network enters 'connecting' and 'connected states for Settings and OOBE.

Actually assigning to lpalmaro@ to get her feedback on what is/isn't blocking from an accessibility perspective.