NVDA repeats input label text #1650

nvaccessAuto opened this Issue Jul 5, 2011 · 5 comments


None yet
4 participants

Reported by stevefaulkner on 2011-07-05 15:14
when an author codes a HTML label element in certain ways NVDA announces the label text twice when an input receives focus.

I have provided test cases and results here:

Comment 3 by jteh on 2011-07-05 23:22
For Firefox, this is partially due to MozillaBug:669312.

There are two other problems here:

  1. We're reading labels in the focus ancestry. Mick, is there a reason for this? I can't think of one. It might be because we're just relying on presentationType and we want labels to be content if they are leaf nodes. In that case, we should check childCount or make a special case in isPresentableFocusAncestor.
  2. In IE, labels seem to have a role of text instead of label. If we can fix this, (1) will apply to IE as well.
    Milestone changed from None to 2011.3

Comment 4 by jteh (in reply to comment 3) on 2011-09-01 02:55
Replying to jteh:

For Firefox, this is partially due to MozillaBug:669312.

MozillaBug:682790 is now the relevant bug. The other was closed as a duplicate.

Comment 5 by mdcurran on 2011-09-12 03:38
Partial fix in ca39a43. Label elements are no longer spoken in both IE and Firefox when focus moves to a control inside of them. Remaining issue of Firefox showing duplicated label in accName must be fixed in Gecko.
Milestone changed from 2011.3 to near-term

@nvaccessAuto nvaccessAuto added the bug label Nov 10, 2015

@nvaccessAuto nvaccessAuto added this to the near-term milestone Nov 10, 2015

@jcsteh jcsteh removed this from the near-term milestone Jun 24, 2016


ehollig commented Oct 18, 2017

It sounds as if MozillaBug:682790 has been resolved in Firefox 10. When opening the above link, http://www.html5accessibility.com/tests/form-labels.html, I believe everything works as expected, but am not exactly clear on what is the original issue is. No labels double speak when I navigate the example site.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment