Skip to content

fix: Screen Readers: Many Pages: The status message of no results is not announced.#85166

Merged
marcaaron merged 15 commits intoExpensify:mainfrom
Krishna2323:krishna2323/issue/76958
Mar 17, 2026
Merged

fix: Screen Readers: Many Pages: The status message of no results is not announced.#85166
marcaaron merged 15 commits intoExpensify:mainfrom
Krishna2323:krishna2323/issue/76958

Conversation

@Krishna2323
Copy link
Contributor

@Krishna2323 Krishna2323 commented Mar 13, 2026

Explanation of Change

Fixed Issues

$ #76958
PROPOSAL:

Tests

  • Same as QA Steps

  • Verify that no errors appear in the JS console

Offline tests

  • Same as QA Steps

QA Steps

  1. Using Chrome+JAWS, open the URL - https://new.expensify.com/
  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. Verify when no matching results are found, the screen reader announces 'No results found'.

Other Occurrences:

  1. On Settings - Profile - Pronouns
  2. On Settings - Profile - Address - Country
  3. On Workspace - Categories
  4. On Workspace - Company cards: the options of countries
  5. On Workspace - Create Workspace - Default Currency
  6. On Track Distance - Choose Recipient
  7. On Wallet - Add bank account
  8. On Chat - Contacts
  • 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
    • MacOS: Desktop
  • 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
android_native.mp4
Android: mWeb Chrome
android_chrome.mp4
iOS: Native
iOS: mWeb Safari
ios_safari.mp4
MacOS: Chrome / Safari
web_chrome.mp4

…not announced.

Signed-off-by: krishna2323 <belivethatkg@gmail.com>
@melvin-bot
Copy link

melvin-bot bot commented Mar 13, 2026

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

Signed-off-by: krishna2323 <belivethatkg@gmail.com>
@Krishna2323
Copy link
Contributor Author

@codex review

Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 1a417b0e23

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

…picker, workflows page, and import contacts

Signed-off-by: krishna2323 <belivethatkg@gmail.com>
Signed-off-by: krishna2323 <belivethatkg@gmail.com>
@codecov
Copy link

codecov bot commented Mar 13, 2026

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/CONST/index.ts 93.54% <ø> (ø)
.../components/SelectionList/components/TextInput.tsx 100.00% <100.00%> (ø)
...ListWithSections/BaseSelectionListWithSections.tsx 74.31% <100.00%> (-0.06%) ⬇️
src/components/Table/TableBody.tsx 100.00% <100.00%> (ø)
...rc/hooks/useAccessibilityAnnouncement/index.ios.ts 100.00% <ø> (ø)
...hooks/useAccessibilityAnnouncement/index.native.ts 0.00% <ø> (ø)
src/hooks/useDebouncedAccessibilityAnnouncement.ts 100.00% <100.00%> (ø)
src/hooks/useDebouncedValue.ts 100.00% <100.00%> (ø)
src/components/AddressSearch/index.tsx 47.66% <25.00%> (-1.38%) ⬇️
src/components/SearchBar.tsx 0.00% <0.00%> (ø)
... and 6 more
... and 49 files with indirect coverage changes

Signed-off-by: krishna2323 <belivethatkg@gmail.com>
Signed-off-by: krishna2323 <belivethatkg@gmail.com>
…ements on Android

Signed-off-by: krishna2323 <belivethatkg@gmail.com>
Signed-off-by: krishna2323 <belivethatkg@gmail.com>
@Krishna2323 Krishna2323 marked this pull request as ready for review March 13, 2026 07:42
@Krishna2323 Krishna2323 requested review from a team as code owners March 13, 2026 07:42
@melvin-bot melvin-bot bot requested review from aimane-chnaif and removed request for a team March 13, 2026 07:42
@melvin-bot
Copy link

melvin-bot bot commented Mar 13, 2026

@aimane-chnaif 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]

@melvin-bot melvin-bot bot requested review from joekaufmanexpensify and removed request for a team March 13, 2026 07:42
@Krishna2323
Copy link
Contributor Author

@aimane-chnaif The PR is ready for review.

@rushatgabhane I couldn’t test the iOS native app. Should that be tested after the PR is merged, or can QA test it on the PR?

Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 8c1a333df4

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

…ic into reusable hook.

Signed-off-by: krishna2323 <belivethatkg@gmail.com>
@aimane-chnaif
Copy link
Contributor

@aimane-chnaif The PR is ready for review.

@rushatgabhane I couldn’t test the iOS native app. Should that be tested after the PR is merged, or can QA test it on the PR?

I tested on my iPhone and works well.

@Krishna2323
Copy link
Contributor Author

Thanks a lot @aimane-chnaif 🙇🏻

@aimane-chnaif
Copy link
Contributor

On web, "No results found" announcement is cut off in the middle by full search keyword reading. Maybe adjust timeout?

i.e. I type abcde
Screen reader: "No results abcde"

