Use Siftal's custom button styles for actions in forms, dialogs, and more with support for multiple sizes, states, and more.

Simple Examples

Siftal includes several predefined button styles, each serving its own semantic purpose, with a few extras thrown in for more control.

a simple link

Button tags

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.

Link Link Link!

Outline buttons

In need of a button, but not the hefty background colors they bring? Replace the default modifier classes with the .outline ones to remove all background images and colors on any button.

a simple link


A button can be formatted to appear on dark backgrounds

a simple link


Fancy larger or smaller buttons? Add .btn-lg or .btn-sm for additional sizes.

Active state

Buttons will appear pressed (with a darker background) 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 should you need to replicate the state programmatically.

Disabled state

Make buttons look inactive by adding the disabled boolean attribute to any <button> element.

Disabled buttons using the <a> element behave a bit different because <a>s don’t support the disabled attribute, so you must add the .disabled class to make it visually appear disabled.

.disabled Link

Link functionality caveat

The .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 tabindex='-1' attribute on these links (to prevent them from receiving keyboard focus) and use custom JavaScript to disable their functionality.