Didn't the NFB or ACB kind of force Apple to develop a screen reader in
line with the ADA? This may be something I just read and so is pure
speculation.
On 31/03/2015 00:56, Sabahattin Gucukoglu wrote:
I wonder what the catalyst was for Apple’s ultimate choice to develop their
screen reader? The education sector? Government? The mythical two blind
sons? Certainly the APIs are now available for the development of an AT
solution, so it’s entirely possible, technically. But it doesn’t surprise me
to learn that the Jobsian quest for perfection extended further back even than
Apple’s introduction of their own usable screen reader, to the exclusion of
others; I had not heard that story, and merely assumed that OS 9 was the choice
of blind musicians (one of whom I knew) because it happened to be accessible
with OutSpoken. Although I’m not complaining that I didn’t have to pay for
VoiceOver, there’s something to be said for diversification when it actually
has the effect of giving the customer what they ultimately desire.
For my current weekly bash at Apple, see:
http://www.applevis.com/forum/accessibility-advocacy/suggestion-report-accessibility-bug-friday
Sometimes it’s the little things, sometimes not so little. I only started it
recently, because I think the situation for Yosemite is particularly
disturbing, but many of those niggles go back to the very beginning. And yes I
think iOS is starting to feel the effects now as well. It’s very fortunate
that none of these issues currently make the platforms unusable.
--
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/macvisionaries.
For more options, visit https://groups.google.com/d/optout.
