You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[$250] mweb - Blue outline appears on Concierge button and app back button #83313
Version Number: 9.3.25-4 Reproducible in staging?: Yes Reproducible in production?: No If this was caught during regression testing, add the test name, ID and link from BrowserStack:#82518 Email or phone of affected tester (no customers):osidjosdjosdjnodsjni@gmail.com Issue reported by: Applause Internal Team Bug source: Exploratory - Significant User Experience Deterioration Device used: Samsung Galaxy S25 FE / Android 16 App Component: Other
Action Performed:
Go to staging.new.expensify.com on mweb.
Refresh the page.
Open any chat.
Expected Result:
In Step 2, after refreshing the page, no blue outline will appear on any button.
In Step 3, after opening chat, no blue outline will appear on any button.
Actual Result:
In Step 2, after refreshing the page, blue outline appears on Concierge button.
In Step 3, after opening chat, blue outline appears on back button.
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
Identify the pull request that introduced this issue and revert it.
Classification: Frontend bug Causing PR: #82518 - "fix: [Accessibility][Tracking] Other Accessibility Issues" by @TaduJR (High confidence) Related Issues: Part of #79248 (Accessibility Tracking initiative)
Recommendation: REVERT
PR #82518 added ARIA roles (role="row", role="cell", role="table", etc.) to improve accessibility and screen reader support. While this is a valid accessibility improvement, it introduced an unintended side effect: browsers now apply default focus styles (blue outlines) to elements with these semantic roles. On mobile web, where keyboard navigation is not typical, these outlines appear unexpectedly after page refresh or navigation.
The PR should be reverted to unblock the deploy, and a fixed version should be prepared that includes proper CSS to suppress unwanted focus outlines on mobile web while maintaining the accessibility improvements.
Labels: No changes needed. DeployBlockerCash is correctly applied (App deploy is blocked by this frontend bug). The issue is reproducible on staging but not production, confirming it was introduced in the current staging deploy.
While the reported symptoms mention "Concierge button" and "back button," the underlying cause is the same: the PR added semantic ARIA roles throughout the application, which trigger browser default focus styles.
Root Cause
When ARIA semantic roles (row, cell, etc.) are applied to elements on web, browsers automatically apply default focus styling (typically a blue outline) to make keyboard navigation visible for accessibility. This is correct behavior for desktop keyboard users, but on mobile web:
Elements may receive programmatic focus during page load or navigation
The blue outline appears visually even though no keyboard navigation is occurring
The user experience is degraded with unexpected visual artifacts
The PR did not include CSS rules to manage focus styling on these newly-semantic elements, particularly for mobile contexts where keyboard navigation is rare. A proper fix would need to:
Add :focus-visible or :focus CSS rules to suppress outlines on mobile
Or use tabIndex="-1" on non-interactive semantic elements
While preserving keyboard accessibility for screen reader users
Please re-state the problem that we are trying to solve in this issue.
On Android mWeb Chrome, after refreshing the page a blue outline appears on the Concierge button in the sidebar. After opening a chat, a blue outline appears on the back button in the chat header.
What is the root cause of that problem?
The root cause is two mechanisms working together:
shouldMoveAccessibilityFocus in ScreenWrapper (src/components/ScreenWrapper/index.tsx:116) — On mobile web (getPlatform() === CONST.PLATFORM.WEB && isMobile()), after each screen transition, a useEffect (lines 229-265) queries for the first focusable element (button, [href], [role="button"], [role="link"], [tabindex]:not([tabindex="-1"])) and programmatically calls .focus() on it.
Global :focus-visible CSS (web/index.html:64-67) — A global rule applies box-shadow: inset 0px 0px 0px 1px #5AB0FF to any :focus-visible element. On Android Chrome, programmatic .focus() calls can trigger :focus-visible (unlike desktop Chrome which distinguishes keyboard vs programmatic focus).
After a page refresh or navigation, shouldMoveAccessibilityFocus fires, finds the first focusable button (Concierge row in the LHN sidebar, or back button in the chat header), calls .focus(), and Android Chrome applies :focus-visible, which triggers the blue box-shadow.
Note on PR #82518: This PR was flagged as the cause, but after thorough analysis, none of its changes (adding aria-describedby, accessibilityLiveRegion="polite", role="table/row/cell/list/listitem") affect focus management, tab order, or :focus-visible behavior. The roles it added (table, row, cell, columnheader, list, listitem) are NOT in the set of roles that react-native-web makes focusable (button, checkbox, link, radio, textbox, switch). The issue is likely pre-existing or was introduced by a different PR in the same deploy. Other components already work around this exact same blue focus ring problem by calling .blur() after interactions (see FloatingActionButton.tsx:77-78, FloatingReceiptButton.tsx:36, AttachmentPickerWithMenuItems.tsx:448).
What changes do you think we should make in order to solve the problem?
Option A (targeted fix): In ScreenWrapper/index.tsx, after the programmatic .focus() call on line 259, immediately call .blur() if the focus was applied only for accessibility purposes (i.e., when shouldMoveAccessibilityFocus is true but the focus is not from a keyboard interaction). Alternatively, use element.focus({ preventScroll: true, focusVisible: false }) where supported.
Option B (CSS-level fix): Add a CSS rule that suppresses :focus-visible box-shadow specifically on mobile/touch devices where programmatic focus shouldn't show visual focus indicators. For example, adding a data-focus-from-a11y attribute when focusing programmatically and a CSS rule like [data-focus-from-a11y]:focus-visible { box-shadow: none; }.
Option C (consistent with existing patterns): Follow the pattern already used in FloatingActionButton, FloatingReceiptButton, and AttachmentPickerWithMenuItems — call .blur() immediately after .focus() in the shouldMoveAccessibilityFocus effect. This preserves the accessibility announcement while removing the visual focus ring.
What alternative solutions did you explore? (Optional)
Adding outline: none or box-shadow: none to individual Pressable components was considered, but this would be a whack-a-mole approach since any focusable element can be affected.
Using :focus:not(:focus-visible) CSS selector was considered but has inconsistent support on Android Chrome.
Detailed Investigation
Evidence Chain
Global :focus-visible CSS at web/index.html:64-67:
changed the title [-]mweb - Blue outline appears on Concierge button and app back button[/-][+][$250] mweb - Blue outline appears on Concierge button and app back button[/+]on Feb 24, 2026
📣 @genesis-ai-labs-star! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:
Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.
Format:
Contributor details
Your Expensify account email: <REPLACE EMAIL HERE>
Upwork Profile Link: <REPLACE LINK HERE>
Activity
melvin-bot commentedon Feb 24, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #82518
melvin-bot commentedon Feb 24, 2026
💬 A slack conversation has been started in #expensify-open-source
melvin-bot commentedon Feb 24, 2026
Triggered auto assignment to @kadiealexander (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.github-actions commentedon Feb 24, 2026
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
OSBotify commentedon Feb 24, 2026
🔍 Investigation Summary
Classification: Frontend bug
Causing PR: #82518 - "fix: [Accessibility][Tracking] Other Accessibility Issues" by @TaduJR (High confidence)
Related Issues: Part of #79248 (Accessibility Tracking initiative)
Recommendation: REVERT
PR #82518 added ARIA roles (
role="row",role="cell",role="table", etc.) to improve accessibility and screen reader support. While this is a valid accessibility improvement, it introduced an unintended side effect: browsers now apply default focus styles (blue outlines) to elements with these semantic roles. On mobile web, where keyboard navigation is not typical, these outlines appear unexpectedly after page refresh or navigation.The PR should be reverted to unblock the deploy, and a fixed version should be prepared that includes proper CSS to suppress unwanted focus outlines on mobile web while maintaining the accessibility improvements.
Labels: No changes needed.
DeployBlockerCashis correctly applied (App deploy is blocked by this frontend bug). The issue is reproducible on staging but not production, confirming it was introduced in the current staging deploy.📋 Detailed Analysis
Evidence
role=\"table\",role=\"row\",role=\"columnheader\", androle=\"cell\""Verification
PR #82518 modified these key files that could affect button focus styling:
PressableWithoutFeedbackrole fromBUTTONto conditionalROWrole on wider screensrole="cell"to multiple View componentsaria-describedbyattribute linking inputs to error messagesnativeIDprop for ARIA associationsThe PR diff shows this critical change in WorkspacesListPage.tsx:
While the reported symptoms mention "Concierge button" and "back button," the underlying cause is the same: the PR added semantic ARIA roles throughout the application, which trigger browser default focus styles.
Root Cause
When ARIA semantic roles (
row,cell, etc.) are applied to elements on web, browsers automatically apply default focus styling (typically a blue outline) to make keyboard navigation visible for accessibility. This is correct behavior for desktop keyboard users, but on mobile web:The PR did not include CSS rules to manage focus styling on these newly-semantic elements, particularly for mobile contexts where keyboard navigation is rare. A proper fix would need to:
:focus-visibleor:focusCSS rules to suppress outlines on mobiletabIndex="-1"on non-interactive semantic elementsMelvinBot commentedon Feb 24, 2026
Proposal
Please re-state the problem that we are trying to solve in this issue.
On Android mWeb Chrome, after refreshing the page a blue outline appears on the Concierge button in the sidebar. After opening a chat, a blue outline appears on the back button in the chat header.
What is the root cause of that problem?
The root cause is two mechanisms working together:
shouldMoveAccessibilityFocusinScreenWrapper(src/components/ScreenWrapper/index.tsx:116) — On mobile web (getPlatform() === CONST.PLATFORM.WEB && isMobile()), after each screen transition, auseEffect(lines 229-265) queries for the first focusable element (button, [href], [role="button"], [role="link"], [tabindex]:not([tabindex="-1"])) and programmatically calls.focus()on it.Global
:focus-visibleCSS (web/index.html:64-67) — A global rule appliesbox-shadow: inset 0px 0px 0px 1px #5AB0FFto any:focus-visibleelement. On Android Chrome, programmatic.focus()calls can trigger:focus-visible(unlike desktop Chrome which distinguishes keyboard vs programmatic focus).After a page refresh or navigation,
shouldMoveAccessibilityFocusfires, finds the first focusable button (Concierge row in the LHN sidebar, or back button in the chat header), calls.focus(), and Android Chrome applies:focus-visible, which triggers the bluebox-shadow.Note on PR #82518: This PR was flagged as the cause, but after thorough analysis, none of its changes (adding
aria-describedby,accessibilityLiveRegion="polite",role="table/row/cell/list/listitem") affect focus management, tab order, or:focus-visiblebehavior. The roles it added (table,row,cell,columnheader,list,listitem) are NOT in the set of roles that react-native-web makes focusable (button,checkbox,link,radio,textbox,switch). The issue is likely pre-existing or was introduced by a different PR in the same deploy. Other components already work around this exact same blue focus ring problem by calling.blur()after interactions (seeFloatingActionButton.tsx:77-78,FloatingReceiptButton.tsx:36,AttachmentPickerWithMenuItems.tsx:448).What changes do you think we should make in order to solve the problem?
Option A (targeted fix): In
ScreenWrapper/index.tsx, after the programmatic.focus()call on line 259, immediately call.blur()if the focus was applied only for accessibility purposes (i.e., whenshouldMoveAccessibilityFocusis true but the focus is not from a keyboard interaction). Alternatively, useelement.focus({ preventScroll: true, focusVisible: false })where supported.Option B (CSS-level fix): Add a CSS rule that suppresses
:focus-visiblebox-shadow specifically on mobile/touch devices where programmatic focus shouldn't show visual focus indicators. For example, adding adata-focus-from-a11yattribute when focusing programmatically and a CSS rule like[data-focus-from-a11y]:focus-visible { box-shadow: none; }.Option C (consistent with existing patterns): Follow the pattern already used in
FloatingActionButton,FloatingReceiptButton, andAttachmentPickerWithMenuItems— call.blur()immediately after.focus()in theshouldMoveAccessibilityFocuseffect. This preserves the accessibility announcement while removing the visual focus ring.What alternative solutions did you explore? (Optional)
outline: noneorbox-shadow: noneto individual Pressable components was considered, but this would be a whack-a-mole approach since any focusable element can be affected.:focus:not(:focus-visible)CSS selector was considered but has inconsistent support on Android Chrome.Detailed Investigation
Evidence Chain
:focus-visibleCSS atweb/index.html:64-67:shouldMoveAccessibilityFocusatScreenWrapper/index.tsx:116:ScreenWrapper/index.tsx:248-259:FloatingActionButton.tsx:77:// Drop focus to avoid blue focus ring.FloatingReceiptButton.tsx:36:// Drop focus to avoid blue focus ring.AttachmentPickerWithMenuItems.tsx:448:// Drop focus to avoid blue focus ring.Relevant Code
src/components/ScreenWrapper/index.tsx:116,229-265- TheshouldMoveAccessibilityFocusmechanismweb/index.html:64-67- Global:focus-visibleCSS rulesrc/components/Pressable/GenericPressable/implementation/index.tsx:16- WebGenericPressable setstabIndex=0src/components/LHNOptionsList/OptionRowLHN.tsx:214-251- LHN rows (Concierge) userole=BUTTONsrc/components/HeaderWithBackButton/index.tsx:225-248- Back button usesPressableWithoutFeedbacksrc/components/Pressable/GenericPressable/implementation/BaseGenericPressable.tsx:194-noSelect(withboxShadow: 'none') only applied when disabledNext Steps for Contributor+ team: Reply with
@MelvinBot implement thisto create a draft PR, or@MelvinBot <your feedback>to refine this analysis.3 remaining items
[-]mweb - Blue outline appears on Concierge button and app back button[/-][+][$250] mweb - Blue outline appears on Concierge button and app back button[/+]melvin-bot commentedon Feb 24, 2026
Job added to Upwork: https://www.upwork.com/jobs/~022026251252315025549
TaduJR commentedon Feb 24, 2026
Taking a look
melvin-bot commentedon Feb 24, 2026
📣 @genesis-ai-labs-star! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:
Format:
victoreronmosele commentedon Feb 24, 2026
Proposal
Please re-state the problem that we are trying to solve in this issue.
On mobile web, a blue outline appears on the Concierge button after refreshing and on the app back button after opening a chat.
What is the root cause of that problem?
On mobile web, we move focus to the first focusable element after a screen ends its transition.
Here we set
shouldMoveAccessibilityFocuswhen the app is running on mobile web:App/src/components/ScreenWrapper/index.tsx
Line 116 in d9e056b
shouldMoveAccessibilityFocusis then used in a check before moving the focus when transition ends:App/src/components/ScreenWrapper/index.tsx
Lines 229 to 265 in d9e056b
What changes do you think we should make in order to solve the problem?
We detect when we move focus programmatically and hide the outline in that case.
Set an attribute
data-programmatic-focuswhen we focus programmatically.if (focusedElement === focusTarget || (focusedElement && focusTarget.contains(focusedElement))) { + focusTarget.setAttribute('data-programmatic-focus', ''); + const removeProgrammaticFocusAttr = () => { + focusTarget.removeAttribute('data-programmatic-focus'); + }; + focusTarget.addEventListener('blur', removeProgrammaticFocusAttr, {once: true}); return; }Update the
focus:visibleCSS style inweb/index.htmlto not show the outline when focus is programmatic:TaduJR commentedon Feb 24, 2026
I investigated, and I don't think it's regression from my PR.
I am suspecting this PR #81390
TaduJR commentedon Feb 24, 2026
Can you confirm the above?
cc @marufsharifi @suneox
Julesssss commentedon Feb 24, 2026
Attempting a revert
Julesssss commentedon Feb 24, 2026
Verified the issue came from this ^ reverted here and now awaiting QA testing.
m-natarajan commentedon Feb 24, 2026
Can’t reproduce, Xiaomi Redmi Note 10 / Chrome, 9.3.25-13
Screenrecorder-2026-02-24-23-15-40-407.mp4