WCAG Understandable Support

According to the Web Content Accessibility Guidelines (WCAG) definition of the Understandable accessibility principle, "information and the operation of user interface must be understandable".

The Understandable principle provides the following categories of success criteria:

Readable

The 3.1 Readable WCAG category requires you to "make text content readable and understandable" and includes the following success criteria:

  • 3.1.1 Language of Page, Conformity Level A.
    • The criteria is not applicable to Kendo UI for Angular because the programmatically determined language of each web page depends on the application logic and browser specifics.
  • 3.1.2 Language of Parts, Conformity Level AA.
    • The criteria is not applicable to Kendo UI for Angular because the programmatically determined language of each passage or phrase in the content of each web page depends on the application logic and browser specifics.
  • 3.1.3 Unusual Words, Conformity Level AAA.
    • The messages included in the Kendo UI for Angular components do not use words or phrases used in an unusual way.
  • 3.1.4 Abbreviations, Conformity Level AAA.
    • The messages included in the Kendo UI for Angular components do not include abbreviations.
    • (Tip) Use the Tooltip Component to display the expanded form of abbreviations.
  • 3.1.5 Reading Level, Conformity Level AAA.
    • The messages included in the Kendo UI for Angular components do not require reading ability more advanced than the lower secondary education level.
  • 3.1.6 Pronunciation, Conformity Level AAA.
    • The messages included in the Kendo UI for Angular components do not include words whose meaning in context is ambiguous without knowing their pronunciation.

Predictable

The 3.2 Predictable WCAG category requires you to "make Web pages appear and operate in predictable ways" and includes the following success criteria:

  • 3.2.1 On Focus, Conformity Level A.
    • The Kendo UI for Angular components do not require additional actions to meet this criteria.
  • 3.2.2 On Input, Conformity Level A.
    • The Kendo UI for Angular components do not require additional actions to meet this criteria.
  • 3.2.3 Consistent Navigation, Conformity Level AA.
    • The criteria is not applicable to Kendo UI for Angular because the implementation of consistent navigation within a set of web pages depends on the application logic.
  • 3.2.4 Consistent Identification, Conformity Level AA.
    • The criteria is not applicable to Kendo UI for Angular because the implementation of consistent identification within a set of web pages depends on the application logic.
  • 3.2.5 Change on Request, Conformity Level AAA.
    • The criteria is not applicable to Kendo UI for Angular because the implementation of any changes on request depends on the application logic.

Input Assistance

The 3.3 Input Assistance WCAG category requires you to "help users avoid and correct mistakes" and includes the following success criteria:

  • 3.3.1 Error Identification, Conformity Level A.
    • The Kendo UI for Angular components ship with full support for Angular Forms and form validation.
  • 3.3.2 Labels or Instructions, Conformity Level A.
    • The Kendo UI for Angular components do not require additional actions to meet this criteria.
  • 3.3.3 Error Suggestions, Conformity Level AA.
    • The criteria is not applicable to Kendo UI for Angular because the implementation of error suggestions depends on the application logic.
  • 3.3.4 Error Prevention (Legal, Financial, Data), Conformity Level AA.
    • The criteria is not applicable to Kendo UI for Angular because the implementation of error prevention for legal, financial, or data content depends on the application logic.
  • 3.3.5 Help, Conformity Level AAA.
    • The criteria is not applicable to Kendo UI for Angular because the implementation of context-sensitive help depends on the on the application logic.
  • 3.3.6 Error Prevention (All), Conformity Level AAA.
    • The criteria is not applicable to Kendo UI for Angular because the implementation of error prevention depends on the application logic.

In this article