Remove interactive role and double announcement for switches by Uzaifm127 · Pull Request #80765 · Expensify/App

Uzaifm127 · 2026-01-28T17:52:00Z

Explanation of Change

Removed the double announcement for Switches.
Removed the "double tap to activate" for menu item for plain text in Android/iOS.

Fixed Issues

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

Tests

Test 1: Double announcement for switches.

Precondition: User is logged in.

Using VoiceOver on iOS or TalkBack on Android, open the app.
Swipe right to focus the Workspaces tab and double-tap to activate it.
Choose a workspace, if workspace list is there otherwise skip this step.
Swipe right to focus the More features option and double-tap to activate it.
Swipe right to focus on any switch on More features.
Verify that each switch is announced only once.

Other occurrence for this:

From Step 2 or 3.

Swipe right to focus the Workflows option and double-tap to activate it.
Swipe right to focus on "Submissions", "Approvals" and "Payment" switches.
Verify that each switch is announced only once.

Test 2: Plain text announced as actionable (Android)

Precondition: You must have a virtual Expensify Card issued and visible in the wallet.

Enable TalkBack on Android.
Open the Expensify app.
Swipe right to focus the Account tab and double-tap to activate it.
Swipe right to focus the Wallet button and double-tap to activate it.
Swipe right to focus the Expensify Card menu item near "Assigned cards" and double-tap to activate it.
Swipe right to focus either on "Virtual card number", "Remaining limit" or Smart limit" menu item.
Verify that Talkback doesn't announce "double tap to activate it".

Test 3: Toggle/checkbox label announced twice - #77497

Precondition: User is logged in.

Using VoiceOver on iOS or TalkBack on Android, open the app or open the web app on Android chrome.
Swipe right to focus the Account tab and double-tap to activate it.
Swipe right to focus the Preferences button and double-tap to activate it.
Swipe right to focus the toggle buttons and the visible text next to toggle buttons.
Verify that Only the toggle buttons receive focus.
Verify that the visible text next to the toggle is not be focusable.
Verify that screen readers announce the label once via the toggle

Verify that no errors appear in the JS console

Offline tests

These are accessibility changes that don't affect offline behavior.

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

Screenshots/Videos

Android: Native

Double announcement for switches.

Android-native-3.mov

Plain text announced as actionable

Android-native-2.mov

Toggle/checkbox label announced twice

Android-native-1.mov

Android: mWeb Chrome

Double announcement for switches.

Android-mWeb-3.mov

Plain text announced as actionable

Android-mWeb-2.mov

Toggle/checkbox label announced twice

Android-mWeb-1.mov

iOS: Native

Double announcement for switches.

ios-native-3.mov

Toggle/checkbox label announced twice

ios-native-1.mp4

iOS: mWeb Safari

Double announcement for switches.

ios-mWeb-3.mov

Toggle/checkbox label announced twice

ios-mWeb-1.mov

MacOS: Chrome / Safari

…ve platforms like Android or iOS

codecov · 2026-01-29T13:23:41Z

Codecov Report

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

Files with missing lines	Coverage Δ
src/components/ImportSpreadsheetColumns.tsx	`0.00% <ø> (ø)`
src/components/MenuItem.tsx	`88.34% <100.00%> (+0.05%)`	⬆️
...c/components/ReportActionItem/MoneyRequestView.tsx	`0.24% <ø> (ø)`
src/components/TestToolMenu.tsx	`88.57% <100.00%> (+1.07%)`	⬆️
src/components/TestToolRow.tsx	`100.00% <100.00%> (ø)`
...ages/workspace/categories/CategorySettingsPage.tsx	`0.00% <ø> (ø)`
...ges/workspace/rules/RulesProhibitedDefaultPage.tsx	`0.00% <ø> (ø)`
src/pages/workspace/tags/TagSettingsPage.tsx	`0.00% <ø> (ø)`
...pages/workspace/tags/WorkspaceTagsSettingsPage.tsx	`0.00% <ø> (ø)`
src/pages/domain/Saml/SamlLoginSectionContent.tsx	`0.00% <0.00%> (ø)`
... and 10 more
... and 12 files with indirect coverage changes

melvin-bot · 2026-01-29T14:39:41Z

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

Uzaifm127 · 2026-01-29T14:48:28Z

@dominictb Here is the overview of this PR.

We've got two issues.

#77497 - Not reproducible now
#77496 - Reproducible now

The first issue isn't reproducible so instead of that we are covering this issue pointed out by @dominictb

I've provided the recordings on Android native for both issues we are solving in this PR. We might need to run the test build for this to check on other platforms.

Uzaifm127 · 2026-02-02T14:12:02Z

