<html><head><meta http-equiv="content-type" content="text/html; charset=us-ascii"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">Hi Brian, please contact me off list regarding this issue, NFDB might be asking you, to explain iOS 17 problems at the next public DeafBlind division meeting on Oct 7 2023.<div><br></div><div><p class="MsoNormal" style="margin: 0in 0in 8pt; line-height: 15.693334px; font-size: 11pt; font-family: Calibri, sans-serif;"><o:p> </o:p></p><p class="MsoNormal" style="margin: 0in 0in 8pt; line-height: 15.693334px; font-size: 11pt; font-family: Calibri, sans-serif;"><o:p> </o:p></p><p class="MsoNormal" style="margin: 0in 0in 8pt; line-height: 15.693334px; font-size: 11pt; font-family: Calibri, sans-serif;">Maurice Mines, President <o:p></o:p></p><p class="MsoNormal" style="margin: 0in 0in 8pt; line-height: 15.693334px; font-size: 11pt; font-family: Calibri, sans-serif;">National Federation of the Blind Deaf-Blind Division <o:p></o:p></p><p class="MsoNormal" style="margin: 0in 0in 8pt; line-height: 15.693334px; font-size: 11pt; font-family: Calibri, sans-serif;">Email: mmines@mauricemines.org <o:p></o:p></p><p class="MsoNormal" style="margin: 0in 0in 8pt; line-height: 15.693334px; font-size: 11pt; font-family: Calibri, sans-serif;">Website: www.nfb.org <http://www.nfbdeaf-blind.org> <o:p></o:p></p><p class="MsoNormal" style="margin: 0in 0in 8pt; line-height: 15.693334px; font-size: 11pt; font-family: Calibri, sans-serif;">Live the life you want. <o:p></o:p></p><p class="MsoNormal" style="margin: 0in 0in 8pt; line-height: 15.693334px; font-size: 11pt; font-family: Calibri, sans-serif;">The National Federation of the Blind Deaf-Blind Division, a proud division <o:p></o:p></p><p class="MsoNormal" style="margin: 0in 0in 8pt; line-height: 15.693334px; font-size: 11pt; font-family: Calibri, sans-serif;">of the National Federation of the Blind, is a community of members and <o:p></o:p></p><p class="MsoNormal" style="margin: 0in 0in 8pt; line-height: 15.693334px; font-size: 11pt; font-family: Calibri, sans-serif;">friends who believe in the hopes and dreams of the nation's blind. Every day <o:p></o:p></p><p class="MsoNormal" style="margin: 0in 0in 8pt; line-height: 15.693334px; font-size: 11pt; font-family: Calibri, sans-serif;">we work together to help blind people live the lives they want. <o:p></o:p></p><p class="MsoNormal" style="margin: 0in 0in 8pt; line-height: 15.693334px; font-size: 11pt; font-family: Calibri, sans-serif;"><o:p> </o:p></p><div><br><blockquote type="cite"><div>On Sep 20, 2023, at 14:03, Gary Wunder via NFBCS <nfbcs@nfbnet.org> wrote:</div><br class="Apple-interchange-newline"><div><div>I think you are spot on. In addition to resourcing, it comes down to valuing<br>us as customers. When a VoiceOver tester brings you a problem and includes<br>video, how can you not take it seriously. Again, I think the things Jonathan<br>said in his speech are spot on.<br><br>-----Original Message-----<br>From: NFBCS <nfbcs-bounces@nfbnet.org> On Behalf Of Brian Buhrow via NFBCS<br>Sent: Tuesday, September 19, 2023 8:24 PM<br>To: NFB in Computer Science Mailing List <nfbcs@nfbnet.org><br>Cc: Brian Buhrow <buhrow@nfbcal.org><br>Subject: Re: [NFBCS] IOS 17 rolling out tomorrow<br><br><span class="Apple-tab-span" style="white-space:pre"> </span>Hello. I suspect the problem with these bugs is not that there<br>isn't time to fix them,<br>but rather, Apple isn't able to reproduce them. For example, there is a<br>long standing bug in<br>iOS, since iOS 10 at least, whereby if one is playing an mp3 media file in<br>Safari, one is not<br>able to move the playback slider by more than 5 or 10 seconds in either<br>direction at a time;<br>yet that slider works perfectly fine if operated without VoiceOver. When I<br>opened a ticket<br>with Apple Accessibility, they said they couldn't reproduce the problem,<br>even when I provided<br>videos showing them how to reproduce it. The challenge is that, in my view,<br>most folks,<br>including those people who develop them, don't know how to troubleshoot<br>nonvisual access issues<br>because, as I say, even though they develop the tools, they don't use them<br>regularly and don't<br>rely on them for their daily experience. Many of these bugs are subttle<br>and, unless you're<br>intimately familiar with the access technology, because you use it, you're<br>going to miss the<br>bug when it occurs unless it's painfully obvious. <br><span class="Apple-tab-span" style="white-space:pre"> </span>In short, it's not a time problem, but a resourcing issue in<br>general. And, no matter how<br>long one delays a software release, if access technology isn't given enough<br>resources relative<br>to the project as a whole, the issues will never be addressed.<br><br>-thanks<br>-Brian<br><br>_______________________________________________<br>NFBCS mailing list<br>NFBCS@nfbnet.org<br>http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org<br>To unsubscribe, change your list options or get your account info for NFBCS:<br>http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/gwunder%40earthlink.net<br><br><br>_______________________________________________<br>NFBCS mailing list<br>NFBCS@nfbnet.org<br>http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org<br>To unsubscribe, change your list options or get your account info for NFBCS:<br>http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/maurice%40maurice-amines.com<br></div></div></blockquote></div><br></div></body></html>