For what it's worth, I think it is always a good idea to restart one's
phone after an update, whether it's a minor or major update, to insure
there's no issues or glitches. Sorry you've had a bad go of it.
Hopefully 14.1 will resolve some of your issues, or you can get back
to 13.7 until Apple puts out fixes.

Wayne

On 9/17/20, Cristóbal Muñoz <[email protected]> wrote:
> The only way I was able to get rid of the screen recognition even after
> turning it back off was to completely restart the phone. It really does make
> apps unusable.
>
> The text editing bugs are a real pain even if using the secondary language
> profile. When I want to delete multiple characters, I’ll usually double tap
> and hold on the delete button and with another finger, split tap as many
> times as I want to go back. This has worked fine, but now, if I do that, I’m
> taken to the beginning of the edit field. Not… ideal.
>
> VO can’t seem to maintain focus on the dictate button either. It just
> flickers and studders and the haptic feedback goes off as if the phone’s
> doing the jitterbug if trying to navigate to it. I’ve resorted to using the
> two finger double tap in the edit field to invoke dictation which means I
> more often than not have to now use two hands instead of just one hand which
> is more annoying.
>
> Don’t’ even try to share an item via the share sheet. VO is all sorts of
> buggy to the point where you can’t do anything. It’s jumpy, gets stuck on
> elements and in short makes this feature completely useless now.
>
> VoiceOver says toolbar when on the toolbar. I mean… it seems like it’s one
> of those well intentione things where more description is better, but after
> the umpteenth time… So not necessary.
>
> I’m really considering rolling back to iOS 13.7.
>
>
>
> Cristóbal
>
>
>
> From: [email protected] <[email protected]> On Behalf Of
> Richard Turner
> Sent: Thursday, September 17, 2020 7:06 AM
> To: [email protected]
> Subject: Moderate and minor bugs plus Accessibility improvements from
> Applevis.com
>
>
>
> Applevis listed no serious bugs.
>
>
>
> Moderate Bugs
>
> *     On occasions, there may be a ‘lag’ in VoiceOver speech; or your device
> might feel generally less responsive than it was on iOS 13. It should be
> noted that not all of our testers experienced this issue, and we believe the
> severity of the issue is likely somewhat subjective. One workaround is to
> switch to a VoiceOver voice that does not exhibit this behaviour, though
> this may take some trial and error to find a voice that works for you. A
> slightly more involved workaround is to add a second voice to VoiceOver's
> language rotor; set the voice in that secondary language to your preferred
> voice; then use the rotor to switch to your preferred voice in the secondary
> language. Our experience indicates that the latter workaround can make
> VoiceOver and your device more responsive, even though you are still using
> the same voice - just not as the "default" language. It has also been
> suggested that deleting and re-downloading your preferred VoiceOver voice
> can resolve this behavior.
> *     On some web pages in Safari; web views in apps; and pages in apps, you 
> may
> find that VoiceOver focus will spontaneously ‘jump’ to another UI element.
> This behaviour does not appear to be widespread, but can make navigation
> difficult and confusing when it does occur. One example of this behaviour
> can typically be seen with Google search results when using the VoiceOver
> rotor to navigate by heading. Similar behaviour has also been noticed inside
> some apps. Our suspicion is that this is when an app uses HTML in the code
> that generates the page. One example of this behaviour in an app is the App
> Store app. In this app, if you go to the Today tab; double tap on “My
> Account”; and then double-tap on your name, the contents of the ‘Account’
> page and many that it link to are extremely difficult to navigate due to
> VoiceOver focus constantly ‘jumping’.
> *     When editing a typed note using a braille display, information about the
> text field will randomly display and cause VoiceOver to wrongly show the
> cursor at the top of the document.
> *     The ‘Radio’ tab in the native Music app contains some graphical UI
> elements which are not recognized by VoiceOver and can interfere with the
> movement of VoiceOver focus when swiping through the contents of this tab.
> This behaviour may understandably have you assume that there is nothing more
> on this screen, when in fact there is. To fully discover everything which is
> accessible on this screen, we recommend that you make use of the 3 finger
> swipe up or down to scroll the screen contents and explore using a
> combination of touch, the scroll bar, and swiping. Additionally, you are
> likely to encounter a number of “Play” and “Schedule” buttons on this tab,
> where the UI element they are associated with is not recognized or spoken by
> VoiceOver.
> *     There are a number of issues with the new widgets introduced with iOS 14
> and iPadOS 14. In some cases, this results in VoiceOver focus getting
> ‘stuck’ when swiping through widgets on the Today view or the Today view not
> scrolling to make all widgets accessible to VoiceOver. Also, on occasions,
> the VoiceOver rotor's Action menu may not be present or work as expected on
> stacked widgets.
> *     The performance of Apple's new VoiceOver recognition features is
> inconsistent and unreliable, particularly that of Screen Recognition. It
> should be noted that these features are a work-in-progress, and your mileage
> may vary. As things are now, you should expect to find that there will be
> situations where having one or more of these features enabled will provide a
> worse experience than having them disabled.
> *     The Detected Text feature that's part of the VoiceOver Recognition
> features does not work with braille displays.
>
> Minor Bugs
>
> *     There are situations system-wide where you will find that some VoiceOver
> voices will announce punctuation such as apostrophes and quotation marks
> when they should not be spoken. One workaround is to switch to a voice that
> does not exhibit this behaviour. A slightly more involved workaround is to
> add a second voice to VoiceOver's language rotor; set the voice in that
> secondary language to your preferred voice; then use the rotor to switch to
> your preferred voice in the secondary language. Note that it may take some
> trial and error to find a voice that will behave as expected for your
> specific region and language needs.
> *     After assigning a braille display command to VoiceOver Recognition,
> pressing the command will not toggle the feature.
> *     When using a braille display, after modifying the layout of the Home
> screen (such as adding or deleting an app), pressing space with dots 4-5-6
> no longer functions.
> *     On occasions, when editing the Today view, it is not possible to swipe 
> to
> the ‘Done’ and ‘Add Widget' buttons located at the top of the screen (note
> that they can be located by touch).
> *     On occasions, when editing the App Library screen available on iOS 14, 
> it
> is not possible to swipe to the ‘Done’ button located at the top of the
> screen (note that it can be located by touch).
> *     On occasions, VoiceOver will not announce “Control Center” when the
> Control Center is activated.
> *     In the Translate app that's new in iOS 14 and iPadOS 14, , the ‘drag’
> options available from the VoiceOver rotor when on translated items do not
> work.
> *     VoiceOver speaks “New line” when announcing the languages in the new
> Translate app. For example, “Spanish Spain” is spoken as “Spanish. New line.
> Spain.”
> *     In the Translate app, there is an unlabelled UI element on the Listen
> screen. If you activate the ‘Listen’ button and swipe to explore the screen,
> you will notice a dimmed text field, a 'Close’ button, as well as an element
> that is not identified by VoiceOver and which does not appear to do anything
> when activated.
> *     On iPhone or iPod touch and in the last page of a Home screen folder,
> performing a three-finger swipe to the left will wrongly load the App
> Library.
> *     When navigating the App Library on iPhone or iPod touch using the
> Containers option from VoiceOver's rotor, the page does not scroll beyond
> what is currently visually on screen.
> *     When running a Shortcut that prompts the user to select from a menu,
> VoiceOver users are unable to dismiss the menu with a gesture (something
> which can be done when VoiceOver is not enabled).
>
> If you encounter any additional accessibility bugs in iOS 14 or iPadOS 14,
> please let others know by posting a reply below. When doing so, please
> provide as much information as possible so that others know exactly what to
> expect; when and where the problem occurs; and any possible workarounds you
> have found.
>
> Accessibility Improvements in iOS 14 and iPadOS 14
>
> Our testing suggests that the following pre-existing accessibility bugs have
> been resolved or partially addressed in iOS 14 and iPadOS 14:
>
> *     Apple has continued to make improvements in regard to the consistency 
> and
> reliability of behavior when both Dark Mode and Smart Invert are enabled.
> There are still situations system-wide where the colors used may not be
> optimal or consistent in behavior, but our experience suggests that these
> are fewer in number. The color inversion of websites in Safari also appears
> to be improved; and our suspicion is that in some cases where this does not
> work as desired, it is actually due to the website rather than iOS and
> iPadOS.
> *     When deleting text from a text field, the audio and haptic feedback that
> follows each deletion is no longer that which should indicate that you have
> reached the start of the text field (unless you actually have).
> *     When answering a phone call using the 2-finger Double-Tap ('Magic Tap')
> gesture, the vibrations which accompany the ringer now stop as soon as the
> gesture is performed.
> *     When listening to an audio file in the Files app, flicking up or down on
> the playback scrubber control will now move the playback position.
> *     You can now navigate by line when composing a message in the Mail app,
> although there is no audible feedback as you would expect (and is what you
> hear when navigating by character or word).
> *     Apple has made some improvements in regard to the frequency and number 
> of
> situations in which VoiceOver focus will spontaneously 'jump' to another UI
> element. There are still some occasions when this does happen (most notably
> the behavior in Safari and some apps mentioned in our list of new moderate
> bugs), but this issue appears to be much improved.
> *     The Edit menu in VoiceOver's rotor is now more consistently and reliably
> present when VoiceOver focus is in a text field.
> *     The Two-Finger Double-Tap ('Magic Tap') gesture once again reliably 
> works
> to pause and resume audio playback in Safari.
>
>
>
>
>
>
>
> Richard
>
> "He that cannot forgive others breaks the bridge over which he must pass
> himself,” and we forget that only grace can break the cycle of ancient
> hatreds among peoples. (It is notable that while I have regretted not
> granting grace to others, I’ve never once regretted extending it.)" - Edward
> Herbert
>
>
>
> --
> 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:
> [email protected] <mailto:[email protected]> . Your list owner is Cara Quinn - you
> can reach Cara at [email protected] <mailto:[email protected]>
>
> The archives for this list can be searched at:
> http://www.mail-archive.com/[email protected]/
> ---
> 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 [email protected]
> <mailto:[email protected]> .
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/viphone/MWHPR17MB1981FBF9350BFD276764BF4AB73E0%40MWHPR17MB1981.namprd17.prod.outlook.com
> <https://groups.google.com/d/msgid/viphone/MWHPR17MB1981FBF9350BFD276764BF4AB73E0%40MWHPR17MB1981.namprd17.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:
> [email protected].  Your list owner is Cara Quinn - you can reach Cara at
> [email protected]
>
> The archives for this list can be searched at:
> http://www.mail-archive.com/[email protected]/
> ---
> 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 [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/viphone/00b601d68d0e%24dccfc1f0%24966f45d0%24%40gmail.com.
>


-- 
Connect with me on GoodReads:
www.goodreads.com/waynesbooks

-- 
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:  
[email protected].  Your list owner is Cara Quinn - you can reach Cara at 
[email protected]

The archives for this list can be searched at:
http://www.mail-archive.com/[email protected]/
--- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/viphone/CAOYhKtd91u7CTKQo61JTEgoEMpLnShhOUsof68GQkpmi%2BnMJYg%40mail.gmail.com.

Reply via email to