Parsing (Obsolete)
Disclaimer:
Please note, as of the WCAG 2.2 this criterion is obsolete. Initially, it addressed the challenges assistive technologies faced with HTML parsing. However, advancements in technology have mitigated these issues, and any remaining concerns are now addressed by other criteria. Consequently, 4.1.1 has been phased out by W3C.
Summary:
WCAG criterion 4.1.1 is all about making sure the code behind your web content plays nicely with assistive technologies like screen readers. This criterion is fairly broad.
What:
The 4.1.1 guideline, titled "Parsing," focuses on the need for web content to have correct syntax so assistive technologies can accurately interpret and present the content to users. It mandates that elements have complete start and end tags, elements are nested according to their specifications, and IDs are unique unless the specifications allow for duplicates. Basically, write good code.
Why:
Assistive technologies rely on the underlying code structure to present content to users with disabilities. If the code is messy or incorrect, it can lead to content being misinterpreted or inaccessible, creating barriers for users who rely on these technologies to navigate the web.
Examples and Scenarios:
- A webpage with broken HTML: If a webpage's HTML is not properly structured (e.g., missing end tags or incorrectly nested elements), screen readers might skip over content or read it in the wrong order.
- Forms with duplicate IDs: Forms that use the same ID for multiple elements can confuse assistive technologies, leading to incorrect field descriptions being read out.
- Navigation menus with improper structure: If a navigation menu is coded incorrectly, it might not be accessible through keyboard navigation, making it difficult for users who cannot use a mouse to navigate the site.
How to Comply:
- Web: Use validators to check your HTML/CSS for errors. Ensure your code follows the specifications for properly nested tags and unique IDs.
- Mobile apps (iOS/Android): Although 4.1.1 specifically addresses web content, the principle of clean, accessible code applies. Use the respective platform's accessibility tools and guidelines to ensure your app's components are accessible.