These articles provide practical advice on how to write your web content so that it conforms to the success criteria outlined in the Understandable principle of the Web Content Accessibility Guidelines (WCAG) 2.0 and 2.1. Understandable states that information and the operation of user interface must be understandable.
Easy to understand Information and the operation of a user interface must be understandable: Users must be able to understand the information as well as the operation of the user interface. Under this principle you will find guidelines relating but not limited to: Readable: Make text content readable and understandable. Predictable: Make Web pages appear and …
WCAG Success Criterion for Understandable Principle Read More »
3.1.1 Language of Page: The default human language of each Web page can be programmatically determined. (Level A) Requirements The default language for the content of a page or app must be defined in the code. Why is it important? This makes sure that screen readers automatically use the correct speech libraries for accent and …
3.1.2 Language of Parts: The human language of each passage or phrase in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text. (Level AA) Requirements Content that is written in a different …
3.2.1 On Focus: When any component receives focus, it does not initiate a change of context. (Level A) Requirements When a user interface element receives keyboard focus (for example when users reach it by pressing the ‘Tab’ key, or when they click on it), that should not cause any big change to happen, such as: …
3.2.2 On Input: Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component. (Level A) Requirements Changing the state of any user interface component (like a dropdown or a checkbox) must not automatically cause unexpected changes …
3.2.3 Consistent Navigation: Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user. (Level AA) Requirements Navigational items that are repeated on multiple pages of a website (e.g. Search field, social …
3.2.4 Consistent Identification: Components that have the same functionality within a set of Web pages are identified consistently. (Level AA) This applies to native apps by replacing “Web pages” with “screens”. Requirements When the same user interface components, with the same functionality, are used in multiple places, they must be identified in a consistent way. …
WCAG – 3.2.4 Consistent Identification (Level AA) Read More »
3.3.1 Error Identification: If an input error is automatically detected, the item that is in error is identified and the error is described to the user with text. (Level A) Requirements Each form validation error is described with text, and the form input that is in error is in error is clearly identified; The error …
3.3.2 Labels or Instructions: Labels or instructions are provided when content requires user input. (Level A) Requirements Labels Required fields Additional instructions Why is it important? This ensures that everyone understands any requirements for entering data, and that screen reader users are made aware of it. Summary Common mistakes Design Guide Examples for Android For …
3.3.3 Error Suggestion: If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content. (Level AA) Requirements When a form validation error is detected, a suggestion is provided to help the user correct the …
