When in browse mode in Chrome the label for a `div` `contentEditable` is read out as if it is the current value when there is no aria role. #7153
Labels
Milestone
Comments
feerrenrut
added a commit
that referenced
this issue
May 9, 2017
This has been split out into another bug, see #7153
feerrenrut
added a commit
that referenced
this issue
May 12, 2017
feerrenrut
added a commit
that referenced
this issue
May 30, 2017
- PR #7169 : Editable div elements in Chrome are no longer have their label reported as their value while in browse mode. (Issue #7153) - PR #6396 : An unbound gesture (script_restart) has been added to allow NVDA to be restarted quickly. (PR #6396) - PR #6777 : A Braille setting has been added to "show messages indefinitely". (Issue #6669) - PR #7133 : Pressing end while in browse mode of an empty Microsoft Word document no longer causes a runtime error. (Issue #7009) - PR #6868 : The keyboard layout can now be set from the NVDA Welcome dialog. (Issue #6863) - PR #6813 : The names of "landmarks" are abbreviated in Braille (Issue #3975)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
ofnvdaHelper/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)The text was updated successfully, but these errors were encountered: