Skip to content

fix(a11y): Improve screen reader support for Settings > Profile context menu#82932

Merged
lakchote merged 28 commits into
Expensify:mainfrom
marufsharifi:fix/sr-settings-profile-context-menu-instructions
Mar 26, 2026
Merged

fix(a11y): Improve screen reader support for Settings > Profile context menu#82932
lakchote merged 28 commits into
Expensify:mainfrom
marufsharifi:fix/sr-settings-profile-context-menu-instructions

Conversation

@marufsharifi

@marufsharifi marufsharifi commented Feb 19, 2026

Copy link
Copy Markdown
Contributor

Explanation of Change

Improved desktop web accessibility for link context menus in Settings by adding clear screen-reader hints (“Context menu available, press Shift+F10 to open”), ensuring hints are announced on the web, applying the behavior consistently across shared menu components, and localizing the new hint across all supported languages.

Fixed Issues

$ #76948
PROPOSAL: #76948 (comment)

Tests

  1. Using Windows + Chrome + JAWS, open the page /settings/profile
  2. Navigate using TAB to the 'Help' and 'What's New' links in the 'General' section
  3. Observe that there is no announcement for the context menus available
  4. When users navigate through the profile page, onto the general section, verify that it informes that there is a context menu with information for the 'Help' and 'What's New' links.
    -"Help, link, Context menu available, press SHIFT F10 to activate."
  • Verify that no errors appear in the JS console

Offline tests

Same as Tests.

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

  • 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

Android: Native

Not applicable

Android: mWeb Chrome

Not applicable

iOS: Native

Not applicable

iOS: mWeb Safari

Not applicable.

MacOS: Chrome / Safari
Screen.Recording.2026-02-23.at.12.47.53.PM.mov

@melvin-bot

melvin-bot Bot commented Feb 19, 2026

Copy link
Copy Markdown

Hey, I noticed you changed src/languages/en.ts in a PR from a fork. For security reasons, translations are not generated automatically for PRs from forks.

If you want to automatically generate translations for other locales, an Expensify employee will have to:

  1. Look at the code and make sure there are no malicious changes.
  2. Run the Generate static translations GitHub workflow. If you have write access and the K2 extension, you can simply click: [this button]

Alternatively, if you are an external contributor, you can run the translation script locally with your own OpenAI API key. To learn more, try running:

npx ts-node ./scripts/generateTranslations.ts --help

Typically, you'd want to translate only what you changed by running npx ts-node ./scripts/generateTranslations.ts --compare-ref main

@codecov

codecov Bot commented Feb 19, 2026

Copy link
Copy Markdown

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/LHNOptionsList/OptionRowLHN.tsx 79.28% <100.00%> (-0.72%) ⬇️
src/components/MenuItem.tsx 87.27% <100.00%> (+0.17%) ⬆️
src/components/MenuItemList.tsx 70.00% <100.00%> (+3.33%) ⬆️
...e/GenericPressable/implementation/index.native.tsx 100.00% <100.00%> (ø)
...omponents/utils/getContextMenuAccessibilityHint.ts 100.00% <100.00%> (ø)
...mponents/utils/getContextMenuAccessibilityProps.ts 100.00% <100.00%> (ø)
src/pages/ReferralDetailsPage.tsx 0.00% <ø> (ø)
src/pages/settings/AboutPage/AboutPage.tsx 0.00% <ø> (ø)
src/pages/settings/AppDownloadLinks.tsx 0.00% <ø> (ø)
src/pages/settings/InitialSettingsPage.tsx 0.00% <ø> (ø)
... and 1 more
... and 12 files with indirect coverage changes

@marufsharifi
marufsharifi marked this pull request as ready for review February 23, 2026 12:55
@marufsharifi
marufsharifi requested review from a team as code owners February 23, 2026 12:55
@melvin-bot
melvin-bot Bot requested review from suneox and trjExpensify February 23, 2026 12:55
@melvin-bot

melvin-bot Bot commented Feb 23, 2026

Copy link
Copy Markdown

@suneox 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 removed request for a team February 23, 2026 12:55
Comment thread src/components/LHNOptionsList/OptionRowLHN.tsx Outdated
Comment thread src/components/MenuItem.tsx Outdated
Comment thread src/components/LHNOptionsList/OptionRowLHN.tsx Outdated
Comment thread src/components/MenuItem.tsx Outdated
Comment thread src/components/MenuItemList.tsx Outdated

