# Support Time to Take Action with Compose

DevFeed: [Support Time to Take Action with Compose](<https://devfeed.tech/articles/support-time-to-take-action-with-compose-38496.md>)

Original publisher: [Read original article](<https://eevis.codes/blog/2024-12-28/support-time-to-take-action-with-compose/>)

Author: Eevis Panula

Published: 2024-12-28T09:46:59.418000Z

Content type: tutorial

Language: en

Sources: [Eevis Blog](<https://devfeed.tech/sources/eevis-blog.md>)

Topics: [Accessibility](<https://devfeed.tech/topics/accessibility.md>), [Android](<https://devfeed.tech/topics/android.md>), [Compose](<https://devfeed.tech/topics/compose.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>), [Code](<https://devfeed.tech/topics/code.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [android](<https://devfeed.tech/tags/android.md>), [blog-post](<https://devfeed.tech/tags/blog-post.md>), [components](<https://devfeed.tech/tags/components.md>), [compose](<https://devfeed.tech/tags/compose.md>), [custom](<https://devfeed.tech/tags/custom.md>), [developers](<https://devfeed.tech/tags/developers.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [settings](<https://devfeed.tech/tags/settings.md>), [users](<https://devfeed.tech/tags/users.md>)

## AI overview

This tutorial explains Android's Time to take action accessibility setting, which controls how long temporary messages remain visible. It describes why users may need additional time and shows why custom Compose components must explicitly support the setting.

## Source excerpt

While working on my master's thesis and the Android Accessibility Checklist, one of the answers to my survey mentioned an accessibility setting called time to take action. Since then, I've been curious about it and wanted to write a blog post as I feel it's one of the undersupported accessibility settings and really useful for those who utilize it. So, what is time to take action, and why would someone use it? And why should we, as developers, care? Let's talk about that first. Time to Take Action Time to take action is a setting that controls the minimum time in which temporary messages asking a user to take action are shown. So, for example, when you press the volume buttons on your Android phone, you should see the volume controls next to the volume buttons, and this setting controls how long they're visible. This setting has different options: Default, 10 seconds, 30 seconds, 1 minute and 2 minutes. You can find them from Settings -> Accessibility Settings -> Timing controls -> Time to take action (Accessibility timeout). The screen looks something like this, depending on your phone's version and manufacturer: And why would someone need this setting? Well, the source code and documentation for a method we're going to use in a moment puts it pretty well: Some users may need extra time to review the controls, or to reach them, or to activate assistive technology to activate the controls automatically. Okay, now we've established what the time to take action is. However, the question of relevance remains: Why should we care as developers? Isn't it something that the operating system handles automatically? The answer is yes and no. Most components on the operating system level and Material3 components respect this setting. However, when you're building a custom component, it's not automatically respected, and you'll need to add support for it. That's why the settings page mentions that not all apps support the setting. The thing is, developers usually don't know abo