Some attributes in ARIA are boolean(-like). These attributes may seem a lot like boolean attributes in HTML, but there are some important differences to be aware of.

George Boole, the philosopher and mathematician who came up with a type of algebra that has just true and false as its variables

Boolean attributes in HTML

In HTML, some attributes are boolean attributes, which basically means they can be true or false. They’ll be the case, or not the case. Some examples: checked, required, disabled and open.

Boolean attributes in HTML are true when they are present:

The presence of a boolean attribute on an element represents the true value, and the absence of the attribute represents the false value.

(From: HTML, Common microsyntaxes, Boolean attributes)

So, if a checkbox is checked, it has the checked attribute, otherwise it does not. The attribute, when present, can have any value, like checked="checked", though the HTML spec explicitly says we should not use true or false as attribute values for boolean attributes:

The values “true” and “false” are not allowed on boolean attributes. To represent a false value, the attribute has to be omitted altogether.

It would work though: the checked attribute works with any value, even checked="true" or checked="false" represents that the input is checked:

 <!--  
  on first render, the following 
  checkboxes are in checked state 
-->
<input type="checkbox" checked="true" />
<input type="checkbox" checked="false" />
<input type="checkbox" checked="hello" />

 <!--  
  on first render, the following 
  checkboxes are not in checked state 
-->
<input type="checkbox" />

In some cases, browsers will help us manage the presence of these attributes. They don’t for checked, but they do for details/summary (the open attribute on the details element when its summary is expanded or collapsed). In other cases, the browser can’t manage presence or absence, like for the required attribute. Whether an element is set to required, is up to the author’s intention, there are no browser defaults.

The attributes I discussed earlier are what specifications call ‘content attributes’, we write them in our markup. In JavaScript, we can also affect the truth value of these HTML attributes with so-called IDL attributes, for instance:

element.checked = true; // sets checked state to true
element.checked = 'checked'; // sets checked state to true
element.checked = 'foo'; // also sets checked state to true
element.checked = false; // sets checked state to false
element.checked = ''; // sets checked state to false

Boolean attributes in ARIA

In ARIA, there are also attributes that can be true or false, but their state is expressed differently. It is a different language than HTML, after all. HTML is the most common host for it, but ARIA can also be used in other languages, like XML and SVG.

As explained previously, HTML has the concept of boolean attributes. It also has the concept of keyword and enumerated attributes. These attributes can come with a fixed number of string values. When ARIA is used in HTML, we use these types of attributes. This means that when we say “boolean” in ARIA, we’re realling talking about strings that happen to be use the words “true” or “false”.

According to the type mapping table in the WAI-ARIA 1.1 specification, there are three different attribute types in ARIA that explictly list ”true” and “false” as possible values:

• attributes that are “boolean”, which accept only "true" or "false" (eg aria-busy and aria-multiline, aria-readonly)
• attributes that accept "true", "false" and "undefined" (eg aria-expanded, aria-grabbed, aria-selected)
• “tristate” attributes, which accept ”true”, "false" or "mixed" (eg aria-checked, aria-pressed)

That’s not all, as there are also properties with different and larger sets of possible values:

• aria-invalid (takes "grammar", "spelling", "false" and "true")
• aria-haspopup (takes "true", "false", "listbox", "menu", "tree", "grid" and "dialog")
• aria-current (takes "true", "false", "page", "step", "location", "date" and "time")

All of these fall into that “keyword and enumerated attributes” bracket.

ARIA attributes can be set using setAttribute(). From ARIA 1.2, which is currently a “Candidate Recommendation Draft” (it’s like a Candidate Recommendation, but with significant updates made to it), ARIA attributes can be specified using IDL attributes, too, for instance:

element.ariaChecked = "true"; // sets `aria-checked` to true

Scott O’Hara wrote about this in more detail about this upcoming feature in his recent post New in ARIA 1.2: ARIA IDL attributes.

HTML vs ARIA booleans

So, for HTML boolean attributes it’s all about presence and absence, while in ARIA boolean attributes, the boolean state is expressed via "true" and "false" string values and there are bunch of attributes that take those strings and a couple more.

Some examples of these differences:

• The absence of the checked boolean attribute maps to aria-checked="false" (unless it was modified, that is… so this mapping only applies in the elements default state)
• The presence of the disabled attribute maps to aria-disabled="true"
• The presence of the open attribute on details maps the state of its summary to aria-expanded="true", the absence of it maps it to aria-expanded="false"

Summary

So, there’s boolean attributes and keyword and enumerated attributes in HTML. Booleans in ARIA are of the latter type, so they work slightly differently than boolean attributes in HTML and take a number of keywords, sometimes many more than true and false, at which point they aren’t really booleans.

---

The post Boolean attributes in HTML and ARIA: what's the difference? was first posted on hiddedevries.nl blog | Reply via email