5.7 KiB
| layout | title |
|---|---|
| page | Buttons |
Use any of the available button classes to quickly create a styled button.
{% example html %}
Primary
Secondary
Success
Warning
Danger
Link {% endexample %}
Conveying meaning to assistive technologies
Using color to add meaning to a button 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 (the visible text of the button), or is included through alternative means, such as additional text hidden with the .sr-only class.
Button tags
Use the button classes on an <a>, <button>, or <input> element.
{% example html %} Link Button {% endexample %}
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".
Cross-browser rendering
As a best practice, we highly recommend using the <button> element whenever possible to ensure matching cross-browser rendering.
Sizes
Fancy larger or smaller buttons? Add .btn-lg, .btn-sm, or .btn-xs for additional sizes.
{% example html %} Large button Large button {% endexample %}
{% example html %} Small button Small button {% endexample %}
{% example html %} Extra small button Extra small button {% endexample %}
Create block level buttons—those that span the full width of a parent—by adding .btn-block.
{% example html %} Block level button Block level button {% endexample %}
Active state
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.
{% example html %} Primary link Link {% endexample %}
Disabled state
Make buttons look unclickable by adding the disabled boolean attribute to any <button> element.
{% example html %} Primary button Button {% endexample %}
As <a> elements don't support the disabled attribute, you must add the .disabled class to fake it.
{% example html %} Primary link Link {% endexample %}
Cross-browser compatibility
If you add the disabled attribute to a <button>, Internet Explorer 9 and below will render text gray with a nasty text-shadow that we cannot fix.
Link functionality caveat
This class uses pointer-events: none to try to disable the link functionality of <a>s, but that CSS property is not yet standardized and isn't fully supported in Opera 18 and below, or in Internet Explorer 11. 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, use custom JavaScript to disable such links.
Context-specific usage
While button classes can be used on <a> and <button> elements, only <button> elements are supported within our nav and navbar components.