Skip to content

[$250] Other A11y: Global: The page title does not describe the purpose of page #74767

Closed

Description

@nbhardwaj-del

Action Performed

Prerequisite:

  • User is logged in
  1. Using Chrome, open the URL: https://new.expensify.com/
  2. Activate the "My Settings" button
  3. Activate the "Subscription" menu item
  4. Inspect the code and note the title of the page.

Expected Result

The page title should clearly describe the purpose or content of the page to help users understand its context and differentiate it from other open tabs, e.g.:

  • 'Settings - Subscription - Expensify' or similar

Actual Result

Currently, the page title is displayed as “(1) New Expensify,” which does not provide a meaningful or descriptive indication of the page’s purpose or content. As a result, users may have difficulty identifying the page when multiple tabs are open.

HTML:

(1) New Expensify

Area issue was found

Settings–Subscription

Failed Checkpoint

WCAG 2.4.2 Page Titled
https://www.w3.org/WAI/WCAG22/Understanding/page-titled.html
https://www.w3.org/WAI/WCAG22/Understanding/page-titled.html

User Impact

People with visual disabilities will benefit from being able to differentiate content when multiple Web pages are open. People with cognitive disabilities, limited short-term memory and reading disabilities also benefit from the ability to identify content by its title. People with severe mobility impairments whose mode of operation relies on audio when navigating between Web pages will benefit from page titles.

Suggested Resolution

Update the element to include clear and descriptive text that reflects the specific page content or function, rather than a generic label, e.g.:

Environment(s)

Windows 11 Home - Chrome

Image

Version Number: NA
Reproducible in staging?: NA
Reproducible in production?: Yes
Email or phone of affected tester (no customers): NA
Logs: https://stackoverflow.com/c/expensify/questions/4856 NA
Notes/Photos/Videos: Any additional supporting documentation Yes
Expensify/Expensify Issue URL: https://platform.applause.com/products/36605/community-issues/6995830
Issue reported by: NA
Slack conversation: NA
Reproducible in staging?: NA
Reproducible in production?: Yes
Email or phone of affected tester (no customers): NA
Logs: https://stackoverflow.com/c/expensify/questions/4856 NA
Notes/Photos/Videos: Any additional supporting documentation Yes
Expensify/Expensify Issue URL: https://platform.applause.com/products/36605/community-issues/6995830
Issue reported by: NA
Slack conversation: NA

Upwork Automation - Do Not Edit
Issue Owner

Current Issue Owner: @mallenexpensify

Activity

  1. melvin-bot commented on Nov 11, 2025

    @melvin-bot

    📣 @nbhardwaj-del! 📣
    Please report bugs or suggest features in the #expensify-open-source Slack channel, don't directly open issues in this repo!
    Instructions here to join the channel 📖

  2. mallenexpensify commented on Nov 26, 2025

    @mallenexpensify
    Contributor

    Accessibility issue, will be addressed soon.

  3. removed their assignment
    on Dec 4, 2025
  4. mallenexpensify commented on Dec 4, 2025

    @mallenexpensify
    Contributor

    Accessibility, unassigning, will be addressed in bulk once all issues are created.

  5. removed theissue type on Dec 4, 2025
  6. 102 remaining items

  7. mananjadhav commented on Apr 13, 2026

    @mananjadhav
    Collaborator

    Yes that looks correct. I'll check the open issue in a while.

  8. twisterdotcom commented on Apr 14, 2026

    @twisterdotcom
    Contributor

    @mananjadhav has submitted payment for this report on ND here.

    SO: https://stackoverflowteams.com/c/expensify/questions/7582

    Zapier Logs Run ID: 00040eee-0e19-ae55-b55a-820d4351ba64
  9. mallenexpensify commented on Apr 17, 2026

    @mallenexpensify
    Contributor

    I raised the price on the open issue since @mananjadhav mentioned multiple proposals didn't work

  10. mallenexpensify commented on Apr 29, 2026

    @mallenexpensify
    Contributor

    Cleanup issue has a PR raised so gonna close this. Comment/reopen, if needed.

  11. quinthar commented on May 12, 2026

    @quinthar
    Contributor

    Approved $250 for @daledah

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

AccessibilityIssues affecting WACG accessibility on any platform.Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.ExternalAdded to denote the issue can be worked on by a contributorWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions