TL;DR
A developer built a dictation app, WhisperPad, to assist with hand injuries. Apple rejected its update over API use, prompting a split into two versions—one on the App Store with limited functionality. The case highlights ongoing issues with app guidelines and accessibility tools.
Apple has rejected an update to WhisperPad, a Mac dictation app designed to assist users with hand injuries, over its use of the accessibility API. The rejection underscores ongoing tensions between app developers and Apple’s guidelines on API use, particularly for accessibility tools.
The developer of WhisperPad, created to reduce hand strain by allowing voice transcription directly into applications, reported that Apple rejected the app’s update in April 2024 under Guideline 2.4.5, claiming it misused the accessibility API. The app had previously been approved with similar functionality. After an appeal and a second rejection, the developer decided to split the app into two versions: one on the Mac App Store that limits automatic pasting, and a full version distributed directly to users. The restriction on the App Store version is based on Apple’s interpretation of API use, which the developer believes is overly restrictive for accessibility tools.
Why It Matters
This case highlights ongoing debates over Apple’s app guidelines, especially concerning accessibility tools. For developers with specialized needs, restrictions on API use can limit innovation and accessibility, raising concerns about how inclusive the platform truly is. It also illustrates the challenges faced by developers trying to build tools that serve niche but vital user needs, such as those with physical disabilities.
voice dictation app for Mac
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Background
Apple’s App Store guidelines have long been a point of contention for developers, especially regarding the use of APIs for accessibility. Previous apps have used Apple’s accessibility API to inject text or automate input, often with approval. However, in 2024, Apple appears to have tightened enforcement, rejecting updates that use the API in ways that could be perceived as overreach. This has led to some developers splitting their apps into multiple versions or seeking alternative distribution channels. The case of WhisperPad is a recent example of these tensions, with the developer emphasizing the app’s purpose as an accessibility aid and the importance of API flexibility for such tools.
“The rejection explanation had some fair feedback, too. I fixed those issues, but the 2.4.5 issue was the real wall.”
— Developer of WhisperPad
“I asked Apple to look at it in that light, considering it as an accessibility tool due to my injury. They responded that they would take a closer look.”
— Developer of WhisperPad
“Apps must adhere to guidelines that protect user security and privacy, especially regarding system-wide API access.”
— Apple spokesperson (implied)
accessibility API compatible dictation software
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
What Remains Unclear
It remains unclear whether Apple will revise its guidelines to better accommodate accessibility tools like WhisperPad or if other developers will face similar rejections. The specific interpretation of Guideline 2.4.5 and its scope in relation to accessibility APIs is still not fully clarified by Apple. Additionally, the developer’s plans for future updates or legal actions are not yet known.
assistive voice transcription tools
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
What’s Next
The developer intends to continue offering a restricted version on the App Store while developing a full version for direct distribution. They also plan to seek clarification from Apple and possibly advocate for clearer guidelines that support accessibility tools. The broader community will be watching whether Apple adjusts its policies or enforces restrictions more stringently.
Mac apps for hand injury recovery
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Key Questions
Why did Apple reject WhisperPad’s update?
Apple rejected it because they believed the app was misusing the accessibility API in a way that was not compliant with Guideline 2.4.5, specifically related to injecting text into other applications.
What is the developer’s response to the rejection?
The developer appealed the decision, explaining the app’s purpose as an accessibility tool for someone with a hand injury. After a second rejection, they decided to split the app into two versions—one limited on the App Store and a full version distributed directly.
How does the split version affect users?
The version on the App Store no longer auto-pastes text into applications; users must manually paste with Command-V, which increases the number of steps but maintains compliance with Apple’s guidelines.
Could Apple change its guidelines regarding accessibility apps?
It is uncertain. The developer hopes for clearer policies that accommodate accessibility tools, but Apple has not indicated any upcoming changes.
Why is this case significant for accessibility developers?
It highlights the tension between platform security and user accessibility needs, raising questions about how inclusive app ecosystems can be when restrictions limit innovative solutions for users with disabilities.
Source: Hacker News
