FlickType disputes this in the original Twitter thread that made it to the front page yesterday (https://twitter.com/FlickType/status/1427292830523744257 https:

FlickType disputes this in the original Twitter thread that made it to the front page yesterday (https://twitter.com/FlickType/status/1427292830523744257 https://twitter.com/FlickType/status/1427292830523744257 on Twitter, https://news.ycombinator.com/item?id=28200288 https://news.ycombinator.com/item?id=28200288 on HN). They originally dealt with a rejection for that reason several years ago, and managed to clear it up with Apple because they feel they don't require full access. (Although the Verge article says if you don't have full access you need to use VoiceOver, which doesn't make sense to me, but I've never used the keyboard and given the very accessibility-specific purpose of the app maybe that makes sense?) So in general I agree that using "full access" should require, say, closer review. But in this case, they've been closely reviewed & approved over the same issue in the past, and FlickType says the keyboard continues to work when full access is off, as it should. Pretty much no matter how you cut it, in the absolute best-for-Apple interpretation here, Apple is still doing a pretty awful job of explaining their review criteria or enforcing them consistently.