---
title: "Verify Android large text keeps critical actions usable"
description: "Exercise an Android approval form with text scaling prepared externally to catch clipped decisions, inaccessible validation, and hidden final actions."
canonical_url: "https://vostride.com/agent-library/android-flows/large-text-critical-action.md"
md_url: "https://vostride.com/agent-library/android-flows/large-text-critical-action.md"
content_kind: "recipe"
topic: "android-flows"
---

# Verify Android large text keeps critical actions usable

Exercise an Android approval form with text scaling prepared externally to catch clipped decisions, inaccessible validation, and hidden final actions.

## Risk

Text scaling can change which control receives a tap and can hide the explanation for a blocked action. Verify the whole decision journey at the prepared size rather than relying on a static screenshot.

## Fixtures

- An external Android device fixture configured to the product-supported large text setting; record that setting without assuming agent-qa changes accessibility controls.
- A sandbox approval app target with explicit mobile app state and a pending request containing a long title, amount, and explanatory text.
- A test approver with a read-only approval-history oracle and a requirement that rejection requires a reason.

## Steps

1. Open the fixture request and verify its complete amount, requester, and decision status are readable at the prepared text size.
2. Choose Reject without a reason and verify a visible reason-specific validation message appears while the request remains pending.
3. Enter the unique reason, scroll through the form if needed, and verify the final rejection control is reachable and distinguishable from approval.
4. Submit the rejection and verify the request detail shows Rejected with the complete reason rather than an approval state.
5. Inspect the independent decision history and verify one rejection by the test approver, no approval entry, and the exact untruncated reason.

## Expected results

- Critical identity, amount, validation, and final-action text remain discoverable at the prepared setting.
- The committed decision is rejection with the intended complete reason.
- The approval history contains no competing or duplicate decision for the request.

## False-pass traps

- A readable heading does not establish that the final action below the fold is reachable.
- A green completion banner can appear after the wrong decision control was activated.

## Cleanup

- Reset the request through the sandbox fixture and restore the external text-size baseline.

## Use with agent-qa

Adapt this test design to your application's acceptance criteria and configured target using the [recipe execution guide](/agent-library/software-factory/turn-a-recipe-into-an-agent-qa-test.md). External fixture setup and non-UI checks require your own supported hooks or test tooling. Validate the authored test, execute it, and inspect the completed evidence; this recipe is not a recorded test result.

## References

- [agent-qa mobile testing](/docs/agent-qa/guides/mobile-testing.md)
- [agent-qa test](/docs/agent-qa/configuration/test.md)
- [agent-qa hooks](/docs/agent-qa/guides/hooks.md)

- [Android application QA recipes](/agent-library/android-flows.md)
- [Software factory QA library](/agent-library.md)