[PWA Builder]: Screen Reader Omits Announcing No Results Information After Search.

[Anshi0420]

What happened?

After performing a search on the website, when no results are found, the screen reader fails to announce or provide any audible feedback regarding the absence of search results.

How do we reproduce the behavior?

Repro Steps:

1. Open the given PWA Builder URL in Anaheim dev browser.
2. Turn on narrator using Ctrl + win + Enter.
3. Navigate to the search edit field present in the left pane.
4. Now search any random letters.
5. Observe the narrator's announcement.

What do you expect to happen?

The screen reader should announce or indicate to the user that no results were found after a search query, ensuring that users relying on auditory feedback are informed of the search outcome.

What environment were you using?

Test Environment:

OS Build: Windows 11 Enterprise Insider Preview 24H2 (26120.461) Edge Browser: Version 123.0.2400.1 (Official build) dev (64-bit) URL: https://docs.pwabuilder.com/#/home/sw-intro Screen Reader: Narrator

Additional context

User Impact: Users who depend on screen readers (such as individuals with visual impairments or those preferring auditory interfaces) may not be aware when their search yields no results.

WCAG Reference: https://www.w3.org/WAI/WCAG22/Understanding/info-and-relationships

Attachments:

https://github.com/pwa-builder/PWABuilder/assets/117908911/feb4787f-e6f0-4869-a0fc-2320b8e15421

[microsoft-github-policy-service[bot]]

This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue .

[microsoft-github-policy-service[bot]]

This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue .

[microsoft-github-policy-service[bot]]

This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue .

[microsoft-github-policy-service[bot]]

This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue .

[microsoft-github-policy-service[bot]]

This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue .

[microsoft-github-policy-service[bot]]

This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue .

[microsoft-github-policy-service[bot]]

This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue .

[microsoft-github-policy-service[bot]]

This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue .

[microsoft-github-policy-service[bot]]

This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue .

[microsoft-github-policy-service[bot]]

This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue .

[microsoft-github-policy-service[bot]]

This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue .

[microsoft-github-policy-service[bot]]

This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue .

[microsoft-github-policy-service[bot]]

This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue .

[microsoft-github-policy-service[bot]]

This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue .

[microsoft-github-policy-service[bot]]

This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue .

[microsoft-github-policy-service[bot]]

This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue .