Accessible Android Investigates: Do Google Apps for Android Have Accessibility Actions?

Last updated on 6 December 2024

Google—arguably the heart and soul of Android—offers a plethora of apps that dominate our productivity, entertainment, and navigation needs. But how well do these apps cater to users who rely on screen readers? Specifically, how many of Google’s 17 major Android apps utilize Accessibility Actions—a feature designed to make app interaction smoother and more intuitive for users with disabilities?

This investigation focuses solely on the implementation of Accessibility Actions, not on other potential accessibility issues within these apps. It’s important to note that some Google apps have accessibility challenges beyond the lack of Accessibility Actions. By narrowing the scope of this evaluation, we do not imply that these apps are otherwise flawless. Instead, this article highlights one key accessibility feature and how well it is supported.

Almost a year ago, I argued that very few Google apps implement this feature. Today, we’ll evaluate many Google apps for Android, providing a clear picture of where they stand in terms of accessibility and usability. Additionally, we’ll consider the ripple effect Google’s decisions have on third-party developers and their accessibility practices.

Spoiler alert: If you were hoping for a dramatic transformation in accessibility across the board, let’s just say you might want to keep your popcorn for another show.

Accessibility Actions: A Quick Recap

Accessibility Actions serve as shortcuts for users relying on screen readers like TalkBack or Jieshuo, streamlining interactions with app elements. Instead of double-tapping and long-pressing to reveal options tucked away in menus or corners of the screen, these actions allow users to perform tasks—like deleting an email, saving a file or calling a person—with a single, efficient gesture. While they can greatly improve usability, their effectiveness depends on developers making a deliberate effort to implement them.

Google’s apps hold a pivotal position in setting accessibility standards for Android. If Google fully embraces Accessibility Actions, it can influence third-party developers to follow suit. Conversely, when Google doesn’t prioritize accessibility, it sends a message that these features aren’t essential, discouraging broader adoption.

So, how do Google’s 17 apps measure up? Let’s find out.

Gmail

The Claim: Gmail should make managing emails seamless for everyone.

Reality Check: Gmail not only implements Accessibility Actions for tasks like Add star, Archive and Delete, but it was also the first Google app to include them. Back when Accessibility Actions were still a novel concept in the Android arena, Gmail bravely stepped forward to show the possibilities. However, while it leads the pack in terms of usability, it’s a small pack, and more actions haven’t been added recently either. Google’s decision to implement these features in Gmail but not universally across its ecosystem is like giving one child all the toys while the rest look on longingly.

Google Calendar

The Claim: Organizing events should be straightforward and accessible.

Reality Check: Google Calendar does not utilize Accessibility Actions. Users must double-tap and hold to access additional options like Edit or Delete. This lack of direct action shortcuts adds unnecessary complexity for screen reader users, making the app less efficient to navigate. It’s like being invited to a party where the snacks are locked behind a cabinet, and you have to figure out the combination yourself.

Google Keep

The Claim: Note-taking should be easy and intuitive for all users.

Reality Check: Google Keep follows the same disappointing pattern as Calendar. To archive or delete a note, users must double-tap and hold to bring up a menu. The absence of Accessibility Actions makes the app slower and less accessible for those relying on assistive technology. Keep feels like that friend who promises to show up early but arrives just as the party ends—not entirely helpful.

Google Maps

The Claim: Navigating the world should be accessible to everyone.

Reality Check: On Android, Google Maps does not feature Accessibility Actions. Tasks like toggling directions or setting destinations require users to rely heavily on gestures and menus, which can be cumbersome. However, the story is different on iOS. Google Maps on iOS offers Rotor Options—the equivalent of Accessibility Actions—allowing smoother navigation for VoiceOver users. iOS VoiceOver users can even call locations via a dedicated Rotor item. It’s almost as if Google is treating Android users like the neglected middle child while rolling out the red carpet for iOS.

Google Drive

The Claim: Managing files should be simple and accessible.

Reality Check: Google Drive partially implements Accessibility Actions, but only on its Home tab. The single available action, More actions, provides options like Add to starred, Make available offline, and Copy link. It’s better than nothing, but it’s like giving someone a single slice of pizza when they’re expecting the whole pie.

