Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for fieldset/legend #535

Closed
nvaccessAuto opened this issue Jan 21, 2010 · 6 comments
Closed

Support for fieldset/legend #535

nvaccessAuto opened this issue Jan 21, 2010 · 6 comments
Labels
Milestone

Comments

@nvaccessAuto
Copy link

Reported by jongund on 2010-01-21 22:33
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.

@nvaccessAuto
Copy link
Author

Comment 1 by jongund on 2011-05-17 19:00
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

@nvaccessAuto
Copy link
Author

Comment 2 by jteh on 2011-05-17 23:48
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.
Changes:
Milestone changed from None to near-term

@nvaccessAuto
Copy link
Author

Comment 3 by jongund on 2011-05-18 13:26
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?

@nvaccessAuto
Copy link
Author

Comment 4 by jteh on 2011-05-18 20:26
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.

@nvaccessAuto
Copy link
Author

Comment 5 by mdcurran on 2011-05-18 22:52
Fixed in 9515036. IE9 did not properly support this on its own either.
Changes:
State: closed

@nvaccessAuto
Copy link
Author

Comment 6 by jteh on 2011-05-18 22:55
Changes:
Milestone changed from near-term to 2011.2

@nvaccessAuto nvaccessAuto added this to the 2011.2 milestone Nov 10, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant