Ticket #535 (closed defect: fixed)

Opened 2 years ago

Last modified 9 months ago

Support for fieldset/legend

Reported by: jongund Owned by:
Priority: major Milestone: 2011.2
Component: Core Version:
Keywords: Cc:
Operating system: Blocked by:
Blocking:

Description

When a form control with proper labeling is encapsulated by a fieldset/legend, the legend content should be appended to the label of the form control.

This is important to provide more context to the user of the form controls purpose in a website and to help make form control labels more unique.

This is also a feature of other commercial screen readers for windows.

Change History

comment:1 Changed 9 months ago by jongund

Is there any update on the status of this bug fix?

It is hard to tell web developers to use fieldset/legend when it does not have an effect on assistive technology

comment:2 Changed 9 months ago by jteh

  • Keywords fieldset legend form label removed
  • Milestone set to near-term

Appending the text of the legend to the end of every form control's label would be fairly inefficient in terms of verbosity and extremely hacky. However, NVDA already reads new focus ancestors as you move inside them. For example, if you tab into a fieldset in Firefox, you will hear the legend followed by the first form control, but you won't hear the legend again on subsequent tabs. Note that a bug was fixed recently which makes this behaviour more consistent in browse mode.

Unfortunately, this doesn't work in IE8 due to its poor support for accessibility APIs, so any solution there will have to be a work around on our side.

comment:3 Changed 9 months ago by jongund

Thank you for the response. I will try in Firefox and IE 9.

If it doesn't work in IE 9, is there a bug that can be reported in IE 9 that would make it work?

comment:4 Changed 9 months ago by jteh

Unfortunately, past attempts have made it clear that Microsoft are very unlikely to fix accessibility issues in IE9. We might have a chance of getting it fixed in IE10, though. IN the meantime, we'll probably have to work around the issue with specific code in NVDA.

comment:5 Changed 9 months ago by mdcurran

  • Status changed from new to closed
  • Resolution set to fixed

Fixed in changeset:main,4289. IE9 did not properly support this on its own either.

comment:6 Changed 9 months ago by jteh

  • Milestone changed from near-term to 2011.2
Note: See TracTickets for help on using tickets.