you have:
-       the accessibility layer itself (compontents of the os that provide 
accessibility information)
-       voiceover screen that interacts with the accessibility layer.

VoiceOver can like other programs have bugs that has nothing to do with the 
underlying accessibility layer of the os.

just my 2 cents


On Thu, Oct 31, 2013 at 07:13:55AM -0600, Tim Kilburn wrote:
> Hi,
> 
> The issue with automatic updates to VoiceOver has been skirted around here 
> but not clearly enough in my opinion.  VoiceOver is not just a bolted on app 
> to the MacOS, it is a part of the OS itself.  While you could update specific 
> code within the screenreader service, the majority of fixes actually are 
> within the coding of the system itself.  That is, the way that either the OS 
> handles a process or the method by which Apple or third party apps handle 
> system resources often cause the problems we have with the VO interface.  The 
> use of custom elements within apps is outside the scope and of VO updates 
> but, when, addressed affect VO accessibility.  So, what I’m saying, is that I 
> don’t believe that updates to VO can necessarily be easily separated from OS 
> updates other than through “Supplemental” sorts of things.
> 
> JMO.
> 
> Later…
> 
> Tim Kilburn
> Fort McMurray, AB Canada
> 
> On Oct 31, 2013, at 3:17 AM, mario navarro <mario....@gmail.com> wrote:
> 
> > 
> > 
> > no, what I said, is that the voice over also has bugs independently of apps.
> > sorry but I do not think that way .
> > 
> > I only want the best for the voice over, I'm not comparing windows and mac.
> > please do not misunderstand me .
> > 
> > cheers.
> > Em 31/10/2013 08:49, BBS escreveu:
> >> I can tell you my answer right now. Voiceover doesn’t need to be like Jaws 
> >> or Window-Eyes updating all the time. Even if Voiceover were updated 
> >> constantly, that wouldn’t solve anything. The apps that have been 
> >> inaccessible will remain inaccessible until the app developers fix those 
> >> issues themselves. And as far as Voiceover having bugs in the app, hate to 
> >> say this, but you’ve pretty much said your problem yourself, that the apps 
> >> are the problem and not Voiceover. So no, Voiceover doesn’t need automatic 
> >> updates. We don’t need to go through the same hell we go through with 
> >> Windows screen readers.
> >> 
> >> Shawn
> >> Sent From My White Mac Book
> >> 
> >> On Oct 31, 2013, at 3:29 AM, mario navarro <mario....@gmail.com> wrote:
> >> 
> >>> 
> >>> hi nicholas.
> >>> I know that most times the problems are the apps, apps are standard 
> >>> sustema osx, or other companies.
> >>> but the voice over also has some bugs in certain apps that  to be fixed.
> >>> The voice over is not immune to bugs.
> >>> we all know that screen readers have bugs whatever they are.
> >>> and also has voice over.
> >>> It would also automatic updates for new features.
> >>> nicholas ok, if the group agrees with the automatic updates, I want you 
> >>> to write the ticket for me to send.
> >>> I'll be super grateful.
> >>> 
> >>> thanks friend nicholas.
> >>> cheers.
> >>> Em 31/10/2013 06:29, Nicholas Parsons escreveu:
> >>>> Seems to me Apple could push out updates to VoiceOver if they wanted to, 
> >>>> just as they push other updates for raw camera compatibility and the 
> >>>> like, even though those aren't separate applications.
> >>>> More frequent updates to VoiceOver would be good. However, the main 
> >>>> accessibility issues we have are not problems with VoiceOver, but 
> >>>> typically problems in other apps. It's those apps that need to be 
> >>>> updated to improve accessibility, not VoiceOver. For instance, in 
> >>>> Mountain Lion it's iBooks, Pages, Mail, Calendar and Finder which need 
> >>>> updates, not VoiceOver. Well, there are a couple of issues with some of 
> >>>> the voices messing some things up, but that's a different issue as it's 
> >>>> Nuance that needs to address those issues.
> >>>> Having said all this, Mario, I'd be happy to write the email for you if 
> >>>> you like, and then you can send it from your own email account. I'll 
> >>>> wait and hear what other people on this list have to say first, however, 
> >>>> as it's probably wise to take on board other feedback.
> >>>> Cheers,
> >>>> Nic
> >>>> 
> >>> -- 
> >>> You received this message because you are subscribed to the Google Groups 
> >>> "MacVisionaries" group.
> >>> To unsubscribe from this group and stop receiving emails from it, send an 
> >>> email to macvisionaries+unsubscr...@googlegroups.com.
> >>> To post to this group, send email to macvisionaries@googlegroups.com.
> >>> Visit this group at http://groups.google.com/group/macvisionaries.
> >>> For more options, visit https://groups.google.com/groups/opt_out.
> > 
> > -- 
> > You received this message because you are subscribed to the Google Groups 
> > "MacVisionaries" group.
> > To unsubscribe from this group and stop receiving emails from it, send an 
> > email to macvisionaries+unsubscr...@googlegroups.com.
> > To post to this group, send email to macvisionaries@googlegroups.com.
> > Visit this group at http://groups.google.com/group/macvisionaries.
> > For more options, visit https://groups.google.com/groups/opt_out.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "MacVisionaries" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to macvisionaries+unsubscr...@googlegroups.com.
> To post to this group, send email to macvisionaries@googlegroups.com.
> Visit this group at http://groups.google.com/group/macvisionaries.
> For more options, visit https://groups.google.com/groups/opt_out.

-- 
You received this message because you are subscribed to the Google Groups 
"MacVisionaries" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to macvisionaries+unsubscr...@googlegroups.com.
To post to this group, send email to macvisionaries@googlegroups.com.
Visit this group at http://groups.google.com/group/macvisionaries.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to