File Upload - aria-describedby Not Announced Immediately After uploading file.

[nofarbaranesRG]

Steps to reproduce:

1. Open NVDA and a browser (tested in Chrome, Edge).
2. Navigate to a file input with an aria-describedby reference to an error message.
3. Upload a file with an invalid type (e.g., upload a .txt file when only images are allowed).
4. Observe that NVDA does not immediately announce the error message.
5. Press Tab to move focus away from the input.
6. Press Shift + Tab to move focus back to the file input.
7. Now NVDA announces the error message correctly.

🔗 Live Demo (CodeSandbox): CodeSandbox Reproduction

Actual behavior:

• NVDA does not announce the error message immediately when an invalid file is uploaded.
• The error message is only announced after tabbing away and back to the file input.
• Other screen readers (e.g., VoiceOver on Mac) announce the error message immediately without requiring a focus change.

Expected behavior:

• NVDA should immediately announce the error message referenced by aria-describedby after an invalid file is uploaded.
• The expected announcement should be:
“Upload file. Invalid file type.”
• No focus change (Tab → Shift+Tab) should be needed to trigger the announcement.

NVDA logs, crash dumps and other attachments:

N/A – This is a screen reader announcement issue, not a crash.

System configuration

NVDA installed/portable/running from source:

Installed version.

NVDA version:

Tested on NVDA 2024.4.2. (latest at time of testing).

Windows version:

Windows 10 & Windows 11 (both tested).

Name and version of other software in use when reproducing the issue:

• Google Chrome (l133.0.6943.60.)
• Other screen readers tested: VoiceOver (Mac) → Works as expected

Other information about your system:

Other questions

Does the issue still occur after restarting your computer?

Yes.

Have you tried any other versions of NVDA? If so, please report their behaviors.

Yes, the issue persists in older and latest versions.

If NVDA add-ons are disabled, is your problem still occurring?

Yes, this issue is unrelated to add-ons.

Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?

Yes.

[CyrilleB79]

Hi @nofarbaranesRG

Could you explicitly specify the version of the browser used (Chrome) instead of specifying "latest"?

Also you write:

Tested on NVDA 2023.3 (latest at time of testing).

Please note that latest version of NVDA is 2024.4.2. Could you please install it and re-test to confirm the issue is still present?

Thanks.

[nofarbaranesRG]

Hi @nofarbaranesRG

Could you explicitly specify the version of the browser used (Chrome) instead of specifying "latest"?

Also you write:

Tested on NVDA 2023.3 (latest at time of testing).

Please note that latest version of NVDA is 2024.4.2. Could you please install it and re-test to confirm the issue is still present?

Thanks.

Thank you for your fast reply.
The Chrome version is 133.0.6943.60.
The NVDA version is 2024.4.2.

I've updated NVDA and the Chrome, and the issue is still present

[seanbudd]

Is it possible to provide a vanilla HTML/JS sample? it can be quite difficult to debug frameworks like React, given that the problem could be introduced by the transpiling from React to JS