In December 2012, I decided to leave Symbian and try a new operating system. At that time, I was torn between trying Android, despite not having enough information about its accessibility, or going for an iPhone, knowing that many blind people were already using it. I even had the chance to test an iPhone 3GS. My mind, eager to try new things, even considered getting one of the few of the Blackberry phones equipped with a screen reader to see how the experience would be for a blind user. I finally settled on Android and bought the Galaxy Nexus as my first Android phone. And so, my interesting Android journey began.
Now, in December 2023, I’m taking a trip down memory lane, reflecting on some of the changes I’ve witnessed throughout my years using Android.
Table of Contents
Google TTS:
When the screen reader started on my first Android phone, I was greeted by an awful-sounding TTS engine called Pico TTS, the free built-in TTS engine.
After updating my Galaxy Nexus to Android 4.2.1, I had a pleasant surprise – a different, better-sounding voice. I realized this was the Google TTS engine that replaced Pico on Android. I’m unsure if Google TTS was introduced before Android 4.2 because I upgraded directly from 4.0 to 4.2. Google TTS continues to be a good free TTS, especially after it supported more languages and improved voice quality. It still needs work in some areas, but as a built-in TTS engine, it gets the job done.
Better Permission Handling:
Prior to Android 6.0, when installing an app, users would encounter a list of requested permissions. To proceed with the installation, agreeing to all permissions was necessary—it was essentially a “take it or leave it” scenario, lacking an officially supported way to revoke permissions. Although Android 4.4 had a somewhat hidden permission manager, it wasn’t an ideal solution.The shift came with Android 6.0, introducing a significant change in how permissions were handled. Since then, apps are expected to request a permission when they need it. Over the years, Android’s permission handling has seen improvements, granting users much better control compared to the situation 11 years ago.
Separation of Accessibility Volume and Media Volume:
With the release of Android 8.0, Accessibility Volume became independent from the media channel. Previously, the screen reader volume was linked to the media volume channel. This change separated the screen reader volume, making it entirely independent of other volume settings. Despite seeming like a minor adjustment, the introduction of the Accessibility Channel stands out as a significant improvement to accessibility.
Multi-finger Gestures:
Single-finger gestures for screen readers were introduced to Android in version 4.1. However, those gestures received mixed reviews, with some users finding them difficult or confusing. Also, they were limited in number.
Interestingly, Google didn’t incorporate support for multi-finger screen reader gestures until Android 11. Initially, these gestures functioned well on Pixel and Samsung phones, while users of other devices had to wait until Android 12 for seamless integration.
Notably, Samsung’s UI had included multi-finger gestures long before their official support on Android, but they were exclusive to Samsung’s own screen reader, the Voice Assistant. With the arrival of Android 11, other screen readers, alongside Samsung’s Talkback (replacing Voice Assistant), could benefit from these gestures. Curiously, Google’s TalkBack required users to wait until Android 12 to utilize these gestures on Samsung phones.
More Accessible UIs:
An essential aspect of an independent and accessible experience is the ability to activate the screen reader during the initial phone setup. Unfortunately, for many years, some manufacturers overlooked this necessity, omitting the accessibility shortcut from their software. In certain instances, TalkBack was not pre-installed on some phones, leading to instances like a Lenovo phone that, after a system update, surprisingly lacked a screen reader. Upon seeking sighted assistance, I discovered TalkBack had been removed during the update.
Thankfully, there’s a noticeable shift as manufacturers now care more for accessibility. With major manufacturers, it’s unlikely to encounter a device without TalkBack pre-installed or the inability to activate it during setup using the volume keys holding shortcut. Additionally, user interfaces (UIs) have become more screen reader friendly, enabling users to accomplish basic tasks and adjust settings with no issues.
While strides have been made, Android remains an operating system open to alternatives. If, for example, the phone app or launcher lacks accessibility, users have the option to seek out third-party accessible replacements.
Enhanced Update Commitments and Delivery:
For many years, Android devices suffered from severe neglect in terms of support. Waiting over a year for a promised Android version upgrade became the norm. Only Nexus phones, later replaced by Pixels, received prompt updates. Midrange and low-end models typically received just one or no updates at all, while even flagship models were restricted to a maximum of two Android versions. The update policies were vague, leaving consumers uncertain about the support they could expect when purchasing a particular phone.
Recent years have witnessed a notable transformation, largely attributed to efforts by Google and Samsung. Updates are now quicker to reach devices, and the duration of support has extended. Moreover, there’s increased attention to providing security patches across a wider range of devices.
Given the multitude of Android devices in the market, each with its unique UI modifications, update delivery speed and consistency vary among manufacturers. Nevertheless, it’s evident that the current state of Android updates is far improved compared to how things were in 2012 or even as recently as 2018.
Midrange Phones Becoming Reliable Daily Drivers:
Android, as an open-source operating system, has always been available across a wide price range, catering to diverse budgets. However, merely owning an Android phone didn’t always guarantee a good or acceptable user experience, especially considering the historical lack of newer Android versions for non-high-end devices.
In recent years, advancements in hardware and software, coupled with intensified competition, have resulted in a significant boost in midrange phones performance and support.
For instance, Samsung now supports phones like the A34, priced at less than $300, for up to 4 Android upgrades—a possibility unimaginable in the past.
TalkBack Highs and Lows:
TalkBack, a very basic screen reader with minimal customization in 2012, has undergone numerous modifications and substantial progress over time.
One of its early improvements introduced the ability to label unlabeled buttons. Presently, TalkBack offers customizable gestures, enhanced reading controls, a more adaptable menu, a braille keyboard, spell check, and more.
However, the situation is not always bright and positive. TalkBack betas, once available to everyone, are now limited to trusted testers chosen by Google from a very limited set of countries. Moreover, the closure of the Eyes-Free public group, a platform for discussions involving Google accessibility representatives, has shifted communication to the Google Disability support team. This team sometimes shows a lack of necessary qualifications or influence in accessibility matters.
Observing TalkBack’s progress, it’s evident that development hasn’t always moved in the right direction. Some bugs have lingered without fixes for extended periods, and certain features and options were removed without justification, forcing developers’ choices on users instead of providing a flexible experience. Moreover, Many expected features and basic customizations in a screen reader are still missing.
As the built-in screen reader supported by Google on Android, the expectation remains that Google, with its extensive resources, can make TalkBack more responsive and feature-rich, meeting the diverse needs of users across the platform.
Screen Reader Choices:
Android’s openness has allowed competitive screen readers to emerge as alternatives to TalkBack. While attempts like Spiel and Shine+ were short-lived, the Chinese-developed Jieshuo screen reader has gained a strong user base, exemplifying the capabilities of a screen reader on Android.
The door remains open for other advanced screen readers to emerge on Android, as long as there are determined individuals committed to development and creation.
Closing Thoughts:
If I could return to 2012, I would unhesitatingly make the same choice. Moving to Android has never been a source of regret for me. The platform has continuously impressed me despite its occasional issues and the emerging limitations in newer versions. Android’s openness and customizable nature remain the reasons for my loyalty.
Now more than ever, I’m dedicated to advocating for Android, discussing both its positives and negatives. Over the years, I’ve witnessed the substantial evolution of Android and the diminishing misconceptions about its accessibility.
The community of Android blind users is growing, far beyond a small minority.
To ensure that everyone’s Android experience is delightful, it’s crucial to press Google for better adherence to accessibility standards across its apps. Raising awareness among app developers is equally vital, as apps play a significant role in shaping user experiences on any platform. We must collectively expand resources about Android, its features, and its accessibility for a more inclusive environment.
Comments