TalkBack, a screen reader developed by Google for Android, has undergone exciting cycles throughout the years. One of the decisions that created a lot of buzz in the visually impaired Android community was the surprising announcement from Google few years ago to close the TalkBack public beta, relying instead on a trusted tester program. Initially limited to the United States, it slowly expanded to a very few other countries.
While geo-restricting services or privileges is not something new, applying a similar restriction to TalkBack’s beta testing wasn’t a wise decision. This article aims to discuss the reasons why.
Table of Contents
A quick look at the history of TalkBack’s beta distribution
In 2013, when TalkBack was still a very basic screen reader, there was a dedicated page for beta releases. Another page allowed users to report issues and request features. During this time, beta releases were accessible to everyone interested in testing them.
Shortly afterward, in an effort to better organize beta announcements and discussions, Google introduced a Play Store beta program for TalkBack. The only requirement for participation was being a member of the “Eyes-Free” group.
The “Eyes-Free” group wasn’t solely focused on TalkBack’s developments; it covered everything Android-related and was a very active community. Beta announcement posts often descended into chaos, with replies ranging from feature requests to disrespectful attacks directed towards the TalkBack team or even heated, unrelated discussions.
After a few years, Google surprised the beta testing community by informing most of them that their accounts were no longer able to receive beta versions. Subsequently, a new beta program emerged.
I won’t delve into specific dates here, as this is just a quick glimpse of how it all began.
Reasons Why the Current Geo-Limitation on TalkBack Beta Participation isn’t the Right Choice
The Nature of the Product
Some may argue that developers have the right to limit the scope and availability of beta testing for their products. However, when the product in question is an internationally used screen reader released by the Android developer itself, this argument becomes questionable.
TalkBack is a screen reader found on devices worldwide. Given its global usage, it is crucial to conduct international beta testing for timely issue identification. Swift bug discovery in a screen reader, especially before public releases, is essential for ensuring stability and reliability, which are core elements of any successful screen reader.
The Proportion of Users
It is an undeniable fact, without needing proof, that Android is not the dominant operating system in the United States, which happens to be the primary testing ground for TalkBack. Logically, if you aim for a successful service or product, testing should occur where it is most widely used. This doesn’t imply excluding the United States from beta testing TalkBack; rather, it emphasizes the importance of also hearing and representing the voices of users in other markets within the beta testing program.
Objectivity in Setting Standards and Conditions
Major companies developing widely-used services and apps are expected to adhere to a certain level of objectivity and carefully considered standards for qualifying individuals to test their services or apps. Undoubtedly, the requirement for a person to reside in a specific country to test an internationally essential service is far from fair or unbiased. This geo-restriction resembles some unaccepted requirements like being from a certain race or ethnicity, even if it appears otherwise.
Respect for Users’ Abilities and Experiences
The Android blind community, spanning the globe, is rich with many capable users who excel in effective communication, product testing, providing constructive feedback, and reporting issues clearly. Excluding these individuals solely based on their residence in a specific country constitutes discrimination against them. This is not to imply that the U.S. or the few other countries where the TalkBack testing program is conducted lacks qualified individuals, nor does it suggest that those selected are incapable of fulfilling the intended mission. Rather, it prompts the question: If these same individuals were residing in another country, would they still be chosen for the TalkBack testing program? Additionally, is it fair to exclude every other qualified user simply because being in a certain country is a crucial condition for entering the TalkBack beta testing?
The Desire for Improvement
If you develop an app and aim for it to be successful and bug-free, thorough testing is a must. Applying this straightforward concept to the development of TalkBack, the logical outcome is that, in order to advance this screen reader, Google should establish an enthusiastic and diverse beta testing community that represents all beneficiaries of TalkBack’s features. However, the current reality presents an opposite approach: a very small, somewhat secretive beta testing group located in one or very few areas. Unfortunately, this gives the impression that Google may not be fully committed to significantly enhancing TalkBack’s performance and responsiveness across all phones and tablets from different manufacturers.
Other screen readers have public and international beta-testing cycles
JAWS, NVDA, Narrator, and VoiceOver all can be tested both publically and internationally in various ways. In the case of VoiceOver, Apple’s screen reader for iOS, joining the public beta program, internationally, is quite easy and requires updating one’s operating system to a public beta. Unlike Google, Apple, Microsoft, NVAccess and FreedomScientific don’t employ such a strange geo-blocking mechanism.
The Current Trusted Testing Program
It is not uncommon to hear from Google’s proponents that the Trusted Testing Program is not exclusive to TalkBack but extends beyond the screen reader to cover the accessibility of other Google services. The geographical limitation is often justified by the necessity for Google to provide testers with devices or other required tools. There is no need to discuss or disagree with this claim since there is nothing wrong with the presence of the Trusted Testing Program; it can coexist side by side with a more open TalkBack beta program. This independent beta program allows more qualified users to play a role in discussing the screen reader’s new features and contributing to bug discovery and identification, ultimately resulting in a better public product.
Final Thoughts
Criticizing Google’s approach to TalkBack’s beta testing is not mere criticism; it is grounded in strong reasoning. If there is a sincere desire to elevate TalkBack as a central component of Android’s accessibility to the next level, a genuine collaboration between the global blind Android community and Google should occur. This collaboration cannot be achieved with the current Google strategies. Marginalizing capable, experienced individuals simply because they are not residents of a particular country shows disrespect, to say the least. Moreover, this discourages active participation in promoting TalkBack or providing feedback for its improvement.
Additionally, advocating the current Google strategy by some of those fortunate U.S. citizens is not the way to go, especially when their arguments are weak, such as the baseless statement blaming the community for Google’s decision because there were insults directed towards Google during the Eyes-Free days.
In the Internet age, there is no excuse for a major company to impose strange geo-restrictions on essential global services. However, a successful TalkBack beta program is not a disorganized, standard-free, open one; it is a well-organized program adhering to standards based on experience, qualification, and good bug reporting and communication skills. Beta testers, representing the international community, should be able to directly contact Google’s accessibility team to discuss developments and express opinions, ultimately resulting in a more advanced, reliable, competitive, and satisfying TalkBack for all.
I totally agree with this article, and I’m also annoyed because I can’t test talkback just because I’m not an US resident. I think the accessibility suite should have an open google play testing program like many apps do. I hope this article will reach google’s accessibility team and that they will take it seriously.
I’ll quote your article in part”disrespectful attacks directed towards the TalkBack team ” this is why it was closed. Those that behaved in such a manner is who you should blame.
Sorry, but this argument may work when kids are playing together, not when we are talking about real products and big companies. In school, for example, if a kid insults another, the other kid may feel upset and stop playing with everyone else. Companies’ operations and actions are much more mature than that.
Also, considering that this was really the reason, were the offenses only coming from people who live outside of the U.S., while the U.S. people were the well-behaved ones? Instead of using such excuses, it is better to encourage a more inclusive organized global beta system.