Man, why does this continue to happen. I don't understand how or why breaking accessibility happens. I thought that if the programmers coded the app incorporating Apple's accessibility guidelines, it would simply work. For that matter, I thought that if the programmer simply used Cocoa as the programming language, it would work. Can someone explain to me how exactly this works please? Do developers have to make a large effort to make apps accessible? I've always been a little unclear on this. Thanks.
Friendly, Chris On Feb 11, 2011, at 1:00 PM, Maccessibility wrote: > Twitterific for Mac 4.0 Is Released Sans VoiceOver Accessibility > > The IconFactory has released the much anticipated Twitterific 4.0 for Mac OS > X. > Though Twitterific was one of the first OS X Twitter clients to incorporate > accessibility, the application has taken a huge step backward with this > release. > The message timelines are not exposed to VoiceOver, making the app unusable. > Interestingly, much of the app elsewhere [...] > > You can read the rest of this news item at: > http://www.lioncourt.com/2011/02/11/twitterific-for-mac-4-0-is-released-sans-voiceover-accessibility/ > > The Mac-cessibility Network > "...it's all within our reach..." > http://maccessibility.net > > -- > You received this message because you are subscribed to the Google Groups > "MacVisionaries" group. > To post to this group, send email to macvisionaries@googlegroups.com. > To unsubscribe from this group, send email to > macvisionaries+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/macvisionaries?hl=en. > -- You received this message because you are subscribed to the Google Groups "MacVisionaries" group. To post to this group, send email to macvisionaries@googlegroups.com. To unsubscribe from this group, send email to macvisionaries+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/macvisionaries?hl=en.
