Fix: "No results" status message not announced by screen readers

[marufsharifi]

Explanation of Change

Before, when a search returned nothing, “No results found” appeared visually but was often silent to assistive tech. Now, that message is exposed as a polite status update on the web, so screen readers announce it when it appears.

Fixed Issues

$ #76958
PROPOSAL: #76958 (comment)

Tests

1. Using Chrome+JAWS, open the web app.
2. Navigate using the tab key to the Account button and press Enter to activate it.
3. Navigate using the tab key to the Security button and press Enter to activate it.
4. Move to the Address input field.
5. Start typing an invalid address to trigger No results found.
6. Observe the screen reader announcement.
7. When no matching results are found, verify the screen reader announces the displayed status message: 'No results found.`

• Verify that no errors appear in the JS console

Offline tests

Same as Tests.

QA Steps

Same as Tests.

// TODO: These must be filled out, or the issue title must include "[No QA]."

• Verify that no errors appear in the JS console

PR Author Checklist

• I linked the correct issue in the ### Fixed Issues section above
• I wrote clear testing steps that cover the changes made in this PR
  • I added steps for local testing in the Tests section
  • I added steps for the expected offline behavior in the Offline steps section
  • I added steps for Staging and/or Production testing in the QA steps section
  • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
  • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
• I included screenshots or videos for tests on all platforms
• I ran the tests on all platforms & verified they passed on:
  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
• I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
• I verified there are no new alerts related to the canBeMissing param for useOnyx
• I followed proper code patterns (see Reviewing the code)
  • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
  • I verified that comments were added to code that is not self explanatory
  • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
  • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
    • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
  • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
  • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
  • I verified the JSDocs style guidelines (in STYLE.md) were followed
• If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• I followed the guidelines as stated in the Review Guidelines
• I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
• I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
• I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
• I verified that if a function's arguments changed that all usages have also been updated correctly
• If any new file was added I verified that:
  • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
• If a new CSS style is added I verified that:
  • A similar style doesn't already exist
  • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
• If new assets were added or existing ones were modified, I verified that:
  • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
  • The assets load correctly across all supported platforms.
• If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
• If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
• If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
• If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
• If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
  • I verified that all the inputs inside a form are aligned with each other.
  • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
• If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
• I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
• If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Screen.Recording.2026-02-28.at.9.49.16.AM.mov

Android: mWeb Chrome

Screen.Recording.2026-02-25.at.2.40.03.PM.mov

iOS: Native

Screen.Recording.2026-02-28.at.10.00.50.AM.mov

iOS: mWeb Safari

Screen.Recording.2026-03-02.at.9.36.54.AM.mov

MacOS: Chrome / Safari

Screen.Recording.2026-03-01.at.2.22.26.PM.mov

[melvin-bot]

Hey! I see that you made changes to our Form component. Make sure to update the docs in FORMS.md accordingly. Cheers!

[codecov]

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.

Files with missing lines	Coverage Δ
src/App.tsx	100.00% <ø> (ø)
.../components/SelectionList/components/TextInput.tsx	100.00% <100.00%> (ø)
...onents/utils/useStatusAccessibilityAnnouncement.ts	100.00% <100.00%> (ø)
src/styles/index.ts	47.64% <ø> (ø)
...ListWithSections/BaseSelectionListWithSections.tsx	73.91% <71.42%> (-0.17%)	⬇️
src/components/AddressSearch/index.tsx	47.22% <42.85%> (-0.82%)	⬇️
src/components/SearchBar.tsx	0.00% <0.00%> (ø)
src/components/StatusAccessibilityAnnouncer.tsx	68.75% <68.75%> (ø)
src/libs/StatusAccessibilityAnnouncement.ts	12.50% <12.50%> (ø)
... and 17 files with indirect coverage changes

[rushatgabhane]

@marufsharifi is this ready for review?

[melvin-bot]

@suneox Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

[github-actions]

❌ CONSISTENCY-1 (docs)

StatusAccessibilityAnnouncer uses Platform.OS !== 'web' checks in both its useEffect (line 18) and its render return (line 62) to gate all behavior to web only. The codebase already has an established pattern for this: platform-specific file extensions. For example, useFormHelpMessageAccessibilityAnnouncement uses .ios.ts for iOS-specific logic and .ts as a no-op default.

Split StatusAccessibilityAnnouncer into platform-specific files:

• StatusAccessibilityAnnouncer.tsx (or index.web.tsx) with the web implementation
• StatusAccessibilityAnnouncer.native.tsx (or index.native.tsx) returning null

This eliminates the Platform.OS checks entirely and follows the project convention.

---

Please rate this suggestion with 👍 or 👎 to help us improve! Reactions are used to monitor reviewer efficiency.

[github-actions]

❌ CONSISTENCY-3 (docs)

The NoResultsStatusMessage component duplicates the same pattern used in SearchBar.tsx (lines 52-58), SelectionList/components/TextInput.tsx (lines 145-152), and BaseSelectionListWithSections.tsx (lines 1031-1037): a <Text> element with accessibilityLiveRegion="polite" and role="status" combined with a useStatusAccessibilityAnnouncement hook call. This pattern is repeated across four components.

Consider extracting a single shared NoResultsStatusMessage (or AccessibleStatusText) component that encapsulates both the hook call and the ARIA live region Text. This would consolidate the duplicated pattern into one reusable component used across all four integration points.

---

Please rate this suggestion with 👍 or 👎 to help us improve! Reactions are used to monitor reviewer efficiency.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e99424a15b

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[dubielzyk-expensify]

LGTM 👍 There seems to be a tiny delay on iOS native, but no big deal

[rushatgabhane]

@suneox all yours

[suneox]

@marufsharifi There's a conflict & almost rule ❌ CONSISTENCY is make sense we need to apply & if any rule doesn't apply please provide comment feedback on these rules

[marufsharifi]

@suneox, could you please take a look at the conflicts, since I don't have access to those files. thanks.

[suneox]

@suneox, could you please take a look at the conflicts, since I don't have access to those files. thanks.

Since you have commit src include Mobile-Expensify You can remove Mobile-Expensify folder & re-run git submodule init

[marufsharifi]

@suneox, I've addressed all your comments. Please take another look. thanks.

[marufsharifi]

@suneox, kindly bump. thanks.

[suneox]

Let waiting for #83801 as a comment

[suneox]

This change shouldn't include in the PR, if can not resolve we need to create new PR after finish #83801

[rushatgabhane]

@marufsharifi gentle bump ^^

[rushatgabhane]

hey, im closing this and reassigning because it's at risk of not being implemented in the deadline

i noticed a lot of anti patterns in this PR - eg: use of platform in files. so it is gonna take time to fix all that