Base

  • Colors
    Colors have been developed to help guide a user through our interface.
  • Icons
    Icons add a visual layer to written information. They should be used to inform and enhance components. The purpose of the icon will determine whether or not it needs to receive focus or not.
  • Logos
  • Shadows and Elevations
    Shadows and Elevations to be used in Usertesting Next theme.
  • Spacing
  • Typography
    We also use the 8-pt methodology to control the vertical rhythm of our typography. Our base type size is 16px with a 1.5 line-height for optimal reading.

Components

  • Accordion
    Accordion is a toggle component to help customers expand and collapse sections of data
  • Avatars
    Avatars are used to quickly identify a customer’s properties including: studies, drafts, highlight reels, etc.
  • Badges
    Badges help inform customers on the state of a study. They also communicate and indicate number-driven information.
  • Buttons
    Buttons are useful to draw attention to a goal or action. Calls to actions within buttons should be explicit.
  • Cards
    Cards are useful to hold content. They have been used to contain content related to screeners and tasks.
  • Character Counter
    Wrap an input or textarea to keep count
  • Device Type Icons
  • Draggables
    Draggables are items that can be moved about the interface. Customers use this pattern to add and reorder elements to fit their needs.
  • Dropdowns
    Dropdowns are used to present individuals with a wide range of options and actions they can take.
  • Droppables
    Droppables are containers that can receive draggable components and files. They help customers transfer information across the interface.
  • Expandable image
    An image that can be be enlarged to view in full detail using the Lightbox.
  • Filters
    Filters are a way for users to drill down information.
  • Gallery card
    This component is in Beta. Gallery Cards are used to hold specific types of content. They have been used to preview content on the dashboard such as highlight reels and insights.
  • Icon Button
    The icon button is used to trigger a secondary action when we want to reduced visual noise.
  • Indicators
    Indicators are a source of metadata that help customers find what they need quickly.
  • Lightbox image
    A lightbox is a UI component used to display (in this case) an image in a modal overlay appearing on top of the main content. It provides users with an immersive way to focus on content without disrupting the overall layout, while also allowing them to quickly navigate back to the content beneath the lightbox.
  • Lists
    The List Row component helps group overview information. The information presented should be scannable and actionable.
  • Loading
    A visual indicator that a process is happening in the background but the interface is not yet ready for interaction.
  • Messages
    Messages enable customers and testers to communicate with each other.
  • Pictogram
    This component provides pictogram typed icons.
  • Poster Play
    This component is a button that provides a preview image for videos.
  • Progress bar
    General purpose component to track progress
  • QR Code
    This component is a component that will render a QR code of the value provided.
  • Rating stars
    Rating stars component that supports half stars
  • Row Selector
    The row selector component allows the user to select a list for bulk actions. It should only be used within tk-list-row.
  • Segmented Controls
    Use segment controls for mutually exclusive selections that directly controls another component.
  • Sentiment
  • Split View
    The split view component is made up of two content areas. The description area on the left and with the data/information area on the right. This pattern helps customers focus on data-heavy information.
  • Tables
    Tables are used to arrange and display data in a well-structured and meaningful way.
  • Tags
    Tags are compact elements that represent an input or attribute.
  • Tester vitals
    Configurable widget to display tester demographics along with an optional rating
  • Toggle button
  • Typeahead
    Typeahead helps customers find teammates and reduce the likelihood of errors.

Form

  • Checkbox
    A checkbox is used to give a user a way to select a value.
  • Combobox
    Combobox lets you choose a single or multiple values from a list of options.
  • Form Rule
    Form rules are used to divide content within forms.
  • Hint
    A prompt for inputs
  • Input
    A controllable input box. Note: we are currently in the midst of breaking out TkInput into several smaller, more focused components.
  • Input Title
    Input titles are used to name many different elements. Note: This is not yet a web component.
  • Label
    A label for inputs.
  • Multi-select List
    A checkbox list is used to give a user a way to select any number of a set of choices.
  • Search
    This component is still in Beta. Please reach out to Design System team before using it.
  • Select
    Make a selection using a dropdown.
  • Single-select List
    A radio box list is used to give a user a way to select one from a set of choices.
  • Sliders
    The range slider component allows the user to select a value or range.
  • Switch
    Switch for users to customize their experience.
  • Text Area
    A controllable text area box.

