Is this the standard reply from Apple Accessibility?

Forum
iOS & iPadOS

I sent a bug to Apple Accessibility for the focus jumping around mail bug and got this reply:

Thank you very much for your email and your kind words. We appreciate you taking the time to report this behavior with VoiceOver in Mail, and wanted to let you know that our teams are aware of this and investigating. We will follow up if we have any additional questions or recommendations.

Sincerely,

Apple Accessibility

Is this the standard reply from Apple Accessibility?

Options

Comments

Submitted by JC Alicea on Wednesday, July 1, 2020

Hi,
Yes, that's a great reply. hopefully your issue that you mentioned will be fixed soon.

Submitted by Pyro2790 on Wednesday, July 1, 2020

Definitely looks like it to me. Nothing about that seems personalized at all and it says Apple accessibility team. there isn't an individuals name or anything that would make it not a standard reply. Looks very cookie cutter copy and paste or just an automatic reply that is sent if you submit something.

Submitted by Karina Velazquez on Wednesday, July 1, 2020

Well parrt of it, it is in fact, but the only time I reported a bug, that was some weeks ago, they also told me that they where able to reproduce the bug I mentioned, and that they will take care about it to solve it asap.

Submitted by dvdmth on Wednesday, July 1, 2020

Club AppleVis Member

I have submitted bug reports to Apple Accessibility several times over the years, and the response I get from them has always been different, to the point that I'm sure the replies are written individually rather than being canned. Sometimes I am told that the issue is already known and being investigated, while other times I am told that my issue has been forwarded to the appropriate teams for consideration. I have also been told if an issue can be reproduced by them or not, and there have been a couple of instances where I was asked to submit additional details or a diagnostic log.

Whether my reported issues actually get resolved or not also tends to vary. In a couple of instances the issue I reported was resolved quickly, while in other instances it took a long time, and in a few cases the issues remain to this day. I fully understand the situation, given how complex their software is, how many bugs and features they have to deal with, and how difficult it sometimes is to resolve a tricky issue, particularly if it's intermittent or only happens to some people or on some devices.

Submitted by peter on Wednesday, July 1, 2020

I believe that these replies actually come from real people since they all seem to be customized and different. Test teams don't generally have the bandwidth to get into details or an extended back and forth with each user and their suggestions/bugs.

On the other hand, Siri is getting so good these days it is just possible that no one is there at all and we're just talking to a giant super computer! (tongue in cheek).

BTW, at least one can actually provide input to Apple's accessibility team and get some feedback. Not true for all vendors.

--pete

Submitted by Devin Prater on Thursday, July 2, 2020

Club AppleVis Member

Just wait for iOS14. I predict that it'll be fixed.

Submitted by Khushi on Thursday, July 2, 2020

I have never reported things to apple. but when I read it, it seems it is not automated. and if this is the case, I'm very pleased that apple accessibility team sends customized replies.
I shifted to apple just because of its accessibility and I'm glad they pay attention to it.

Submitted by Holger Fiallo on Thursday, July 2, 2020

Yes. It is.

Submitted by Troy on Thursday, July 2, 2020

I have gotten different replies as well. The reason why they might look a little canned is they probably have a template that they use where the agent adds in their own text and everything else is the same.

Submitted by KE7ZUM on Thursday, July 2, 2020

Iv'e gotten the exact same words you have gotten, sometimes years later on bugs that are no longer relivent. Actually got one about 3-4 months ago on an issue I reported with ios 12, or was it 10 . I can't remember now it is canned.