![\"Adrian](\"https:\/\/html5accessibility.com\/stuff\/wp-content\/uploads\/2026\/01\/IMG_1526.jpg\")
<\/p>\n<\/p>\n
2026 is upon us and the work of the W3C Accessibility Guidelines Working Group<\/a> (AGWG) continues…<\/p>\n From reading the draft minutes for the AGWG meeting 13th January<\/a> 2026, there is skepticism about the working groups ability to get WCAG3 to Candidate Recommendation status (CR) within 4 years<\/p>\n CR does not mean that WCAG3 is finished<\/strong><\/p>\n Wilco said<\/a>:<\/strong><\/p>\n \u00a0Timeline concerns me more. To be able to get to Candidate Rec within 4 years, I’d sign up for that but I don’t buy it. Most of work is still ahead of us.<\/strong> So many edge cases and exceptions to write. I don’t see how this will be done in the timeline proposed and there’s barely a timeline.<\/p><\/blockquote>\n If<\/strong><\/em> the WCAG3 timeline is 4 years<\/strong> to W3C Candidate Recommendation<\/a><\/p>\n A Candidate Recommendation is a document that satisfies the technical requirements of the Working Group that produced it and their dependencies, and has already received wide review. W3C publishes a Candidate Recommendation to<\/p>\n So in 2030.<\/strong><\/p>\n Is a Candidate Recommendation endorsed by the W3C?<\/strong><\/p>\n NO<\/strong><\/a><\/p>\n In 2030 WCAG3 will be at the stage before becoming a W3C Recommendation<\/a>. I expect it to be a further year or so for it to become a fully fledged W3C Recommendation…<\/p>\nWCAG3 – 4 MORE YEARS?<\/h2>\n
\n
In the year 2031…<\/h2>\n
Mirror in the bathroom<\/h2>\n