Layout

  • Containers
    Containers are a stylized component to hold content. Containers provide the visual foundation for most views.
  • Layers
    Layers are used to give order and preference on components. The most common applications of Layer are on Modals and Tooltips.
  • Layout
    Use the Toolkit helper classes to maintain harmony and alignment in the UI.
  • Split Layout
    Two columns layout with main left side content and secondary right side.
  • Wrappers
    Wrappers have specific widths to hold content blocks. Wrappers help organize content on a page to ensure a comfortable reading length.

Navigation

  • Context Switcher
    This component is still in Beta. Please reach out to Design System team before using it.
  • Nav bar
    These components are located near the top of views and help orient customers when they arrive to new pages.
  • Navigation
    These components are located near the top of views and help orient customers when they arrive to new pages.
  • Pagination
    Pagination allows customers to navigate between multiple pages worth of items in a single view.
  • Sidebar Navigation
    This component is still in Beta. Please reach out to Design System team before using it.
  • Step Navigation
    Step Navigation guides users through a workflow.
  • Tabs
    Tabs are used as a form of navigation within the same context, allowing the user to alternate between views that provide different information. A count badge can also be used in a tab.

Overlay

  • Banners
    When considering the use of a banner, it's best to evaluate the level of the message first. Content within banners must be important or require action taken by the customer.
  • Bulk Selector
    The bulk selector gives individuals the ability to take complex actions on a group of items.
  • Modals
    Modals are overlaying patterns and will intentionally obscure information behind it as such they can be disruptive. Modals require action before the user can continue interacting with the rest of UserTesting.
  • Popovers
    Popovers are components that overlay on top of the interface. Popovers can contain a mix of information. Popovers are used to inform customers about specific content and actions.
  • Toast
    Toast gives customers helpful information about the success or failure of their action
  • Tooltips
    Tooltips provide contextual information about a particular element.
  • User Notifications
    The notifications appear when the logged in user has new or existing notifications.

Patterns

  • Full Page Message
    A template that defines a simple message page, with options to include an image, banner and/or button if required.
  • Question card & Group Questions Container
    Question cards allow users to customize their tasks or Screener questions. Group Question Containers show multiple questions that are related to a bigger task or question.

Visualizations

  • Data Colors
    A color palette to help guide our Data Visualizations.

Buttons

Buttons are useful to draw attention to a goal or action. Calls to actions within buttons should be explicit.

For information about how to write button copy, check out the typography page.

Playground 👩🏽‍🔬

Send
Alignment
Size

Used only when there is a need to conserve space.

This size is only for the merged platform and is not production ready.

Width
Status
Type

Contained buttons have more emphasis, as they use a primary colour fill. A layout and/or container should contain a single prominent button that makes it clear that other buttons have less importance in the hierarchy. This high-emphasis button commands the most attention.

Use contained buttons for high prioritized interactions as they should guide the user. Use only as stand-alone or in combination with outline or ghost buttons. Use sparingly, as overuse can cause confusion to a user.

Outlined buttons are used for more emphasis than text buttons due to the stroke. Outline buttons are intended for general use buttons and actions like triggering popouts, filtering and sharing actions, when a number of buttons have the same priority but none of them are more important than the others.

This is typically the most appropriate button type because of its neutral visual weight. Also use outline buttons for low prioritized interactions that need to be available for the user (e.g. Back, Cancel). Use only in combination with primary or highlight buttons.

Ghost buttons have the same spacing and alignment rules as other buttons, however they are the most minimal visually. This allows them to be used alongside buttons when a low priority action is required, the element is placed alongside buttons, or when a tap target area should be considered.

Ghost buttons are typically used for less important actions. Use ghost buttons for very low prioritized interactions as they draw little attention from the user. Use only in combination with other ghost buttons or primary buttons. Note: Ghost buttons are meant to be used for interactions, they are not links.

The outline dark button should only be paired with the background of the same hue.

This is typically the most appropriate button type because of its neutral visual weight on dark backgrounds. Also use outline dark buttons for low prioritized interactions that need to be available for the user (e.g. Back, Cancel). Use only in combination with outline buttons.

Variant

When a user attempts a potentially destructive action we use red to warn them of the potential risk involved with completing such an action.

Defaults

Example
Copy 
  <tk-button
    alignment="center"
    size="standard"
    status="ready"
    type="contained"
    variant="standard"
  >
    Example
  </tk-button>

Usage

Do

  • Limit the number of contained buttons per page
  • Keep content within buttons clear, concise, actionable and no longer than 40 characters
  • Group like-sized buttons

Don't

  • Wrap TkButton in an <a> or <button>
  • Use contained and destructive buttons together
  • Write button text that is greater than 40 characters
  • Use other colors for button link
  • Put default buttons next to compact buttons

Submit

Submit
Copy 
  <form action="http://www.google.com" id="formId">
    <tk-button
      action-type="submit"
      form="formId">
      Submit
    </tk-button>
  </form>

Text + Icon

Locked feature
10:03
Expand Copy 
<tk-button type="outline">
  Locked feature
  <tk-icon class="ml-2x" name="lock" size="small"></tk-icon>
</tk-button>
<hr class="horizontal-rule" />
<tk-button
  type="outline"
>
  <tk-icon class="mr-2x" name="play" size="small"></tk-icon>
  10:03
</tk-button>

Description

Occasionally, an icon helps provide necessary context to an action. For example, we use a lock icon to visibly communicate to a customer that a feature or flow is unavailable.

For video play buttons that utilize preview images, use the tk-poster-play component that can be found here.

Icon only

Expand Copy 
  <tk-icon-button>
    <tk-icon name="close"></tk-icon>
  </tk-icon-button>

Description

Please use the TkIconButton component for this. Full reference here.

Usage

Do

  • Ensure the action of the button matches the icon of the button
  • Ensure buttons with locks are clickable
  • Place locks after a string of text.
  • Set the status Prop to disabled when applicable.
  • Only show locks when the feature or flow relevant to the user is blocked.

Don't

  • Add lock icons without context
  • Add more than one lock to a button
  • Use icons for complex actions

Inverse

Copy 
<button class="btn--inverse mb-2x">Button inverse</button>
<button class="btn--inverse active">Button inverse</button>

Description

This style of button is used as a toggle to select one or more options. Button Inverse should always have a .input--hidden:checked + .btn--inverse applied to one of the options. For buttons that require more text, use .btn--multiline with this class.

Stacking utils

Contained Outline Ghost
Copy 
<div class="l-flex l-flex-wrap">
  <tk-button class="mb-2x btn-md-block mr-lg-1x">Contained</tk-button>
  <tk-button class="mb-2x btn-md-block mr-lg-1x" type="outline">Outline</tk-button>
  <tk-button class="mb-2x btn-md-block" type="ghost">Ghost</tk-button>
</div>

Description

For times when buttons are next to each other on larger screens, but need to stack at smaller screens, we have classes to stack them. Use btn-md-block for screens stacking at medium screensizes and use btn-sm-block for stacking at small screensizes.

Group

Cancel Send
Copy 
<div class="btn-group">
  <tk-button class="mr-2x" type="outline">Cancel</tk-button>
  <tk-button>Send</tk-button>
</div>

Description

When two or more buttons need to be next to each other. Commonly used in modals.

Usage

Do

  • Have clear actions for grouped buttons

Don't

  • Use three or more buttons in a group without a good reason

Accessibility

  • Receives :focus

  • Buttons without content or a name should have aria-label such as icons.

Usage

Do

  • Ensure one Radio Button Group item is selected
  • Provide clear copy with each radio selection

Don't

  • Allow more than one radio button group to be selected at a time

Accessibility

  • Receives :focus

  • Groups of radio buttons should share the same :name