Use Awesome's custom button styles for actions in forms, dialogs and more with support for multiple sizes, states and more.
Bootstrap includes several predefined button styles, each serving its own semantic purpose, with a few extras thrown in for more control.
Conveying meaning to assistive technologies
Using color to add meaning only provides a visual indication, which will not be conveyed to users of assistive technologies – such as screen readers. Ensure that information denoted by the color is either obvious from the content itself (e.g. the visible text), or is included through alternative means, such as additional text hidden with the
Fancy larger or smaller buttons? Add
.btn-sm for additional sizes.
Create block level buttons — those that span the full width of a parent — by adding
Buttons will appear pressed (with a darker background, darker border and inset shadow) when active. There's no need to add a class to
<button>s as they use a pseudo-class. However, you can still force the same active appearance with
.active (and include the
aria-pressed="true" attribute) should you need to replicate the state programmatically.
Make buttons look inactive by adding the
disabled boolean attribute to any
Disabled buttons using the
<a> element behave a bit different:
<a>s don't support the
disabled attribute, so you must add the
.disabled class to make it visually appear disabled.
- Some future-friendly styles are included to disable all
pointer-events on anchor buttons. In browsers which support that property, you won't see the disabled cursor at all.
- Disabled buttons should include the
aria-disabled="true" attribute to indicate the state of the element to assistive technologies.
Link functionality caveat
.disabled class uses
pointer-events: none to try to disable the link functionality of
<a>s, but that CSS property is not yet standardized. In addition, even in browsers that do support
pointer-events: none, keyboard navigation remains unaffected, meaning that sighted keyboard users and users of assistive technologies will still be able to activate these links. So to be safe, add a
data-toggle="button" to toggle a button's
active state. If you're pre-toggling a button, you must manually add the
.active class and
aria-pressed="true" to the
|Toggles push state. Gives the button the appearance that it has been activated.
|Destroys an element's button.