From: Mark Otto <markdotto@gmail.com>
Date: Wed, 29 Apr 2015 18:44:19 +0000 (-0700)
Subject: remove some callouts on buttons by rewriting things a bit
X-Git-Tag: v4.0.0-alpha~232
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=a999a0aff20ff210731540d353c808a0b80f0022;p=thirdparty%2Fbootstrap.git

remove some callouts on buttons by rewriting things a bit
---

diff --git a/docs/components/buttons.md b/docs/components/buttons.md
index 79777e4ca3..f84376c610 100644
--- a/docs/components/buttons.md
+++ b/docs/components/buttons.md
@@ -37,7 +37,9 @@ Using color to add meaning to a button only provides a visual indication, which
 
 ## Button tags
 
-Use the button classes on an `<a>`, `<button>`, or `<input>` element.
+As a best practice, **we highly recommend using the `<button>` element whenever possible** to ensure matching cross-browser rendering. However, you may also use button classes on `<a>`, `<button>`, or `<input>` elements.
+
+When using button classes on `<a>` elements, be sure to include the `role="button"` for improved accessibility.
 
 {% example html %}
 <a class="btn btn-secondary" href="#" role="button">Link</a>
@@ -46,18 +48,6 @@ Use the button classes on an `<a>`, `<button>`, or `<input>` element.
 <input class="btn btn-secondary" type="submit" value="Submit">
 {% endexample %}
 
-{% callout warning %}
-#### Links acting as buttons
-
-If the `<a>` elements are used to act as buttons – triggering in-page functionality, rather than navigating to another document or section within the current page – they should also be given an appropriate `role="button"`.
-{% endcallout %}
-
-{% callout warning %}
-#### Cross-browser rendering
-
-As a best practice, **we highly recommend using the `<button>` element whenever possible** to ensure matching cross-browser rendering.
-{% endcallout %}
-
 ## Sizes
 
 Fancy larger or smaller buttons? Add `.btn-lg`, `.btn-sm`, or `.btn-xs` for additional sizes.