Hi, Kiran Kaja <[email protected]> wrote:> > KK: if history is any indication, Nokia hasn't done much to > promote accessibility of its devices. We have solutions now > for Symbian because of couple of excellent developers who > figured out means to get into the operating system. Symbian > has *no* accessibility API while every other mobile platform > except Windows Phone 7 has it. And I haven't seen any > indication of an accessibility API in Meego.
Sure, which is why I said that the third party screen reader developers would have to innovate. The recent example of Code Factory improving accessibility of Ovi Maps is a perfect example of this. Nokia has plans for improving the cell phone experience which is not specifically for the blind, but which is going to benefit the community all the same. Things like: Tactile feedback http://www.engadget.com/2008/07/08/nokias-haptikos-tactile-feedback-tech-revealed-in-patent- applic/ and indoor location http://www.allaboutsymbian.com/features/item/12145_Indoor_Location-Future_tech_fr.php Symbian was trying to get an accessibility API, but I haven’t been keeping track of what happened their. > KK: Wrong information. A properly implemented Accessibility > API doesn't lead to any security or stability issues. In the > early part of this decade, OS developers did have a > misconception that some accessibility features lead to > security leaks but I haven't seen any such issues for more > than 6 years of accessibility related work experience. Developers have a number of reasons for leaving out accessibility frameworks, obviously they are not valid all the time. stability and security issues is just one of them. I always check my facts and if you are looking for documented evidence, then here it is. Over at the Speakup list, we are having a discussion after a developer raised an issue that world writable files for Speakup (files used for changing user configurations) is a security risk. http://speech.braille.uwo.ca/pipermail/speakup/2010-December/051463.html and http://speech.braille.uwo.ca/pipermail/speakup/2010-December/051478.html Here is BlackBerry asking users not to run text-to-speech applications again for security reasons. http://docs.blackberry.com/en/admin/deliverables/14557/Text-To-Speech_API-Security_Note--1048931-0319124239-001-5.0-US.pdf And if text-to-speech poses no security risks, then I wonder why do secured PDF documents prevent text-to-speech from running? Yes, efforts should be made to encorporate accessibility right from the start. The company should be held responsible and not a specific section. Something like what this open letter does. http://blind.wikia.com/wiki/Open_Letter_Initiative Regards To unsubscribe send a message to [email protected] with the subject unsubscribe. To change your subscription to digest mode or make any other changes, please visit the list home page at http://accessindia.org.in/mailman/listinfo/accessindia_accessindia.org.in
