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
form.docx. This file contains an edit box and a combo box created using html, along with labels and preset values. It seems they have been imported as legacy controls. NVDA behaves very strange and inconsistent in this document. Behaviour I've seen so far:
NVDA just says embedded object
NVDA says embedded object edit value
NVDA says embedded object edit value and repeats itself multiple times
New and legacy form controls.docx. This document has been made using Word itself, you will need to enable the developer tab for this. During the creation of this document, I noticed that NVDA started being sluggish after I inserted the legacy form controls. Those legacy controls also cause the strange behaviour described above.
Overall, it is not possible to change values in form controls in a reliable way. I think this is a show stopper for #6643. Especially the sluggishness with legacy controls is something which should also be fixed before we even start thinking about making editing them accessible.
The text was updated successfully, but these errors were encountered:
It seems that #7849 doesn't improve this much. The new style check boxes are navigable using browse mode, they can't be toggled in browse mode though. All other form controls do not have proper control types assigned.
This ticket is related to #2295, #4709 and #6643.
Example materials:
form.docx. This file contains an edit box and a combo box created using html, along with labels and preset values. It seems they have been imported as legacy controls. NVDA behaves very strange and inconsistent in this document. Behaviour I've seen so far:
New and legacy form controls.docx. This document has been made using Word itself, you will need to enable the developer tab for this. During the creation of this document, I noticed that NVDA started being sluggish after I inserted the legacy form controls. Those legacy controls also cause the strange behaviour described above.
Overall, it is not possible to change values in form controls in a reliable way. I think this is a show stopper for #6643. Especially the sluggishness with legacy controls is something which should also be fixed before we even start thinking about making editing them accessible.
The text was updated successfully, but these errors were encountered: