Skip to content

[$250] [Due for payment 2026-04-01] Screen Reader: Many Pages: The displayed error messages are not announced once they appear #74866

Closed

Description

@nbhardwaj-del

Action Performed

Prerequisites:

  • The user is signed in
  1. Using Chrome + JAWS, open the URL - https://new.expensify.com/
  2. Navigate to the 'Account' and press Enter > Navigate to the 'Settings - Save the world' and press Enter
  3. Tab to the 'I know a teacher' and press Enter
  4. Leave the fields empty or add invalid input
  5. Tab to the 'Let's do this' button and press Enter
  6. Observe the screen reader announcement

Other Occurrences:

  1. On Settings - Save the world - Intro your school principal
  2. On Settings - Security - Close account
  3. On Settings - Security - Two-factor authentication
  4. On Settings - Security - Two-factor authentication (step 2 of 2)
  5. On Settings - Profile - Display name
  6. On Settings - Profile - DOB
  7. On Settings - Profile - Phone number
  8. On Settings - Profile - Legal name
  9. On Settings - Profile - Address
  10. On Workspaces - Duplicate Workspaces
  11. On Workspaces - Overview - Workspace Name
  12. On Workspace - Categories - Add Category
  13. On Workspace - Expensify Card - Bank info
  14. On Workspace - Create Workspace - Confirm Workspace
  15. On Create Report - Add payment card

Expected Result

When validation errors occur, the error message should be automatically announced by screen readers and user should receive immediate auditory feedback about the error and its location

  • Focus or programmatic notification should help users understand what needs to be corrected

Actual Result

When form validation fails and error messages appear, the error text is displayed visually on the screen, but the screen reader does not announce the error messages automatically; users relying on the screen reader are not informed that an error has occurred or which fields need correction

HTML:

This field is required

Area issue was found

Settings-Save the World

Failed Checkpoint

WCAG 4.1.3 Status Messages
https://www.w3.org/WAI/WCAG22/Understanding/status-messages

User Impact

When appropriate roles or properties are assigned to status messages, the new content is spoken by screen readers in such a way as to assist blind and low vision users. Assigning proper roles or properties to status messages provides possible future uses and personalization opportunities, such as the potential to be exploited by assistive technologies created for users with some cognitive disabilities.

Suggested Resolution

Wrap the error message container in an ARIA live region (role="alert" or aria-live="assertive") so messages are announced when they appear.
Ensure that error messages are programmatically associated with their corresponding input fields using aria-describedby
https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Reference/Roles
https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Reference/Attributes

Environment(s)

Windows Windows 11 Home - Chrome

Screenshots/Videos

Bug6994039_1762281532801.The_displayed_error_messages_are_not_announced_once_they_appears.mp4
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/company/12102/products/36605/community-issues/6994039
Issue reported by: NA
Slack conversation: NA

Issue OwnerCurrent Issue Owner: @aimane-chnaif
Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~022039541552026174475
  • Upwork Job ID: 2039541552026174475
  • Last Price Increase: 2026-04-02

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. 79 remaining items

  7. mallenexpensify commented on Apr 3, 2026

    @mallenexpensify
    Contributor

    @Yatin-Bhatti apparently your GH or Upwork is already associated with another account. We're working on updating error messaging to provide more details. Maybe check your earliest comments here to when you might have posted the details before?

  8. mallenexpensify commented on Apr 3, 2026

    @mallenexpensify
    Contributor

    @aimane-chnaif paid, summary updated above. Thx.

  9. Krishna2323 commented on Apr 4, 2026

    @Krishna2323
    Contributor

    Requested in ND.

  10. twisterdotcom commented on Apr 5, 2026

    @twisterdotcom
    Contributor

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

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

    Zapier Logs Run ID: 00040eee-c379-af61-a186-e5a2434d8c24
  11. quinthar commented on Apr 13, 2026

    @quinthar
    Contributor

    Approved $250 to @Krishna2323

  12. marufsharifi commented on May 11, 2026

    @marufsharifi
    Contributor

    @mallenexpensify, I have a question about this issue.

    I was initially assigned/hired, had already opened a PR, tested, and requested review of the PR before it was reassigned due to the deadline and estimation concerns here:

    https://expensify.slack.com/archives/C01GTK53T8Q/p1772739593580499

    pr colosed based on this comment

    Am I still eligible for compensation in this case? This is a similar case to here.

    Thanks in advance for your guidance!

  13. mallenexpensify commented on May 11, 2026

    @mallenexpensify
    Contributor

    @rushatgabhane 👀 above please, espec the Slack post.
    Thx

  14. rushatgabhane commented on May 11, 2026

    @rushatgabhane
    Member

    Similar here, the solution by @Krishna2323 is different from @marufsharifi's PR

    So I don't think it is eligible for comp 😅

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 productionDailyKSv2DesignExternalAdded to denote the issue can be worked on by a contributorMelvin TriageAutomatic AI Analysis of an issue

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions