From 78e60ffc7dc6ac67f9ece8d54a3c3eccc9acb5e6 Mon Sep 17 00:00:00 2001
From: Chris Rebert Extend form controls by adding text or buttons before, after, or on both sides of any text-based Extend form controls by adding text or buttons before, after, or on both sides of any text-based 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 ( The exact technique to be used (visible Place one add-on or button on either side of an input. You may also place one on both sides of an input. We do not support multiple add-ons on a single side. We do not support multiple add-ons ( We do not support multiple form-controls in a single input group. Place any checkbox or radio option within an input group's addon instead of text. Buttons in input groups are a bit different and require one extra level of nesting. Instead of
Date: Thu, 1 Oct 2015 11:14:55 -0700
Subject: [PATCH] Apply updates to components/index.html
---
components/index.html | 60 ++++++++++++++++++++++++++++++++++++++-----
1 file changed, 54 insertions(+), 6 deletions(-)
diff --git a/components/index.html b/components/index.html
index 3197712530..e3fb571152 100644
--- a/components/index.html
+++ b/components/index.html
@@ -2223,7 +2223,7 @@
Input groups
- <input>
. Use .input-group
with an .input-group-addon
to prepend or append elements to a single .form-control
.<input>
. Use .input-group
with an .input-group-addon
or .input-group-btn
to prepend or append elements to a single .form-control
.Textual
@@ -2241,12 +2241,12 @@
<input>
s onlyAlways add labels
<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.<label>
elements, <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
.input-group-addon
or .input-group-btn
) on a single side.<div class="input-group">
<span class="input-group-addon" id="basic-addon1">@</span>
@@ -2279,6 +2285,12 @@
<span class="input-group-addon">$</span>
<input type="text" class="form-control" aria-label="Amount (to the nearest dollar)">
<span class="input-group-addon">.00</span>
+</div>
+
+<label for="basic-url">Your vanity URL</label>
+<div class="input-group">
+ <span class="input-group-addon" id="basic-addon3">https://example.com/users/</span>
+ <input type="text" class="form-control" id="basic-url" aria-describedby="basic-addon3">
</div>
Sizing
@@ -2314,7 +2326,6 @@
<input type="text" class="form-control" placeholder="Username" aria-describedby="sizing-addon3">
</div>Checkboxes and radio addons
Button addons
.input-group-addon
, you'll need to use .input-group-btn
to wrap the buttons. This is required due to default browser styles that cannot be overridden.