You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The label is not being read when focused on the input element.
Expected behavior:
When using the ElementInternals API, form-associated custom elements should be able to be referenced by <label> elements using the for attribute and it should be read when focused.
NVDA logs, crash dumps and other attachments:
System configuration
NVDA installed/portable/running from source:
NVDA version:
2023.1
Windows version:
10.0.22621 Build 22621
Name and version of other software in use when reproducing the issue:
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.
No
If NVDA add-ons are disabled, is your problem still occurring?
Yes
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
I'm not sure
The text was updated successfully, but these errors were encountered:
In this case the label is being associated with the parent "my-input" tag, rather than the input box.
It seems that invalid HTML is being generated here.
Steps to reproduce:
Actual behavior:
The label is not being read when focused on the input element.
Expected behavior:
When using the ElementInternals API, form-associated custom elements should be able to be referenced by
<label>
elements using thefor
attribute and it should be read when focused.NVDA logs, crash dumps and other attachments:
System configuration
NVDA installed/portable/running from source:
NVDA version:
2023.1
Windows version:
10.0.22621 Build 22621
Name and version of other software in use when reproducing the issue:
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.
No
If NVDA add-ons are disabled, is your problem still occurring?
Yes
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
I'm not sure
The text was updated successfully, but these errors were encountered: