Checkboxes can be used when a site visitor to select one or more options from a list in a form.
Use the .vf-form__checkbox
when you want the site visitor to select 0, 1 or multiple options from the predefined list of checkboxes.
Do not use the .vf-form__checkbox
when you need a site visitor to only pick one option from the available selection. For this use case you should use the vf-radio button component.
A vf-form__checkbox
must be accompanied by a vf-form__label
inside a vf-form__item
with the vf-form__item--checkbox
variant.
You can also use the vf-form__helper
to add some more descriptive, explanitory text under the vf-form__label
. See the examples for the correct markup.
The .vf-form__checkbox
needs to grouped into a vf-form__fieldset
and using the vf-form__label
to help the site visitor understand what they are choosing for.
Generally the vf-form__fieldset
will use the vf-stack
layout component to stack the vf-form__checkbox
on top of each other. You can set these to be inline by using the vf-cluster
layout component as well. See the examples for the correct markup.
Depending on your environment you'll want to use render
or include
. As a rule of thumb: server-side use include
, precompiled browser use render
. If you're using vf-eleventy you should use include
.
include
You'll need to pass a context object from your code or Yaml file (example), as well as the path to the Nunjucks template. Nunjucks' include
is an abstraction of render
and provides some additional portability.
{% set context fromYourYamlFile %}
- or -
{% set context = {
"component-type" : "form",
"checkbox_legend" : [object Object],
"required" : true,
"checkbox_label" : [object Object],
"checkbox_group" : "agreement",
"checkbox_value" : "pizza-agreement",
}
%}
{% include "../path_to/vf-form__checkbox/vf-form__checkbox.njk" %}
render
This approach is best for bare-bones Nunjucks environments, such as precompiled templates with the Nunjucks slim runtime where include
is not be available.
{% render '@vf-form__checkbox', {
"component-type" : "form",
"checkbox_legend" : [object Object],
"required" : true,
"checkbox_label" : [object Object],
"checkbox_group" : "agreement",
"checkbox_value" : "pizza-agreement",}
%}
<div class="vf-form__item vf-form__item--checkbox">
<input type="checkbox" name="agreement" value="pizza-agreement" id="commit-to-newsletters" class="vf-form__checkbox">
<label for="commit-to-newsletters" class="vf-form__label">By selecting this checkbox you agree you like pizza.</label>
</div>
Depending on your environment you'll want to use render
or include
. As a rule of thumb: server-side use include
, precompiled browser use render
. If you're using vf-eleventy you should use include
.
include
You'll need to pass a context object from your code or Yaml file (example), as well as the path to the Nunjucks template. Nunjucks' include
is an abstraction of render
and provides some additional portability.
{% set context fromYourYamlFile %}
- or -
{% set context = {
"component-type" : "form",
"checkbox_legend" : [object Object],
"item_01" : [object Object],
"item_02" : [object Object],
"item_03" : [object Object],
"item_04" : [object Object],
"item_05" : [object Object],
"item_06" : [object Object],
}
%}
{% include "../path_to/vf-form__checkbox/vf-form__checkbox.njk" %}
render
This approach is best for bare-bones Nunjucks environments, such as precompiled templates with the Nunjucks slim runtime where include
is not be available.
{% render '@vf-form__checkbox', {
"component-type" : "form",
"checkbox_legend" : [object Object],
"item_01" : [object Object],
"item_02" : [object Object],
"item_03" : [object Object],
"item_04" : [object Object],
"item_05" : [object Object],
"item_06" : [object Object],}
%}
<fieldset class="vf-form__fieldset vf-stack vf-stack--400">
<legend class="vf-form__legend">Pick your favourite(s).</legend>
<div class="vf-form__item vf-form__item--checkbox">
<input type="checkbox" name="fruits" value="apples" id="fruit_01" class="vf-form__checkbox">
<label for="fruit_01" class="vf-form__label">Apples</label>
</div>
<div class="vf-form__item vf-form__item--checkbox">
<input type="checkbox" name="fruits" value="bums" id="fruit_02" class="vf-form__checkbox">
<label for="fruit_02" class="vf-form__label">Bananas</label>
<p class="vf-form__helper">Some text to help with things</p>
</div>
<div class="vf-form__item vf-form__item--checkbox">
<input type="checkbox" name="fruits" value="mangos" id="fruit_03" class="vf-form__checkbox">
<label for="fruit_03" class="vf-form__label">Mangos</label>
</div>
<div class="vf-form__item vf-form__item--checkbox">
<input type="checkbox" name="fruits" value="oranges" id="fruit_04" class="vf-form__checkbox">
<label for="fruit_04" class="vf-form__label">Oranges</label>
</div>
<div class="vf-form__item vf-form__item--checkbox">
<input type="checkbox" name="fruits" value="pears" id="fruit_05" class="vf-form__checkbox" disabled>
<label for="fruit_05" class="vf-form__label">Pears</label>
</div>
<div class="vf-form__item vf-form__item--checkbox">
<input type="checkbox" name="fruits" value="strawberries" id="fruit_06" class="vf-form__checkbox vf-form__checkbox--invalid">
<label for="fruit_06" class="vf-form__label | vf-form__label--required">Strawberries<span class="vf-u-sr-only">field is required.</span>
<svg class="vf-icon vf-icon--asterick" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24">
<title>asterick</title>
<path d="M23.555,8.729a1.505,1.505,0,0,0-1.406-.98H16.062a.5.5,0,0,1-.472-.334L13.405,1.222a1.5,1.5,0,0,0-2.81,0l-.005.016L8.41,7.415a.5.5,0,0,1-.471.334H1.85A1.5,1.5,0,0,0,.887,10.4l5.184,4.3a.5.5,0,0,1,.155.543L4.048,21.774a1.5,1.5,0,0,0,2.31,1.684l5.346-3.92a.5.5,0,0,1,.591,0l5.344,3.919a1.5,1.5,0,0,0,2.312-1.683l-2.178-6.535a.5.5,0,0,1,.155-.543l5.194-4.306A1.5,1.5,0,0,0,23.555,8.729Z" />
</svg>
</label>
<p class="vf-form__helper vf-form__helper--error">You didn't pick Strawberries?</p>
</div>
</fieldset>
Depending on your environment you'll want to use render
or include
. As a rule of thumb: server-side use include
, precompiled browser use render
. If you're using vf-eleventy you should use include
.
include
You'll need to pass a context object from your code or Yaml file (example), as well as the path to the Nunjucks template. Nunjucks' include
is an abstraction of render
and provides some additional portability.
{% set context fromYourYamlFile %}
- or -
{% set context = {
"component-type" : "form",
"checkbox_legend" : [object Object],
"inline" : true,
"item_01" : [object Object],
"item_02" : [object Object],
"item_03" : [object Object],
"item_04" : [object Object],
"item_05" : [object Object],
"item_06" : [object Object],
}
%}
{% include "../path_to/vf-form__checkbox/vf-form__checkbox.njk" %}
render
This approach is best for bare-bones Nunjucks environments, such as precompiled templates with the Nunjucks slim runtime where include
is not be available.
{% render '@vf-form__checkbox', {
"component-type" : "form",
"checkbox_legend" : [object Object],
"inline" : true,
"item_01" : [object Object],
"item_02" : [object Object],
"item_03" : [object Object],
"item_04" : [object Object],
"item_05" : [object Object],
"item_06" : [object Object],}
%}
<fieldset class="vf-form__fieldset | vf-stack vf-stack--400">
<legend class="vf-form__legend">Pick your favourite(s).</legend>
<div class="vf-cluster vf-cluster--400">
<div class="vf-cluster__inner">
<div class="vf-form__item vf-form__item--checkbox">
<input type="checkbox" name="travel" value="walking" id="travel_01" class="vf-form__checkbox">
<label for="travel_01" class="vf-form__label">Walking</label>
</div>
<div class="vf-form__item vf-form__item--checkbox">
<input type="checkbox" name="travel" value="bike" id="travel_02" class="vf-form__checkbox">
<label for="travel_02" class="vf-form__label">Bike</label>
</div>
<div class="vf-form__item vf-form__item--checkbox">
<input type="checkbox" name="travel" value="car" id="travel_03" class="vf-form__checkbox">
<label for="travel_03" class="vf-form__label">Car</label>
</div>
<div class="vf-form__item vf-form__item--checkbox">
<input type="checkbox" name="travel" value="bus" id="travel_04" class="vf-form__checkbox">
<label for="travel_04" class="vf-form__label">Bus</label>
</div>
<div class="vf-form__item vf-form__item--checkbox">
<input type="checkbox" name="travel" value="train" id="travel_05" class="vf-form__checkbox" disabled>
<label for="travel_05" class="vf-form__label">Train</label>
</div>
<div class="vf-form__item vf-form__item--checkbox">
<input type="checkbox" name="travel" value="airplane" id="travel_06" class="vf-form__checkbox vf-form__checkbox--invalid">
<label for="travel_06" class="vf-form__label | vf-form__label--required">Airplane<span class="vf-u-sr-only">field is required.</span>
<svg class="vf-icon vf-icon--asterick" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24">
<title>asterick</title>
<path d="M23.555,8.729a1.505,1.505,0,0,0-1.406-.98H16.062a.5.5,0,0,1-.472-.334L13.405,1.222a1.5,1.5,0,0,0-2.81,0l-.005.016L8.41,7.415a.5.5,0,0,1-.471.334H1.85A1.5,1.5,0,0,0,.887,10.4l5.184,4.3a.5.5,0,0,1,.155.543L4.048,21.774a1.5,1.5,0,0,0,2.31,1.684l5.346-3.92a.5.5,0,0,1,.591,0l5.344,3.919a1.5,1.5,0,0,0,2.312-1.683l-2.178-6.535a.5.5,0,0,1,.155-.543l5.194-4.306A1.5,1.5,0,0,0,23.555,8.729Z" />
</svg>
</label>
</div>
</div>
</div>
</fieldset>
This component is distributed with npm. After installing npm, you can install the .vf-form__checkbox
with this command.
$ yarn add --dev @visual-framework/vf-form__checkbox
The source files included are written in Sass(scss
). You can point your Sass include-path
at your node_modules
directory and import it like this.
@import "@visual-framework/vf-form__checkbox/index.scss";
Make sure you import Sass requirements along with the modules. You can use a project boilerplate or the vf-sass-starter
set-
style functions to cleaner versionvf-form__checkbox--inline
into it's own .njk file
File system location: components/vf-form__checkbox
Find an issue on this page? Propose a change or discuss it.