RE: The Accessibility Bugs Introduced and Resolved in iOS 13 for Blind and Low Vision Users | AppleVis

2019-09-17 Thread Sieghard Weitzel
I also experience this, but for me mostly this happens when I ask SIRI to make a call and use a wired headset and then use the headset remote to hang up the call. But I do know that others experience this as well and some a lot more than me and not only for phone calls but also with Skype

Re: The Accessibility Bugs Introduced and Resolved in iOS 13 for Blind and Low Vision Users | AppleVis

2019-09-16 Thread Justin Harris
> I haven't experienced that one. I have been running the beta from almost day > one. Actually the first two were so buggy that I had to do a restore and > downgrade in iTunes. I removed the beta profile when they started coming out > with 13.1, as I no longer have the developer account. Hoping

Re: The Accessibility Bugs Introduced and Resolved in iOS 13 for Blind and Low Vision Users | AppleVis

2019-09-16 Thread Anthony Vece
Well, I’m going to update as soon as possible. Maybe I could help remove some bugs by making suggestions to Apple and their accessibility department. Sent from my Verizon iPhone XR!!! > On Sep 15, 2019, at 3:30 PM, William Green wrote: > > I would personally recommend waiting at least a few

Re: The Accessibility Bugs Introduced and Resolved in iOS 13 for Blind and Low Vision Users | AppleVis

2019-09-16 Thread lenron brown
I hate the one that kills voice over for me after a call a lot of the time. I wondered if it was just my phone but this only popped up a few days ago. On 9/16/19, Steve Matzura wrote: > Yeah,and give VoiceOver some love and care in Catolina while they're at it. > > > On 9/15/2019 12:36 PM,

Re: The Accessibility Bugs Introduced and Resolved in iOS 13 for Blind and Low Vision Users | AppleVis

2019-09-16 Thread Steve Matzura
Yeah,and give VoiceOver some love and care in Catolina while they're at it. On 9/15/2019 12:36 PM, CrazyEyez wrote: Man apple people who write code for this software need to lose their jobs. Each and every one of them. There's no excuse for all these bugs. Lay off the drugs.I don't understand

Re: The Accessibility Bugs Introduced and Resolved in iOS 13 for Blind and Low Vision Users | AppleVis

2019-09-16 Thread Steve Matzura
Haha, and more introduced! On 9/15/2019 12:09 PM, Gerardo Corripio wrote: Yes I read through the bugs, and they don’t seem, for my use at least, too bad a game-changer. Thanks though for sharing. Good thing we’ll only have to wait 10 days for the iOS13.1 to come out, in which I’m sure most

Re: The Accessibility Bugs Introduced and Resolved in iOS 13 for Blind and Low Vision Users | AppleVis

2019-09-16 Thread Joshua Hendrickson
For me and to just be sure, I'll not update until 13.1. I checked and my software automatic updates are currently turned off. On 9/16/19, Dave wrote: > no there are 2 automatic update settings. 1 is for apps, and the other is > for updating the firmware. > > Dave. > > > From: Christopher

Re: The Accessibility Bugs Introduced and Resolved in iOS 13 for Blind and Low Vision Users | AppleVis

2019-09-16 Thread Dave
no there are 2 automatic update settings. 1 is for apps, and the other is for updating the firmware. Dave. From: Christopher Chaltain Sent: Monday, September 16, 2019 2:06 AM To: viphone@googlegroups.com ; Andy Baracco Subject: Re: The Accessibility Bugs Introduced and Resolved in iOS 13 for

RE: The Accessibility Bugs Introduced and Resolved in iOS 13 for Blind and Low Vision Users | AppleVis

2019-09-15 Thread Sieghard Weitzel
I think it was in iOS 12 when the automatic updates option was introduced in Settings > General > Software Updates. From: viphone@googlegroups.com On Behalf Of Marie Sent: Sunday, September 15, 2019 6:09 PM To: viphone@googlegroups.com Subject: Re: The Accessibility Bugs Introduced and Resolved

Re: The Accessibility Bugs Introduced and Resolved in iOS 13 for Blind and Low Vision Users | AppleVis

2019-09-15 Thread Marie
There are separate settings for auto updates for each. For software updates, go to Settings/General/Software Update. Marie From: Christopher Chaltain Sent: Sunday, September 15, 2019 6:06 PM To: viphone@googlegroups.com ; Andy Baracco Subject: Re: The Accessibility Bugs Introduced and

