npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@utrecht/checkbox-css

v1.3.0

Published

Checkbox component for the Municipality of Utrecht based on the NL Design System architecture

Downloads

102

Readme

Checkbox

Terminologie

Class names

  • utrecht-checkbox

Introduction

Checkboxes are usually used to provide a way for users to make a range of selections (zero, one or more). They can also be used to tell users that they agree to specific terms.

When to use

Checkboxes are used for multiple choices, not for mutually exclusive choices. Each checkbox works independently from other checkboxes in the list, therefore checking an additional box does not affect any other selections.

Forms

Can be used in forms on a full page or in modals.

Terms and conditions

Turning the checkbox input on or off can indicate whether you agree to the terms.

Alternatives and related components

Use radio buttons to display a list of options where users can only make one choice.

Anatomy

The checkbox consists of:

  1. Label (optional): indicates what should be selected below.
  2. Checkbox input: a checkbox input that indicates the correct status. By default it is not active.
  3. Checkbox label: describes the information you can select or deselect.
  4. Helper text (optional): displays more information about the checkboxes

(Interactive) states

The checkbox contains the states normal, hover, disabled, error and focus.

Accessibility

Screen readers automatically report the status of the check box.

Labeling

External links

Keyboard support

  • Move focus to each checkbox using the tab key (or shift + tab when tabbing backwards)
  • Activate or deactivate checkboxes with the space key

Content guidelines

Checkbox labels

Checkbox labels must:

  • Start with a capital letter
  • Not end in punctuation if it’s a single sentence, word, or a fragment
  • In case the checkbox asks to agree to the terms and conditions, use the first person

Best practices

Do's

Checkboxes must:

  • Work independently of each other: selecting a checkbox may not change the selection status of another checkbox in the list.
  • Be positively boxed: for example “Enable notifications” instead of “Disable notifications”.
  • Always have a label handy when you use it to turn a setting on or off.
  • Use label tags as click targets.
  • Be arranged in a logical order, whether alphabetical, numeric, time-based or some other clear system.
  • Link to more information or have a subtitle for more explanation. Don't rely on tooltips to explain a checkbox.
  • If they are too long, run over the second line. This is preferable than truncation.
  • If they are too long, they will be aligned left
  • If they are too long, let the text flow under the checkbox so that the control and label are aligned at the top.

Don'ts

Checkboxes must:

  • Not cut with an omit task if the label is too long and run over 2 lines.

Relevante WCAG eisen

  • WCAG eis 1.3.5:
    • Gebruik aria-controls als de checkbox een regio zichtbaar of onzichtbaar maakt.
  • WCAG eis 2.4.7: focus moet zichtbaar zijn.
  • WCAG eis 2.5.5: de checkbox moet groot genoeg zijn om aan te klikken, ten minste 44×44px.

References