Use Boosted’s custom button styles for actions in forms, dialogs, and more with support for multiple sizes, states, and more.
Boosted 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 .sr-only class.
To get the inversed button behaviour, simply add .btn-inverse class to your <button> or <a> tag.
The default styles can be used on secondary colors backgrounds, in this case remove the .btn-inverse class if any.
In need of a social media button? Some helper classes are designed to be used with the .btn element.
.btn-fbk, .btn-tw, .btn-gplus, .btn-lin, .btn-mail are available for light and dark background.
The .btn classes are designed to be used with the <button> element. However, you can also use these classes on <a> or <input> elements (though some browsers may apply a slightly different rendering).
When using button classes on <a> elements that are used to trigger in-page functionality (like collapsing content), rather than linking to new pages or sections within the current page, these links should be given a role="button" to appropriately convey their purpose to assistive technologies such as screen readers.
In need of a button, but not the hefty background colors they bring? Replace the default modifier classes with the .btn-outline-* ones to remove all background images and colors on any button.
Fancy larger or smaller buttons? Add .btn-xlg, .btn-lg or .btn-sm for additional sizes.
Create block level buttons—those that span the full width of a parent—by adding .btn-block.
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.
Do more with buttons. Control button states or create groups of buttons for more components like toolbars.
Add data-toggle="button" to toggle a button’s active state. If you’re pre-toggling a button, you must manually add the .active class andaria-pressed="true" to the <button>.
Checkbox and radio buttons
The checked state for these buttons is only updated via click event on the button. If you use another method to update the input—e.g., with <input type="reset"> or by manually applying the input’s checked property—you’ll need to toggle .active on the <label> manually.
Note that pre-checked buttons require you to manually add the .active class to the input’s <label>.
Toggles push state. Gives the button the appearance that it has been activated.