Chrome 63.0.3236.0 (Official Build) canary (64-bit) (cohort: 64-Bit) and
Chrome 61.0.3136.100 (Official Build) (64-bit)
macOS Sierra version 10.12.6 with VoiceOver 7.0 (477.40.6)
Opening bug based on this email thread: https://groups.google.com/forum/#!topic/axs-chrome-discuss/gU5IlsUAApM
What steps will reproduce the problem?
1. Launch voiceover.
2. Go to any site for example anchor.fm/clip log in if you have an account and fill in the file description
3. Type in the edit fields and try and edit your mistake, or try and even left or right arrow.
What is the expected result? Deleting characters should indicate that the deletion happened. Also, typing characters into the field should be echoed.
What happens instead? In Chrome 61, sometimes the typed characters are not echoed. This is resolved in 62 per the developer, and tested in 63 by me to verify the fix.
In both 61 and 63, VoiceOver doesn't say anything specific to indicate that a deletion happened. There isn't an obvious feedback that the backspace character has been pressed. There is a change in pitch that goes a bit lower when pressing backspace.
I also tested the change of pitch on Safari Version 11.0 (12604.1.38.1.7) and I saw the same behavior. Since this is the same behavior on Safari and on Chrome, this appears to be an issue specific to VoiceOver.
I am resolving this bug as Verified since text echo is now working.
Comment 1 by leberly@chromium.org
, Oct 13 2017