# WCAG 2.2 Source: https://ordergroup.co/glossary/wcag-2-2/ Last updated: 2026-10-10 > WCAG 2.2 for teams ordering an app - success criteria and levels, what is new since 2.1, EN 301 549, the EAA, Polish law and accepting the work. [AI](https://ordergroup.co/glossary/ai/)[Accessibility](https://ordergroup.co/glossary/accessibility/) 7 min read # WCAG 2.2 Web Content Accessibility Guidelines 2.2 Also known as: WCAG, Web Content Accessibility Guidelines, WCAG AAA, WCAG 2.2 AA Definition WCAG 2.2 is the W3C standard for accessible web content. It sets 86 testable success criteria at three levels, A, AA and AAA. Content that meets WCAG 2.2 also meets 2.1, the version that EU and Polish rules for websites and apps point to at level AA. Cite this entry Text "WCAG 2.2". Order Group, Software glossary, 10 October 2026. https://ordergroup.co/glossary/wcag-2-2/ HTML `WCAG 2.2 - Order Group` Reviewed by [Daria Gusieva](https://ordergroup.co/authors/daria-gusieva/), Head of Design Last reviewed 10 October 2026 ## How WCAG 2.2 works The Web Content Accessibility Guidelines are published by the W3C. Version 2.2 was first published on October 5, 2023, and republished with corrections on December 12, 2024. The structure has three layers: four principles (perceivable, operable, understandable and robust), guidelines under each principle, and success criteria under each guideline. The success criteria are what a buyer can check. W3C writes them as testable statements that do not depend on a particular technology. Every success criterion has a level. In WCAG 2.2 there are 31 criteria at level A, 24 at AA and 31 at AAA, 86 in total. Conformance at a level means meeting every criterion at that level and all levels below it, so AA means all 55 criteria at A and AA. Conformance applies to full pages only and cannot be claimed if part of a page is excluded. When a page is one step in a process, such as a checkout or an application form, every page in that process has to conform. WCAG 2.2 builds on 2.1 and is backward compatible: content that conforms to WCAG 2.2 also conforms to WCAG 2.0 and 2.1. It adds nine success criteria and removes one, 4.1.1 Parsing, now marked obsolete. The W3C names users with cognitive or learning disabilities, users with low vision and users with disabilities on mobile devices as the groups this version focuses on. In practice, a control must stay at least partly visible when it receives keyboard focus, pointer targets must be at least 24 by 24 CSS pixels unless an exception applies, anything done by dragging must also work with a single pointer, and login must not depend on a cognitive function test, such as remembering a password, unless there is an alternative or a mechanism that helps. For level AAA, the W3C states that it is not recommended that Level AAA conformance be required as a general policy for entire sites, because some content cannot satisfy all AAA criteria. Two examples are 1.4.6 Contrast (Enhanced), which raises the text contrast ratio from 4.5:1 to 7:1, and 3.1.5 Reading Level, which asks for a simpler version of text that needs more than lower secondary reading ability. The [easy-to-read](https://ordergroup.co/glossary/easy-to-read/) entry covers that criterion in detail. Success criteria added in WCAG 2.2 CriterionLevelWhat changes in the app 2.4.11 Focus Not Obscured (Minimum)AASticky headers, banners and chat widgets must not fully hide the focused control2.4.12 Focus Not Obscured (Enhanced)AAANo part of the focused control may be hidden2.4.13 Focus AppearanceAAAThe focus indicator is at least as large as a 2 CSS pixel thick perimeter of the control and has 3:1 contrast2.5.7 Dragging MovementsAASliders, reordering and maps also work with taps or clicks2.5.8 Target Size (Minimum)AAButtons and links of at least 24 by 24 CSS pixels, or enough spacing3.2.6 Consistent HelpAHelp and contact links repeated across pages appear in the same order3.3.7 Redundant EntryAData given earlier in the process is filled in or offered for selection3.3.8 Accessible Authentication (Minimum)AANo password memory test without an alternative or a helping mechanism3.3.9 Accessible Authentication (Enhanced)AAAStricter version of 3.3.8 ## What WCAG 2.2 means for your software For a public body or a company covered by the European Accessibility Act, WCAG is the yardstick at acceptance. A contract that says "accessible" or "WCAG compliant" without a version and a level cannot be tested. Requirements for an app you are ordering: - The contract names the version, the level and the scope: WCAG 2.2 at AA, for example, for the web app, the mobile apps and the documents the system generates. EN 301 549 covers non-web documents and software in separate clauses, so exports such as DOCX or PDF need their own checks. - If you want AAA, list the AAA criteria you mean, for example 7:1 contrast or a simpler version of difficult text, instead of all 31 AAA criteria on every screen. - Every requirement in the backlog carries the number of the success criterion it serves, and every criterion has a test the buyer can run at acceptance. - Screen reader labels, error messages and status messages are content. Keep them in one catalog, write them in plain language and review them like any other text. WCAG 4.1.3 requires status messages to reach assistive technology without moving focus. - Testing combines tools and people. Automatic checkers find missing labels and low contrast. Keyboard-only navigation, screen readers on each platform and zoom to 200% need a person. - The new 2.2 criteria change design early: target sizes, sticky headers that hide the focused field, dragging alternatives, help links kept in the same order across pages, no re-entering data already given in the same process, and login without a memory test. - If the system generates text with AI, the output is content too. Reading level, structure and labels apply to it, and the checks belong in the [evaluation](https://ordergroup.co/glossary/llm-evaluation/) of the model. - Acceptance ends with a report and a retest. In Poland, a public body also has to publish an accessibility statement for every language version of its site or app. Writing the specification? Add WCAG 2.2 to your requirements checklist Collect the terms your project touches and get their system requirements in one e-mail, ready for an RFP. WCAG 2.2 levels and what they mean in a contract LevelCriteria in WCAG 2.2ExamplesWhen it is required A311.1.1 Non-text Content, 2.1.1 Keyboard, 3.3.7 Redundant EntryAlways part of a conformance claimAA241.4.3 Contrast 4.5:1, 1.4.4 Resize Text to 200%, 2.5.8 Target Size 24 by 24 CSS pixels, 3.3.8 Accessible AuthenticationThe level that EN 301 549 and Polish public sector law use, through WCAG 2.1AAA311.4.6 Contrast 7:1, 2.4.13 Focus Appearance, 3.1.5 Reading LevelOnly for criteria named in the contract; W3C advises against requiring all of AAA ## Rules and standards EN 301 549 is the European standard for the accessibility of ICT products and services. Version V3.2.1 (2021-03) is the harmonized standard under the Web Accessibility Directive, Directive (EU) 2016/2102, which covers public sector websites and apps; Commission Implementing Decision (EU) 2021/1339 cites it. Its clause 9 covers web content and states that conformance with WCAG 2.1 at level AA is equivalent to meeting clauses 9.1 to 9.4 and the conformance requirements of clause 9.6. Clause 10 covers non-web documents and clause 11 covers software, including mobile apps. Version V4.1.1 (2026-09), adopted on August 24, 2026, aligns clauses 9, 10 and 11 with WCAG 2.2 and was prepared for the European Accessibility Act. The standard itself states that it gives a presumption of conformity under that act once it is cited in the Official Journal of the EU. The European Accessibility Act, Directive (EU) 2019/882, applies to listed products placed on the market and services provided to consumers after June 28, 2025. The services include e-commerce, consumer banking, e-books, electronic communications and elements of passenger transport. Under its Annex I, services must make their websites, related online applications and mobile services accessible by making them perceivable, operable, understandable and robust. Products and services that meet published harmonized standards are presumed to conform. Microenterprises providing services are exempt. In Poland, public bodies follow the 2019 Act on digital accessibility of websites and mobile applications of public bodies (ustawa o dostępności cyfrowej stron internetowych i aplikacji mobilnych podmiotów publicznych). Its annex lists the WCAG 2.1 success criteria at levels A and AA, and the requirements are deemed met when a body satisfies clauses 9, 10 and 11 of the Polish standard implementing EN 301 549 V3.2.1. Article 10 requires an accessibility statement (deklaracja dostępności) for every language version of a website or app. Companies fall under the Act of April 26, 2024, which implements the European Accessibility Act in Poland and has applied since June 28, 2025, except to services provided by microenterprises. ## From our projects For PSONI we are building Generator ETR, an app that turns documents into [easy-to-read](https://ordergroup.co/glossary/easy-to-read/) Polish. The project specification requires WCAG 2.2 level AAA. The W3C advice against AAA is about whole sites as a general policy; here the users are people with intellectual disabilities and the app has a narrow set of screens and content. The requirements list ties items to success criteria. An error message must say what to do, not only what is wrong, ideally with an example (3.3.3 Error Suggestion). Deleting a document needs a confirmation dialog with the default focus on Cancel (3.3.4 Error Prevention). Every icon needs a visible text label (1.1.1 requires a text alternative; the visible label follows the W3C cognitive accessibility guidance). Testing in June 2026 found that text over the length limit only changed color and the character counter, while the submit button went gray with no explanation. We added a validation message next to the counter, and the retest passed in September 2026. The missing delete confirmation was fixed and passed its retest on September 21, 2026. In September and October 2026 we adapted the web and mobile apps for screen readers and collected every ARIA label in one sheet, which also serves as the catalog of error and status messages. The first tests on the web found text that was not read at all or read character by character, Tab focus that skipped the page heading and document titles, and loading states that were never announced. The tester recommended verification by the client, and fixes from the web screen reader report are a separate open task. On October 1, 2026, the scope of text settings was narrowed to three font sizes, 100%, 150% and 200%, which covers the 200% that 1.4.4 Resize Text names; layout at 200% still has to be tested. The settings also include a male or female voice and reading speed for text-to-speech. Typeface, spacing, margins and per-document settings were left out. DOCX is the only export format, so the generated file gets its own accessibility test of headings, lists, bold text and screen reader reading; in October 2026 that test is in progress. ## Related terms - [Accessibility audit](https://ordergroup.co/glossary/accessibility-audit/) Accessibility audit (WCAG audit) An accessibility audit is a structured check of a website or app against a standard, usually WCAG 2.1 or 2.2 at level AA. It combines automated scans with manual testing by keyboard and screen reader, and ends with a report that lists each failed success criterion, where it fails and how to fix it. - [Easy-to-read (ETR)](https://ordergroup.co/glossary/easy-to-read/) Easy-to-read Easy-to-read (ETR) is a way of writing information so that people with intellectual disabilities can understand it, with everyday words, short sentences and one idea per line, checked by readers from that group. Inclusion Europe publishes the European standard. - [Focus management](https://ordergroup.co/glossary/focus-management/) Focus management (keyboard and screen reader focus) Focus management is how an app decides which element receives keyboard or screen reader focus when the screen changes: after navigation, when a dialog opens or closes, or when an error appears. Done right, the user always knows where they are and cannot reach controls that are hidden. - [LLM evaluation](https://ordergroup.co/glossary/llm-evaluation/) LLM evaluation is the systematic testing of a language model's outputs on a fixed set of inputs against agreed acceptance criteria, using automatic checks, model-based grading and human review. It decides whether a model, prompt or version is good enough to ship. - [Screen reader testing](https://ordergroup.co/glossary/screen-reader-testing/) Screen reader testing (VoiceOver, TalkBack, NVDA) Screen reader testing checks an app or website with VoiceOver, TalkBack, NVDA or another reader that blind and low-vision people use to hear the interface. A tester goes through every screen and checks what is announced, in what order, and whether every task can be finished. ## Sources 1. [Web Content Accessibility Guidelines (WCAG) 2.2](https://www.w3.org/TR/WCAG22/) - W3C 2. [EN 301 549 V3.2.1 (2021-03) Accessibility requirements for ICT products and services](https://www.etsi.org/deliver/etsi_en/301500_301599/301549/03.02.01_60/en_301549v030201p.pdf) - ETSI CEN CENELEC 3. [EN 301 549 V4.1.1 (2026-09) Accessibility requirements for ICT products and services](https://www.etsi.org/deliver/etsi_en/301500_301599/301549/04.01.01_60/en_301549v040101p.pdf) - ETSI CEN CENELEC 4. [Commission Implementing Decision (EU) 2021/1339 (harmonised standard for Directive (EU) 2016/2102)](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32021D1339) - EUR-Lex 5. [Directive (EU) 2019/882 on the accessibility requirements for products and services (European Accessibility Act)](https://eur-lex.europa.eu/eli/dir/2019/882/oj/eng) - EUR-Lex 6. [Ustawa z dnia 4 kwietnia 2019 r. o dostępności cyfrowej stron internetowych i aplikacji mobilnych podmiotów publicznych, tekst jednolity Dz.U. 2023 poz. 1440](https://eli.gov.pl/eli/DU/2023/1440/ogl/pol/pdf) - Dziennik Ustaw 7. [Ustawa z dnia 26 kwietnia 2024 r. o zapewnianiu spełniania wymagań dostępności niektórych produktów i usług przez podmioty gospodarcze, Dz.U. 2024 poz. 731](https://eli.gov.pl/eli/DU/2024/731/ogl/pol/pdf) - Dziennik Ustaw Daria Gusieva reviewed this entry. Ask how it applies to your project. [Ask an engineer](https://ordergroup.co/contact-us/) ## FAQ ![Daria Gusieva](https://ordergroup.co/media/images/T02DHCC1Z-U0B48S6GQTV-7fae05753481-512.format-webp.webp) Daria Gusieva Head of Design [Talk to an engineer](https://ordergroup.co/contact-us/) ### What is the difference between WCAG 2.1 and WCAG 2.2? WCAG 2.2 adds nine success criteria, aimed mainly at users with cognitive or learning disabilities, low vision and disabilities on mobile devices, and removes 4.1.1 Parsing. Content that conforms to 2.2 also conforms to 2.1, so building to 2.2 also covers rules that cite 2.1, apart from 4.1.1 Parsing where those rules still list it. ### Should we require WCAG AAA in the contract? Not as a blanket rule. The W3C does not recommend requiring AAA for entire sites, because some content cannot meet every AAA criterion. Name the AAA criteria that matter for your users, such as 7:1 contrast or a simpler version of difficult text. ### Does WCAG apply to mobile apps? WCAG is written for web content, but EN 301 549 applies its criteria to non-web software in clause 11, and Polish law for public bodies covers mobile apps explicitly. Treat the mobile app as part of the scope from the start. ### Is an automated accessibility scan enough to accept the app? No. Scanners catch missing labels and low contrast, but keyboard navigation, screen reader output, focus order and the clarity of messages need manual testing on each platform. ### Which WCAG version does the law require? EN 301 549 V3.2.1 and the Polish act for public bodies point to WCAG 2.1 at level AA. Conforming to WCAG 2.2 at AA satisfies that, except 4.1.1 Parsing, which those texts still list, and adds the newer criteria. EN 301 549 V4.1.1 moves to WCAG 2.2. Building a system that depends on WCAG 2.2? See how we build software for this domain, with case studies and the stack we use. [See AI Software Development Services](https://ordergroup.co/ai-software-development/) Requirements checklist For each term we send the definition and what it requires from your software. Free, no sales call needed. Your checklist is empty. Use the plus next to a term to add it.