{"id":7557,"date":"2025-04-07T09:15:31","date_gmt":"2025-04-07T08:15:31","guid":{"rendered":"https:\/\/lawwwing.com\/?p=7557"},"modified":"2025-04-07T12:41:28","modified_gmt":"2025-04-07T11:41:28","slug":"wcag-2-2-what-you-need-to-know","status":"publish","type":"post","link":"https:\/\/lawwwing.com\/en\/wcag-2-2-what-you-need-to-know\/","title":{"rendered":"WCAG 2.2: What you need to know"},"content":{"rendered":"\n<p>In today\u2019s digital age, ensuring that web content is accessible to everyone\u2014regardless of their abilities or disabilities\u2014is no longer just a best practice: it\u2019s a necessity. The <strong>Web Content Accessibility Guidelines (WCAG)<\/strong> are the international standard developed to achieve this goal.<\/p>\n\n\n\n<p>The most recent version, <strong>WCAG 2.2<\/strong>, published in October 2023, introduces significant improvements aimed at expanding <strong>inclusion in digital environments<\/strong>. In this article, we explain what WCAG 2.2 is, why it\u2019s important, what\u2019s new, and how you can start applying it.<\/p>\n\n\n\n<div style=\"height:40px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<h2 class=\"wp-block-heading\">What is WCAG 2.2?<\/h2>\n\n\n\n<p><a href=\"https:\/\/www.w3.org\/TR\/WCAG22\/\" data-type=\"link\" data-id=\"https:\/\/www.w3.org\/TR\/WCAG22\/\" target=\"_blank\" rel=\"noreferrer noopener\"><strong>WCAG 2.2<\/strong> <\/a>is a set of technical guidelines developed by the <strong><a href=\"https:\/\/www.w3.org\/\" target=\"_blank\" rel=\"noreferrer noopener\">World Wide Web Consortium (W3C)<\/a><\/strong>\u2014an international organization based in the United States that develops the standards that ensure the web continues to grow and function in an accessible way for all.<\/p>\n\n\n\n<p>Its goal is to make digital content: such as websites, mobile apps, or interactive platforms, <strong>accessible to everyone<\/strong>, including people with disabilities, older adults, or those who may face challenges when interacting with digital environments.<\/p>\n\n\n\n<p>These guidelines provide detailed criteria to ensure that information is <strong>perceivable, operable, understandable, and robust<\/strong>.<\/p>\n\n\n\n<p>They are based on four key principles:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Perceivable<\/strong>: Information must be presented in a way that users can perceive it, such as by including alternative text for images.<\/li>\n\n\n\n<li><strong>Operable<\/strong>: Users must be able to navigate the website, even if they only use a keyboard.<\/li>\n\n\n\n<li><strong>Understandable<\/strong>: Content should be clear, consistent, and easy to follow.<\/li>\n\n\n\n<li><strong>Robust<\/strong>: The website must be able to function properly across different browsers and assistive technologies.<\/li>\n<\/ol>\n\n\n\n<p>Version 2.2, released in October 2023, builds on previous versions (2.0 and 2.1), incorporating new recommendations focused on <strong>improving the experience for users with cognitive or mobility-related disabilities<\/strong>, as well as those using mobile devices.<\/p>\n\n\n\n<div style=\"height:40px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<h2 class=\"wp-block-heading\">What\u2019s new in WCAG 2.2?<\/h2>\n\n\n\n<p>WCAG 2.2 adds <strong>nine new success criteria<\/strong>, many of which are designed to make it <strong>easier for users to navigate and interact<\/strong> with digital content, especially on mobile devices or for individuals with cognitive or physical challenges. A few notable examples include:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Focus Not Obscured (2.4.11 \u2013 Level AA)<\/strong>:When an element receives keyboard focus (for example, when navigating with the tab key), it must be visible to the user. In other words, nothing should cover it or prevent it from being seen.<\/li>\n\n\n\n<li><strong>Dragging Movements (2.5.7 \u2013 Level AA)<\/strong>:There must be an alternative to complex gestures like dragging with a finger (drag and drop), which can be difficult for people with limited mobility.<\/li>\n\n\n\n<li><strong>Redundant Entry (3.3.7 \u2013 Level A)<\/strong>:The site should not require users to enter the same information more than once during a process, such as filling out a form or completing a registration. This helps reduce the cognitive load for many users.<\/li>\n<\/ol>\n\n\n\n<div style=\"height:40px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<h2 class=\"wp-block-heading\">Legal situation in Spain: Is it mandatory to comply with WCAG 2.2?<\/h2>\n\n\n\n<p>Although WCAG guidelines do not have the force of law on their own, as they are issued by a private organization, their adoption as a technical standard is widely recognized internationally.<\/p>\n\n\n\n<p>In the European context, and specifically in Spain, the new<a href=\"https:\/\/www.boe.es\/eli\/es\/l\/2023\/05\/08\/11\" data-type=\"link\" data-id=\"https:\/\/www.boe.es\/eli\/es\/l\/2023\/05\/08\/11\" target=\"_blank\" rel=\"noreferrer noopener\"> <strong>Law 11\/2023<\/strong><\/a>\u2014commonly referred to as the <strong>\"Accessibility Law\"<\/strong>\u2014sets out clear accessibility obligations for private companies that offer products or services online, aligning with <strong>EU Directive 2019\/882<\/strong>. This law requires that, as of <strong>28 June 2025<\/strong>, all new websites and apps comply with accessibility criteria, and that <strong>existing services be adapted before 2030.<\/strong><\/p>\n\n\n\n<h6 class=\"wp-block-heading\">Law 11\/2023 on accessibility<\/h6>\n\n\n\n<p>Although the law does not specifically mention <strong>WCAG 2.2<\/strong>, it does refer to technical standards such as:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>UNE 139803<\/strong>, the Spanish standard for accessible web content.<\/li>\n\n\n\n<li><strong>EN 301 549<\/strong>, the European standard that is already aligned with WCAG 2.1 and is expected to be updated to incorporate WCAG 2.2.<\/li>\n<\/ul>\n\n\n\n<p>This set of European requirements, which is currently aligned with WCAG 2.1, will likely be updated to reflect version 2.2.<\/p>\n\n\n\n<div style=\"height:40px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<h2 class=\"wp-block-heading\">Why is it important to comply with WCAG?<\/h2>\n\n\n\n<p>Adapting your website or app to accessibility guidelines brings both legal and practical benefits:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Ensures compliance<\/strong> with regulations and prevents potential fines<\/li>\n\n\n\n<li><strong>Expands your reach<\/strong> to new audiences<\/li>\n\n\n\n<li><strong>Improves SEO <\/strong>and visibility<\/li>\n\n\n\n<li><strong>Strengthens your brand image<\/strong> as an inclusive company<\/li>\n\n\n\n<li>I<strong>ncreases conversion rates in key processes <\/strong>(sign-ups, purchases, contact forms)<\/li>\n<\/ul>\n\n\n\n<div style=\"height:40px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<h2 class=\"wp-block-heading\">How to start adapting to WCAG 2.2<\/h2>\n\n\n\n<p>You don\u2019t need to rebuild your entire website from scratch or be an accessibility expert. Here are some practical steps to get started:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Evaluate your website<\/strong>: Use tools like <strong><a href=\"https:\/\/lawwwing.com\/?_gl=1%2Afyrvgv%2A_up%2AMQ..%2A_ga%2AMTIwMjE2NzMwNy4xNzQzNzY0NDQz%2A_ga_PVQTMLESR8%2AMTc0Mzc2NDQ0My4xLjEuMTc0Mzc2NDQ1Ny4wLjAuMA..\" data-type=\"link\" data-id=\"https:\/\/lawwwing.com\/?_gl=1%2Afyrvgv%2A_up%2AMQ..%2A_ga%2AMTIwMjE2NzMwNy4xNzQzNzY0NDQz%2A_ga_PVQTMLESR8%2AMTc0Mzc2NDQ0My4xLjEuMTc0Mzc2NDQ1Ny4wLjAuMA..\" target=\"_blank\" rel=\"noreferrer noopener\">Lawwwing<\/a><\/strong> to identify the most obvious errors.<\/li>\n\n\n\n<li><strong>Prioritize the essentials<\/strong>: Start with key pages (home, contact, registration, forms\u2026) and fix high-impact issues such as missing labels, low contrast, inaccessible buttons, etc.<\/li>\n\n\n\n<li><strong>Make small, visible improvements<\/strong>: Add alt text to images, increase color contrast, improve text size and legibility, and ensure everything can be done using only a keyboard.<\/li>\n\n\n\n<li><strong>Get your team involved<\/strong>: Designers, content creators, and developers should follow a shared accessibilty guide to avoid inconsistencies and new errors.<\/li>\n\n\n\n<li><strong>Test with real users<\/strong>: If possible, have people who use assistive technologies or who have different abilities test your site. Their feedback is the most reliable way to know if your website is truly accessible.<\/li>\n\n\n\n<li><strong>Document and train<\/strong>: Keep an internal guide of best practices to ensure that new content or future updates maintain your accessibility standards.<\/li>\n<\/ul>\n\n\n\n<div style=\"height:40px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<h2 class=\"wp-block-heading\">Conclusion<\/h2>\n\n\n\n<p><strong>Digital accessibility is no longer optional.<\/strong> Adapting to WCAG 2.2 <strong>not only improves the experience for all users<\/strong>, it also prepares your business for the legal changes ahead. The sooner you start, the easier it will be to meet the June 2025 deadline and offer a truly inclusive digital experience.<\/p>\n\n\n\n<p>Making your website accessible doesn\u2019t mean making it more complex. It means making it <strong>clearer, more usable, and more human<\/strong>. And that benefits everyone.<\/p>\n\n\n\n<p>Do you have questions about whether your website is compliant? Do you need help getting up to date with the regulations?<\/p>\n\n\n\n<p>We\u2019re here to help from <strong>Lawwwing.<\/strong><\/p>\n","protected":false},"excerpt":{"rendered":"<p>A clear and up-to-date guide to understanding the new digital accessibility guidelines.<\/p>\n","protected":false},"author":9,"featured_media":7645,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"content-type":"","inline_featured_image":false,"footnotes":""},"categories":[326,464,494,501,508],"tags":[360,504,509,510,511],"class_list":["post-7557","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-legislacion-web-en","category-tecnology","category-lawwwing-2","category-accesibility","category-website","tag-2025-2","tag-accesibility","tag-website","tag-wcag","tag-technology"],"acf":[],"_links":{"self":[{"href":"https:\/\/lawwwing.com\/en\/wp-json\/wp\/v2\/posts\/7557","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/lawwwing.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/lawwwing.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/lawwwing.com\/en\/wp-json\/wp\/v2\/users\/9"}],"replies":[{"embeddable":true,"href":"https:\/\/lawwwing.com\/en\/wp-json\/wp\/v2\/comments?post=7557"}],"version-history":[{"count":5,"href":"https:\/\/lawwwing.com\/en\/wp-json\/wp\/v2\/posts\/7557\/revisions"}],"predecessor-version":[{"id":7590,"href":"https:\/\/lawwwing.com\/en\/wp-json\/wp\/v2\/posts\/7557\/revisions\/7590"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/lawwwing.com\/en\/wp-json\/wp\/v2\/media\/7645"}],"wp:attachment":[{"href":"https:\/\/lawwwing.com\/en\/wp-json\/wp\/v2\/media?parent=7557"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/lawwwing.com\/en\/wp-json\/wp\/v2\/categories?post=7557"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/lawwwing.com\/en\/wp-json\/wp\/v2\/tags?post=7557"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}