A couple of days ago I wrote about Apple and accessibility, and the work they've done not only implementing but promoting accessibility — or better put, inclusivity. The same day an article from Reuters hit the wires that managed to mangle the story of the National Federation of the Blind (NFB). It was unfortunate, but it has given the NFB a chance to tell it again, tell it directly, and hopefully to reach even more people. From the NFB blog:
Apple is singled out, probably, because they're the industry leader. Just like the environmental movements and others have singled out Apple in the past. It's the equal and opposite reaction to the headlines Apple gets when a new iPhone or iPad is launched.
The idea is, where Apple goes, so goes the rest of the industry. That's worked in the past at motivating Apple, because the people at Apple seem to care deeply about issues just like this. Unfortunately, it's hard to tell if it's motivated anyone beyond Apple.
Rather than seeing the attention Apple gets as a competitive challenge, some competitors see it as competitive advantages — something that lets them save time and money by ignoring things while all eyes are on Apple.
I think it'd be hard to argue, however, that Google, Microsoft, BlackBerry, Samsung, Amazon and any and everyone else with skin in the platform game should be and has to be part of the discussion. For accessibility and inclusivity to be real, it can't depend on any one vendor.
Some customers will choose to use Android or ChomeOS, TouchWiz or Sense, Windows or Windows Phone, FireOS or BB10 — shouldn't they be able to experience the same level of support that OS X and iOS users enjoy? Better even, if they can?
The second part is harder to unpack. The NFB calls for policies, standards, and procedures, and the enforcement thereof. What does enforcement mean? Should apps be rejected from the App Store, Google Play Store, or Windows Phone Store if they fail accessibility, the same way they would if they crashed on launch? If so, which accessibility technologies should be enforced? What kind of team or teams would be needed to review them?
If not outright rejection, then should non-accessible, non-inclusive apps be excluded from featured promotions on the various app stores? Would loss of such an important marketing opportunity incentivize developers to make accessibility and inclusivity a priority? Or, if a carrot works better than a stick, could accessible, inclusive apps be included in special promotions, with dedicated sections, badges, indicators, awards, and other forms of recognition?
If we push down to the developer level, should dedicated advisors, evangelists, "kitchens" and other workshops, code and design reviews, and consulting resources and services be made available, or perhaps even be subsidized by the platform owners?
Should peer and customer pressure be applied, with non-accessible, non-inclusive apps receiving the same kind of scorn as those with horrible visual design or terrible interactivity?
That's a lot of questions. I ask them because I don't know the answers. Maybe there are no easy answers to know, at least not yet. I think the NFB understands the complexities and nuances involved far, far better than most, and even they used the language "work with", because there's a lot of work to be done.
Accessibility and inclusivity, after all, don't just mean making an iPhone or iPad or Mac that can be used by the blind or the deaf, the motor impaired or those with autism, the very, very young or the very, very old, the absolute beginner or the person for whom technology still feels like a challenge even after decades.
It means making an iPhone or iPad or Mac that can be used by everyone. And an Android or ChromeOS device, and a Windows or BlackBerry device. All of them. Everyone.
Give the NFB resolution a read and then let me know — what do you think?
Master your iPhone in minutes
iMore offers spot-on advice and guidance from our team of experts, with decades of Apple device experience to lean on. Learn more with iMore!
Rene Ritchie is one of the most respected Apple analysts in the business, reaching a combined audience of over 40 million readers a month. His YouTube channel, Vector, has over 90 thousand subscribers and 14 million views and his podcasts, including Debug, have been downloaded over 20 million times. He also regularly co-hosts MacBreak Weekly for the TWiT network and co-hosted CES Live! and Talk Mobile. Based in Montreal, Rene is a former director of product marketing, web developer, and graphic designer. He's authored several books and appeared on numerous television and radio segments to discuss Apple and the technology industry. When not working, he likes to cook, grapple, and spend time with his friends and family.