Dear Apple Customer Support,
I am writing to report a critical accessibility issue I am experiencing after upgrading to macOS Ventura yesterday. As a user of VoiceOver with both Arabic and English languages, I have discovered a significant bug impacting the functionality of VoiceOver with Arabic text.
Specifically, VoiceOver is unable to read Arabic text properly in several key applications, including TextEdit and Numbers. While it can recognize words within TextEdit, it fails to pronounce individual Arabic letters. In Numbers, the issue is even more severe, with VoiceOver simply reading out the individual letters instead of the intended word (e.g., "Arabic letter waw, Arabic letter dal").
Unfortunately, the only workaround currently available is to switch my VoiceOver language entirely to Arabic. This is not a viable solution for me, as my system language and most of my applications are in English.
Therefore, I urgently request a swift resolution to this critical accessibility issue. Ideally, a patch would be released to address the bug within macOS Ventura itself. However, if the only solution currently available is to upgrade to macOS 14, I regret that this is not feasible for me at this time due to compatibility issues with essential software I use in my studio.
I would greatly appreciate your immediate attention to this matter and any assistance you can provide in resolving this critical accessibility bug.
Sincerely,
By Ramy, 10 December, 2023
Forum
macOS and Mac Apps
Comments
Have you tried any system…
Have you tried any system resets or VoiceOver reconfigurations? Sometimes, even minor adjustments can yield surprising results.
Since this is a more complex issue, reaching out to Apple's customer support or submitting feedback through the macOS Feedback Assistant might be your next best step. Given the critical nature of the bug, they should take it seriously.
also in 14
I knew yesterday that this issue still persists on mac os14,
I Contacted apple customer accessibility support and i stated the importance of this bug,
they told me that they will have a look, and that is it.
wish it will be fixed soon.
do not know really how i did not see any complains about this issue from another users?