Cirrus includes several predefined button styles, each serving its own semantic purpose, with a few extras thrown in for more control. `btn-secondary` is a ghost button with no background color applied.
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.
Icon Buttons
Icons should have a touch point of 30+ x 30+. Preferably 40x40 or higher.
Any button with just an icon, should have an aria-label attribute. This is mandatory.
primary
secondary
tertiary
alternate
Button Link
Text With Icon Buttons
These buttons will keep their text and icon on all screen sizes. You can have left aligned or right aligned buttons using `btn-icon-text-left` and `btn-icon-text-right`.
Text + Icon on Desktop, Icon Only on Mobile
In this example, the text will drop out at the specific break point. You can use any of the built in Cirrus breakpoints to accomplish this. You must wrap the text in a span tag for the CSS to work properly.
Scale your screen to see each button drop the text at it's specific breakpoint.
Each of these buttons should have an aria-label attribute. This is mandatory.
Processing States
This helpful state shows the user that something is happening, but the button is not a generic "disabled" state. Typically a success message or quick redirect will happen when the action is complete and the following page or content should let the user know the status of their action.
When using a form or showing a user that something is processing, add the `disabled-processing` class to the button with Javascript, along with setting the button to be disabled.
`div` tags are not valid HTML inside of the button tag so make sure to always use span tags.
primary
secondary
tertiary
alternate
Button Link
Example Processing Button
This button will update to say "success" when the processing is completed.
Javascript example
Buttons on backgrounds
Some buttons have a transparent background and will show the foreground color through them. Make sure to use the appropriate button for these situations.
Example Title
Example Title
Example Title
Example Title
Disable text wrapping
If you don't want the button text to wrap, you can add the `.text-nowrap` class to the button. In Sass, you can set `$btn-white-space: nowrap` to disable text wrapping for each button.
Button tags
The `.btn` classes are designed to be used with the `button` element. However, you can also use these classes on `anchor tags` or `input tags` elements (though some browsers may apply a slightly different rendering).
When using button classes on `anchor tags` 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.
Fancy smaller buttons? Add `.btn-sm` for additional sizes.
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.
This button is sized up to show specifics more clearly.
Make buttons look inactive by adding the `disabled` boolean attribute to any `button tag` element.
Disabled buttons using the `anchor` element behave a bit different:
`anchors`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.
The `.disabled` class uses `pointer-events: none` to try to disable the link functionality of `anchor`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 `tabindex="-1"` attribute on these links (to prevent them from receiving keyboard focus) and use custom JavaScript to disable their functionality.
Button plugin
Do more with buttons. Control button states or create groups of buttons for more components like toolbars.
Toggle states
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 and `aria-pressed="true"` to the `button`.
Checkbox and radio buttons
Cirrus's `.button` styles can be applied to other elements, such as `label`s, to provide checkbox or radio style button toggling.
Add `data-toggle="buttons"` to a `.btn-group` containing those modified buttons to enable their toggling behavior via JavaScript and add `.btn-group-toggle` to style the `input`s within your buttons. Note that you can create single input-powered buttons or groups of them.
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`.
Methods
Method
Description
$().button('toggle')
Toggles push state. Gives the button the appearance that it has been activated.