1. Type some characters in the search field
2. Use the arrow keys to move back and forth through the text
Observed: no read out of characters
Expected: Characters are read when arrowing through them and text can be reviewed with INSERT+5, INSERT+8
Also make sure to test if search autocomplete is being read out when you arrow through the results of in: or from: (note that on:/before:/after: autocomplete does not support JAWS yet).
Should be fixed on https://accessibility-demo.test.spinmint.com/accessibility
can you try this repo:
Type ~ and notice the 4th option is focused by default:
This does not repro on other servers
Should not be specific to my PR.
It reads whatever one you last left selected.
So if you go to the first, and then close it, and then open it again, the first will be focused, if you go to the 3rd or 4th, and leave it, then the next time you open it, the 3rd or 4th will be focused.
Hey , I don't have any particular repro steps for the reading the word 'MISPELLED' on Chrome/Win10 other than:
Virtual PC cursor is OFF
In message input box in center panel or RHS, type `@[user] ~[channel]` but don't post
Hit "Home" to position cursor at the beginning of the input box and press INS+8 to read the string
Reader reads 'MISPELLED' after the at-sign (see screenshot)
The same is true for Search input box (see screenshot for where reader reads 'MISPELLED'
At first, I thought it was reading 'MISPELLED' where I had perhaps backspaced to correct a word but I made sure to type into both the message input box and search input box without hitting the backspace key to correct anything and it still read out 'MISPELLED' in these places (as per screenshot)
On the misspelled discussion, I’m sure that’s not even an issue.
Thanks AM, this is fixed and v5.14.1 has shipped. Closing.
QA test note: test added to spreadsheet and PR labelled.