Parsing was all about ensuring that code was clean and consistent enough for user agents—like browsers and assistive technologies—to process it without breaking.
What happened to Parsing?
In WCAG 2.2, Parsing was officially removed and retroactively set to “always passes” under WCAG 2.1. Why? Modern browsers and tools have become much better at handling messy or imperfect code, making this criterion less relevant for today’s web. Think of it as the ROBUST principle in action: technology evolved to bridge the gap Parsing once filled.
Why this matters
While Parsing may be gone, the spirit of it remains. Writing clean, valid code is still best practice—it supports better performance, reduces errors, and ensures compatibility with assistive technologies.
Top tips (for developers who still care)
- Use semantic HTML: Even if Parsing is no longer a requirement, semantic code improves accessibility and user experience.
- Test with assistive technologies: Make sure screen readers and other tools can navigate your site as intended.
- Embrace the ROBUST principle: Focus on creating resilient code that works across diverse platforms and devices.