Skip to content

fix: Hide from Assistive Tech and Remove Interactive Role#79590

Closed
Uzaifm127 wants to merge 10 commits intoExpensify:mainfrom
Uzaifm127:fix/79243
Closed

fix: Hide from Assistive Tech and Remove Interactive Role#79590
Uzaifm127 wants to merge 10 commits intoExpensify:mainfrom
Uzaifm127:fix/79243

Conversation

@Uzaifm127
Copy link
Contributor

Explanation of Change

Two accessibility issues:

  • Toggle/checkbox labels announced twice: Text labels next to Switch components were being announced separately from the Switch's accessibilityLabel, causing duplicate announcements.
  • Plain text elements announced as actionable: MenuItem components with interactive={false} were still receiving accessibility props (role, accessibilityLabel, accessible) that made screen readers announce them as actionable elements.

Fixed Issues

$ #79243
$ #77497
$ #77496
PROPOSAL: #79243 (comment)

Tests

  1. Enable VoiceOver (iOS/Mac) or TalkBack (Android)

First issue: Toggle/checkbox labels announced twice

  1. Navigate to Settings > Preferences
    • Swipe through toggle switches ("Receive relevant feature updates" and "Mute all sounds")
    • Verify each label is announced only once (from the Switch, not from the Text)
  2. Navigate to Workspace > Tags > Settings
    • Swipe through "Requires tag" and "Track billable" switches
    • Verify labels are announced only once
  3. Navigate to Workspace > Tags > Tag Settings (open an individual tag)
    • Swipe through the "Enable tag" switch
    • Verify label is announced only once
  4. Navigate to Workspace > Tags > Import Multi-Level Tags
    • Swipe through all three switches ("First row is header", "Independent tags", "GL adjacent column")
    • Verify each label is announced only once
  5. Navigate to Workspace > Taxes > Edit Tax
    • Swipe through the "Enable" switch
    • Verify label is announced only once
  6. Navigate to Workspace > Rules > Prohibited Expenses
    • Swipe through prohibited expense toggles (Adult Entertainment, Alcohol, Gambling, Hotel Incidentals, Tobacco)
    • Verify each label is announced only once
  7. Navigate to Workspace > Categories > Category Settings
    • Swipe through "Enable category" and "Require description" switches
    • Verify labels are announced only once
  8. Navigate to Workspace > Distance Rates > Settings
    • Swipe through the "Track tax" switch
    • Verify label is announced only once
  9. Navigate to Domain > SAML Login Settings
    • Swipe through "Enable SAML login" and "Require SAML login" switches
    • Verify labels are announced only once
  10. Navigate to Workspace > Report Fields > Value Settings
    • Swipe through the "Enable value" switch
    • Verify label is announced only once
  11. Navigate to Settings > Profile > Timezone
    • Swipe through the "Get location automatically" switch
    • Verify label is announced only once

Second issue: Plain text elements announced as actionable

  1. Navigate to Settings > Wallet > Expensify Card
    • Swipe to "Virtual card number" (masked card number)
    • Verify it's announced as static text without "double-tap to activate" hint
  2. Navigate to Settings > Wallet > Card Details (after revealing card details)
    • Swipe through card number, expiration, CVV, and address
    • Verify all are announced as static text without actionable hints
  3. Navigate to Workspace > Company Cards > Card Details
    • Swipe through card number and available spend
    • Verify they're announced as static text without actionable hints
  4. Navigate to Workspace > Expensify Card > Card Details
    • Swipe through card number and available spend
    • Verify they're announced as static text without actionable hints
  5. Navigate to Workspace > Report Fields > Settings
    • Swipe through "Name" and "Type" fields
    • Verify they're announced as static text without actionable hints
  6. Navigate to Workspace > Members > Member Details
    • Swipe through email/phone number field
    • Verify it's announced as static text without actionable hints
  • Verify that no errors appear in the JS console

Offline tests

N/A - These are accessibility attribute changes that don't affect offline behavior or network requests.

QA Steps

  1. Enable screen reader on device (VoiceOver on iOS/Mac or TalkBack on Android)
  2. Navigate through all affected screens:
    • Settings > Preferences
    • Workspace > Tags > Settings
    • Workspace > Tags > Tag Settings
    • Workspace > Tags > Import Multi-Level Tags
    • Workspace > Taxes > Edit Tax
    • Workspace > Rules > Prohibited Expenses
    • Workspace > Categories > Category Settings
    • Workspace > Distance Rates > Settings
    • Domain > SAML Login
    • Workspace > Report Fields > Value Settings
    • Settings > Profile > Timezone
    • Settings > Wallet > Expensify Card
    • Settings > Wallet > Card Details
    • Workspace > Company Cards > Card Details
    • Workspace > Expensify Card > Card Details
    • Workspace > Report Fields > Settings
    • Workspace > Members > Member Details
  3. For each screen with toggle switches:
    • Swipe through each switch
    • Verify the label is announced only once (not duplicated)
  4. For each screen with static text elements (card numbers, amounts, etc.):
    • Swipe to static text elements
    • Verify they're announced as static text without "double-tap to activate" hints

