Text Alternatives

1.1 Text alternatives

1.1 Text Alternatives

Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.

Non-text Content

(A)

1.1.1 Non-text content

1.1.1 Non-text content

9.1.1.1a Alternative texts for operating elements

All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for the situations listed below.

Controls, input If the non-text content is a control or accepts input from the user, it has a name that describes its purpose. (Refer to Success Criterion 4.1.2 for additional requirements for controls and content that accepts user input)

Time-based media If the non-text content is time-based media, then text alternatives provide at least a descriptive identification of the non-text content. (Refer to Guideline 1.2 for additional requirements for media)

Test If the non-text content is a test or exercise that would be void if presented as text, then text alternatives at least provide a descriptive identification of the non-text content.

Sensory If non-text content is primarily intended to create a particular sensory experience, then text alternatives provide at least a descriptive identification of the non-text content.

CAPTCHA If the purpose of the non-text content is to confirm that a person and not a computer is accessing the content, then text alternatives are provided that identify the purpose of the non-text content. And alternative forms of CAPTCHA using output modes for different types of sensory perception are provided to accommodate different disabilities.

Decoration, formatting, invisible If the non-text content is pure decoration, is only used for visual formatting or is not presented to the user at all, then the content is implemented in such a way that it can be ignored by assistive technology.

Description

The meaning or function of screen buttons, icons, graphics, etc. cannot be perceived or inferred by non-sighted people.

Example: screen button with plus icon

These buttons are usually immediately apparent to a sighted user, since they can perceive the (visual) context. The seeing user will realize that when they click on this button, for example, they will create a new customer or a new item.

For a non-sighted user, the function of the screen button is not perceptible. A screen reader can recognize and read out that it is a button based on the HTML tag <button>. But the plus symbol and its meaning in the current operating context is "invisible" to a screen reader. Therefore, it is necessary to make the function of the button accessible to the screen reader by using alternative text.

It is crucial for the perceptibility of a portal or application page that you provide text alternatives for all non-textual content. Text alternatives play an essential role in accessibility, as they can be transformed into other forms of perception (visual, auditory, tactile) by assistive technologies.

For example, a screen reader reads out textual descriptions of images and animations, and a Braille display shows them in Braille. A text alternative for acoustic information makes content accessible for deaf people.

Text alternatives also help everyone understand non-textual information and make content accessible to search engines.

The WCAG describes some exceptions to the guideline described here. These are described under the following link: Non-text content - exceptions

Relevance and applicability

This guideline is relevant when implementing accessibility for your portal. It is one of the best practicesHow to make your pages accessible - Best practices).

General implementation

Below is some general guidance on the implementation of this guideline.

  • An alternative text should be short. It should convey the purpose of the image, not describe the image. When writing the text alternative, think about which details are important. Depending on the context, a completely different text alternative can be useful for the one image.

  • Text alternatives are crucial to assistive technologies. For accessibility reasons, it is not necessary to give an image a title (title attribute). You should only do this if you want to convey additional information in the title that goes beyond the information in the text alternative.

  • Image links should describe the purpose of the link, not the actual image.

  • Decorative images should have a blank (or meaningless) text alternative.

  • Complex images, such as charts or graphs, should have a long description close to the image. The text alternative for the image should describe where the nearby image is located.

Detailed implementation

More information

Insert elements on pages