<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:"var\(--font-sans\)";}
@font-face
        {font-family:Georgia;
        panose-1:2 4 5 2 5 4 5 2 3 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        font-size:11.0pt;
        font-family:"Calibri",sans-serif;
        mso-ligatures:standardcontextual;}
h3
        {mso-style-priority:9;
        mso-style-link:"Heading 3 Char";
        mso-margin-top-alt:auto;
        margin-right:0in;
        mso-margin-bottom-alt:auto;
        margin-left:0in;
        font-size:13.5pt;
        font-family:"Calibri",sans-serif;
        font-weight:bold;}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:#0563C1;
        text-decoration:underline;}
span.Heading3Char
        {mso-style-name:"Heading 3 Char";
        mso-style-priority:9;
        mso-style-link:"Heading 3";
        font-family:"Calibri",sans-serif;
        font-weight:bold;}
span.EmailStyle22
        {mso-style-type:personal-reply;
        font-family:"Times New Roman",serif;
        color:windowtext;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;
        mso-ligatures:none;}
@page WordSection1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
        {page:WordSection1;}
/* List Definitions */
@list l0
        {mso-list-id:167252195;
        mso-list-template-ids:-183053428;}
@list l0:level1
        {mso-level-number-format:bullet;
        mso-level-text:\F0B7;
        mso-level-tab-stop:.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l0:level2
        {mso-level-number-format:bullet;
        mso-level-text:\F0B7;
        mso-level-tab-stop:1.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l0:level3
        {mso-level-number-format:bullet;
        mso-level-text:\F0B7;
        mso-level-tab-stop:1.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l0:level4
        {mso-level-number-format:bullet;
        mso-level-text:\F0B7;
        mso-level-tab-stop:2.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l0:level5
        {mso-level-number-format:bullet;
        mso-level-text:\F0B7;
        mso-level-tab-stop:2.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l0:level6
        {mso-level-number-format:bullet;
        mso-level-text:\F0B7;
        mso-level-tab-stop:3.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l0:level7
        {mso-level-number-format:bullet;
        mso-level-text:\F0B7;
        mso-level-tab-stop:3.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l0:level8
        {mso-level-number-format:bullet;
        mso-level-text:\F0B7;
        mso-level-tab-stop:4.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l0:level9
        {mso-level-number-format:bullet;
        mso-level-text:\F0B7;
        mso-level-tab-stop:4.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l1
        {mso-list-id:685323364;
        mso-list-template-ids:1555064414;}
@list l1:level1
        {mso-level-number-format:bullet;
        mso-level-text:\F0B7;
        mso-level-tab-stop:.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l1:level2
        {mso-level-number-format:bullet;
        mso-level-text:\F0B7;
        mso-level-tab-stop:1.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l1:level3
        {mso-level-number-format:bullet;
        mso-level-text:\F0B7;
        mso-level-tab-stop:1.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l1:level4
        {mso-level-number-format:bullet;
        mso-level-text:\F0B7;
        mso-level-tab-stop:2.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l1:level5
        {mso-level-number-format:bullet;
        mso-level-text:\F0B7;
        mso-level-tab-stop:2.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l1:level6
        {mso-level-number-format:bullet;
        mso-level-text:\F0B7;
        mso-level-tab-stop:3.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l1:level7
        {mso-level-number-format:bullet;
        mso-level-text:\F0B7;
        mso-level-tab-stop:3.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l1:level8
        {mso-level-number-format:bullet;
        mso-level-text:\F0B7;
        mso-level-tab-stop:4.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l1:level9
        {mso-level-number-format:bullet;
        mso-level-text:\F0B7;
        mso-level-tab-stop:4.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l2
        {mso-list-id:926421682;
        mso-list-template-ids:-911540592;}
@list l3
        {mso-list-id:1388988681;
        mso-list-template-ids:1781534228;}
@list l4
        {mso-list-id:1538196010;
        mso-list-template-ids:1795477830;}
@list l4:level1
        {mso-level-tab-stop:.5in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l4:level2
        {mso-level-tab-stop:1.0in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l4:level3
        {mso-level-tab-stop:1.5in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l4:level4
        {mso-level-tab-stop:2.0in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l4:level5
        {mso-level-tab-stop:2.5in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l4:level6
        {mso-level-tab-stop:3.0in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l4:level7
        {mso-level-tab-stop:3.5in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l4:level8
        {mso-level-tab-stop:4.0in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l4:level9
        {mso-level-tab-stop:4.5in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l5
        {mso-list-id:1574193456;
        mso-list-template-ids:-417700812;}
@list l5:level1
        {mso-level-tab-stop:.5in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l5:level2
        {mso-level-tab-stop:1.0in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l5:level3
        {mso-level-tab-stop:1.5in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l5:level4
        {mso-level-tab-stop:2.0in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l5:level5
        {mso-level-tab-stop:2.5in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l5:level6
        {mso-level-tab-stop:3.0in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l5:level7
        {mso-level-tab-stop:3.5in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l5:level8
        {mso-level-tab-stop:4.0in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l5:level9
        {mso-level-tab-stop:4.5in;
        mso-level-number-position:left;
        text-indent:-.25in;}
ol
        {margin-bottom:0in;}
ul
        {margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link="#0563C1" vlink="#954F72" style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'>            Oh, definitely agreed—just saying how it is…<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'>Nicole<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='mso-ligatures:none'>From:</span></b><span style='mso-ligatures:none'> NFBCS <nfbcs-bounces@nfbnet.org> <b>On Behalf Of </b>Gary Wunder via NFBCS<br><b>Sent:</b> Tuesday, September 19, 2023 3:35 PM<br><b>To:</b> 'NFB in Computer Science Mailing List' <nfbcs@nfbnet.org><br><b>Cc:</b> Gary Wunder <gwunder@earthlink.net><br><b>Subject:</b> Re: [NFBCS] IOS 17 rolling out tomorrow<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'>A focus problem in which one can tap on the wrong item because an essential function of VoiceOver is not working should be considered major. Not arguing, but just saying that there is a real limit to how valuable we are in the scheme of things with these tech corporations.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='mso-ligatures:none'>From:</span></b><span style='mso-ligatures:none'> NFBCS <<a href="mailto:nfbcs-bounces@nfbnet.org">nfbcs-bounces@nfbnet.org</a>> <b>On Behalf Of </b>Nicole Torcolini via NFBCS<br><b>Sent:</b> Tuesday, September 19, 2023 5:28 PM<br><b>To:</b> 'NFB in Computer Science Mailing List' <<a href="mailto:nfbcs@nfbnet.org">nfbcs@nfbnet.org</a>><br><b>Cc:</b> Nicole Torcolini <<a href="mailto:torcolini@comcast.net">torcolini@comcast.net</a>><br><b>Subject:</b> Re: [NFBCS] IOS 17 rolling out tomorrow<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'>            Having worked in the tech industry, I can say that, once a release date is set, companies try to stick to that—only moving it for major problems—so relatively minor stuff often slips through. And, yes, sadly, many accessibility bugs are demoted to “minor” unless they are really bad.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='mso-ligatures:none'>From:</span></b><span style='mso-ligatures:none'> NFBCS <<a href="mailto:nfbcs-bounces@nfbnet.org">nfbcs-bounces@nfbnet.org</a>> <b>On Behalf Of </b>Gary Wunder via NFBCS<br><b>Sent:</b> Tuesday, September 19, 2023 2:14 PM<br><b>To:</b> 'NFB in Computer Science Mailing List' <<a href="mailto:nfbcs@nfbnet.org">nfbcs@nfbnet.org</a>><br><b>Cc:</b> Gary Wunder <<a href="mailto:gwunder@earthlink.net">gwunder@earthlink.net</a>><br><b>Subject:</b> Re: [NFBCS] IOS 17 rolling out tomorrow<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'>One is reminded of Jonathan’s speech that is on the website and appears as the first article in the October Monitor. As he said, no one expects a program to be completely bug free, but the flipside is that when I was a programmer, we sometimes made the decision that sometimes one or more of them were show stoppers and we would fix before release. I love my iPhone, but I do not  think that the commitment to a smooth VoiceOver experience is hi in the corporation. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='mso-ligatures:none'>From:</span></b><span style='mso-ligatures:none'> NFBCS <<a href="mailto:nfbcs-bounces@nfbnet.org">nfbcs-bounces@nfbnet.org</a>> <b>On Behalf Of </b>Curtis Chong via NFBCS<br><b>Sent:</b> Sunday, September 17, 2023 5:08 PM<br><b>To:</b> 'NFB in Computer Science Mailing List' <<a href="mailto:nfbcs@nfbnet.org">nfbcs@nfbnet.org</a>><br><b>Cc:</b> Curtis Chong <<a href="mailto:chong.curtis@gmail.com">chong.curtis@gmail.com</a>>; <a href="mailto:nancy.l.coffman@gmail.com">nancy.l.coffman@gmail.com</a><br><b>Subject:</b> Re: [NFBCS] IOS 17 rolling out tomorrow<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'>Hello:<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'>Here are the bug reports as shown on the Applevis website.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p><h3 style='background:white'><span style='font-family:"var\(--font-sans\)";color:black'>Serious Bugs</span><span style='font-family:"var\(--font-sans\)"'><o:p></o:p></span></h3><p style='background:white;box-sizing: border-box;margin-block-start: var(--sp2);margin-block-end: var(--sp2);font-variant-ligatures: normal;font-variant-caps: normal;orphans: 2;text-align:start;widows: 2;-webkit-text-stroke-width: 0px;text-decoration-thickness: initial;text-decoration-style: initial;text-decoration-color: initial;word-spacing:0px'><span style='font-size:13.5pt;font-family:"Georgia",serif;color:#2B353B'>Some users may encounter <a href="https://www.applevis.com/bugs/ios/intermittent-failure-voiceover-double-tap-triple-tap-gestures">an intermittent issue that affects the operation of the VoiceOver double-tap gesture on iOS 17.</a> When attempting to double-tap an actionable interface element, the resulting behaviour experienced is as if the user touched with 1 finger the area of the screen where they performed the gesture, rather than performed a double tap on the element that VoiceOver focus was on.<o:p></o:p></span></p><p style='background:white;box-sizing: border-box;margin-block-start: var(--sp2);margin-block-end: var(--sp2);font-variant-ligatures: normal;font-variant-caps: normal;orphans: 2;text-align:start;widows: 2;-webkit-text-stroke-width: 0px;text-decoration-thickness: initial;text-decoration-style: initial;text-decoration-color: initial;word-spacing:0px'><span style='font-size:13.5pt;font-family:"Georgia",serif;color:#2B353B'>For instance, with VoiceOver focus on a button within Safari's toolbar, performing a double tap might result in VoiceOver speaking the text content of the webpage that was under your finger at the time you performed the gesture, instead of activating the intended button in the toolbar.<o:p></o:p></span></p><p style='background:white;box-sizing: border-box;margin-block-start: var(--sp2);margin-block-end: var(--sp2);font-variant-ligatures: normal;font-variant-caps: normal;orphans: 2;text-align:start;widows: 2;-webkit-text-stroke-width: 0px;text-decoration-thickness: initial;text-decoration-style: initial;text-decoration-color: initial;word-spacing:0px'><span style='font-size:13.5pt;font-family:"Georgia",serif;color:#2B353B'>When this behaviour occurs, VoiceOver focus typically moves to the interface element that was spoken. It's necessary to relocate focus back to the intended element before attempting the double-tap again. While this movement of focus may sound similar to the longstanding issue for many users involving VoiceOver focus, the issue described here is new and noticeably different when experienced.<o:p></o:p></span></p><p style='background:white;box-sizing: border-box;margin-block-start: var(--sp2);margin-block-end: var(--sp2);font-variant-ligatures: normal;font-variant-caps: normal;orphans: 2;text-align:start;widows: 2;-webkit-text-stroke-width: 0px;text-decoration-thickness: initial;text-decoration-style: initial;text-decoration-color: initial;word-spacing:0px'><span style='font-size:13.5pt;font-family:"Georgia",serif;color:#2B353B'>This issue is not limited to specific apps; it occurs across native and third-party applications. It impacts various types of actionable interface elements, including activating items on the VoiceOver rotor's action menu.<o:p></o:p></span></p><p style='background:white;box-sizing: border-box;margin-block-start: var(--sp2);margin-block-end: var(--sp2);font-variant-ligatures: normal;font-variant-caps: normal;orphans: 2;text-align:start;widows: 2;-webkit-text-stroke-width: 0px;text-decoration-thickness: initial;text-decoration-style: initial;text-decoration-color: initial;word-spacing:0px'><span style='font-size:13.5pt;font-family:"Georgia",serif;color:#2B353B'>In some cases, the double tap might function correctly on the second attempt, while in others, it might require multiple tries before registering accurately.<o:p></o:p></span></p><p style='background:white;box-sizing: border-box;margin-block-start: var(--sp2);margin-block-end: var(--sp2);font-variant-ligatures: normal;font-variant-caps: normal;orphans: 2;text-align:start;widows: 2;-webkit-text-stroke-width: 0px;text-decoration-thickness: initial;text-decoration-style: initial;text-decoration-color: initial;word-spacing:0px'><span style='font-size:13.5pt;font-family:"Georgia",serif;color:#2B353B'>The underlying issue can also cause problems with the operation of the 1 finger triple-tap gesture and the 1 finger double-tap and hold.<o:p></o:p></span></p><p style='background:white;box-sizing: border-box;margin-block-start: var(--sp2);margin-block-end: var(--sp2);font-variant-ligatures: normal;font-variant-caps: normal;orphans: 2;text-align:start;widows: 2;-webkit-text-stroke-width: 0px;text-decoration-thickness: initial;text-decoration-style: initial;text-decoration-color: initial;word-spacing:0px'><span style='font-size:13.5pt;font-family:"Georgia",serif;color:#2B353B'>It is important to note that this behaviour is not consistent—it doesn’t happen every time. Based on our testing, there is no discernible pattern to predict when it will occur or how frequently. But based on experience, it likely won't be highly frequent for impacted users.<o:p></o:p></span></p><p style='background:white;box-sizing: border-box;margin-block-start: var(--sp2);margin-block-end: var(--sp2);font-variant-ligatures: normal;font-variant-caps: normal;orphans: 2;text-align:start;widows: 2;-webkit-text-stroke-width: 0px;text-decoration-thickness: initial;text-decoration-style: initial;text-decoration-color: initial;word-spacing:0px'><span style='font-size:13.5pt;font-family:"Georgia",serif;color:#2B353B'>While serious, this issue does not appear to be widespread Based on our tracking of user experiences during the beta cycle. It has been encountered by five members of our Editorial Team. Additionally, A few other users across the wider community have reported experiencing this behaviour, including Jonathon Mosen and a listener to his <a href="https://www.livingblindfully.com/lb0244transcript/">Living Blindfully podcast.</a> Beyond these known cases, there has been no indication that a significant portion of users are affected. Overall, current evidence suggests this is an intermittent issue impacting a small subset of users rather than something everyone should expect to encounter.<o:p></o:p></span></p><p style='background:white;box-sizing: border-box;margin-block-start: var(--sp2);margin-block-end: var(--sp2);font-variant-ligatures: normal;font-variant-caps: normal;orphans: 2;text-align:start;widows: 2;-webkit-text-stroke-width: 0px;text-decoration-thickness: initial;text-decoration-style: initial;text-decoration-color: initial;word-spacing:0px'><span style='font-size:13.5pt;font-family:"Georgia",serif;color:#2B353B'>Adjusting the Double-Tap Timeout in Settings > Accessibility > VoiceOver has been <a href="https://www.applevis.com/comment/152899#comment-152899">suggested as a partial workaround for the issue.</a> However, based on limited testing, changing this setting does not appear to resolve the underlying problem. While you may want to experiment with adjusting the Timeout interval, keep in mind that this could disrupt your natural double-tap muscle memory which is accustomed to the default timing. Any benefits in reliability would need to outweigh the effort required to learn the new timing. At this point, the setting change seems unlikely to provide a sufficient or permanent fix.<o:p></o:p></span></p><p style='background:white;box-sizing: border-box;margin-block-start: var(--sp2);margin-block-end: var(--sp2);font-variant-ligatures: normal;font-variant-caps: normal;orphans: 2;text-align:start;widows: 2;-webkit-text-stroke-width: 0px;text-decoration-thickness: initial;text-decoration-style: initial;text-decoration-color: initial;word-spacing:0px'><span style='font-size:13.5pt;font-family:"Georgia",serif;color:#2B353B'>We chose to rate this issue as serious because of the importance of the double-tap gesture and its frequency of use. Moreover, our assessment has taken into account the potential impact of this behaviour on individuals who are new to or less familiar with iOS. These users might reasonably assume that the behaviour is due to them not correctly performing the double tap gesture, possibly leading them to conclude that using an iPhone is more difficult than it actually is.<o:p></o:p></span></p><h3 style='background:white;box-sizing: border-box;font-size:1.5rem;line-height:var(--sp2);margin-block: var(--sp2);color:var(--color-text-neutral-loud);font-variant-ligatures: normal;font-variant-caps: normal;orphans: 2;text-align:start;widows: 2;-webkit-text-stroke-width: 0px;text-decoration-thickness: initial;text-decoration-style: initial;text-decoration-color: initial;word-spacing:0px'><span style='font-family:"var\(--font-sans\)";color:black'>Moderate Bugs</span><span style='font-family:"var\(--font-sans\)"'><o:p></o:p></span></h3><ol start=1 type=1><li class=MsoNormal style='color:#2B353B;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l4 level1 lfo3;background:white;box-sizing: border-box'><span style='font-size:13.5pt;font-family:"Georgia",serif'><a href="https://www.applevis.com/bugs/ios/inconsistent-voiceover-focus-navigation-weather-app-main-screen">When using VoiceOver to navigate the main screen of the native Weather app, the movement of focus is inconsistent and unreliable.</a> Specifically, focus can become stuck on an interface element, falsely suggesting there are no further elements to the right or left. Or focus may unexpectedly jump over elements as if they don't exist on the screen. As a workaround, you will need to explore the screen by touch in order to locate all weather data.<o:p></o:p></span></li><li class=MsoNormal style='color:#2B353B;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l4 level1 lfo3;background:white;box-sizing: border-box'><span style='font-size:13.5pt;font-family:"Georgia",serif'><a href="https://www.applevis.com/bugs/ios/voiceover-rotor-drag-action-inconsistent-when-rearranging-home-screen-icons">Using the "drag" action in the VoiceOver rotor to rearrange app icons on the Home Screen often does not work as expected.</a> Specifically, when attempting to drag an app icon to a new position and place it before or after another app, the dragged app frequently ends up in a folder with the target app rather than moving to the desired location. It's also been reported that on occasions some drag action options, such as “drop before” or “drop after”, may not always be available.<o:p></o:p></span></li><li class=MsoNormal style='color:#2B353B;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l4 level1 lfo3;background:white;box-sizing: border-box'><span style='font-size:13.5pt;font-family:"Georgia",serif'><a href="https://www.applevis.com/bugs/ios/voiceover-speech-output-will-occasions-stop-after-phone-calls">An intermittent bug can cause VoiceOver speech to stop after ending a phone call, while sound effects remain.</a> There is no clear pattern as to when this issue occurs. Similar behaviour has also been reported when using WhatsApp.<o:p></o:p></span></li><li class=MsoNormal style='color:#2B353B;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l4 level1 lfo3;background:white;box-sizing: border-box'><span style='font-size:13.5pt;font-family:"Georgia",serif'><a href="https://www.applevis.com/bugs/ios/incoming-banner-notifications-interrupt-voiceover-speech-when-speak-notifications-setting">Incoming banner notifications interrupt VoiceOver speech when the “Speak Notifications” accessibility setting is enabled.</a> Specifically, any time a new notification banner appears, VoiceOver will immediately stop reading the current on-screen text or menu to announce the notification. This interrupts VoiceOver mid-sentence or mid-menu in a disruptive manner. In previous iOS versions, VoiceOver would finish reading the current paragraph, sentence, or menu before speaking a new notification. This prevented jarring mid-sentence interruptions.<o:p></o:p></span></li><li class=MsoNormal style='color:#2B353B;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l4 level1 lfo3;background:white;box-sizing: border-box'><span style='font-size:13.5pt;font-family:"Georgia",serif'>The new predictive text feature in iOS 17 provides recommended words inline as you type using the onscreen keyboard. There are verbosity settings that allow VoiceOver users to control what happens when predictive text appears and when predictive text feedback is entered. However, <a href="https://www.applevis.com/bugs/ios/predictive-text-verbosity-settings-do-not-consistently-behave-configured">some users report that these verbosity settings are not being applied consistently across different apps.</a> When the predictive text verbosity setting is set to speak recommendations, some VoiceOver users report that recommendations are silent in certain apps, even though they expect them to be spoken. Conversely, other users have found that with the predictive text setting configured to not speak recommendations, VoiceOver will still read out the recommendations in some apps like Mail.<o:p></o:p></span></li><li class=MsoNormal style='color:#2B353B;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l4 level1 lfo3;background:white;box-sizing: border-box'><span style='font-size:13.5pt;font-family:"Georgia",serif'><a href="https://www.applevis.com/bugs/ios/it-not-possible-mark-certain-actions-favorites-system-share-sheet">It is not possible to mark certain actions as favourites in the system share sheet due to the ‘Insert’ button and checkbox being recognised as part of a single element.</a> Specifically, when editing the list of actions to be shown in the Share sheet and focusing on an action that can be enabled/disabled via a checkbox, VoiceOver announces the checkbox state and "Insert" together rather than separately. Double tapping toggles the checkbox but does not allow inserting the action as a favourite.<o:p></o:p></span></li></ol><h3 style='background:white;box-sizing: border-box;font-size:1.5rem;line-height:var(--sp2);margin-block: var(--sp2);color:var(--color-text-neutral-loud);font-variant-ligatures: normal;font-variant-caps: normal;orphans: 2;text-align:start;widows: 2;-webkit-text-stroke-width: 0px;text-decoration-thickness: initial;text-decoration-style: initial;text-decoration-color: initial;word-spacing:0px'><span style='font-family:"var\(--font-sans\)";color:black'>Minor Bugs</span><span style='font-family:"var\(--font-sans\)"'><o:p></o:p></span></h3><ol start=1 type=1><li class=MsoNormal style='color:#2B353B;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l5 level1 lfo6;background:white;box-sizing: border-box'><span style='font-size:13.5pt;font-family:"Georgia",serif'><a href="https://www.applevis.com/bugs/ios/voiceover-fails-announce-time-when-waking-iphone-if-notifications-are-present">VoiceOver no longer announces the time when the device wakes if there are pending notifications. Instead, it states the number of notifications present.</a><o:p></o:p></span></li><li class=MsoNormal style='color:#2B353B;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l5 level1 lfo6;background:white;box-sizing: border-box'><span style='font-size:13.5pt;font-family:"Georgia",serif'><a href="https://www.applevis.com/bugs/ios/when-performing-voiceover-find-braille-display-after-typing-text-pressing-enter-will-not">When using VoiceOver Find with a braille display, searching does not function as expected.</a> Specifically, pressing dot 8 does nothing after typing in a VoiceOver Find query with a connected braille display. The search is not carried out. As a workaround, prior to pressing dot 8 to execute the find function, press dots 2-7 followed by space with dot 8. Your search will now work as expected.<o:p></o:p></span></li><li class=MsoNormal style='color:#2B353B;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l5 level1 lfo6;background:white;box-sizing: border-box'><span style='font-size:13.5pt;font-family:"Georgia",serif'><a href="https://www.applevis.com/bugs/ios/voiceover-fails-announce-read-when-marking-emails-read-rotor-native-mail-app">When using the VoiceOver rotor to mark an email as read in the native Mail app, VoiceOver fails to provide clear confirmation feedback.</a> Instead of announcing "read" to confirm the action, VoiceOver speaks an unclear and incomprehensible word or phrase.<o:p></o:p></span></li><li class=MsoNormal style='color:#2B353B;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l5 level1 lfo6;background:white;box-sizing: border-box'><span style='font-size:13.5pt;font-family:"Georgia",serif'><a href="https://www.applevis.com/bugs/ios/voiceover-announces-incorrect-volume-level-after-adjustments-control-center">When you adjusts the volume slider in Control Center using the flick gesture, VoiceOver announces the previous volume level rather than the new level after the adjustment.</a> Specifically, when a user focuses on the volume slider in Control Center with VoiceOver enabled, then performs a 1 finger flick up or down to change the volume, VoiceOver speaks the volume percentage. However, instead of announcing the new volume level, VoiceOver reads out the volume level prior to the flick gesture adjustment.<o:p></o:p></span></li><li class=MsoNormal style='color:#2B353B;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l5 level1 lfo6;background:white;box-sizing: border-box'><span style='font-size:13.5pt;font-family:"Georgia",serif'><a href="https://www.applevis.com/bugs/ios/voiceover-incorrectly-prepends-website-names-remove-when-editing-safari-bookmarks">When editing Safari bookmarks, the bookmark names and reorder icon label are incorrectly announced with "remove" prepended.</a><o:p></o:p></span></li><li class=MsoNormal style='color:#2B353B;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l5 level1 lfo6;background:white;box-sizing: border-box'><span style='font-size:13.5pt;font-family:"Georgia",serif'><a href="https://www.applevis.com/bugs/ios/double-tapping-safari-bookmarks-or-folders-edit-mode-activates-delete-button-instead-edit">Double tapping on a bookmark or folder title in Safari's edit bookmarks screen incorrectly activates a delete button rather than opening the edit view.</a> As a workaround, the contextual menu for actions includes an Edit option.<o:p></o:p></span></li><li class=MsoNormal style='color:#2B353B;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l5 level1 lfo6;background:white;box-sizing: border-box'><span style='font-size:13.5pt;font-family:"Georgia",serif'><a href="https://www.applevis.com/bugs/ios/some-users-may-experience-less-descriptive-labels-control-center-toggles-including-lock">Some users may experience inconsistent and less descriptive labelling of Control Center toggles.</a> For example, the toggle for locking device screen orientation may simply be announced as “Locked” or “Unlocked” rather than using the more descriptive label “Lock Rotation” that was present in previous iOS versions. This degraded labelling does not appear isolated to any specific VoiceOver voice. Users of the Alex voice have reported experiencing the unclear labels, while others using Alex still hear the expected descriptive labels. Additionally, isolated reports indicate similar degraded labelling for other Control Center toggles beyond just the orientation lock. This bug seems to manifest unpredictably, affecting only a small subset of iOS 17 users. The inconsistent experience suggests an underlying issue, rather than a deliberate change in labelling.<o:p></o:p></span></li></ol><h3 style='background:white;box-sizing: border-box;font-size:1.5rem;line-height:var(--sp2);margin-block: var(--sp2);color:var(--color-text-neutral-loud);font-variant-ligatures: normal;font-variant-caps: normal;orphans: 2;text-align:start;widows: 2;-webkit-text-stroke-width: 0px;text-decoration-thickness: initial;text-decoration-style: initial;text-decoration-color: initial;word-spacing:0px'><span style='font-family:"var\(--font-sans\)";color:black'>Other Reported Issues</span><span style='font-family:"var\(--font-sans\)"'><o:p></o:p></span></h3><p style='background:white;box-sizing: border-box;margin-block-start: var(--sp2);margin-block-end: var(--sp2);font-variant-ligatures: normal;font-variant-caps: normal;orphans: 2;text-align:start;widows: 2;-webkit-text-stroke-width: 0px;text-decoration-thickness: initial;text-decoration-style: initial;text-decoration-color: initial;word-spacing:0px'><span style='font-size:13.5pt;font-family:"Georgia",serif;color:#2B353B'>The Messages app will now automatically transcribe audio messages into plain text, a valuable addition for deaf-blind users. However, some users report the transcript preview and ‘Show More” button appear visually but cannot be accessed through Braille commands, VoiceOver gestures or menus. Our testing could not reproduce this inaccessibility - VoiceOver consistently announced no transcription available for our audio messages. As we were unable to independently validate the issue, we have not filed a formal bug report yet. We will continue investigating this issue to clarify its specific behaviour.<o:p></o:p></span></p><p style='background:white;box-sizing: border-box;margin-block-start: var(--sp2);margin-block-end: var(--sp2);font-variant-ligatures: normal;font-variant-caps: normal;orphans: 2;text-align:start;widows: 2;-webkit-text-stroke-width: 0px;text-decoration-thickness: initial;text-decoration-style: initial;text-decoration-color: initial;word-spacing:0px'><span style='font-size:13.5pt;font-family:"Georgia",serif;color:#2B353B'>Additional user-reported issues that we have not independently validated are discussed in these forum threads. While our team has not personally reproduced or confirmed these bugs, the threads are worth reading to potentially identify other problems you may encounter:<o:p></o:p></span></p><ul type=disc><li class=MsoNormal style='color:#2B353B;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo9;background:white;box-sizing: border-box'><span style='font-size:13.5pt;font-family:"Georgia",serif'><a href="https://www.applevis.com/forum/apple-beta-releases/rcs-are-now-available-ios-17-macos-14-watchos-10-more">RC's are now available for iOS 17, macOS 14, watchOS 10, and more!</a><o:p></o:p></span></li><li class=MsoNormal style='color:#2B353B;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo9;background:white;box-sizing: border-box'><span style='font-size:13.5pt;font-family:"Georgia",serif'><a href="https://www.applevis.com/forum/apple-beta-releases/braille-screen-input-not-reporting-deleted-word-if-cursor-not-end-text">Braille Screen input not reporting deleted word if cursor not at end of text</a><o:p></o:p></span></li><li class=MsoNormal style='color:#2B353B;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo9;background:white;box-sizing: border-box'><span style='font-size:13.5pt;font-family:"Georgia",serif'><a href="https://www.applevis.com/forum/apple-beta-releases/while-using-voiceover-bluetooth-keyboard-unable-review-or-edit-text-notes">While using Voiceover and a bluetooth keyboard, unable to review or edit text in notes</a><o:p></o:p></span></li></ul><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'>Cordially,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'>Curtis Chong<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='mso-ligatures:none'>From:</span></b><span style='mso-ligatures:none'> NFBCS <<a href="mailto:nfbcs-bounces@nfbnet.org">nfbcs-bounces@nfbnet.org</a>> <b>On Behalf Of </b>nancy.l.coffman--- via NFBCS<br><b>Sent:</b> Sunday, September 17, 2023 4:59 PM<br><b>To:</b> 'NFB in Computer Science Mailing List' <<a href="mailto:nfbcs@nfbnet.org">nfbcs@nfbnet.org</a>><br><b>Cc:</b> <a href="mailto:nancy.l.coffman@gmail.com">nancy.l.coffman@gmail.com</a><br><b>Subject:</b> [NFBCS] IOS 17 rolling out tomorrow<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Hello:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>There are some factors you may want to consider before you install IOS 17 which will begin rolling out on Monday, September 18. The accessibility bug report can be found at<o:p></o:p></p><p class=MsoNormal><a href="https://www.applevis.com/blog/ios-17-ipados-17-accessibility-report-voiceover-braille-low-vision-issues-improvements">https://www.applevis.com/blog/ios-17-ipados-17-accessibility-report-voiceover-braille-low-vision-issues-improvements</a><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>There are some Voiceover bugs that started in earlier IOS versions and have not been fixed. Others are new and should be taken into consideration before installing the update.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Nancy Coffman<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>