From: Patrick H. Lauke <redux@splintered.co.uk>
Date: Sun, 7 Dec 2014 15:11:28 +0000 (+0000)
Subject: Expand advice about adding labels
X-Git-Tag: v3.3.2~5^2~112^2~1
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=353d8395aea20dad7d59bb54b8972a29ab2cb6e2;p=thirdparty%2Fbootstrap.git

Expand advice about adding labels

Harmonizing this with same advice given for CSS inline forms
---

diff --git a/docs/_includes/components/navbar.html b/docs/_includes/components/navbar.html
index c8107c017a..6cd731ac6c 100644
--- a/docs/_includes/components/navbar.html
+++ b/docs/_includes/components/navbar.html
@@ -208,7 +208,7 @@
 
   <div class="bs-callout bs-callout-warning" id="callout-navbar-form-labels">
     <h4>Always add labels</h4>
-    <p>Screen readers will have trouble with your forms if you don't include a label for every input. For these inline navbar forms, you can hide the labels using the <code>.sr-only</code> class.</p>
+    <p>Screen readers will have trouble with your forms if you don't include a label for every input. For these inline forms, you can hide the labels using the <code>.sr-only</code> class. There are further alternative methods of providing a label for assistive technologies, such as the <code>aria-label</code>, <code>aria-labelledby</code> or <code>title</code> attribute. If none of these is present, screen readers may resort to using the <code>placeholder</code> attribute, if present, but note that use of <code>placeholder</code> as a replacement for other labelling methods is not advised.</p>
   </div>