Customer report:
"i cannot see in braille what i am typing, nor is JAWS able to speak it."
"From my own user perspective, the only show stopper I see would be not being able to read in braille, or hear with speech what is being written in the message window."
Repro:
1. Type some characters in the message input box
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
Note: This should apply to the RHS and main message input fileds
Also make sure to test if message autocomplete is being read out when you arrow through the results of @ or ~
Should be fixed on https://accessibility-demo.test.spinmint.com/accessibility
Confirmed that reading out ~ and @ drop down is now working on desktop
Regression tested ~ and @ drop down in browser no issue found
Commented in regarding different behavior for insert+5 and insert+8.
Thanks - was indeed using the numbers 5 & 8 along the top of my keyboard!
Confirmed by customer that the fix is working
Tested on v5.14.1 RC1 on both Win/Chrome and Desktop app
No issues found on Desktop app
Random read-out of `MISPELLED` on browser (see screenshot)
Working as expected on both browser & desktop app:
INS+5
using left/right arrows to move through text
read-out of `~` and `@` in message input box in center and RHS
read-out of `in:` and `from:` in search input box
Thanks AM, this is fixed and working as expected. Closing.
QA test note: test added to Accessibility tab of spreadsheet, Labelled PR.