Hi, new release here, we're very close to the first stable.
No change observed so far, good or bad. The tab key bug in a webpage in safari not working sometimes (work around: restart voiceover once) is still there. For the 1password autofill with down arrow not working on any site, this seems to only occur in safari, not chrome, discovered in beta 8 and same in this current one. In safari you can always use quick access manually. I don't know if this is a VO specific bug or not, though it's likely. I will contact both apple and 1password on this topic. 1password have an incredible accessibility track record imo, a good web ui working insanely well with screen readers on windows, gnome, mac, chromevox... and the ios and watch os app is very good too. Hopefully they can report this to apple too if it's not something on their end, very unlikely as 1password (the extension) still works well on my stable partition. Nothing similar observed on windows side either.
Please post anything you think is relevant below!
By TheBlindGuy07, 7 September, 2025
Share Your Bug Reports with AppleVis
If you experience a bug in Apple Beta Software, the most important thing you can do is to file a report in Feedback Assistant. Please do not assume that Apple is already aware of a bug or that your report won't make a difference; your report may provide crucial information, and submitting bug reports directly to Apple helps them reproduce and resolve the issue faster. The more reports they receive, the higher the priority Apple is likely to give to fixing the bug.
If you are using beta software, please use the Feedback Assistant on your device to submit feedback and bug reports. If you are using a public release, this blog post explains how to report the issue and what information to include.
In 2025, AppleVis launched the Community Bug Reporting Program with the goal of improving the quality and quantity of information we share with the community about bugs in Apple software releases. If you would like to contribute to this effort, please submit your reports via our Community Bug Report Form.
All reports shared with AppleVis must first be filed with Apple via Feedback Assistant. More information about the Community Bug Program is available here.
Comments
Also an important note
For a very weird reason, the developer options I mentioned in the first beta thread:
1. They don't seem that useful, I don't know if they add anything new other than some more structure, as we already seem to gather those information and much more with the vo-shift-z command to save last phrase to desktop as audio file. They just seem to be more selective in terms of what we want, just a couple of hashes. The timeout seems the only real interesting thing, I don't have enough knowledge nor have I tested this enough to see if this does anything for my use case. I believe this was meant to mitigate the appname does not respond bug.
2. They are very hidden, not accessible with the vo-h-h command help menu, which only contains 15 items and not the 16th developer category. The easiest way I found to access them is through the braille section, we always have one display shown now braille keyboard input, Assign commands, and you pick anything item in the table and in the popup menu with the similar category submenus as vo-h-h you will see this and some more commands, we have a section about 2d braille which I asume is for multiline displays, it was already there as of sequoia or sonoma, if not ventura.
I think this something a lot of people could not be aware of as this is so hidden, and since we don't have the documentation yet... I believe they will fix that on the first stable probably as they'd want to document it anyway.
That is it! :)
personal voice is easyer to use on the latest bet
As of the latest beta, personal voice is much easyer to use. You now have 10 frases to record, which now makes it faster to handle. I haven't tryed it myself, but I just saw the option when exploring the changes in the final revision of the software. Cannot wait until the RC is released. it'll be released tomorrow following the apple event.
Issue between personal voice and VoiceOver Utility
I would be curious to know if anyone else has seen this issue. I have recorded a personal voice. The process itself is seamless and relatively easy. Using headphones is the best way to do this and it goes through without a problem. The instructions are self-explanatory and the process is seamless. The problem occurs, when you access the personal voice in the VoiceOver Utility to add to your voice rotor. You record the voice in English. It shows up as an English voice and gives you the option of having it in either Spanish or Chinese. When you use the voice within your voice rotor after you have added it to using the VoiceOver Utility it will see it is either Spanish or Chinese when you recorded it in English. This has no effect on whether or not the voice is usable. The voice works just fine. I guess my sense of order and continuity is a little bit baffled by the voice showing up as Chinese when it's actually English. It is also showed up as Spanish as well. It's almost as if the technology gods or attempting to drive me a little bit crazy by their h inability to pr inability to properly recognize the voice the way it was recorded. I'm also not exactly sure that this is a bug so that's why II'm also not exactly sure that this is a bug so that's why I have not reported it. Consider me a bit baffled. ha
@Eric Davis
Sorry. I couldn't understand your post. My Mac kept speaking Chinese.