Brief summary

This issue affects users relying on screen readers, causing confusion and potential misunderstanding of the selection status of Bluetooth hearing devices. The user is trying to connect a second Bluetooth hearing device and receive correct screen reader feedback. When connecting a Bluetooth hearing device, a suggestion appears stating "We found the other hearing aid. Connect now." NVDA announces this information but incorrectly adds the status "not selected.

Steps to reproduce

1. Open NVDA.
2. Turn on both the Hearing Aids.
3. Open Settings page (Win + I) and Tab to "Bluetooth & Devices" and press enter.
4. Press tab to "Add Device" and press enter.
5. Observe and note the instruction "Make sure your device is turned on and discoverable...".x
6. Press tab to "Bluetooth" and press enter.
7. Press tab to "V949" device and press enter to connect one Hearing aid.
8. Observe the suggestion message "We found the other hearing aid. Connect now."
9. Verify that NVDA announces this message along with "not selected" status or not.

Actual behavior

NVDA announces the suggestion message "We found the other hearing aid. Connect now." with an incorrect "not selected" status.

Refer Attachment:
Screen reader incorrectly announces 'Not Selected' status when focus is on the second hearing device connection suggestion tile in Windows.mp4

Expected behavior

NVDA should announce the suggestion message "We found the other hearing aid. Connect now." without adding the "not selected" status.

NVDA logs, crash dumps and other attachments

No response

NVDA type

installed copy

NVDA version

NVDA (2025.2)

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

No response

Windows version

Windows 11 Version 25H2 (OS Build 26200.6584)

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

Application Name: Settings: Bluetooth & devices
Windows Feature Experience Pack 1000.26203.1000.0
OS Branch: GE_current_directplat_scon_ux

Other information about your system

No response

Does the issue still occur after restarting your computer?

I have restarted my computer and the issue still occurs

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

I have restarted NVDA with add-ons disabled and the issue still occurs

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

I have run the COM Registration Fixing Tool and the issue still occurs