TL;DR
Get privacy and security gear delivered free with Prime
- Fast, free delivery on millions of items
- Prime Video, Amazon Music and more included
- Member-only deals all year
A developer created WhisperPad, a voice-to-text app designed to reduce hand strain for users with injuries. Apple rejected the app twice, citing misuse of the accessibility API, prompting the developer to split the app into two versions. The case highlights ongoing tensions around accessibility API policies.
Apple has rejected WhisperPad, a Mac dictation app designed to assist users with hand injuries, citing improper use of the accessibility API. This rejection raises questions about Apple’s API policies and their impact on accessibility tools.
The developer of WhisperPad, created to reduce hand strain by allowing voice transcription directly into applications without sending audio to servers, experienced rejection from Apple in April 2024 under Guideline 2.4.5. Apple claimed the app misused the accessibility API by injecting text into other applications, despite earlier versions with similar functionality being approved. The developer appealed, explaining the app’s purpose for accessibility and injury mitigation, but received another rejection in May after follow-up inquiries. To comply with App Store rules, the developer split WhisperPad into two versions: one on the App Store that does not auto-paste, requiring manual pasting, and a full version distributed directly to users outside the store. This compromise aims to balance compliance with accessibility needs and app distribution goals.
Why It Matters
This case underscores the ongoing challenges developers face when creating accessibility tools within Apple’s app ecosystem. The rejection highlights potential restrictions on how apps can use accessibility APIs to assist users with disabilities or injuries, raising broader questions about the balance between security, API control, and accessibility innovation. For users with similar needs, it could limit the availability of specialized tools if restrictions tighten.
Products Worth Considering
DJI Osmo Mobile 7P Smartphone Gimbal Stabilizer with Mic Mini Transmitter
Bose SoundLink Flex Bluetooth Speaker (2nd Gen), Black
LG UltraGear 34GX90SA-W 34-inch WQHD Curved OLED Gaming Monitor
As an affiliate, we earn on qualifying purchases.
Background
In 2024, Apple tightened its review process for apps utilizing accessibility APIs. Previously approved apps with similar functionalities, like WhisperPad, now face rejection under new interpretations of Guideline 2.4.5. The developer’s app was built to address a personal injury and aimed to improve productivity and comfort by minimizing keystrokes through direct text injection, a feature that Apple now deems problematic for security or misuse reasons. The developer’s experience reflects broader tensions around API restrictions affecting accessibility applications.
“The app exists because I have a hand injury. I wanted to create a tool that helps people like me avoid unnecessary keystrokes.”
— Developer of WhisperPad
“Apps that inject text into other applications without proper authorization may violate our guidelines.”
— Apple representative (implied)
“I split the app into two versions to comply with the rules, but I still want to deliver the full functionality outside the App Store.”
— Developer of WhisperPad
What Remains Unclear
It remains unclear whether Apple will clarify or modify its interpretation of Guideline 2.4.5 regarding accessibility API use, or if other developers will face similar rejections. The precise boundaries of acceptable API usage for accessibility tools are still being defined, and the developer’s case may set a precedent.
What’s Next
The developer plans to continue distributing WhisperPad outside the App Store and may seek further clarification from Apple. Future updates could involve negotiations or policy adjustments, and the developer intends to monitor Apple’s stance on accessibility API restrictions.
Key Questions
Why did Apple reject WhisperPad?
Apple rejected WhisperPad because it used the accessibility API to inject text into other applications, which Apple considers an improper use under Guideline 2.4.5.
Can the developer still distribute WhisperPad?
Yes, the developer is distributing a limited version through the App Store that requires manual pasting but plans to continue offering the full version outside the App Store via direct distribution.
What does this mean for accessibility apps on iOS and macOS?
This case highlights potential restrictions on how accessibility APIs can be used, which could impact the development of future accessibility tools that rely on injecting text or automating interactions across applications.
Will Apple clarify its API policies?
It is not yet clear whether Apple will provide further guidance or modify its policies regarding accessibility API use, leaving the future landscape uncertain for developers.
Source: Hacker News
