diff --git a/docs/_includes/components/input-groups.html b/docs/_includes/components/input-groups.html index 8a07735d2b..ba14573ba2 100644 --- a/docs/_includes/components/input-groups.html +++ b/docs/_includes/components/input-groups.html @@ -16,7 +16,11 @@

Don't mix with other components

Do not mix form groups or grid column classes directly with input groups. Instead, nest the input group inside of the form group or grid-related element.

- +
+

Always add labels

+

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, aria-labelledby, aria-describedby, title or placeholder attribute) 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.

+

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.

@@ -24,35 +28,35 @@

We do not support multiple form-controls in a single input group.

- @ - + @ +

- - .00 + + @example.com

$ - + .00
{% highlight html %}
- @ - + @ +
- - .00 + + @example.com
$ - + .00
{% endhighlight %} @@ -61,34 +65,34 @@

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.

- @ - + @ +

- @ - + @ +

- @ - + @ +
{% highlight html %}
- @ - + @ +
- @ - + @ +
- @ - + @ +
{% endhighlight %} @@ -100,17 +104,17 @@
- + - +
- + - +
@@ -120,17 +124,17 @@
- + - +
- + - +
@@ -146,12 +150,12 @@ - +
- + @@ -166,12 +170,12 @@ - +
- + @@ -196,12 +200,12 @@
  • Separated link
  • - +
    - +
    - +
    - +
    - +
    - +
    - +