[Accessibility] Fix accessibility roles and states for radio buttons, checkboxes, and tabs by ashu75575 · Pull Request #81054 · Expensify/App

ashu75575 · 2026-01-30T19:26:07Z

Explanation of Change

Improves accessibility for selection lists and tab selector

Selection list items
- Radio role and checked/selected state for single-select options (Reports > Filters > Date dropdown).
- Checkbox role and checked/selected state for multi-select options (Reports > Filters > Status dropdown).
Tab selector
- Tab items now use the tab role (and accessibilityRole) instead of button, so screen readers treat them as tabs.

Fixed Issues

$ #79240
PROPOSAL: #79240 (comment)

Tests

Navigate to Reports > Filters > Date dropdown
Verify radio buttons are announced correctly with screen reader (VoiceOver/TalkBack)
Navigate to Track Distance feature (+ button > Track distance)
Verify tabs are announced correctly with screen reader
Navigate to Reports > Filters > Status dropdown
Verify checkboxes are announced correctly with screen reader

[X] Verify that no errors appear in the JS console

Offline tests

QA Steps

Same as tests

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

NOTE: This is a screen reader accessibility change with no visual differences. Testing requires screen reader software (VoiceOver on iOS/macOS or TalkBack on Android).

… tabs

codecov · 2026-01-30T19:55:44Z

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines	Coverage Δ
src/CONST/index.ts	`87.50% <ø> (ø)`
...components/SelectionList/ListItem/BaseListItem.tsx	`96.07% <100.00%> (+0.07%)`	⬆️
...nts/SelectionList/ListItem/MultiSelectListItem.tsx	`0.00% <ø> (ø)`
...omponents/SelectionList/ListItem/RadioListItem.tsx	`100.00% <ø> (ø)`
...ponents/SelectionListWithSections/BaseListItem.tsx	`95.74% <100.00%> (+0.09%)`	⬆️
...onents/SelectionListWithSections/RadioListItem.tsx	`88.00% <ø> (ø)`
...SelectionListWithSections/SingleSelectListItem.tsx	`0.00% <ø> (ø)`
src/components/TabSelector/TabSelectorItem.tsx	`100.00% <ø> (ø)`
... and 8 files with indirect coverage changes

melvin-bot · 2026-01-30T20:06:01Z

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

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 23adcc373d

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

chatgpt-codex-connector · 2026-01-30T20:20:17Z

src/components/SelectionListWithSections/BaseListItem.tsx

+    // Use radio role for single-select (e.g. Date dropdown options), checkbox for multi-select, button otherwise
+    const isRadioOption = !canSelectMultiple && !!rightHandSideComponent;
+    const isCheckboxOption = canSelectMultiple;


Avoid inferring radio roles from right-hand content

The new heuristic const isRadioOption = !canSelectMultiple && !!rightHandSideComponent treats any list row that supplies a right-hand component as a radio button. That’s not always true: e.g., SelectionListWithSections in src/pages/NewChatPage.tsx passes a right-hand component to render the “Add to group” button or select circle (see itemRightSideComponent), but the list isn’t a single-choice radio group and canSelectMultiple isn’t set. With this change those rows will be announced as radios with a checked state based on item.isSelected, which is misleading for screen reader users and changes behavior vs. before. Consider making the radio role explicit (e.g., a prop from RadioListItem) instead of inferring it from rightHandSideComponent presence.

Useful? React with 👍 / 👎.

eh2077

Looks good! @ashu75575 Are you able to test with simulators?

JmillsExpensify

Awesome polish for usability.

ashu75575 · 2026-02-02T18:40:31Z

Looks good! @ashu75575 Are you able to test with simulators?

Yes

#77540

Screen.Recording.2026-02-02.at.8.55.38.PM.mov

#77466

Screen.Recording.2026-02-02.at.8.56.34.PM.1.mov

#74848

Screen.Recording.2026-02-02.at.11.44.18.PM.mov

