I have an apple developer program membership, intending to one day, learn swift and write apps. as there are a lot of blind developers here, I filed a bug with the 'view 'agreement' button with VoiceOver. the feedback number is FB24422024
By Daniel Angus MacDonald, 19 August, 2026
Forum
Apple Beta Releases
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
Congratulations
Submitting bug reports is a rite of passage, and so is having them closed with claims of failure to replicate, either that or 5 years from now Apple will automatically ask whether the bug persists and close the submission if you don't reply.
Not trying to discourage you, but reporting bugs to Apple has been a lot more miss than hit from my experience and the experience of many other developers. I've been on the program since 2011, only got one problem addressed during the iOS 7 beta, and completely gave up reporting bugs in 2023 after asking for code-level support for what to me sounded like poor design of the MLCompute framework, because I was taking my first steps into machine learning so I asked just in case I was misunderstanding something, and got a suggestion to use Metal Performance Shaders instead with no admission of MLCompute's poor design. As for MLCompute, it was deprecated shortly after, but only in the documentation.
interesting
well, everybody has their own experience. in my experience, beta testing Apple operating systems, Apple are quite responsive to bug reports I file. they are always very detailed, I ensure as much as possible, and a large percentage of bug reports I file are fixt in future betas. I get why some are cynical about reporting bugs. however, the more information apple gets about a particular bug, they usually fix it in short order. at least, that has been my personal experience.
Re: interesting
Great! So maybe you should tell Apple about the 7 year old macOS bug where all US voices except for Alex spell out the first 30 characters of any word exceeding that length, like UIDocumentBrowserViewController (31 characters). I tried this with a proper description, Swift code, and even audio clips demonstrating the problem and they claimed failure to reproduce. Oh and while at it, also tell them about the fact that VoiceOver only reads one line when we navigate by paragraph in an
NSTextVieworUITextView, which has been a problem for at least as long as I've been blind (12 years).Editing to switch the format to Markdown.
While you're at it
Please please please, tell the folks at Apple about the focus issues with iOS and VoiceOver.
KayThankYouBuhhBye. 🙄