I am not (visibly) disabled, myself, but write software for a demographic that has a statistically high number of folks dealing with various challenges. Accessibility is a big deal for me (as is Usability –Accessibility's redheaded stepchild). I do things like provide localizable accessibility labels, as well as support for things like colorblind access, high contrast mode, and reduced transparency mode.

I have also released over 20 apps in the App Store (myself), since 2012, and am the proud recipient of many app rejection notes.

One of the more annoying things, is that the reviewers are required to select from a menu of rejection reasons. They can't just write "You need to add a plist row to ensure the new permission we just added is presented to the user." Instead, they have to send you some generalized "blanket" reason that includes that requirement, among a list of others that don't apply.

It's easy to panic, when we get these.

In my case, I sometimes need to break out a Ouija board, to figure out what they mean.

Fortunately, I have had very good luck in getting folks on the phone. They still tend to "beat around the bush," but you can usually figure out what they want.