Category: WCAG

Provide a consistent way to identify components, icons, or other non-text items having the same functionality across the site for easy identification. Official Requirements Success

Maintain a consistent presentation and layout across web pages on your website that follow the same way to navigate content.  Official Requirements 3.2.3 Consistent Navigation:

The purpose of this success criterion is to make sure that functionality is predictable as users navigate through a website’s content. Any element that can

Ensure that there is a way to identify specific definition words such as jargon and idiom. Official Requirements Success Criterion 3.1.3 Unusual Words (Level AAA):

Ensure that the content involving multiple languages on the same page has the human language defined such that it can be programmatically determined.  Official Requirements

Any content that is implemented using markup languages such as HTML should be accessible to Assistive Technologies (AT). This helps user agents to extract and

Each input field should make it easier for all assistive devices to convey the information to their users. Official Requirements Success Criterion 1.3.5 Identify Input

Make sure that the web page and app’s content is not limited to only one orientation (portrait or landscape) unless it is essential.   Official Requirements

Avoid using only sensory characteristics such as shape, size, color, etc to communicate information to users. Official Requirements Success Criterion 1.3.3 Sensory Characteristics (Level A):

The purpose of this success criteria is to provide an alternative representation of the order of content without changing its meaning. It is crucial for

Content structures such as tables, lists, and headings presented to users must ensure that they are not conveyed only through visual cues. Official Requirements Success

Make sure that users can use or switch to different input mechanisms while interacting with your content on the web. Official Requirements Success Criterion 2.5.6