Accessible Name Calculation

W3C Accessible Name and Description Computation Specification
In general only one technique should be used to define an accessible name, if more than on technique is used the following priortiy is used for the calculation.

Accessible Name Techniques

Priority	Technique	Description
1	`aria-labelledby`	The `aria-labelledby` attribute contains a list of `IDREF`s to elements on the page. Text content of referenced elements are concatenated to compute the accessible name. References typically identify visible text on the screen in visual proximity to the control.
2	`aria-label`	The `aria-label` attribute text content defines the accessible name.
3	Encapsulation using the `label` element New in ARIA 1.2	Allows the use of the HTML `label` element to define an accessible name for the following roles: `checkbox` `listbox` `meter` `radio` `searchbox` `spinbutton` `switch` `textbox`
4	The `legend` element for grouping roles New in ARIA 1.2	Allows the use of the HTML `legend` element to define the accessible name for the `group` and `gradiogroup` roles.
5	text content	Some ARIA widget roles allow the text content of the container element to define an accessible name (e.g. `role="checkbox"`). Text content includes text alternatives, for example `alt` attribute content of an `img` element. Text content includes text from generated CSS, for example when the `content` property is used.
6	`title`	If no other source of an accessible name is found and the element has a `title` attribute, the content of the `title` attribute will used to define the accessible name.

Audio Transcript

Most ARIA roles need an accessible name or sometimes referred to as a label in HTML. Using text on the screen are typically the best sources for the accessible name for controls and widgets, since the text will be the same for both the person using the graphical rendering and the person using a screen reader. For example, in the checkbox example we will be going through shortly we will be use the text content of the DIV element for the accessible name. This slide provides an overview of the different techniques that can use used to define an accessible name. Browsers will first look for an aria-labelledby attribute. Aria-labelledby attribute uses ID references to point to text on the web page to create the accessible name. If more than one ID is provided the text is concatenated to compute the accessible name. This is the most complex way to generate the accessible name and can also be used to include values of other controls and widgets on the page. If aria-labelledby is not found the next item the browser will look for is the aria-label attribute. In this case the text content of the aria-label attribute is used as a the accessible name. If the aria-label attribute is not found and starting with the release of ARIA 1.2 the browser will look for a label role for a small subset of widget roles that can be labeled using encapsulation. The label role will typically be ddefined using the standard HTML LABEL element. For the group and radiogroup roles, the LEGEND element can be used to define an accessible name starting in ARIA 1.2. Some widget roles like checkbox in our example today, can be labeled use the child text content. If no other accessible name has been found for a widget and the element has a title attribute, the content of the title attribute will be used for the accessible name. The title attribute is usually not considered a good source for the accessible name, since it is used by many browser to render a tooltip. Tooltips are generally used more to provide help than a label, so therefore usually not too good as a label.