Accessible names convey the purpose or intent of the element. This helps users understand what the element is for and how they can interact with it. In general, accessible names for elements should be unique to a page. This helps users distinguish an element from other elements and helps users identify the element they want to interact with.

Depending on the element and the HTML markup, the value of the accessible name may be derived from visible (e.g., the text within <figcaption > ) or invisible (e.g., the aria-label attribute set on an element) content, or a combination of both. How an element's accessible name is determined is based on the accessible name calculation , which is different for different elements.

It is best to use visible text as the accessible name. Many elements, including <a > , <td > and <button > , can get their accessible name from their content. For example, given <a href="foo.html">Bar </a > , the accessible name of this hyperlink is "Bar."

Other elements get their accessible name from the content of associated elements. For example, when a <fieldset > or <table > element contains a descendant <legend > or <caption > element, respectively, the association of the nested element providing an accessible name for the parent is automatic. For form elements like <textarea > and <input > , the accessible name comes from the associated <label > element. The association needs to be explicitly defined by setting the for attribute in the <label > element to match the form element's id . Alternatively, an implicit association is created when the form control is directly nested within the <label > element.

For some elements, the accessible name comes from the element's attributes; for example, the alt attribute in the case of <img > . Given <img src="grape.jpg" alt="banana"/> , the image's accessible name is "banana."

To create an association between visible content and an element or multiple text nodes and an element, the aria-labeledby attribute can be used. If there is no visible text to associate with a UI element needing an accessible name, the aria-label attribute can be used. Names should not be added to elements marking up inline text, like <code > , <del > , and <mark > .

Many elements, such as sections of textual content, don't need an accessible name. All controls should have an accessible name. All images that convey information and aren't purely presentational do too.

Assistive technologies will provide the user with the accessibility name property, which is the accessible name along with the element's role. While many elements don't need an accessible name, some content roles can benefit from having an accessible name. For example, a tabpanel is a section of content that appears after a user activates the associated element with a tab role. This role can be set on an element with no needed name, like the <div > element. The tab is the control and must have an accessible name. The tabpanel is the child (content section) of the tab . Adding aria-labelledby to the tabpanel is a best practice.