Confusing navigation when using screen readers and arrow keys
When you use a screen reader and you are navigating with arrow keys (Not possible with ChromeVox), the screen reader will read out the buttons (expected behaviour) and also the static labels (unexpected behaviour).
By reading out the static labels the user needs to try out if this is the button. If the focused element is not the button it is not possible to interact. This is confusing because the user using the screen reader always needs to check if he is focusing a button or just a static text.