web.mov

Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f2343cf320

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment on lines +128 to +130
onChangeText={(text: string) => {
setSearchText(text);
filterEmojis(text);

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Preserve native emoji-search debouncing across input changes

Updating searchText inside onChangeText forces a re-render on every keystroke, which recreates filterEmojis (a lodashDebounce defined in render scope) before its previous timer fires. That means each rapid keypress schedules independent stale callbacks, so the list can momentarily render outdated results (a then ab before abc) and do extra filtering work instead of honoring a single debounced update after typing pauses.

Useful? React with 👍 / 👎.

@joekaufmanexpensify
Copy link
Contributor

No product review needed

@MelvinBot
Copy link
Contributor

🔍 Code Review — PR #85166

Summary: This PR adds screen reader announcements for "No results found" across multiple components, implementing a debounced announcement pattern via two new hooks (useDebouncedValue, useDebouncedAccessibilityAnnouncement) and a real web implementation of useAccessibilityAnnouncement.

Overall the approach is sound — the debounce-then-announce pattern is a good way to avoid interrupting the screen reader during typing. A few issues worth addressing:


Issues

1. Missing aria-hidden on visible text in AddressSearchListEmptyComponent and BaseEmojiPickerMenu.ListEmptyComponent

Most components correctly add aria-hidden to the visible "No results found" text so the screen reader only hears the programmatic announcement (via the hidden aria-live region). However, these two components leave the visible <Text> exposed to the accessibility tree:

  • src/components/AddressSearch/index.tsx:59 — no aria-hidden
  • src/components/EmojiPicker/EmojiPickerMenu/BaseEmojiPickerMenu.tsx:87 — no aria-hidden

Compare with SearchBar.tsx:57, SelectionList/components/TextInput.tsx:149, BaseSelectionListWithSections.tsx, and TableBody.tsx:72 which all correctly set aria-hidden. Without this, users may hear the message twice on web — once from the visible text and once from the aria-live region.

2. Broadened announcement scope in SelectionList/components/TextInput.tsx

The old code specifically gated announcements on the "No results found" message:

const shouldAnnounceNoResults = shouldShowHeaderMessage && isNoResultsFoundMessage;

The new code announces any header message when visible and not loading:

useDebouncedAccessibilityAnnouncement(headerMessage ?? '', shouldShowHeaderMessage && !isLoading, value ?? '');

This means any custom headerMessage passed to a SelectionList (not just "No results found") will now be announced via the aria-live region — while also being aria-hidden in the visual text. Is this intentional? If so, it's a good accessibility improvement. If not, the condition should be narrowed back to isNoResultsFoundMessage.

3. Unnecessary dependencies in WorkspaceWorkflowsPage.tsx useMemo

isNoResults and noResultsMessage were added to the optionItems useMemo dependency array (lines 516-517), but neither is used inside the useMemo callback. They're only used in the JSX return below the memo. These should be removed from the dependency array — they're derived from workflowSearchInput and searchFilteredWorkflows which are already tracked, so this won't cause bugs, but it's misleading clutter.

4. Type safety in useDebouncedValue

The hook initializes state as undefined but the return type asserts T:

const [debouncedValue, setDebouncedValue] = useState<T | undefined>(undefined);
// ...
return debouncedValue as T;

The undefined initial value is intentional (to prevent false value === debouncedValue on mount), and the cast works correctly in practice because the only consumer (useDebouncedAccessibilityAnnouncement) compares searchValue === debouncedSearchValuestring !== undefined is always false, which is the desired behavior. However, the type cast hides this from TypeScript. Consider either:

  • Returning T | undefined and updating the caller to handle it, or
  • Adding a brief comment explaining why the cast is safe

Minor observations (non-blocking)

  • Stale announcement children in useAccessibilityAnnouncement: The effect cleanup clears the timeout and resets the ref, but doesn't remove the child <div role="alert"> from the wrapper. Old announcement text stays in the DOM until the next announcement clears it. In practice this is fine since the wrapper is aria-live="assertive" and screen readers only announce changes, but it's worth being aware of.

  • ImportContactButton/index.native.tsx uses useAccessibilityAnnouncement directly (non-debounced) while all other components use useDebouncedAccessibilityAnnouncement. This is presumably intentional since this component is native-only and the announcement is gated by isInSearch, but it breaks the pattern slightly.


What looks good

  • The useDebouncedValue + useDebouncedAccessibilityAnnouncement composition is clean and reusable
  • The singleton getWrapper() pattern for the DOM aria-live container avoids creating multiple live regions
  • The prevShouldAnnounceRef guard in useAccessibilityAnnouncement correctly prevents re-announcing the same message without a shouldAnnounceMessage toggle cycle
  • The 1000ms debounce + 300ms DOM delay timing is well-reasoned for VoiceOver's word echo behavior
  • aria-hidden pattern on visible text (where applied) correctly prevents double announcements

@chatgpt-codex-connector
Copy link

Codex Review: Something went wrong. Try again later by commenting “@codex review”.

We were unable to download your code in a timely manner.
ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

@aimane-chnaif
Copy link
Contributor

Reviewer Checklist

  • I have verified the author checklist is complete (all boxes are checked off).
  • I verified the correct issue is linked in the ### Fixed Issues section above
  • I verified testing steps are clear and they cover the changes made in this PR
    • I verified the steps for local testing are in the Tests section
    • I verified the steps for Staging and/or Production testing are in the QA steps section
    • I verified the steps cover any possible 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 checked that screenshots or videos are included for tests on all platforms
  • I included screenshots or videos for tests on all platforms
  • I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
  • I verified tests pass on all platforms & I tested again on:
    • Android: HybridApp
    • Android: mWeb Chrome
    • iOS: HybridApp
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
    • MacOS: Desktop
  • If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
  • I verified there are no new alerts related to the canBeMissing param for useOnyx
  • I verified proper code patterns were followed (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
    • 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 verified that this PR follows the guidelines as stated in the Review Guidelines
  • I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
  • 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
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately and each prop has a /** comment above it */
    • The file is named correctly
    • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    • The only data being stored in the state is data necessary for rendering and nothing else
    • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
    • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
    • All JSX used for rendering exists in the render method
    • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
  • 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 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.
  • For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this 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.
  • I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp
Android: mWeb Chrome
iOS: HybridApp
iOS: mWeb Safari
MacOS: Chrome / Safari Screenshot 2026-03-15 at 3 37 10 pm Screenshot 2026-03-15 at 3 37 47 pm Screenshot 2026-03-15 at 3 38 10 pm Screenshot 2026-03-15 at 3 38 27 pm Screenshot 2026-03-15 at 3 39 24 pm Screenshot 2026-03-15 at 3 39 50 pm Screenshot 2026-03-15 at 3 40 22 pm Screenshot 2026-03-15 at 3 40 51 pm

Copy link
Contributor

@aimane-chnaif aimane-chnaif left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please address ai reviews above

<Text style={[styles.textLabel, styles.colorMuted, styles.minHeight5]}>{headerMessage}</Text>
<Text
style={[styles.textLabel, styles.colorMuted, styles.minHeight5]}
aria-hidden
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does aria-hidden fix anything? I don't see any changes in behavior, same as production.
On web, text is not readable.
On native, text is readable.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

aria-hidden prevents potential double announcements on web.

@aimane-chnaif
Copy link
Contributor

Failing job 3 is directly related to this PR

Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 5409b5af15

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

…ments

- Add aria-hidden to AddressSearch and BaseEmojiPickerMenu visible text
  to prevent double screen reader announcements (matching other components)
- Extract UseAccessibilityAnnouncementOptions type to shared types file
- Extract WorkflowNoResultsView component in WorkspaceWorkflowsPage and
  remove redundant isNoResults/noResultsMessage from useMemo deps
- Stabilize emoji picker filter debounce/throttle using ref-based pattern
  to prevent re-renders from recreating timers
- Fix DebugReportActionsTest to handle aria-hidden text with includeHiddenElements

Made-with: Cursor
@melvin-bot
Copy link

melvin-bot bot commented Mar 15, 2026

We did not find an internal engineer to review this PR, trying to assign a random engineer to #76958 as well as to this PR... Please reach out for help on Slack if no one gets assigned!

@melvin-bot melvin-bot bot requested a review from marcaaron March 15, 2026 18:45
Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 8ff7400305

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Signed-off-by: krishna2323 <belivethatkg@gmail.com>
@marcaaron marcaaron merged commit c785587 into Expensify:main Mar 17, 2026
31 checks passed
@github-actions
Copy link
Contributor

🚧 @marcaaron has triggered a test Expensify/App build. You can view the workflow run here.

@OSBotify
Copy link
Contributor

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

@OSBotify
Copy link
Contributor

🚀 Deployed to staging by https://github.com/marcaaron in version: 9.3.40-0 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 failure ❌
🍎 iOS 🍎 success ✅

@OSBotify
Copy link
Contributor

🚀 Deployed to staging by https://github.com/marcaaron in version: 9.3.40-0 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

@IuliiaHerets
Copy link

Hi @Krishna2323. Is it enough to test this on Web?

@jponikarchuk
Copy link

@Krishna2323 @aimane-chnaif @joekaufmanexpensify @rushatgabhane Could you please clarify if it's expected that we can't open Start/Stop waypoint in Track distance with Enter key if using Chrome+JAWS? Only Shift + Enter works

Grabando.485.mp4

@Krishna2323
Copy link
Contributor Author

Could you please clarify if it's expected that we can't open Start/Stop waypoint in Track distance with Enter key if using Chrome+JAWS? Only Shift + Enter works

@jponikarchuk no, its not expected. The enter key press should open Start/Stop waypoint page.

@OSBotify
Copy link
Contributor

🚀 Deployed to production by https://github.com/cristipaval in version: 9.3.41-4 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants