Is anyone else on #MacOS #Sonoma having a problem with #VoiceOver where nothing is announced when they arrow through a lot of text fields? Please don't say I'm the only one. I mean it's not even consistent; it'll work completely fine in web apps, but won't in others like Notes, Pages, or Mona. Shocking #a11y and #ScreenReader #Bug here from #Apple. Really quite disappointed with the Sonoma release. Glad that Apple are pausing feature updates to work on #Bugfixes.
Also important to mention that I can use VO+Arrows fine to read and navigate text. It moves the cursor alright, but why should I have to? This bug also happens when selecting text, so that’s not fun.
@Minionslayer I’m noticing this in text documents, and even in menus where it isn’t speaking certain menu items in the list.
@doubletap Yes, thank you! Infuriating, isn't it? Although, regarding menu items not being read out, that buh is at least consistently reproducible. It's because VoiceOver using several voices just cannot read text in quotes a lot of the time for some reason. So menu items in the Menubar or in context menus will be silent if (E.G.) the currently-selected item is in quotes as part of an option in a menu. Stupid, I know. Apparently select voices just aren't affected for some reason.
@Minionslayer Weird question, what is your keyboard echo set to? I find that I have this problem when keyboard echo is set to none, but changing it back to words helps. I reported this bug and hopefully it will be fixed soon, because I also would like to be able to keep my keyboard echoes at none.
@tmmahaff I changed my typing verbosity away from nothing, and lo and behold the bug is gone. Thanks for the #workaround, even if it’s for an issue thats quite frankly ridiculous and in a “stable” version of MacOS.
@tmmahaff At least, this works, until you add a line break with Shift+Enter, in which case #VoiceOver just fails to read anything when navigating the textfield. How on Earth is it this broken?
##A11y #Fail