eh2077 · 2026-02-04T13:47:47Z

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

Screen.Recording.2026-02-04.at.9.50.40.PM.mov

iOS: mWeb Safari

MacOS: Chrome / Safari

eh2077

Looks good and tested well with iOS App

github-actions · 2026-02-04T21:54:51Z

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

github-actions · 2026-02-04T22:25:34Z

🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
Built from App PR #81054.

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-61b9931c578e2f3038d506c26c580cd89822a39a/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-c63ad10025a8003f6fdea06cdfba56769d7cd652/index.html

Web 🕸️
https://81054.pr-testing.expensify.com

👀 View the workflow run that generated this build 👀

OSBotify · 2026-02-05T20:48:27Z

🚀 Deployed to staging by https://github.com/marcochavezf in version: 9.3.13-1 🚀

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

OSBotify · 2026-02-05T21:48:53Z

🚀 Deployed to staging by https://github.com/marcochavezf in version: 9.3.15-0 🚀

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

Fix accessibility roles and states for radio buttons, checkboxes, and…

71ace07

… tabs

melvin-bot bot assigned ashu75575 Jan 30, 2026

code format

e5efd1c

ashu75575 marked this pull request as ready for review January 30, 2026 20:05

ashu75575 requested review from a team as code owners January 30, 2026 20:05

melvin-bot bot requested review from eh2077 and removed request for a team January 30, 2026 20:05

melvin-bot bot requested review from JmillsExpensify and removed request for a team January 30, 2026 20:06

Merge branch 'Expensify:main' into fix/79240

23adcc3

chatgpt-codex-connector bot reviewed Jan 30, 2026

View reviewed changes

ashu75575 and others added 7 commits January 31, 2026 15:31

fix ai comment

c826b49

Merge branch 'Expensify:main' into fix/79240

d6431ac

fix type checks

db43c01

fix eslint

a3d246b

fix tests

20cd080

Refactor accessibility roles in selection list items

79868b7

fix eslint

3360f03

eh2077 reviewed Feb 2, 2026

View reviewed changes

JmillsExpensify approved these changes Feb 2, 2026

View reviewed changes

eh2077 approved these changes Feb 4, 2026

View reviewed changes

melvin-bot bot requested a review from marcochavezf February 4, 2026 13:53

marcochavezf mentioned this pull request Feb 4, 2026

Fix accessibility roles and states for radio buttons and tabs #79704

Closed

17 tasks

marcochavezf approved these changes Feb 4, 2026

View reviewed changes

marcochavezf merged commit cd3b5ba into Expensify:main Feb 4, 2026
30 of 32 checks passed

OSBotify mentioned this pull request Feb 5, 2026

Deploy Checklist: New Expensify 2026-02-05 #81590

Open

Conversation

ashu75575 commented Jan 30, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

codecov bot commented Jan 30, 2026 • edited by github-actions bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

melvin-bot bot commented Jan 30, 2026

Uh oh!

chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

chatgpt-codex-connector bot Jan 30, 2026

Choose a reason for hiding this comment

Uh oh!

eh2077 left a comment

Choose a reason for hiding this comment

Uh oh!

JmillsExpensify left a comment

Choose a reason for hiding this comment

Uh oh!

ashu75575 commented Feb 2, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

eh2077 commented Feb 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviewer Checklist

Screenshots/Videos

Uh oh!

eh2077 left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

github-actions bot commented Feb 4, 2026

Uh oh!

github-actions bot commented Feb 4, 2026

Uh oh!

OSBotify commented Feb 5, 2026

Uh oh!

OSBotify commented Feb 5, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

ashu75575 commented Jan 30, 2026 •

edited

Loading

codecov bot commented Jan 30, 2026 •

edited by github-actions bot

Loading

ashu75575 commented Feb 2, 2026 •

edited

Loading

eh2077 commented Feb 4, 2026 •

edited

Loading