@joekaufmanexpensify @dominictb Kindly bump for PR review.

joekaufmanexpensify

Fine from a product perspective

mallenexpensify · 2026-02-04T23:42:34Z

@Uzaifm127 apologies for the delay from @dominictb , they're offboarding. I pinged them in Slack to see if they'll review or if we need a new C+

dominictb

Normally when the implementation deviates from the initial proposal, we'd ask to update the proposal first.

dominictb · 2026-02-05T16:10:55Z

src/pages/workspace/workflows/ToggleSettingsOptionRow.tsx

                    <Switch
                        disabledAction={disabledAction}
-                        accessibilityLabel={typeof subtitle === 'string' && subtitle ? `${switchAccessibilityLabel}, ${subtitle}` : switchAccessibilityLabel}
+                        accessibilityLabel={


Can you explain a bit about your fix here for #79590 (comment)?

Also, can you also give a brief description why the first issue #77497 is no longer reproducible? But we only had this instance left? Are there any similar instances?

Can you explain a bit about your fix here for #79590 (comment)?

#79590 (comment) - This issue is the regression from this PR: #79149, so we aren't removing this completely instead we only preventing it if the accessibilityLabel and subtitle are same.

Also, can you also give a brief description why the first issue #77497 is no longer reproducible? But we only had this instance left? Are there any similar instances?

When I made my proposal, I made it in a hurry and I was brief about the issue. In the PR phase, when I deeply investigated the issues and tested in real android devices then I found the first issue not reproducible so I reverted my fix for first issue.

But we only had this instance left

If you're asking for the issue which we found here then we have several instances in the application but all the instances stems from src/pages/workspace/workflows/ToggleSettingsOptionRow.tsx component as we used ToggleSettingOptionRow in several places, so fixing this ToggleSettingOptionRow will cover every instance.

dominictb · 2026-02-05T16:11:52Z

src/components/MenuItem.tsx

                                accessibilityLabel={accessibilityLabel ?? defaultAccessibilityLabel}
                                accessible={shouldBeAccessible}
-                                tabIndex={tabIndex}
+                                tabIndex={getPlatform() !== CONST.PLATFORM.WEB && !interactive ? -1 : tabIndex}


Can you explain why we previously need to set role, accessible and accessibilityLabel based on interactive. But now we only have tabIndex?

Previously we were trying to make the non interactive menu items non focusable but we don't need to make them non focusable, only "double tap to activate it" shouldn't be there in android and ios and setting the tab index to -1 would work.

I got to know about this when I was testing this in real android device and we are preventing it from web as setting tabIndex to -1 will make menu item non focusable in web which isn't the expected behaviour in the issue.

Uzaifm127 · 2026-02-05T18:11:34Z

Normally when the implementation deviates from the initial proposal, we'd ask to update the proposal first.

@dominictb Should I update my proposal first or we should move with the PR changes?

dominictb · 2026-02-09T15:37:23Z

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

Screen.Recording.2026-02-18.at.00.38.01.mov

iOS: HybridApp

iOS: mWeb Safari

MacOS: Chrome / Safari

dominictb · 2026-02-09T16:38:39Z

Both of the issues are not fixed for me:

Screen.Recording.2026-02-09.at.23.37.30.mov

Screen.Recording.2026-02-09.at.23.31.18.mov

Uzaifm127 · 2026-02-09T18:16:56Z

Will look into it.

Uzaifm127 · 2026-02-13T18:34:04Z

@dominictb Thanks for pointing out that the issue #77497 is reproducible.

When I said

#77497 - Not reproducible now

Then I only tested it on Android native and macOS, but it was reproducible on mWeb (Android and iOS) and iOS native.

For MenuItem.tsx issue, this issue was fixed in Android native by setting tabIndex to -1 but was still reproducible on Android mWeb. Now I fixed on mWeb and native android.

Now we are solving all three issues in all platforms, I added the video recordings and updated the PR description.

Let me know if that sounds good to you.

dominictb · 2026-02-17T17:12:55Z

src/pages/workspace/workflows/ToggleSettingsOptionRow.tsx

    const {isAccordionExpanded, shouldAnimateAccordionSection} = useAccordionAnimation(isActive);

+    // We are disabling the announcement for subtitle if subtitle and switchAccessibilityLabel are equal
+    const isSubtitleAndSwitchAccessibilityLabelAreEqual = switchAccessibilityLabel === subtitle;


Suggested change

const isSubtitleAndSwitchAccessibilityLabelAreEqual = switchAccessibilityLabel === subtitle;

const areSubtitleAndSwitchAccessibilityLabelEqual = switchAccessibilityLabel === subtitle;

dominictb · 2026-02-17T17:15:01Z

src/pages/workspace/workflows/ToggleSettingsOptionRow.tsx

+             * We hide the subtitle from screen readers if it is identical to the switch's accessibility label.
+             * 'aria-hidden' is used for compatibility with iOS mWeb, while 'accessible={false}'
+             * is required for iOS native.


Suggested change

* We hide the subtitle from screen readers if it is identical to the switch's accessibility label.

* 'aria-hidden' is used for compatibility with iOS mWeb, while 'accessible={false}'

* is required for iOS native.

* We hide the subtitle from screen readers to avoid double announcements

* 'aria-hidden' is used for compatibility with iOS mWeb, while 'accessible={false}' works on iOS native.

dominictb · 2026-02-17T17:17:27Z

src/components/MenuItem.tsx

+    const platform = getPlatform(true);
+    // This is required because we are preventing the "double tap to activate" announcement on Android web
+    const isAndroidWeb = platform === CONST.PLATFORM.MOBILE_WEB && getOperatingSystem() === CONST.OS.ANDROID;


This can be moved out of functional component.

Not required now.

dominictb · 2026-02-17T17:20:04Z

src/components/MenuItem.tsx

+    const platform = getPlatform(true);
+    // This is required because we are preventing the "double tap to activate" announcement on Android web
+    const isAndroidWeb = platform === CONST.PLATFORM.MOBILE_WEB && getOperatingSystem() === CONST.OS.ANDROID;


Suggested change

const platform = getPlatform(true);

// This is required because we are preventing the "double tap to activate" announcement on Android web

const isAndroidWeb = platform === CONST.PLATFORM.MOBILE_WEB && getOperatingSystem() === CONST.OS.ANDROID;

const platform = getPlatform(true);

// This is required because we are preventing the "double tap to activate" announcement on Android web

const isAndroidWeb = Browser.isMobileChrome();

Not required now.

dominictb · 2026-02-17T17:36:24Z

BUG

Virtual card number menu item and Reveal details button are announced as disabled. The button is unresponsive as well.

dominictb · 2026-02-17T17:43:33Z

@Uzaifm127 How did you test VoiceOver on iOS?

Uzaifm127 · 2026-02-17T17:45:05Z

@dominictb I used accessibility inspector built in mac.

P.S - Looking into the bug.

Uzaifm127 · 2026-02-17T18:08:48Z

@dominictb I looked into the bug, this is occuring because we are giving fullDisabled to MenuItem which makes it and it's children disabled.

I found giving fullDisabled as the only way to fix this on Android chrome, this is too confusing as the platform is web (Android chrome) and in mac it is not announcing but with Talkback it is announcing on Android web. I tried every possible way I could.

A help would be appreciable from your side.

cc: @rushatgabhane

rushatgabhane · 2026-02-18T20:57:57Z

@Uzaifm127 we could fix the bug on Android web in a follow up, if that helps unblock us.

Uzaifm127 · 2026-02-19T10:48:04Z

@dominictb As per @rushatgabhane

@Uzaifm127 we could fix the bug on Android web in a follow up, if that helps unblock us.

I've reverted the changes in MenuItem.tsx and keep the fix for Android native only and implemented your suggestions. You can review now.

dominictb

🎀

situchan

Just approving to assign engineer

Valforte · 2026-02-24T21:53:25Z

Can you merge main to fix conflict so I can review?

Uzaifm127 · 2026-02-25T10:52:22Z

@Valforte Resolved the merge conflicts.

I've removed the fix from MenuItem.tsx file as this PR already fixed that.

Valforte

LGTM

github-actions · 2026-02-25T12:45:09Z

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

github-actions · 2026-02-25T12:49:34Z

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

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-7475511-0dbc7e1-f23c824995d4cfe3c6aef0d059fc9d14e7c8b1dc/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-7475511-0dbc7e1-177e7e714a38e4f50f6e08f8b14ddc54c1a7835c/index.html

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

👀 View the workflow run that generated this build 👀

OSBotify · 2026-02-25T12:52:12Z

✋ 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 · 2026-02-25T18:23:12Z

🚀 Deployed to staging by https://github.com/Valforte in version: 9.3.26-0 🚀

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

izarutskaya · 2026-02-25T18:34:00Z

Hi @Uzaifm127 Is verification required only for Android and iOS apps?

Uzaifm127 · 2026-02-25T18:38:48Z

@izarutskaya
For this #77496, only android native.
For this #77497, only android and ios.
For this (from PR description) Test 1: Double announcement for switches., on all platforms.

OSBotify · 2026-02-27T14:54:45Z

🚀 Deployed to production by https://github.com/puneetlath in version: 9.3.26-8 🚀

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

Uzaifm127 added 2 commits January 28, 2026 23:12

Fixed the double announcement for switches

93495cc

Removed interactive roles from MenuItem

d3a874c

melvin-bot bot assigned Uzaifm127 Jan 28, 2026

Uzaifm127 changed the title ~~Fix/79243~~ Remove interactive role and double announcement for switches Jan 28, 2026

Uzaifm127 added 2 commits January 29, 2026 16:32

Updated the tabIndex to prevent actionable announcement only for Nati…

46be5fc

…ve platforms like Android or iOS

Fixed the minor bug in double announcement issue

7622586

Uzaifm127 marked this pull request as ready for review January 29, 2026 14:39

Uzaifm127 requested review from a team as code owners January 29, 2026 14:39

melvin-bot bot requested review from dominictb and joekaufmanexpensify January 29, 2026 14:39

melvin-bot bot removed request for a team January 29, 2026 14:39

Uzaifm127 mentioned this pull request Jan 29, 2026

[$250][Accessibility][Tracking] Hide from Assistive Tech / Remove Interactive Role #79243

Open

joekaufmanexpensify previously approved these changes Feb 2, 2026

View reviewed changes

dominictb reviewed Feb 5, 2026

View reviewed changes

Uzaifm127 requested a review from dominictb February 9, 2026 04:55

This comment was marked as resolved.

Sign in to view

Uzaifm127 added 2 commits February 13, 2026 22:59

Modified the second issue solution and solved the first issue

7cae57c

Resolved merge conflicts

d972363

Uzaifm127 dismissed joekaufmanexpensify’s stale review via d972363 February 13, 2026 17:34

Fixed the spell check

8ebf835

dominictb suggested changes Feb 17, 2026

View reviewed changes

Reverted the changes in MenuItem.tsx and applied the suggestions

3f80796

dominictb approved these changes Feb 23, 2026

View reviewed changes

situchan approved these changes Feb 24, 2026

View reviewed changes

melvin-bot bot requested a review from Valforte February 24, 2026 02:33

Uzaifm127 added 2 commits February 25, 2026 16:09

Merge branch 'main' of https://github.com/Uzaifm127/App into fix/79243

893b791

Resolved merge conflicts

90926eb

Valforte approved these changes Feb 25, 2026

View reviewed changes

Valforte merged commit 7475511 into Expensify:main Feb 25, 2026
27 checks passed

OSBotify mentioned this pull request Feb 25, 2026

Deploy Checklist: New Expensify 2026-02-25 #83466

Closed

	const isSubtitleAndSwitchAccessibilityLabelAreEqual = switchAccessibilityLabel === subtitle;
	const areSubtitleAndSwitchAccessibilityLabelEqual = switchAccessibilityLabel === subtitle;

Conversation

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

Uh oh!

Explanation of Change

Fixed Issues

Tests

Test 1: Double announcement for switches.

Test 2: Plain text announced as actionable (Android)

Test 3: Toggle/checkbox label announced twice - #77497

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Double announcement for switches.

Plain text announced as actionable

Toggle/checkbox label announced twice

Double announcement for switches.

Plain text announced as actionable

Toggle/checkbox label announced twice

Double announcement for switches.

Toggle/checkbox label announced twice

Double announcement for switches.

Toggle/checkbox label announced twice

Uh oh!

codecov bot commented Jan 29, 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 29, 2026

Uh oh!

Uzaifm127 commented Jan 29, 2026

Uh oh!

Uzaifm127 commented Feb 2, 2026

Uh oh!

joekaufmanexpensify left a comment

Choose a reason for hiding this comment

Uh oh!

mallenexpensify commented Feb 4, 2026

Uh oh!

dominictb left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

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

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uzaifm127 commented Feb 5, 2026

Uh oh!

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

Uh oh!

Reviewer Checklist

Screenshots/Videos

Uh oh!

This comment was marked as resolved.

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

Uh oh!

Uh oh!

Uzaifm127 commented Feb 9, 2026

Uh oh!

Uzaifm127 commented Feb 13, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uzaifm127 commented Jan 28, 2026 •

edited

Loading

codecov bot commented Jan 29, 2026 •

edited by github-actions bot

Loading

Uzaifm127 Feb 5, 2026 •

edited

Loading

dominictb commented Feb 9, 2026 •

edited

Loading

dominictb commented Feb 9, 2026 •

edited

Loading

dominictb commented Feb 17, 2026 •

edited

Loading

Uzaifm127 commented Feb 17, 2026 •

edited

Loading

Uzaifm127 commented Feb 17, 2026 •

edited

Loading

Uzaifm127 commented Feb 25, 2026 •

edited

Loading