---
title: "Expose an asynchronous result update to assistive technology"
description: "Verify an async search has a visible result-count update and a separately observed assistive-technology announcement that describes the new result state."
canonical_url: "https://vostride.com/agent-library/accessibility-flows/async-result-announcement.md"
md_url: "https://vostride.com/agent-library/accessibility-flows/async-result-announcement.md"
content_kind: "recipe"
topic: "accessibility-flows"
---

# Expose an asynchronous result update to assistive technology

Verify an async search has a visible result-count update and a separately observed assistive-technology announcement that describes the new result state.

## Risk

A result count can update on screen without being announced, while a live region can announce stale or duplicate text. An independent screen-reader or semantic audit is required for the announcement claim.

## Fixtures

- A test directory contains exactly three records matching cedar and zero matching absent-cedar-qa.
- The design contract announces completed search result counts without moving focus away from the search field.
- A prepared assistive-technology session records announcements and focus behavior for both controlled query outcomes.

## Steps

1. Open the directory and verify the search control and baseline result area are visible.
2. Search cedar and verify exactly the three prepared record keys appear with a visible three-result count.
3. Use the separate assistive-technology procedure to verify a completed three-result announcement and retained search-field focus.
4. Replace the query with absent-cedar-qa and verify a visible no-results state.
5. Review the independent announcement log to verify the zero-result outcome is announced without repeating an obsolete three-result message after completion.

## Expected results

- The visible count and result membership agree with the fixture manifest for both queries.
- The separate assistive-technology evidence captures the required completed-result announcements.
- Focus behavior follows the stated non-disruptive contract; these findings are limited to this search flow and tested assistive setup.

## False-pass traps

- A live-region attribute in markup does not establish that the intended announcement was actually delivered.
- A visible no-results message alone cannot prove a nonvisual user received the update.

## Cleanup

- Clear the search query, close the assistive-technology fixture session, and remove directory fixtures.

## 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 test](/docs/agent-qa/configuration/test.md)
- [agent-qa first test](/docs/agent-qa/guides/first-test.md)
- [agent-qa web testing](/docs/agent-qa/guides/web-testing.md)

- [Accessibility workflow QA recipes](/agent-library/accessibility-flows.md)
- [Software factory QA library](/agent-library.md)