[NFBCS] IOS 17 rolling out tomorrow

[mmines1]

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.

 

 

Maurice Mines, President 

National Federation of the Blind Deaf-Blind Division 

Email: mmines at mauricemines.org  

Website: www.nfb.org <http://www.nfbdeaf-blind.org> 

Live the life you want. 

The National Federation of the Blind Deaf-Blind Division, a proud division 

of the National Federation of the Blind, is a community of members and 

friends who believe in the hopes and dreams of the nation's blind. Every day 

we work together to help blind people live the lives they want.   

 


> On Sep 20, 2023, at 14:03, Gary Wunder via NFBCS <nfbcs at nfbnet.org> wrote:
> 
> I think you are spot on. In addition to resourcing, it comes down to valuing
> us as customers. When a VoiceOver tester brings you a problem and includes
> video, how can you not take it seriously. Again, I think the things Jonathan
> said in his speech are spot on.
> 
> -----Original Message-----
> From: NFBCS <nfbcs-bounces at nfbnet.org> On Behalf Of Brian Buhrow via NFBCS
> Sent: Tuesday, September 19, 2023 8:24 PM
> To: NFB in Computer Science Mailing List <nfbcs at nfbnet.org>
> Cc: Brian Buhrow <buhrow at nfbcal.org>
> Subject: Re: [NFBCS] IOS 17 rolling out tomorrow
> 
> 	Hello.  I suspect the problem with these bugs is not that there
> isn't time to fix them,
> but rather, Apple isn't able to reproduce them.  For example, there is a
> long standing bug in
> iOS, since iOS 10 at least, whereby if one is playing an mp3 media file in
> Safari, one is not
> able to move the playback slider by more than 5 or 10 seconds in either
> direction at a time;
> yet that slider works perfectly fine if operated without VoiceOver.  When I
> opened a ticket
> with Apple Accessibility, they said they couldn't reproduce the problem,
> even when I provided
> videos showing them how to reproduce it.  The challenge is that, in my view,
> most folks,
> including those people who develop them, don't know how to troubleshoot
> nonvisual access issues
> because, as I say, even though they develop the tools, they don't use them
> regularly and don't
> rely on them for their daily experience.  Many of these bugs are subttle
> and, unless you're
> intimately familiar with the access technology, because you use it, you're
> going to miss the
> bug when it occurs unless it's painfully obvious.  
> 	In short, it's not a time problem, but a resourcing issue in
> general.  And, no matter how
> long one delays a software release, if access technology isn't given enough
> resources relative
> to the project as a whole, the issues will never be addressed.
> 
> -thanks
> -Brian
> 
> _______________________________________________
> NFBCS mailing list
> NFBCS at nfbnet.org
> http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
> To unsubscribe, change your list options or get your account info for NFBCS:
> http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/gwunder%40earthlink.net
> 
> 
> _______________________________________________
> NFBCS mailing list
> NFBCS at nfbnet.org
> http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
> To unsubscribe, change your list options or get your account info for NFBCS:
> http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/maurice%40maurice-amines.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20230920/14530ee7/attachment.html>