Re: The Accessibility Bugs Introduced and Resolved in iOS 13 for Blind and Low Vision Users | AppleVis

2019-09-15 Thread Christopher Chaltain
I thought automatic updates just applied to apps and not to operating system updates. On 9/15/19 2:27 PM, Andy Baracco wrote: You can wait providing that you do not have automatic updates enabled. Andy - Original Message - *From:* Matthew Bullis

Re: The Accessibility Bugs Introduced and Resolved in iOS 13 for Blind and Low Vision Users | AppleVis

2019-09-15 Thread lenron brown
13.1 should be fine, I still have one where voice over goes silent after some phone calls though. On 9/15/19, Alan Lemly wrote: > Richard, > > > > No, the third party keyboards while using Voiceover in iOS 13 bug was not > discussed in the AppleVis blog. I was surprised by this and posted

RE: The Accessibility Bugs Introduced and Resolved in iOS 13 for Blind and Low Vision Users | AppleVis

2019-09-15 Thread Alan Lemly
Richard, No, the third party keyboards while using Voiceover in iOS 13 bug was not discussed in the AppleVis blog. I was surprised by this and posted comment #35 in their blog to ask about it. Alan Lemly From: viphone@googlegroups.com [mailto:viphone@googlegroups.com] On Behalf Of

Re: The Accessibility Bugs Introduced and Resolved in iOS 13 for Blind and Low Vision Users | AppleVis

2019-09-15 Thread William Green
I would personally recommend waiting at least a few weeks unless absolutely necessary. No need to risk the chance of getting bugs when you can wait until the software is more tested towards Christmas time. Thanks Will Sent from my iPhone > On 15 Sep 2019, at 20:27, Andy Baracco wrote: >

Re: The Accessibility Bugs Introduced and Resolved in iOS 13 for Blind and Low Vision Users | AppleVis

2019-09-15 Thread Andy Baracco
You can wait providing that you do not have automatic updates enabled. Andy - Original Message - From: Matthew Bullis To: viphone@googlegroups.com Sent: Sunday, September 15, 2019 9:52 AM Subject: Re: The Accessibility Bugs Introduced and Resolved in iOS 13 for Blind and

Re: The Accessibility Bugs Introduced and Resolved in iOS 13 for Blind and Low Vision Users | AppleVis

2019-09-15 Thread Jennie Facer
> You can definitely wait. You don't have to get 13.0 before 13.1. > > Jenn > > Jenn and Kumi > > On Sep 15, 2019, at 10:52 AM, Matthew Bullis > wrote: > >  > Hello, if anyone feels like doing so, can you actually wait to upgrade from > version 12 to 13.1, or do you need to upgrade to 13

Re: The Accessibility Bugs Introduced and Resolved in iOS 13 for Blind and Low Vision Users | AppleVis

2019-09-15 Thread Matthew Bullis
Hello, if anyone feels like doing so, can you actually wait to upgrade from version 12 to 13.1, or do you need to upgrade to 13 first in order to then get the incremental update? Thanks, Matthew -- The following information is important for all members of the V iPhone list. If you have any

Re: The Accessibility Bugs Introduced and Resolved in iOS 13 for Blind and Low Vision Users | AppleVis

2019-09-15 Thread CrazyEyez
Man apple people who write code for this software need to lose their jobs. Each and every one of them. There's no excuse for all these bugs. Lay off the drugs.I don't understand how they can release this garbage. Get rid of the useless dead weight, and find people who actually know what they are

RE: The Accessibility Bugs Introduced and Resolved in iOS 13 for Blind and Low Vision Users | AppleVis

2019-09-15 Thread Richard Turner
As I read through them again, was there mention of third party keyboards being silent? So if you use Flicktype or MBraille as a third party keyboard, you may want to wait. Richard  Live long and prosper Check out my web site at: www.turner42.com From:

Re: The Accessibility Bugs Introduced and Resolved in iOS 13 for Blind and Low Vision Users | AppleVis

2019-09-15 Thread Gerardo Corripio
Yes I read through the bugs, and they don’t seem, for my use at least, too bad a game-changer. Thanks though for sharing. Good thing we’ll only have to wait 10 days for the iOS13.1 to come out, in which I’m sure most of these bugs will be resolved. Gera Enviado desde mi iPhone SE de Telcel El