Taylor Arndt
Apple put an AI coding assistant directly into Xcode.
I tested it with VoiceOver.
Some of it is genuinely useful. It can generate code, fix errors, and work across files.
But the accessibility problems are serious: unlabeled controls, confusing labels, and response views that can become difficult or unsafe to navigate with a screen reader.
I wrote up the full teardown here:
https://taylorarndt.substack.com/p/taylors-teardowns-xcode-intelligence
Taylor’s Teardowns is back, just in writing now.
#Accessibility #AppleDevelopment #SwiftDevelopment
Taylor’s Teardowns: Xcode Intelligence

Taylor’s Teardowns: Xcode Intelligence

Taylor’s Substack
Mar 21 at 11:05pmWeb
Show threadParham Doustdar1d ago
@tayarndt I use Gemini CLI with the Xcode MCP. Works very well, especially with Gemini CLI's --screen-reader flag.
Show threadRobin Kipp8h ago
@tayarndt Just had a chance to read through this, and I think it's a very well structured, clear and comprehensive list of accessibility issues present in Xcode's AI integration so great job!
However, in order to get these issues fixed in a future release, it's really essential that you take the time to file bug reports through Feedback assistant for all of these. You can put a link to your post in each report, and you can then update your post as well to include the feedback IDs. Yes I know it sounds like tedious work, but in order for the right engineers at Apple to notice these problems it's really a crucial thing to do.
Show threadTaylor Arndt6h ago
@robin I’m already in the process.