-
-
Notifications
You must be signed in to change notification settings - Fork 78.8k
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
Appropriate use of fieldset/div, legends, accessibility advice #17266
Conversation
@mdo note that this introduces one problem with the current styling of |
/cc @cvrebert |
@patrickhlauke: can you rebase? |
Use more generic `<div>` for single form controls, use `<fieldset>` and `<legend>` for radio button groups and checkboxes (where appropriate). Include accessibility advice from v3 Fixes #17248
Port `.help-text` advice and example for `.text-muted`, first stab at generalising the validation accessibility callout (in the absence of glyphicons now) - the latter is not perfect, but better than nothing at this stage
Looks good git-wise :) |
While it's technically right, most folks won't build their forms this way—with the |
@mdo does this mean it's good to be merged, and we'll fix things later with classes? at a stretch, as it's an example of grid, i could probably let those two legends slide (but maybe add a comment to that effect in the HTML). or i could give those two bits of text an |
I mean we need to use classes to style these form labels so they don't get all screwed up :). |
@patrickhlauke Does adding |
As rebasing was starting to get messy, I've made a successor pull request #19277 |
Use more generic
<div>
for single form controls, use<fieldset>
and<legend>
for radio button groups and checkboxes (where appropriate).Include accessibility advice from v3
Fixes #17248