All I can say is to bombard Apple Accessibility wit emails about ithis. From: viphone@googlegroups.com <viphone@googlegroups.com> On Behalf Of ke...@kellford.com Sent: Sunday, September 29, 2019 2:11 PM To: viphone@googlegroups.com; accessibil...@apple.com Subject: RE: Voiceover, all system sounds an d vibrations stop after making many phone calls
I get this also with more than a few calls I’ve made with iOS 13 and 13.1. Just yesterday it happened on three successive calls for example. Kelly From: viphone@googlegroups.com <viphone@googlegroups.com> On Behalf Of Sieghard Weitzel Sent: Sunday, September 29, 2019 3:24 PM To: 'accessibil...@apple.com' <accessibil...@apple.com> Cc: viphone@googlegroups.com Subject: Voiceover, all system sounds an d vibrations stop after making many phone calls Hello, I have been an iOS/iDevice user since 2009 when the iPhone 3GS and the third Gen iPod Touch were first released with Voiceover and I have also been beta testing new iOS releases for many years. I started Beta testing iOS 13 almost since the start of the public beta program and already experienced the issue I mentioned in the subject line throughout the beta cycle. I as well as other Voiceover beta testers I know have reported this via the Feedback app during the beta cycle. I am sure given how many other Voiceover users experience this, it has also been reported to Apple Accessibility since the official release. I will also CC this to the Viphone list where visually impaired users discuss iOS and iOS devices so they can forward this back to Apple accessibility, I tried to outline the issue in as much detail as possible so there is no point for others to have to re-write all this, but of course everybody can feel free to add any comments to what I wrote. The issue: you make a phone call and after you hang up all sounds go away as do vibrations. Different users seem to be effected differently, some experience this more than others, but it happens on phone calls, Facetime calls as well as calls with other apps such as Skype. It used to be that for me it mostly happened if I was using the wired Apple Earpods and then asked SIRI to call somebody and then used te in-line remote button on the Earpods cable to hang up the call. Now in iOS 13.1.1 it seems worse for me, yesterday I made two calls directly from the phone without any headset and hung up with a 2-finger double tap and both times my phone went silent and it is then extremely difficult for a blind person to get Voiceover and other sounds back. Vibrations also go away except for a very small amount of haptic feedback when I press the virtual home button (I have an iPhone 8), not sure if people who have an X/XR/XS or 11/11 Pro get any haptic/vibration feedback at all. I often use the Mute switch to determine if the phone is still even on when I have an issue with Voiceover going silent. Wen the phone is unlocked or on the lock screen and I flick the switch to Mute, there is a vibration and that is a good way to make sure the phone is on, but even that vibration is not present in this case. If I call my phone from another phone I also get no vibrations even so I have set my phone to vibrate any time a call comes in. To a blind person it almost appears as if the phone was off, but my wife who is sighted says she can do anything on the phone and when I call it the call pops up on the screen and she can answer it. Fixes: I have tried to triple tap the home button which I set up to toggle Voiceover on and off, but that in itself has no effect. Same with asking SIRI to turn Voiceover on and off, when the phone is in this state I also get no SIRI sound, e.g. I can say “Hey SIRI” and my wife says SIRI comes up and is listening, but the tone doesn’t play and if I ask something like “What time is it” SIRI shows the result but it does not speak the time as it usually does. As I said, all sounds are gone as if the volume was completely at 0%. And, before you suggest that it is maybe because the volume dropped to 0%, it is not since I always check this by pressing the volume up button repeatedly and my wife confirms that volume was actually at 100%. Sometimes this resolves itself if I call the phone and answer the call, then hang up the second call and then turn Voiceover on and off, but there have been times when the only solution was to completely turn off the phone and turn it back on. Of course for a completely blind person this is also not always easy if you get no feedback whatsoever, I have to hold the Power button for a bit hoping I did so long enough so the Power Off button is there and then that a double tap will activate it, then wait 30 seconds so hopefully the phone has completely shut down and then push and hold the power button again to start it up again. As I said, I can’t even confirm whether the phone is off or not by flicking the Mute switch, normally I could do this and if I don’t get a vibration when I flick it to Mute it is a pretty good indication that the phone has powered down. Of course a hard reset is also possible. On my iPhone 8 I can press Volume Up followed by Volume Down followed by pushing and holding the power button for about 10 or 12 seconds, but again, I should not have to do this several times a day just because I actually want to use my expensive, high-end iPhone to make phone calls and this bug exists and Apple can’t be bothered to fix it since it only affects Voiceover users. Consider this scenario: a sighted user makes a phone call or a Facetime call and after they tap the end call button the display goes completely black or blank. They now have no visual feedback and if another call comes in the phone rings, but they can’t see anything on the screen, except for the ringing it appears to be a dead phone. They now have to try to answer the call without visual feedback or they have to try and turn the phone off without any visual feedback whatsoever and then back on. I wonder what consumers would post to social media and what the tech press would say about this scenario. One thing I am sure of, such a bug would have never survived even a week before it was fixed and it certainly would not have survived an entire beta cycle and made it into the final release and two subsequent releases, 13.1 and 13.1.1. All I can say is that this issue needs to be fixed asap. This bug should definitely not survive even one more update and in fact a 13.1.2 update should be forthcoming within 1 or at most 2 weeks specifically to address this issue. It is completely unacceptable and it diminishes Apple’s reputation for having the most polished experience and the most accessible devices for people with disabilities. Time Cook once said that “accessibility was a basic human right” and if that is so then such a major issue is violating the human rights of any Voiceover users who experiences this multiple times every day. Best regards, Sieghard Weitzel from Smithers, British Columbia, Canada -- The following information is important for all members of the V iPhone list. If you have any questions or concerns about the running of this list, or if you feel that a member's post is inappropriate, please contact the owners or moderators directly rather than posting on the list itself. Your V iPhone list moderator is Mark Taylor. Mark can be reached at: mk...@ucla.edu. Your list owner is Cara Quinn - you can reach Cara at caraqu...@caraquinn.com The archives for this list can be searched at: http://www.mail-archive.com/viphone@googlegroups.com/ --- You received this message because you are subscribed to the Google Groups "VIPhone" group. To unsubscribe from this group and stop receiving emails from it, send an email to viphone+unsubscr...@googlegroups.com<mailto:viphone+unsubscr...@googlegroups.com>. To view this discussion on the web visit https://groups.google.com/d/msgid/viphone/MWHPR06MB25730146C7FFA2D94428C549C7830%40MWHPR06MB2573.namprd06.prod.outlook.com<https://groups.google.com/d/msgid/viphone/MWHPR06MB25730146C7FFA2D94428C549C7830%40MWHPR06MB2573.namprd06.prod.outlook.com?utm_medium=email&utm_source=footer>. -- The following information is important for all members of the V iPhone list. If you have any questions or concerns about the running of this list, or if you feel that a member's post is inappropriate, please contact the owners or moderators directly rather than posting on the list itself. Your V iPhone list moderator is Mark Taylor. Mark can be reached at: mk...@ucla.edu. Your list owner is Cara Quinn - you can reach Cara at caraqu...@caraquinn.com The archives for this list can be searched at: http://www.mail-archive.com/viphone@googlegroups.com/ --- You received this message because you are subscribed to the Google Groups "VIPhone" group. To unsubscribe from this group and stop receiving emails from it, send an email to viphone+unsubscr...@googlegroups.com<mailto:viphone+unsubscr...@googlegroups.com>. To view this discussion on the web visit https://groups.google.com/d/msgid/viphone/03c501d5770a%246a303460%243e909d20%24%40kellford.com<https://groups.google.com/d/msgid/viphone/03c501d5770a%246a303460%243e909d20%24%40kellford.com?utm_medium=email&utm_source=footer>. -- The following information is important for all members of the V iPhone list. If you have any questions or concerns about the running of this list, or if you feel that a member's post is inappropriate, please contact the owners or moderators directly rather than posting on the list itself. Your V iPhone list moderator is Mark Taylor. Mark can be reached at: mk...@ucla.edu. Your list owner is Cara Quinn - you can reach Cara at caraqu...@caraquinn.com The archives for this list can be searched at: http://www.mail-archive.com/viphone@googlegroups.com/ --- You received this message because you are subscribed to the Google Groups "VIPhone" group. To unsubscribe from this group and stop receiving emails from it, send an email to viphone+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/viphone/MWHPR06MB2573A5AEAC14BA4103E9EE69C7830%40MWHPR06MB2573.namprd06.prod.outlook.com.
