Accessibility: computer-use policy blocks the Kindle app, cutting blind users off from books they own
Summary
Claude Code's computer-use tooling refuses all access to the Amazon Kindle app. request_access returns a policy denial:
"Amazon Kindle" is blocked by policy for computer use. Requests for this app are automatically denied regardless of what the user has approved. There is no Settings override.
For a blind user this is not a minor gap. It removes the ability to have Claude work with a book I have lawfully bought, in the only application that book can be opened in.
Who this affects
I am registered blind and use VoiceOver. I run my working life through Claude Code - correspondence, research, drafting, board papers. Reading is the part of my work where assistance matters most, because I cannot skim. Being able to say "read this chapter and tell me what it argues" is not a convenience feature; it is the difference between using a book and not using it.
The concrete case
A colleague recommended a newly published book directly relevant to my organisation's work. I bought it on Kindle specifically so that Claude could work with it alongside me. Claude cannot open it, cannot read a page of it, and cannot be given access by me under any setting.
The blocked route is not decryption or extraction. It is reading the rendered text through the macOS accessibility layer - the same channel VoiceOver already uses to read that book aloud to me. Apple exposes it precisely so assistive technology can reach it. The policy blocks the assistive use along with everything else.
Why the current design fails
The block is absolute and unconditional. It ignores the user's own authorisation, offers no exemption, and provides no route to request one. A sighted user can read their Kindle book unaided. I need software assistance to do the same thing, and that assistance is refused on my own machine, for my own book, over my own explicit consent.
The practical outcome is that the accessibility-dependent user is worse off than the user who needs no help at all.
What I am asking for
- An accessibility exemption path for screen-reader-equivalent access - reading rendered text through the accessibility API - distinct from general automation of the app.
- Failing that, a documented way for an individual user to request such an exemption, rather than an unconditional refusal with no appeal.
- Clarity in the denial message itself about whether any route exists, so users are not left guessing.
Prior report, unanswered
This is my second accessibility report and I have had no substantive response to the first.
On 1 July 2026 I filed an accessibility regression in Claude Desktop for macOS: read-aloud, or "read from here", began reading from the top of the conversation regardless of where I clicked, which made it impossible to have a single reply read out without manually selecting the passage. Environment: Claude Desktop for macOS v1.17377.1, macOS 26.5.1 on Apple Silicon. It was filed through Help > Get Support, triaged by the automated system and escalated to a human agent, with a reply promised by email.
Support conversation ID: 215474913458745
Two months on I have received no reply.
I am raising this here because the support route did not work. I would rather these were fixed than logged.
I am happy to test, to provide logs, and to be contacted directly.
Dr Tony Rucinski