FloSports Brand has one chip style used to filter content or trigger actions.
Chips are used in the system to filter content, or trigger actions. While buttons are expected to appear consistently and with familiar calls to action, chips should appear dynamically as a group of multiple interactive elements.
Here are extra variations on chips, imported from forking Bootstrap 4. These are not part of the design system, yet could be beneficial in the future.
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
Chips with Close Icon Variant
Disable text wrapping
If you don’t want the chip text to wrap, you can add the
.text-nowrap class to the chip. In Sass, you can set
$chip-white-space: nowrap to disable text wrapping for each chip.
.chip classes are designed to be used with the
<button> element. However, you can also use these classes on
<input> elements (though some browsers may apply a slightly different rendering).
When using chip 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 chip, but not the hefty background colors they bring? Replace the default modifier classes with the
.chip-outline-* ones to remove all background images and colors on any chip.
Fancy larger or smaller chips? Add
.chip-sm for additional sizes.
chips 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 chips look inactive by adding the
disabled boolean attribute to any
Disabled chips using the
<a> element behave a bit different:
<a>s don’t support the
disabledattribute, so you must add the
.disabledclass to make it visually appear disabled.
- Some future-friendly styles are included to disable all
pointer-eventson anchor chips. In browsers which support that property, you won’t see the disabled cursor at all.
- Disabled chips 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