Understanding Success Criterion 1.3.6 Identify Purpose

Understanding Success Criterion 1.3.6 Identify Purpose

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 present the purpose of elements such as user interface components, icons, and regions to users using different modalities.

Official Requirements

Success Criterion 1.3.6 Identify Purpose (Level AAA): In content implemented using markup languages, the purpose of user interface components, icons, and regions can be programmatically determined.

Why is it required?

People with cognitive impairments have difficulty remembering, learning new things, concentrating, or making decisions that affect their everyday life. it may not be possible for them to understand the purpose of icons, UI components, etc. 

Hence, we should provide a way for them to programmatically determine the website elements. This helps user agents such as Web browsers, media players, plug-ins, and other programs retrieve and render content as desired by the user. 

How do we fix it?

  • Make sure that the content implemented using markup languages can be programmatically determined
  • Use ARIA landmarks to markup regions so that AT can identify them
  • Use microdata to markup UI components so that AT can identify them

Aditya Bikkani

Aditya Bikkani

Aditya is the COO of AELData, a growing technology company in the Digital Publishing and Education sectors. He is also an entrepreneur and founder of an accessibility tool called LERA. A W3C COGA (Cognitive and Learning Disabilities Accessibility) Community Member Aditya contributes to researching methodologies to improve web accessibility and usability for people with cognitive and learning disabilities.

Leave a Reply

Your email address will not be published. Required fields are marked *

Share on Social Media

Facebook
Twitter
LinkedIn
Email
Pinterest
Reddit
WhatsApp

Related Blogs

Skip to content