Input Group
Easily extend form controls by adding text, buttons, or button groups on either side of textual inputs, custom selects, and custom file inputs.
Basic example
Place one add-on or button on either side of an input. You may also place one on both sides of an input. Remember to place <label>
s outside the input group.
Sizing
Add the relative form sizing classes to the .input-group
itself and contents within will automatically resizeāno need for repeating the form control size classes on each element.
Sizing on the individual input group elements isn't supported.
Checkboxes and radios
Place any checkbox or radio option within an input group's addon instead of text.
Multiple inputs
While multiple <input>
s are supported visually, validation styles are only available for input groups with a single <input>
.
Multiple addons
Multiple add-ons are supported and can be mixed with checkbox and radio input versions.
Custom forms
Input groups include support for custom selects and custom file inputs. Browser default versions of these are not supported.
Accessibility
Screen readers will have trouble with your forms if you don't include a label for every input. For these input groups, ensure that any additional label or functionality is conveyed to assistive technologies.
The exact technique to be used (<label>
elements hidden using the .sr-only
class, or use of the aria-label
and aria-labelledby
attributes, possibly in combination with aria-describedby
) and what additional information will need to be conveyed will vary depending on the exact type of interface widget you're implementing. The examples in this section provide a few suggested, case-specific approaches.