YouTube

The Claim: Streaming videos should be an accessible experience.

Reality Check: YouTube does not utilize Accessibility Actions. Instead, screen reader users must rely on the More actions or Actions menu button next to each item to access options like Not interested, Send feedback, Play next in queue, or Save to library. For an app that encourages endless scrolling, having to navigate extra menus feels like running a marathon just to grab a glass of water.

YouTube Music

The Claim: Music streaming should be inclusive and easy to use.

Reality Check: Similar to YouTube, YouTube Music also lacks Accessibility Actions. Tasks like adding songs to a playlist or downloading music require users to locate the More actions button manually. It’s a little ironic for an app centered around harmony to feel so disjointed for screen reader users.

Google Chrome

The Claim: Browsing the web should be straightforward for everyone.

Reality Check: Accessibility Actions are absent in Chrome with an exception: in the list of tabs which can be opened via the button titled See X tabs to the left of the Customize and control Google Chrome button, three accessibility actions are available for each tab: Move tab up, Move tab right, and Move tab down. Other than that, screen reader users must rely on gestures and keyboard shortcuts to navigate, which can make some tasks unnecessarily complicated. It’s surprising that the very app synonymous with exploration has made exploration harder for some.

Google Photos

The Claim: Managing your photos should be accessible and intuitive.

Reality Check: Google Photos includes one Accessibility Action labeled Enter selection mode, designed to help users select multiple photos quickly. Unfortunately, this action doesn’t function as intended at the time of writing. Activating it does not check or uncheck the highlighted photo, forcing users to rely on double-tapping and holding to access additional options. It’s like being handed a remote control with buttons that do nothing.

Google Messages

The Claim: Texting should be accessible and efficient.

Reality Check: Google Messages does not utilize Accessibility Actions at all. Instead, users must rely on double-tapping and holding to access options like Archive, Delete, or Report spam. Messaging is supposed to be quick and easy, but Messages feels like trying to send a text via carrier pigeon.

Google Phone

The Claim: Managing calls should be simple and accessible.

Reality Check: Google Phone includes a single Accessibility Action in the Recents and Favorites tabs, labeled Expand or Collapse menu. While this action is helpful for managing contact details, its limited scope means that many tasks still require manual navigation, such as adding or deleting contacts or redialing calls. It’s the app equivalent of handing you a map but forgetting to mark your destination. Moreover, TalkBack can’t detect it as if it were absent. Only Jieshuo can detect the action.

Google Voice

The Claim: Managing calls and messages should be straightforward for everyone.

Reality Check: Google Voice includes a single Accessibility Action, labeled Expand or Collapse menu. However, for actions like Delete or Archive, users must rely on long-pressing, which adds unnecessary complexity for screen reader users. This limited implementation feels like inviting someone to a buffet but offering only a single dish.

Google Meet

The Claim: Communicating via video and voice should be inclusive and intuitive.

Reality Check: Google Meet offers one Accessibility Action, labeled Open contact page. However, this action is available only if the caller’s name is saved in the user’s contacts. For tasks like Remove from list, Add to Home screen, Report, Block user, or Start voice call, users must rely on double-tapping and long-pressing each name in the list. Google Meet, like a spotty internet connection during an important meeting, leaves users wishing for a smoother experience. And like the Phone app, TalkBack can’t detect this accessibility action – only Jieshuo can.

Google News

The Claim: Staying informed should be seamless for all users.

Reality Check: Google News does not implement Accessibility Actions at all. Users must manually navigate to controls like View full coverage for… or More options for… to access relevant options. Interestingly, double-tapping and holding articles opens them in the user’s default browser rather than providing additional accessibility-friendly controls. Google News feels like the enthusiastic waiter who serves your soup but forgets the spoon.

Google Docs

The Claim: Editing and collaborating on documents should be accessible and intuitive.

Reality Check: Google Docs provides Accessibility Actions in both viewing and editing modes, though their availability depends on the context. The Viewing mode offers actions like Select all, Add comment, Add emoji reaction, and Verbalize selection formatting. The Editing mode provides actions like Paste, Select all, Add comment, and Verbalize selection formatting. When a portion of text is selected while editing, additional actions like Cut and Insert link become available.