// 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](http://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

N/A - Accessibility changes

Android: mWeb Chrome

N/A - Accessibility changes

iOS: Native

N/A - Accessibility changes

iOS: mWeb Safari

N/A - Accessibility changes

MacOS: Chrome / Safari

N/A - Accessibility changes

@Uzaifm127 Uzaifm127 requested review from a team as code owners January 14, 2026 17:56
@melvin-bot melvin-bot bot requested review from JmillsExpensify and dominictb and removed request for a team January 14, 2026 17:56
@melvin-bot
Copy link

melvin-bot bot commented Jan 14, 2026

@dominictb 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 a team and Valforte and removed request for a team January 14, 2026 17:56
@melvin-bot
Copy link

melvin-bot bot commented Jan 14, 2026

@Valforte 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]

@codecov
Copy link

codecov bot commented Jan 14, 2026

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: d3e2e0e659

ℹ️ 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".

@dominictb
Copy link
Contributor

TS check is failing.

@Uzaifm127
Copy link
Contributor Author

Fixing...

@Uzaifm127
Copy link
Contributor Author

@dominictb Fixed.

Copy link
Contributor

@JmillsExpensify JmillsExpensify left a comment

Choose a reason for hiding this comment

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

No product review required.

@rushatgabhane
Copy link
Member

@Uzaifm127 please fix conflicts, @dominictb lemme know if rest looks okay?

@Uzaifm127
Copy link
Contributor Author

@rushatgabhane @dominictb

Fixed the conflicts.

@dominictb
Copy link
Contributor

I'm checking this. Should be done today

{(isHovered) => (
<PressableWithSecondaryInteraction
onPress={shouldCheckActionAllowedOnPress ? callFunctionIfActionIsAllowed(onPressAction, isAnonymousAction) : onPressAction}
// eslint-disable-next-line react/jsx-props-no-spreading
Copy link
Contributor

Choose a reason for hiding this comment

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

Let's not disable lint unless we had a very specific reason to do so. If you had one, please add a code comment here explaining.

accessible={shouldBeAccessible}
tabIndex={tabIndex}
role={interactive ? role : undefined}
// eslint-disable-next-line react/jsx-props-no-spreading
Copy link
Contributor

Choose a reason for hiding this comment

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

Same ^

: {
accessible: false,
})}
focusable={interactive}
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we need to set this prop when we already had tabIndex?

@dominictb
Copy link
Contributor

dominictb commented Jan 26, 2026

BUG

The accessibility announced twice issue is not fixed for me in workspace Workflows page:

Screenshot 2026-01-27 at 00 08 12

You can see in the screenshot, VoiceOver announced the label twice. Can you check all places we're using Switch/Checkbox having the same issue and fix them all?

Copy link
Contributor

@dominictb dominictb left a comment

Choose a reason for hiding this comment

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

Please add recordings. You don't have to add recordings for all cases, just the original reported places.

Also please update the QA Steps section to only cover 1-2 places. It's great to see your Tests section should cover all manual test cases but please leave 1-2 cases only for QA Steps to help testing this PR easier.

@dominictb
Copy link
Contributor

@Valforte Can you run test builds for this?

@Valforte
Copy link
Contributor

Building

@github-actions
Copy link
Contributor

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

@github-actions
Copy link
Contributor

@Uzaifm127
Copy link
Contributor Author

@dominictb Thanks for pointing out.

Checking...

@Uzaifm127 Uzaifm127 requested review from a team, stephanieelliott and tgolen as code owners January 28, 2026 17:20
@github-actions
Copy link
Contributor

⚠️ This PR is possibly changing native code and/or updating libraries, it may cause problems with HybridApp. Please check if any patch updates are required in the HybridApp repo and run an AdHoc build to verify that HybridApp will not break. Ask Contributor Plus for help if you are not sure how to handle this. ⚠️

@Uzaifm127 Uzaifm127 closed this Jan 28, 2026
@Uzaifm127
Copy link
Contributor Author

Uzaifm127 commented Jan 28, 2026

Extremely sorry everyone,
I was trying to revert the changes in this branch but it reverted something else by mistake.

Closed the PR.

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.

5 participants