When in browse mode in Chrome the label for a div contentEditable is read out as if it is the current value.
When the IA2 role ends up being section or text frame. This can be reproduced by not having an aria role.
Try this URI (with no role):
data:text/html,<div aria-label="foo" aria-placeholder="bar" contentEditable="true"></div>
This reports "foo" after reporting that we are in an editable section.
Versus this URI (with role textBox):
data:text/html,<div aria-label="foo" aria-placeholder="bar" role="textbox" contentEditable="true"></div>
This is the expected behaviour, which does not report "foo" after reporting that we are in an editable section.
Possible fix: Line 807 of nvdaHelper/vbufBackends/gecko_ia2/gecko_ia2.cpp: Need to make sure that the section and text frame roles aren't considered if they are editable (I think !isEditable will do it)
When in browse mode in Chrome the label for a
divcontentEditableis read out as if it is the current value.When the IA2 role ends up being section or text frame. This can be reproduced by not having an aria role.
Try this URI (with no role):
data:text/html,<div aria-label="foo" aria-placeholder="bar" contentEditable="true"></div>This reports "foo" after reporting that we are in an editable section.
Versus this URI (with role textBox):
data:text/html,<div aria-label="foo" aria-placeholder="bar" role="textbox" contentEditable="true"></div>This is the expected behaviour, which does not report "foo" after reporting that we are in an editable section.
Possible fix: Line
807ofnvdaHelper/vbufBackends/gecko_ia2/gecko_ia2.cpp: Need to make sure that the section and text frame roles aren't considered if they are editable (I think!isEditablewill do it)