However, no Accessibility Actions are available in the Recent file lists, which forces users to navigate manually. Additionally, the user interface is cluttered, and both viewing and editing documents can be challenging for screen reader users. The app demonstrates an attempt to incorporate Accessibility Actions but highlights a broader need for accessibility-focused UI rethinking.

Google Sheets

The Claim: Managing and analyzing data should be inclusive.

Reality Check: Google Sheets also provides Accessibility Actions, but their usefulness depends on the context. General actions include Cut, Copy, Paste, Clear, and Insert link. Specific content like links or dates offers unique actions, such as Open link or Open in Calendar.

However, editing mode is notably limited. Unless a portion of text is selected, no Accessibility Actions are provided. Depending on installed apps, context-sensitive actions may appear, such as Open in Samsung Pass or Listen. Like Google Docs, no Accessibility Actions are available in the Recent file lists, and the app’s interface feels cluttered, making navigation more tedious than necessary.

Google Slides

The Claim: Presenting ideas should be smooth and efficient.

Reality Check: Google Slides offers Accessibility Actions in editing mode, such as Cut, Copy, Paste, Add comment, Delete, Duplicate, and Change layout.

However, as with Docs and Sheets, no Accessibility Actions are available in the Recent file lists, forcing users to navigate manually. Additionally, the cluttered UI of the app adds to the accessibility challenges. While Google Slides provides more robust Accessibility Actions compared to some other apps, the user experience remains less intuitive than it should be for screen reader users.

The Saddening Reality

It’s worth noting that Google has implemented Accessibility Actions in these productivity apps, but their interfaces demand a higher degree of accessibility rethinking. Apps like Google Docs, Sheets, and Slides—where clarity and simplicity are critical for collaboration—suffer from cluttered UIs that make even the well-intended Accessibility Actions less effective. It’s a step in the right direction but falls short of addressing the core accessibility issues these apps present.

The Verdict

Google’s approach to implementing Accessibility Actions across its 17 Android apps remains inconsistent and, in many cases, non-existent. While Gmail and Drive offer some degree of support, most other apps—such as Calendar, Keep, YouTube, Photos, Messages, Phone, Voice, Meet, and News—fail to take full advantage of this powerful feature. Interestingly, Google Maps on iOS demonstrates a more thoughtful approach by providing Rotor Options, an accessibility feature similar to Accessibility Actions. This cross-platform disparity raises questions about Google’s commitment to accessibility on its own operating system.

Final Thoughts

Accessibility Actions have the potential to make apps more inclusive and intuitive for everyone. While Google has made some progress, the overall picture suggests that there’s still a long road ahead. As the leading force behind Android, Google has a responsibility to lead by example.

And yet, Google’s lukewarm embrace of Accessibility Actions still puts it ahead of Samsung, another major Android player. Shockingly—or maybe not so shockingly—Samsung’s apps offer zero Accessibility Actions. It’s almost as if Samsung looked at Google’s sparing implementation and thought, “Why bother trying at all?” This lack of adoption by two of Android’s most prominent players sends a discouraging message to third-party developers.

The ripple effect of Google’s inconsistent approach is already visible. For example, Instagram on Android lacks Accessibility Actions, whereas its iOS counterpart includes them. And while WhatsApp, yet another Meta app, provides ample Rotor options for VoiceOver users on iOS, simple tasks like replying to and forwarding messages on Android require taking several steps. Such disparities highlight how third-party developers often follow the lead of platform creators. If Google doesn’t fully embrace Accessibility Actions, why should others? Of course, it’s comforting to name a few notable exceptions here like FairEmail, Feeder and Tusky for Mastodon which provide both ample and context-sensitive accessibility actions.

If Google consistently implemented and championed Accessibility Actions, third-party developers would likely feel more compelled to adopt them as well. Until Google steps up and prioritizes these improvements across its entire ecosystem, the accessibility community will continue to provide feedback and advocate for more inclusive design. Accessibility is not just about compliance—it’s about creating a better experience for everyone.