* Expand on disabled fieldsets and faked buttons include further advice/information on how to disable faked buttons for keyboard/AT users * Centralise accessible name advice in forms overview seems odd to only mention (separately) label, aria-label etc in input-group and layout. the advice is just as pertinent in other sections like select. checks only skims over this. moving this, in expanded form, into the overview section itself. adding a specific cross-reference (just because they are easily left with no accname at all) in the checks page. * Change warning about accessibility, modify server-side example - paradoxically, due to our current problems with validation (see #28414) and the fact that browsers seem to have improved in this area for the most part, it's now actually better to use browser-native validation - added explicit `id` and `aria-describedby` association to at least the server-side form error messages, to show how it should be done properly, and expanded the prose for that explaining this. * Replace `.sr-only` with `.visually-hidden` in new addition * Copy edits for clarity in parenthetical * Copy and formatting tweaks - Wordsmithing here and there - Turns some hyphens into em dashes - Turns a long running comma separated list into an unordered list - Rearranges some copy just a bit Co-authored-by: Mark Otto <markd.otto@gmail.com>
11 KiB
layout | title | description | group | aliases | toc |
---|---|---|---|---|---|
docs | Checks and radios | Create consistent cross-browser and cross-device checkboxes and radios with our completely rewritten checks component. | forms | /docs/5.0/forms/checks/ | true |
Approach
Browser default checkboxes and radios are replaced with the help of .form-check
, a series of classes for both input types that improves the layout and behavior of their HTML elements, that provide greater customization and cross browser consistency. Checkboxes are for selecting one or several options in a list, while radios are for selecting one option from many.
Structurally, our <input>
s and <label>
s are sibling elements as opposed to an <input>
within a <label>
. This is slightly more verbose as you must specify id
and for
attributes to relate the <input>
and <label>
. We use the sibling selector (~
) for all our <input>
states, like :checked
or :disabled
. When combined with the .form-check-label
class, we can easily style the text for each item based on the <input>
's state.
Our checks use custom Bootstrap icons to indicate checked or indeterminate states.
Checks
{{< example >}}
Indeterminate
Checkboxes can utilize the :indeterminate
pseudo class when manually set via JavaScript (there is no available HTML attribute for specifying it).
{{< example class="bd-example-indeterminate">}}
Disabled
Add the disabled
attribute and the associated <label>
s are automatically styled to match with a lighter color to help indicate the input's state.
{{< example >}}
Radios
{{< example >}}
Disabled
Add the disabled
attribute and the associated <label>
s are automatically styled to match with a lighter color to help indicate the input's state.
{{< example >}}
Switches
A switch has the markup of a custom checkbox but uses the .form-switch
class to render a toggle switch. Switches also support the disabled
attribute.
{{< example >}}
Default (stacked)
By default, any number of checkboxes and radios that are immediate sibling will be vertically stacked and appropriately spaced with .form-check
.
{{< example >}}
{{< example >}}
Inline
Group checkboxes or radios on the same horizontal row by adding .form-check-inline
to any .form-check
.
{{< example >}}
{{< example >}}
Without labels
Omit the wrapping .form-check
for checkboxes and radios that have no label text. Remember to still provide some form of accessible name for assistive technologies (for instance, using aria-label
). See the [forms overview accessibility]({{< docsref "/forms/overview#accessibility" >}}) section for details.
{{< example >}}
Toggle buttons
Create button-like checkboxes and radio buttons by using .btn
styles rather than .form-check-label
on the <label>
elements. These toggle buttons can further be grouped in a [button group]({{< docsref "/components/button-group" >}}) if needed.
Checkbox toggle buttons
{{< example >}} {{< /example >}}
{{< example >}} {{< /example >}}
{{< callout info >}} Visually, these checkbox toggle buttons are identical to the [button plugin toggle buttons]({{< docsref "/components/buttons#button-plugin" >}}). However, they are conveyed differently by assistive technologies: the checkbox toggles will be announced by screen readers as "checked"/"not checked" (since, despite their appearance, they are fundamentally still checkboxes), whereas the button plugin toggle buttons will be announced as "button"/"button pressed". The choice between these two approaches will depend on the type of toggle you are creating, and whether or not the toggle will make sense to users when announced as a checkbox or as an actual button. {{< /callout >}}
Radio toggle buttons
{{< example >}}
{{< /example >}}Outlined styles
Different variants of .btn
, such at the various outlined styles, are supported.
{{< example >}}
{{< /example >}}