Model T Syndrome Continued
This morning, I read and published a comment by an Android user who took offense at being labeled a puppy yapping for a biscuit. The anonymous post stated that this user was a member of the "Eyes Free" mailing list, a group to which I also belong and correctly stated that some of the people on the mailing list were critical of various things regarding Android accessibility. This person also correctly stated that GPS navigation apps designed for people with vision impairment are superior and less costly on Android phones than on any other types of handsets.
Then, the user writes that it is good that Android supports some of the most minimal features like answering and placing calls and entirely dives into symptoms of Model T Syndrome by stating that there is an expectation that Android will get better. The anonymous Com enter then states that it is only due to Android accessibility that a person with vision impairment can use Sprint as a carrier. Sprint, if we forget, is bound by Section 255 of the Telecommunications Act to provide accessible handsets and that it hasn't before should be the basis of an FCC investigation and not a celebration of Android's half assed accessibility.
My point is that it is absolutely unacceptable for any company to release access technology that is too far from the state-of-the-art. On handsets, this means that the AT is competitive with VoiceOver on the iPhone and not a handful of really excellent features like pedestrian GPS and few of the basics like out-of-the-box web browsing.
Let's explore how Android as a whole compares to Android accessibility. How many mainstream users would buy an Android phone if it wasn't competitive with the iPhone? What if such users had no web browsing, could not read descriptions in the Android Market (a problem fixed in 2.3 but not available to any blink with an Android 2.2 based handset), could only "see" some buttons with meaningless information on them in order to do things like installing new software, could not use more than half of the standard apps, could not use the on-screen keyboard, could not use the built-in email client, could not use any of the handsets without a built-in hardware keyboard, could not turn it on without assistance and could not do a panoply of other fundamental smart phone activities? The answer, plain and simply, is that a phone with all of these problems would have been the laughing stock of the telecommunications biz. But, our anonymous comment-or seems to say that we should be grateful and that such failings are acceptable for we blinks.
I'm not suggesting that people with disabilities should have an experience substantially better than that of our mainstream friends but, rather, I'm saying that anything less than parity out-of-the-box is unacceptable. this is entirely the Model T Syndrome and an entirely discriminatory approach to software development on behalf of the technology giants that make such incredibly flawed solutions like we must endure on Android. Google has billions and billions of dollars in its arsenal but cannot make a screen reader superior to that built by a really smart and really terrific 22 year old hacker in his spare time. This would be the equal of Chevy building a new car based not on state-of-the-art electric engine technology but, rather, on the Model T, a vehicle that was pretty wonderful a century or so ago.
Google is not alone in this problem. Microsoft released Windows Phone 7 with no accessibility solution and no way for third parties to create an accessible solution. Symbian seems to have lost its accessibility in more recent releases, Blackberry seems to have broken its accessibility and Palm never had accessibility in the first place. None of the failings of other OS, though, is an excuse for Android to provide such a substandard solution. We have state-of-the-art accessibility from Apple and all comers should provide something quite similar and do so immediately.