@trjExpensify trjExpensify left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Do you need @Expensify/design to look at this PR? The content in this box here in the video doesn't look decipherable a lot of the time:

image

@dubielzyk-expensify

Copy link
Copy Markdown
Contributor

I thought that content box was part of macOS voice over and not something we have in the app!? Maybe I've misunderstood though

@trjExpensify

Copy link
Copy Markdown
Contributor

Ah, could well be. I don't know, I've never seen it before.

@shawnborton

Copy link
Copy Markdown
Contributor

Oh wow, apparently you can right-click on the Help and What's New rows and you see this:
CleanShot 2026-02-25 at 07 21 59@2x

Seems like overkill to support right click to copy URL there...

@dubielzyk-expensify

dubielzyk-expensify commented Feb 25, 2026

Copy link
Copy Markdown
Contributor

Woaaah. Never seen this. That's wild but also kinda useful haha

@dannymcclain

Copy link
Copy Markdown
Contributor

Today I learned!

@rushatgabhane

Copy link
Copy Markdown
Member

@MelvinBot merge main, fix conflicts

@rushatgabhane

Copy link
Copy Markdown
Member

@suneox could you please prioritze this? last update was a long time ago 🙇

@MelvinBot

Copy link
Copy Markdown
Contributor

I can see this PR has merge conflicts with main, but I'm unable to push changes to this branch because I'm not the author or an assignee on this PR.

To have me merge main and resolve the conflicts, please add me as an assignee on this PR and then re-request with @MelvinBot merge main, fix conflicts.

@suneox

suneox commented Mar 4, 2026

Copy link
Copy Markdown
Contributor

@suneox could you please prioritze this? last update was a long time ago 🙇

Yes, I’ll prioritize the review today and provide an update on the plan for the related tasks

@marufsharifi

Copy link
Copy Markdown
Contributor Author

@truph01 I addressed the latest review comments above. Please take another look when you get a chance. Thanks.

@marufsharifi

Copy link
Copy Markdown
Contributor Author

@truph01, gentle bump. thanks.

@truph01

truph01 commented Mar 23, 2026

Copy link
Copy Markdown
Contributor

@codex review

Comment thread src/components/utils/getContextMenuAccessibilityHint.ts Outdated

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

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: 9927f801a6

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

Comment thread src/components/utils/getContextMenuAccessibilityHint.ts Outdated
Comment thread src/components/utils/getContextMenuAccessibilityHint.ts Outdated
Comment thread src/components/MenuItem.tsx Outdated
@truph01

truph01 commented Mar 23, 2026

Copy link
Copy Markdown
Contributor

@marufsharifi We have a few comments

@marufsharifi

Copy link
Copy Markdown
Contributor Author

Working on it

@marufsharifi

Copy link
Copy Markdown
Contributor Author

@truph01, I've addressed all your comments, just waiting for the Spanish translation for the new key. thanks.

Comment thread src/components/LHNOptionsList/OptionRowLHN.tsx Outdated
@truph01

truph01 commented Mar 24, 2026

Copy link
Copy Markdown
Contributor

Duplicated platform-check logic across OptionRowLHN and MenuItem

Both files contain identical logic:

const contextMenuHint = ...;
const platform = getPlatform(true);
const shouldMergeContextMenuHintIntoLabel = platform === CONST.PLATFORM.WEB || platform === CONST.PLATFORM.MOBILE_WEB;
const accessibilityLabelWithContextMenuHint = shouldMergeContextMenuHintIntoLabel && contextMenuHint
    ? [label, contextMenuHint].filter(Boolean).join('. ')
    : label;
const accessibilityHint = shouldMergeContextMenuHintIntoLabel ? undefined : contextMenuHint;

This "merge on web, separate on native" logic could be extracted into a small hook (e.g., useContextMenuAccessibility({ label, shouldShowHint })) that returns { accessibilityLabel, accessibilityHint }. This would reduce duplication and ensure consistency.

Comment thread src/components/MenuItemList.tsx
@marufsharifi

Copy link
Copy Markdown
Contributor Author

@truph01 I addressed the latest review comments. Please take another look when you get a chance.

@lakchote lakchote left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM

@lakchote
lakchote merged commit 3490f36 into Expensify:main Mar 26, 2026
33 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

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

@OSBotify

Copy link
Copy Markdown
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
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/lakchote in version: 9.3.49-0 🚀

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

Bundle Size Analysis (Sentry):

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/grgia in version: 9.3.49-2 🚀

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

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.