Fair, and you are right that nothing has been started and there is no box
you are typing in.

My wording was loose, so let me tighten it. The thing that claims the
arrows does not have to be a field you type into. It only has to be text
VoiceOver can walk through a character or a word at a time, because walking
through text is exactly what those arrows do. The body of a message you
have just received is text like any other. So the question is not whether a
field is open, it is whether the focus is sitting on the words.

There is a second possibility that needs no field to be open either. A
conversation screen carries the box for your reply at the bottom whether
you use it or not, so focus landing there as the message opens would
produce the same thing.

Both of those come apart with the single press I asked about, and that is
still the only thing separating your reading from mine. The moment QuickNav
switches itself off in a message you are only reading, press left or right
once and listen. A character or a word out of the message means the focus
is in the text, and that is the whole answer. The next item, or a heading,
means the focus is not in the text, your reading is right, my explanation
is dead, and something else is switching QuickNav off that is worth chasing
properly.

One press settles it, and your ears are better evidence than my theory.

Does that first press speak a character of the message, or the next item?

VaShaun

On Fri, Oct 23, 2026 10:23 AM, [email protected] wrote:

> I can see that if I were coming back to a text message I had already
> started. F I just received a new text then when I open that text message
> there should not be any open fields.
>
>
>
> *From:* [email protected] <[email protected]> *On Behalf Of
> *vashaun jones
> *Sent:* Friday, October 23, 2026 8:07 AM
> *To:* [email protected]
> *Subject:* Re: bt keyboard and iOS27.1
>
>
>
> You are right, and the distinction you just drew is the part that matters.
>
> What I described covers a box you are typing into. The arrows are needed
> there to move the text cursor, so QuickNav has to step aside. It does not
> explain a message you were only reading, because nothing in there is being
> typed and nothing needs the arrows for a cursor. So your correction stands,
> and my answer only covered half of what you are seeing.
>
> What would explain the reading case is not QuickNav changing, but where
> the focus lands when the message opens. If the focus lands inside the body
> text rather than on the message as one whole im, then the text claims the
> arrows exactly as a compose box does, and QuickNav steps aside in aI can
>  place where it never used to. Same mechanism, different place, and the
> place is the thing that changed.
>
> You can test that with what you already have. Open a message you are only
> reading, and the moment QuickNav switches itself off, press left or right
> once and listen to what comes back. A character or a word out of the
> message means the focus is sitting inside the text, which is the whole
> explanation. The next item or a heading means the focus is not inside the
> text, and then something else is switching QuickNav off and my reading is
> wrong.
>
> Keep the one press versus two as its own symptom. Your before and after is
> better evidence than the guess I offered this morning.
>
> Jenn seeing it too, and seeing it with braille displays as well, says this
> is not your keyboard and not your pairing.
>
> In a message you are only reading, does that first arrow press speak a
> character or word of the message, or the next item?
>
> VaShaun
>
>
>
> On Fri, Oct 23, 2026 08:35 AM, [email protected] wrote:
>
> This was not happening before the update. When I entered a text message to
> read the complete message quick nav stayed on. It only turned off when I
> entered a text field to type. And then I only had to press the arrows once
> and it came back on.
>
>
>
> *From:* [email protected] <[email protected]> *On Behalf Of
> *vashaun jones
> *Sent:* Friday, October 23, 2026 7:06 AM
> *To:* [email protected]
> *Subject:* Re: bt keyboard and iOS27.1
>
>
>
> You are not doing anything wrong, and the first half of this is not a
> fault at all.
>
> QuickNav is a mode that changes what the arrow keys mean. With it on, left
> and right move VoiceOver from one item to the next. Inside a text field
> those same two keys are needed to move the text cursor through what you
> have typed. Two jobs, two keys, and they cannot both have them. In an edit
> field the text cursor wins, so QuickNav steps aside the moment the focus
> lands there. That is also why touching the screen does not do it. A touch
> gesture is not an arrow key, so there is no conflict to settle.
>
> The part worth looking at is having to press twice. One press should do
> it. My guess, and it is a guess, is that the first attempt is being read by
> the text field as two ordinary arrow presses rather than as the two keys
> arriving together, left then right, which cancel each other out and leave
> the cursor where it was. That would be silent, and it would look exactly
> like nothing happening.
>
> You can check that yourself and it costs nothing. In a text field, press
> both arrows at the same instant rather than one just after the other, and
> listen for whether the first attempt announces anything at all. Silence on
> the first and an announcement on the second is the stagger. An announcement
> on both would mean something else is going on.
>
> On whether 27.1 brought this, the switching off is the design and is not
> new, but the two presses might be. Has anyone still on 27.0 got a Bluetooth
> keyboard to try it on?
>
> VaShaun
>
>
>
> On Fri, Oct 23, 2026 07:55 AM, [email protected] wrote:
>
> Is anyone else other than me having issues with quickNav and voiceover?
> When I enter a text message quick nav immediately turns off. I have to
> press the left and right arrows twice to get it back on again. The same
> when I enter an edit field. I don’t have this problem when I touch the
> screen.
>
> --
> 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 visit https://groups.google.com/d/
> msgid/viphone/014a01dd62e5%2474b95a00%245e2c0e00%24%40gmail.com
> <https://groups.google.com/d/msgid/viphone/014a01dd62e5%2474b95a00%245e2c0e00%24%40gmail.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 visit https://groups.google.com/d/
> msgid/viphone/CAL5m5AF7sMBo-yybBpNgXJoc5Vykrx4pd-bx-OB2Y%
> 2B9NzZ2Gvw%40mail.gmail.com
> <https://groups.google.com/d/msgid/viphone/CAL5m5AF7sMBo-yybBpNgXJoc5Vykrx4pd-bx-OB2Y%2B9NzZ2Gvw%40mail.gmail.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 visit https://groups.google.com/d/
> msgid/viphone/047301dd62ea%24f3d22dd0%24db768970%24%40gmail.com
> <https://groups.google.com/d/msgid/viphone/047301dd62ea%24f3d22dd0%24db768970%24%40gmail.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 visit https://groups.google.com/d/
> msgid/viphone/CAL5m5AFWszQvx-GJqnxb1o0bzVk68_PaEy6aupSOu86%
> 2BFn-L2A%40mail.gmail.com
> <https://groups.google.com/d/msgid/viphone/CAL5m5AFWszQvx-GJqnxb1o0bzVk68_PaEy6aupSOu86%2BFn-L2A%40mail.gmail.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 visit https://groups.google.com/d/
> msgid/viphone/045201dd62fa%2403855a40%240a900ec0%24%40gmail.com
> <https://groups.google.com/d/msgid/viphone/045201dd62fa%2403855a40%240a900ec0%24%40gmail.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 visit 
https://groups.google.com/d/msgid/viphone/CAL5m5AGvE0%2Bt3GYaS%3D1xKxzunf0fK1pnACKb6tTTqaUnu0aVZA%40mail.gmail.com.

Reply via email to