Skip to content

[No QA] Make it easier for AI agents to interact with the app#81583

Merged
neil-marcellini merged 14 commits intomainfrom
neil-fix-svg-click-interception
Feb 18, 2026
Merged

[No QA] Make it easier for AI agents to interact with the app#81583
neil-marcellini merged 14 commits intomainfrom
neil-fix-svg-click-interception

Conversation

@neil-marcellini
Copy link
Contributor

@neil-marcellini neil-marcellini commented Feb 5, 2026

Explanation of Change

This PR addresses three separate issues that make it difficult for browser automation tools (AI agents) to interact with the app on web, while also improving real accessibility:

1. SVG click interception (Icon, FloatingActionButton)
SVG <path> elements inside buttons/pressables become the click target instead of the parent pressable on web. Added pointerEvents="none" to the Icon component's wrapper Views and ImageSVG elements, and to the Svg element in FloatingActionButton, so clicks pass through to the parent pressable. This is web-only behavior; native platforms handle SVG hit-testing differently and are unaffected.

2. TextInput role prop leaking to <input> elements (BaseTextInput)
Many TextInput usages pass role={CONST.ROLE.PRESENTATION}, intended for the wrapper, but this leaked through ...inputProps onto the actual <input> element — stripping its native textbox semantics and making it invisible to screen readers and automation tools. Fixed by destructuring role in BaseTextInput so it no longer reaches inputProps. The wrapper PressableWithoutFeedback already has role="presentation" hardcoded. This fixes all 40+ callers at once and improves real screen reader accessibility.

3. Missing accessibility labels on onboarding radio buttons (RadioButtonWithLabel, BaseOnboardingAccounting)
Added an accessibilityLabel prop to RadioButtonWithLabel that passes through to the inner RadioButton, falling back to label if not provided. In BaseOnboardingAccounting, pass accessibilityLabel={item.text} so each radio button is labeled (e.g., "QuickBooks Online"). Also removed a dead accessibilityLabel from the outer PressableWithoutFeedback which had accessible={false} (contradictory no-op), and added required sentryLabel props.

Fixed Issues

$ #82681

Tests

  1. Open the app on web (dev.new.expensify.com)
  2. Sign up with a new account and proceed through onboarding
  3. On the accounting integrations page, verify radio buttons are clickable and hover states work correctly
  4. Create a workspace and create an expense
  5. Verify the merchant, description, and company info text inputs are focusable and typeable
  6. Verify the FAB button (green "+" button) is clickable and hover feedback works
  7. Verify icon buttons throughout the app respond to clicks normally
  8. Open browser DevTools and verify no console errors related to these changes
  • Verify that no errors appear in the JS console

Offline tests

N/A — these changes only affect pointer-events and accessibility attributes, which don't involve network behavior.

QA Steps

No QA

  • Verify that no errors appear in the JS console

PR Author Checklist

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

Screenshots/Videos

On main: AI agent gets stuck trying to click the accounting radio button.

2026-02-12_08-20-17.mp4

On this branch: The test completes fully automated in about 4 minutes (video at 2x speed).

automation-2x.mp4

Only relevant on web. Other platforms will be tested for regressions on staging.

Android: Native

N/A — web-only changes (pointerEvents, role, accessibilityLabel)

Android: mWeb Chrome
iOS: Native

N/A — web-only changes (pointerEvents, role, accessibilityLabel)

iOS: mWeb Safari
MacOS: Chrome / Safari

See videos above

…vent SVG click interception

Browser automation tools (and potentially users) have trouble clicking on certain
UI elements because SVG icons inside buttons/pressables intercept clicks. The SVG
path elements become the click target instead of the parent pressable.

This fix adds pointerEvents="none" to:
- Icon component's View wrapper and ImageSVG (both main and inline rendering)
- FloatingActionButton's Svg component

Co-authored-by: Cursor <cursoragent@cursor.com>
@neil-marcellini neil-marcellini marked this pull request as ready for review February 5, 2026 19:30
@neil-marcellini neil-marcellini requested review from a team as code owners February 5, 2026 19:30
@melvin-bot melvin-bot bot requested review from joekaufmanexpensify and youssef-lr and removed request for a team February 5, 2026 19:30
@melvin-bot
Copy link

melvin-bot bot commented Feb 5, 2026

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

youssef-lr
youssef-lr previously approved these changes Feb 5, 2026
@youssef-lr
Copy link
Contributor

Tests failing @neil-marcellini

@joekaufmanexpensify
Copy link
Contributor

No product review needed

@joekaufmanexpensify joekaufmanexpensify removed their request for review February 6, 2026 17:16
@neil-marcellini
Copy link
Contributor Author

Moving this to a draft, it's quite untested.

@neil-marcellini neil-marcellini marked this pull request as draft February 6, 2026 18:09
Julesssss
Julesssss previously approved these changes Feb 11, 2026
Copy link
Contributor

@Julesssss Julesssss left a comment

Choose a reason for hiding this comment

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

Nice improvement. Would love to see a test demonstrating this, but NAB

@neil-marcellini neil-marcellini dismissed stale reviews from Julesssss and youssef-lr via 4477295 February 12, 2026 16:54
@neil-marcellini neil-marcellini changed the title [No QA] Fix SVG icons intercepting clicks on buttons [No QA] Make it easier for AI agents to interact with the app Feb 17, 2026
@melvin-bot
Copy link

melvin-bot bot commented Feb 17, 2026

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

Co-authored-by: Cursor <cursoragent@cursor.com>
@codecov
Copy link

codecov bot commented Feb 17, 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/components/FloatingActionButton.tsx 95.65% <ø> (ø)
src/components/Icon/index.tsx 74.28% <ø> (ø)
.../OnboardingAccounting/BaseOnboardingAccounting.tsx 2.32% <ø> (ø)
src/components/RadioButtonWithLabel.tsx 5.88% <0.00%> (-0.37%) ⬇️
...s/TextInput/BaseTextInput/implementation/index.tsx 0.00% <0.00%> (ø)
... and 110 files with indirect coverage changes

Co-authored-by: Cursor <cursoragent@cursor.com>
@neil-marcellini neil-marcellini marked this pull request as ready for review February 17, 2026 16:30
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: 5768b015f0

ℹ️ About Codex in GitHub

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

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

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

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

neil-marcellini and others added 2 commits February 17, 2026 13:19
Codex correctly noted that unconditionally dropping role would break
callers like SearchAutocompleteInput that pass role=SEARCHBOX. Now
only role="presentation" is filtered out; all other roles pass through
to the actual <input> element.

Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
- Remove explicit tool name listing (AI can infer available tools)
- Use environment-agnostic language instead of specific tool names
- Keep "Playwright MCP tools" naming for consistency with Melvin
- Condense wait strategy to a single concise instruction

Co-authored-by: Cursor <cursoragent@cursor.com>
@neil-marcellini neil-marcellini merged commit 6a9452e into main Feb 18, 2026
32 of 36 checks passed
@neil-marcellini neil-marcellini deleted the neil-fix-svg-click-interception branch February 18, 2026 14:42
@neil-marcellini
Copy link
Contributor Author

No reviewer checklist is needed, regressions will be caught in staging in the rare chance that there are any.

@github-actions
Copy link
Contributor

🚧 @neil-marcellini 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/neil-marcellini in version: 9.3.22-0 🚀

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

@OSBotify
Copy link
Contributor

🚀 Deployed to production by https://github.com/mountiny in version: 9.3.22-4 🚀

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

@OSBotify
Copy link
Contributor

🚀 Deployed to production by https://github.com/mountiny in version: 9.3.22-4 🚀

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

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.

6 participants