eloquence probably broken on first iOS 16.4 beta

By Alan, 16 February, 2023

Forum
Apple Beta Releases

A quick note: in my device, the first beta makes eloquence not able to speak things like elements (not announcing buttons etc), and stops responding at all after some minutes. Other voices seem to work as expected.
_don't update yet if eloquence is important for your needs.
Please share here your experiences.

Options

Your Feedback is Important to Improving Accessibility on Apple platforms

Don't assume that Apple is aware of a bug or that your report won't make a difference - submitting bug reports directly to the company helps them reproduce and resolve the issue faster. Your report may provide crucial information. The more reports they receive, the higher the priority they give to fixing the bug.

If you're using a beta version, use the Feedback Assistant on your device to submit feedback and bug reports. If you're using a public release, follow the instructions on this page.

Comments

By serrebi on Friday, February 24, 2023 - 02:14

How do you get this to happen.

By Alan on Friday, February 24, 2023 - 02:14

Here, eloquence does not read any tag like buton, heading, etc. And if you keep moving around, sounds like crackling and finally stops speaking until voiceover is restarted.
Other voices work as expected.
IPhone 12 on the 14.4 dev beta 1.

By Igna Triay on Friday, February 24, 2023 - 02:14

Report it to apple accessibility just in case.
accessibility@apple.com
Also, just a heads up, your post title displays as ios14.4 not 16.4.

By KE8UPE on Friday, February 24, 2023 - 02:14

Hello,
It did take a second to begin talking, including speaking it’s own voice name, but for the most part, everything works fine here on my iPhone 13 pro max. The one exception to that, is that I can no longer comment on Facebook posts, because the keyboard comes up, then immediately disappears. This issue only presents itself if voiceover is enabled.

By Tyler on Friday, February 24, 2023 - 02:14

Member of the AppleVis Editorial Team

In addition to or instead of emailing accessibility@apple.com, you should report this issue through Feedback Assistant, describing it similarly to how you described it in this forum topic. As part of your report, it may be helpful for them to know what voice and language you're using, if you've noticed a specific trigger for reliably reproducing the issue, and if possible, a recording of the issue occurring. This can hopefully give them an idea of exactly what is happening and consequently make it more likely that the issue will be fixed.

By Alan on Friday, February 24, 2023 - 02:14

thanks for editing the title etc. for the record, my language is set to spanish, but it crashes when using elotuence in any supported language. Hopefully it will not affect others.

By Julian on Friday, February 24, 2023 - 02:14

So far Eloquence is working as expected here. Did you restart your phone after the update was installed? I make a point of doing this after every iOS update and it seems to clear out a lot of these weird issues.

By Alan on Friday, February 24, 2023 - 02:14

The issue is easily identifiable: if your iPhone ceases to announce buttons and headers, it's a clear indication of the bug. While it could be unique to my settings, it's evident that it only happens with the voice of eloquence, regardless of the language. I'll keep you updated if any further details surface.