What is the most unusual word

Success criteria and compliance requirements of the Web Content Accessibility Guidelines (WCAG) 2.1

This page provides links and notes on Success Criterion 3.1.3 Unusual Words from WCAG 2.1. After BITV 2.0 or EN 301 549, this success criterion is informative and does not have to be implemented for conformity.

Note: There is still no German translation of WCAG 2.1. Therefore, the requirements that were already set in WCAG 2.0 are taken from the German translation of WCAG 2.0. New requirements that were only introduced in WCAG 2.1 originate from the English language WCAG 2.1.

Success Criterion 3.1.3

Success Criterion 3.1.3 Unusual Words is incorporated in the Web Content Accessibility Guidelines (WCAG) 2.1 as follows:

3. Understandable

Information and operation of the user interface must be understandable.

Guideline 3.1 Legible

Make content readable and understandable.

Success Criterion 3.1.3 Unusual Words

(Level AAA)

There is a mechanism to identify specific definitions of words or phrases that are used in unusual or restricted ways, including idioms and jargon.

English-language texts

3. Understandable

Information and the operation of the user interface must be understandable.

Guideline 3.1 Readable

Make text content readable and understandable.

understanding guideline 3.1

Success Criterion 3.1.3 Unusual Words

(Level AAA)

A mechanism is available for identifying specific definitions of words or phrases used in an unusual or restricted way, including idioms and jargon.

understanding success criterion 3.1.3

No information on 3.1.3

There are currently no editorial notes on 3.1.3.

Regarding guideline 3.1:

It is important to make content readable for all user groups. To be taken into account (according to WCAG 2.1, conformity level AA) only speech markings for speech output.

List of all WCAG success criteria 2.1

1. Perceptible

Information and components of the user interface must be presented to users in such a way that they can perceive them.

Guideline 1.1 Text alternatives

Provide text alternatives for all non-text content so that it can be changed into other forms the user needs, such as large print, braille, symbols, or simpler language.

Guideline 1.2 Time-Based Media

Provide alternatives to time-based media.

Guideline 1.3 Customizable

Create content that can be presented in different ways (e.g. simpler layout) without losing information or structure.

Guideline 1.4 Distinguishable

Make it easier for users to see and hear content including separating the foreground and background.

2. Operable

Components of the user interface and navigation must be operable.

Guideline 2.1 Keyboard operable

Make sure that all functionalities are accessible via keyboard.

Guideline 2.2 Sufficient time

Give users enough time to read and use content.

Guideline 2.3 Seizures and physical reactions

Avoid creating content in ways that are known to cause seizures.

Guideline 2.4 Navigable

Provide means to help users navigate, find content, and determine where they are.

Guideline 2.5 Entry Modalities

Make it easier for users to operate functionality through various inputs beyond keyboard.

3. Understandable

Information and operation of the user interface must be understandable.

Guideline 3.1 Legible

Make content readable and understandable.

Guideline 3.2 Foreseeable

Make websites look and work predictably.

Guideline 3.3 Assistance with input

Help users avoid and correct mistakes.

4. Robust

Content must be robust enough that it can be reliably interpreted by a wide variety of user agents, including assistive technology.

Directive 4.1 Compatible

Maximize compatibility with current and future user agents, including assistive technologies.

5. Conformity

This section lists requirements for conformance to WCAG 2.1. It also gives information about how to make conformance claims, which are optional. Finally, it describes what it means to be accessibility supported, since only accessibility-supported ways of using technologies can be relied upon for conformance. [en; https: //www.w3.org/TR/UNDERSTANDING-WCAG20/conformance; Understanding Conformance] includes further explanation of the accessibility-supported concept.

5.2 Conditions of Conformity

For a website to be WCAG 2.1-compliant, all of the following conformity conditions must be met: