[A11y] Labels & Descriptions

[rushatgabhane]

Explanation of Change

Part of

• https://github.com/Expensify/Expensify/issues/575078

Improves screen reader labels and descriptions for better accessibility by adding descriptive accessibility labels to interactive elements, including context like display names, emails, dates in labels, adding format hints for input fields, and properly translating accessibility labels.

Fixed Issues

$ #74843
$ #74865
$ #74871
$ #74881
$ #74887
$ #75469
$ #76904
$ #76912
$ #77371
$ #77378
$ #77424
$ #77449
$ #77456
$ #77457
$ #77464
$ #77533
$ #77557
$ #77559
$ #77569
$ #76913
$ #77450
$ #77452
$ #77453
$ #77455
$ #77461
$ #77564

Tests

1. Enable VoiceOver (iOS/Mac) or TalkBack (Android)
2. Navigate to calendar picker and select a date
3. Verify the date is announced with full format (weekday, month, day, year)
4. Navigate to account switcher
5. Verify it announces profile name and email
6. Navigate to magic code input, verify it says - Magic code 6 digits

---

MenuItem - Title & Description (#74843, #77455, #77564)

1. Navigate to Account > Profile
2. Focus on any menu item with a label and value (e.g., "Display name", "Timezone")
3. Verify: Screen reader announces both label AND value (e.g., "Display name, John Doe")
4. Navigate to Account > About > Keyboard shortcuts
5. Focus on any shortcut
6. Verify: Announces shortcut AND description (e.g., "Shift + Esc, Mark all messages as
   read")

---

---

Text Input with Hint (#77378)

1. Navigate to Account > Profile > Address
2. Focus on the Zip/Postal code field
3. Verify: Announces label AND hint (e.g., "Zip/Postal code, e.g. 12345")

---

Distance Amount Input (#74871)

1. Create expense > Distance
2. Focus on the distance input field
3. Verify: Announces "Distance (mile)" or "Distance (kilometer)" - not "mi" or "km"

---

Money Request Amount (#77557)

1. Create expense > Manual
2. Focus on the amount input field
3. Verify: Announces "Amount (USD)" with currency included

---

Account Button (#75469)

1. Focus on the Account tab at bottom navigation
2. Verify: Announces "Account, My settings" (not just "Account")

---

Search Menu Button (#77464)

1. On narrow screen, navigate to Search
2. Focus on the menu button (hamburger icon)
3. Verify: Announces "Filters" (not "Menu")

---

Referral CTA (#77457)

1. If visible, focus on the referral program banner
2. Verify: Has descriptive accessibility label

---

Selection List Items (#77450)

1. Navigate to any search/selection screen with two-line items (e.g., Status > Vacation
   delegate)
2. Focus on a search result
3. Verify: Announces both name AND email (e.g., "John Doe, john@example.com")

---

Workspace Members (#77453)

1. Navigate to Workspaces > [Workspace] > Members
2. Focus on any member
3. Verify: Announces name, email, AND role (e.g., "John Doe, john@example.com, Owner")

---

Language Selection (#74887)

1. Navigate to Account > Preferences > Language
2. Focus on language options
3. Verify: Each language has proper accessibility label

---

• Verify that no errors appear in the JS console

Offline tests

N/A - These are accessibility attribute changes that don't affect offline behavior.

QA Steps

Same as tests

• 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

MacOS: Chrome / Safari

Screen.Recording.2026-01-21.at.06.22.00.mov

[melvin-bot]

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

[melvin-bot]

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

[melvin-bot]

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

[dangrous]

Just for work tracking, assigned myself to the closed issues due to reviewing this PR

[huult]

@joekaufmanexpensify @dangrous I reviewed this PR and the release 7 days ago. Could you please help process the payment for me?

[dangrous]

ah yep! @huult I reopened #74843 and assigned you, so we can get payment settled there.