Guide pratiche per i criteri di successo WCAG. Ogni articolo spiega la regola, perché è importante per gli utenti, come verificarla e i passaggi tipici di correzione — ottimizzato per i team che creano siti accessibili con accsible.
90 / 90
WCAG 1.1.1 requires that all non-text content — images, icons, controls, and media — has a text alternative that conveys the same purpose or information, enabling users who cannot perceive visual content to access it through assistive technologies such as screen readers.
WCAG 1.2.1 requires that prerecorded audio-only and video-only content have a text-based or media alternative so users who cannot hear or see the media can still access the information. This is a Level A requirement, meaning it is the minimum baseline for web accessibility compliance.
WCAG 1.2.2 requires that all prerecorded audio content in synchronized media (video with audio) includes accurate captions. This ensures deaf and hard-of-hearing users can access spoken dialogue, sound effects, and other meaningful audio information.
WCAG 1.2.3 requires that prerecorded synchronized media (video with audio) provides either an audio description of the visual content or a full text alternative, ensuring users who are blind or have low vision can access information conveyed visually.
WCAG 1.3.1 requires that information, structure, and relationships conveyed through visual presentation can also be determined programmatically or are available in text, ensuring that users of assistive technologies receive the same structural context as sighted users.
WCAG 1.3.2 requires that when the order of content affects its meaning, that sequence must be determinable programmatically so assistive technologies can present it correctly. Failing this criterion causes screen reader users and other AT users to receive content in a confusing or meaningless order.
WCAG 1.3.3 requires that instructions for using content do not rely solely on sensory characteristics such as shape, color, size, visual location, orientation, or sound. This ensures that users who cannot perceive those sensory cues — due to blindness, color blindness, deafness, or other disabilities — can still understand and operate all features.
WCAG 1.4.1 requires that color is never the sole means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. This criterion ensures users who cannot perceive color differences—including people with color blindness or low vision—can still access all content and functionality.
WCAG 1.4.2 requires that any audio playing automatically for more than three seconds must offer users a mechanism to pause, stop, or control its volume independently of the system volume. This prevents audio from interfering with screen reader output and protects users from unexpected, disorienting sound.
WCAG 2.1.1 requires that all functionality available through a mouse or pointer is equally operable via a keyboard alone, with no specific timing required for keystrokes. This criterion is foundational for users who cannot use a mouse, ensuring they can navigate, interact with, and complete tasks on any website or application.
WCAG 2.1.2 requires that keyboard users are never trapped inside a component — if focus can be moved into a UI element using a keyboard, it must also be possible to move focus away using only the keyboard. This criterion is essential for users who rely exclusively on keyboard navigation, including people with motor disabilities and screen reader users.
WCAG 2.1.4 requires that any keyboard shortcut implemented using only a single character key (letter, number, punctuation, or symbol) can be turned off, remapped, or activated only on focus — preventing accidental triggers that harm users who rely on speech input or have motor disabilities.
WCAG 2.2.1 requires that any time limit set by content can be turned off, adjusted, or extended by the user — ensuring people who need more time to interact with web content are not locked out. This Level A criterion is essential for users with motor, cognitive, and visual disabilities.
WCAG 2.2.2 requires that moving, blinking, scrolling, or auto-updating content can be paused, stopped, or hidden by users. This protects people with cognitive disabilities, vestibular disorders, and attention-related conditions from content they cannot control.
WCAG 2.3.1 requires that web content does not contain anything that flashes more than three times per second, unless the flash is below general or red flash thresholds. This criterion is critical for preventing seizures and physical reactions in users with photosensitive epilepsy or similar neurological conditions.
WCAG 2.4.1 requires that web pages provide a mechanism to skip repeated blocks of content, such as navigation menus, so keyboard and assistive technology users can reach main content without tabbing through every link. This is a Level A requirement, meaning it is the baseline for accessible keyboard navigation.
WCAG 2.4.2 requires that every web page has a descriptive, meaningful title that identifies its topic or purpose. This ensures users — especially those relying on screen readers or managing multiple tabs — can quickly orient themselves and navigate efficiently.
WCAG 2.4.3 requires that if a web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components must receive focus in an order that preserves meaning and operability. This criterion is essential for keyboard and assistive technology users who rely on a logical, predictable focus sequence to understand and interact with content.
WCAG 2.4.4 requires that the purpose of every link can be determined from the link text alone, or from the link text together with its surrounding context. This ensures that screen reader users, keyboard-only users, and people with cognitive disabilities can understand where a link leads without needing to follow it.
WCAG 2.5.1 requires that all functionality using multipoint or path-based gestures (such as pinch-to-zoom or swipe) can also be operated with a single pointer without a path-based gesture, unless the gesture is essential. This protects users with motor impairments who cannot reliably perform complex touch gestures.
WCAG 2.5.2 requires that functionality triggered by a single pointer (mouse, touch, or stylus) can be cancelled or reversed, preventing accidental activations. This protects users with motor impairments who may tap or click unintentionally.
WCAG 2.5.3 requires that interactive components with visible text labels have an accessible name that contains the visible text, ensuring speech input users can activate controls by speaking what they see. Mismatches between visible labels and accessible names break voice control navigation and undermine trust for millions of users.
WCAG 2.5.4 requires that any functionality triggered by device or user motion (such as shaking or tilting) must also be operable through conventional user interface components, and users must be able to disable motion actuation to prevent accidental activation.
WCAG 3.1.1 requires that the default human language of each web page can be programmatically determined, primarily by setting a valid lang attribute on the HTML element. This enables assistive technologies like screen readers to pronounce content correctly and helps users with cognitive and language-based disabilities understand the page.
WCAG 3.2.1 On Focus requires that when any user interface component receives keyboard focus, it must not trigger an unexpected change of context. This protects keyboard and assistive technology users from disorienting, unpredictable behavior that can make a page impossible to navigate effectively.
WCAG 3.2.2 On Input requires that changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of that behavior beforehand. This protects users from disorienting, unexpected page changes triggered by form interactions.
WCAG 3.3.1 requires that when an input error is automatically detected, the item in error is identified and the error is described to the user in text. This ensures users with disabilities can recognize, understand, and correct mistakes when filling out forms.
WCAG 3.3.2 requires that labels or instructions are provided when content requires user input, ensuring that all users — regardless of ability — can understand what is expected of them before submitting form data. Failing to label form fields is one of the most common and impactful accessibility barriers on the web.
WCAG 3.3.7 requires that information users have already provided in a multi-step process is either auto-populated or made available for selection, so users never have to re-enter the same data twice. This prevents frustration and errors for users with cognitive, motor, or other disabilities.
WCAG 4.1.2 requires that all user interface components have a programmatically determinable name and role, and that states, properties, and values can be both read and set by assistive technologies. This ensures screen readers and other tools can accurately identify, describe, and interact with every element on the page.
WCAG 1.2.4 requires that all live audio content in synchronized media—such as webinars, live streams, and broadcasts—be accompanied by real-time captions. This ensures that deaf and hard-of-hearing users can access spoken content as it happens, in real time.
WCAG 1.2.5 requires that audio description is provided for all prerecorded video content in synchronized media, ensuring that users who are blind or have low vision can access visual information that is not conveyed through the audio track alone.
WCAG 1.3.4 Orientation requires that content does not restrict its view and operation to a single display orientation, such as portrait or landscape, unless a specific orientation is essential. This criterion ensures users who cannot physically rotate their devices—such as those with mounted tablets or motor impairments—can still access all content.
WCAG 1.3.5 requires that the purpose of each input field collecting personal information can be programmatically determined, enabling browsers and assistive technologies to autofill, label, or adapt fields automatically. This is essential for users with cognitive disabilities and motor impairments who benefit from reduced manual input.
WCAG 1.4.3 requires that text and images of text have a contrast ratio of at least 4.5:1 against their background (3:1 for large text), ensuring that users with low vision or color deficiencies can read content without assistive technology.
WCAG 1.4.4 requires that text can be resized up to 200% without assistive technology and without loss of content or functionality. This criterion is essential for users with low vision who rely on browser zoom or custom font-size settings to read web content comfortably.
WCAG 1.4.5 requires that text conveying information be presented as actual text rather than as an image of text, except where a specific visual presentation is essential or the image can be visually customized by the user. This criterion is critical for users who need to resize, recolor, or reflow text to read it comfortably.
WCAG 1.4.10 Reflow requires that content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions, when displayed at a width equivalent to 320 CSS pixels. This ensures users who rely on zoom or small viewports — including people with low vision and mobile users — can access all content without horizontal scrolling.
WCAG 1.4.11 requires that user interface components and graphical objects have a contrast ratio of at least 3:1 against adjacent colors, ensuring that people with low vision can perceive interactive controls, focus indicators, and meaningful graphics without assistive technology.
WCAG 1.4.12 requires that no loss of content or functionality occurs when users override text spacing properties — line height, letter spacing, word spacing, and spacing after paragraphs — to specific minimum values. This criterion is essential for users with dyslexia, low vision, and cognitive disabilities who rely on custom spacing to read effectively.
WCAG 1.4.13 requires that additional content appearing on pointer hover or keyboard focus is dismissible, hoverable, and persistent — ensuring users with low vision, motor impairments, and cognitive disabilities can access and interact with tooltip-style content without losing it unexpectedly.
WCAG 2.4.5 requires that websites provide more than one way for users to locate any given page within a set of web pages — for example, through a site search, a sitemap, or a navigation menu. This ensures that users with different abilities and preferences can find content using the method that works best for them.
WCAG 2.4.6 requires that headings and labels, when present, must be descriptive and accurately convey the topic or purpose of the content they introduce or identify. This criterion helps users — especially those using assistive technologies — navigate content efficiently and understand the structure and purpose of page sections and form fields.
WCAG 2.4.7 requires that any keyboard-operable user interface has a visible focus indicator so users can always see which element currently has keyboard focus. This is essential for keyboard-only users, people with motor impairments, and anyone who cannot use a mouse.
WCAG 2.4.11 requires that when a UI component receives keyboard focus, it is not entirely hidden by author-created content such as sticky headers, cookie banners, or chat widgets. This criterion ensures keyboard users can always see where they are on the page, which is essential for navigation and usability.
WCAG 2.5.7 requires that any functionality using a dragging movement can also be accomplished with a single pointer without dragging, unless dragging is essential. This ensures users with motor impairments who cannot reliably perform drag gestures can still access all functionality.
WCAG 2.5.8 requires that interactive targets such as buttons and links have a minimum size of 24×24 CSS pixels, or sufficient spacing around smaller targets, so users with motor impairments can activate them reliably. Failing this criterion leads to accidental activations and frustration for anyone who cannot control a pointer with precision.
WCAG 3.1.2 requires that any passage, phrase, or section of web content written in a language different from the page's primary language must be programmatically identified using the lang attribute. This enables assistive technologies, especially screen readers, to switch pronunciation engines automatically and render content accurately for users who rely on audio output.
WCAG 3.2.3 requires that navigation mechanisms appearing on multiple pages within a set of web pages occur in the same relative order each time, unless the user initiates a change. This predictability helps users with cognitive, visual, and motor disabilities build mental models of a site and navigate efficiently.
WCAG 3.2.4 requires that components performing the same function across a website are identified consistently — using the same label, name, or alternative text every time they appear. This prevents confusion for users who rely on consistent patterns to navigate and understand digital interfaces.
WCAG 3.2.6 requires that if a website offers human contact, self-help, or automated assistance mechanisms, those mechanisms appear in the same relative order across pages. This ensures users with cognitive disabilities or memory impairments can reliably locate help without having to re-learn the interface on every page.
WCAG 3.3.3 requires that when an input error is automatically detected, the system must provide a text description suggesting how the user can correct the mistake — unless doing so would jeopardize security or purpose. This criterion is essential for users with cognitive disabilities, screen reader users, and anyone who struggles to understand vague or missing error guidance.
WCAG 3.3.4 requires that web submissions involving legal commitments, financial transactions, or sensitive data can be checked, corrected, or reversed before finalization. This protects all users — especially those with cognitive and motor disabilities — from irreversible, high-stakes mistakes.
WCAG 3.3.8 requires that authentication processes do not rely on cognitive function tests—such as memorizing passwords, solving puzzles, or transcribing characters—unless an alternative method or assistance is available. This protects users with cognitive disabilities from being locked out of digital services.
WCAG 4.1.3 requires that status messages — such as form submission confirmations, error notifications, and cart updates — be programmatically determinable through role or property so assistive technologies can announce them without requiring the user to move focus. This ensures users who rely on screen readers receive important feedback even when focus does not shift to the message.
WCAG 1.2.6 requires that sign language interpretation be provided for all prerecorded audio content in synchronized media. This criterion ensures that Deaf users whose primary language is a sign language can fully access audio information that may not be adequately conveyed through captions alone.
WCAG 1.2.7 requires that when pauses in foreground audio are insufficient to convey all visual information, extended audio descriptions—achieved by pausing the video—must be provided for prerecorded synchronized media. This ensures blind and low-vision users can fully understand complex visual content that standard audio descriptions cannot cover.
WCAG 1.2.8 requires that a full text alternative is provided for all prerecorded synchronized media (audio-video) and prerecorded video-only content, ensuring that users who cannot perceive audio or visual information can access the complete content through text.
WCAG 1.2.9 requires that all live audio-only content — such as live radio broadcasts or audio-only streams — be accompanied by a real-time text alternative equivalent, such as a live captions feed or text transcript updated synchronously. This ensures that users who are deaf or hard of hearing can access live audio content without relying on the audio track itself.
WCAG 1.3.6 requires that the purpose of user interface components, icons, and regions can be programmatically determined so that browsers and assistive technologies can adapt the presentation to meet individual users' needs. This criterion is essential for users with cognitive disabilities who benefit from personalized, simplified, or symbol-augmented interfaces.
WCAG 1.4.6 requires a minimum contrast ratio of 7:1 for normal text and 4.5:1 for large text between foreground and background colors, going beyond the AA threshold to ensure readability for users with low vision, color deficiencies, or those operating in challenging lighting conditions.
WCAG 1.4.7 requires that pre-recorded audio content containing speech either has no background sounds, allows background sounds to be turned off, or keeps background sounds at least 20 dB quieter than the foreground speech. This protects users with hearing loss and cognitive disabilities who struggle to separate speech from competing audio.
WCAG 1.4.8 requires that blocks of text be visually presented in ways users can control — covering foreground and background colors, line width, line spacing, and text alignment — so that people with reading, cognitive, or low-vision disabilities can comfortably read content without loss of information.
WCAG 1.4.9 requires that text be presented using actual text rather than images of text, with no exceptions beyond purely decorative content or cases where the specific visual presentation is essential to the information conveyed. This criterion ensures all users can adjust text rendering to suit their individual needs.
WCAG 2.1.3 requires that every function of a web page or application be operable via a keyboard interface, with no exceptions whatsoever—not even for path-dependent or freehand drawing tasks. This AAA criterion closes the loophole present in WCAG 2.1.1 and ensures full keyboard access for users who cannot use a mouse.
WCAG 2.2.3 (Level AAA) requires that timing is not an essential part of the event or activity presented by content, except for non-interactive synchronized media and real-time events. This ensures users with disabilities who need more time to read, interact, or respond are never excluded by time-dependent design.
WCAG 2.2.4 requires that users can postpone or suppress all interruptions — such as alerts, notifications, and automatic content updates — except those involving an emergency. This criterion is essential for users with attention, cognitive, or neurological disabilities who may be severely disrupted by unexpected interruptions during a task.
WCAG 2.2.5 requires that when an authenticated session expires, users can re-authenticate and continue their activity without losing any data they had entered. This criterion is critical for users with disabilities who may need more time to complete tasks and must not be penalized by session timeouts that erase their work.
WCAG 2.2.6 requires that users are warned about data loss due to inactivity timeouts, and that any such timeout lasts at least 20 hours unless the data is preserved. This protects users with cognitive disabilities, motor impairments, and others who need more time to complete tasks.
WCAG 2.3.2 requires that web pages contain no content that flashes more than three times in any one-second period, with no exception for small or low-contrast flashes. This stricter AAA criterion protects users with photosensitive epilepsy and other seizure disorders from potentially life-threatening neurological reactions.
WCAG 2.3.3 requires that motion animation triggered by user interaction can be disabled, unless the animation is essential to the functionality or the information being conveyed. This matters because motion can trigger vestibular disorders, causing dizziness, nausea, and disorientation in a significant portion of the population.
WCAG 2.4.8 requires that users can determine where they are within a set of web pages — for example, through breadcrumbs, site maps, or highlighted navigation links. This helps users with cognitive disabilities, screen reader users, and anyone navigating complex sites to orient themselves and move through content with confidence.
WCAG 2.4.9 requires that the purpose of every link can be determined from the link text alone, without relying on surrounding context. This stricter AAA criterion ensures all users — especially screen reader users navigating by links — can understand where a link leads without reading the entire page.
WCAG 2.4.10 requires that section headings are used to organize content whenever a page contains multiple sections, enabling users to navigate and understand the structure of the page. This criterion supports screen reader users, cognitive accessibility needs, and anyone who relies on document structure to orient themselves within long or complex content.
WCAG 2.4.12 requires that when a UI component receives keyboard focus, no part of that component is hidden by author-created content — the focused element must be fully visible. This enhanced (AAA) criterion eliminates the partial-visibility allowance of its AA counterpart, ensuring keyboard users always see exactly where focus is.
WCAG 2.4.13 requires that keyboard focus indicators meet minimum size and contrast requirements so that users can clearly see which element has focus. This criterion ensures that people who rely on keyboards or assistive technologies can navigate interfaces without losing track of their current position.
WCAG 2.5.5 requires that interactive targets such as buttons and links be at least 44×44 CSS pixels in size, ensuring people with motor impairments, tremors, or limited dexterity can reliably activate controls without accidentally triggering adjacent elements.
WCAG 2.5.6 requires that web content does not restrict users to a single input modality when multiple input mechanisms are available on the platform, ensuring people can freely switch between touch, keyboard, mouse, voice, and other input methods without losing access to functionality.
WCAG 3.1.3 requires that websites provide a mechanism to identify the specific definition of words or phrases used in an unusual or restricted way, including idioms and jargon. This ensures that users with cognitive disabilities, non-native speakers, and those unfamiliar with specialized terminology can understand the content.
WCAG 3.1.4 requires that a mechanism be available to identify the expanded form or meaning of abbreviations used in content. This criterion ensures that users who are unfamiliar with abbreviations, acronyms, or initialisms can access their full meaning, supporting comprehension for people with cognitive disabilities, non-native speakers, and screen reader users.
WCAG 3.1.5 requires that when content demands a reading ability beyond lower secondary education level, a supplemental version or summary written at a simpler level is provided. This ensures that users with cognitive disabilities, limited literacy, or language barriers can access and understand the information.
WCAG 3.1.6 requires that a mechanism be available to identify the specific pronunciation of words where meaning is ambiguous without knowing the pronunciation. This criterion ensures users who rely on text-to-speech technology or who encounter unfamiliar language can access the correct meaning of ambiguous content.
WCAG 3.2.5 requires that changes of context — such as page navigations, form submissions, or content updates — are initiated only by explicit user action, not triggered automatically. This protects users who rely on screen readers, keyboard navigation, or cognitive support tools from unexpected disruptions to their browsing experience.
WCAG 3.3.5 requires that context-sensitive help is available when a web page requests user input, enabling users to understand what information is required and how to provide it correctly. This criterion reduces errors and supports users with cognitive disabilities, inexperienced users, and anyone navigating complex forms.
WCAG 3.3.6 requires that for any web page requiring user input, submissions are reversible, checked for errors with correction guidance, or confirmable before final submission. This AAA criterion extends 3.3.4 to all forms—not just legal or financial ones—protecting users from irreversible mistakes across every interaction.
WCAG 3.3.9 requires that authentication processes involve no cognitive function test whatsoever — no puzzles, memorization, or transcription — unless a non-cognitive alternative, an assistive mechanism, or an object-based method is available. This Enhanced (AAA) criterion eliminates the last barriers to authentication for users with cognitive, motor, and memory-related disabilities.
WCAG 4.1.1 Parsing requires that web content be free of major HTML/XML errors—such as duplicate IDs—that could cause assistive technologies to misinterpret or fail to process the page. Although deprecated in WCAG 2.2, the underlying axe-core rules remain active and violations still indicate real accessibility risk.
Presidential Circular 2025/10, published in Turkey's Official Gazette No. 32933 on 21 June 2025, mandates WCAG 2.2-aligned accessibility for websites and mobile applications across a wide range of public and private sector organizations, with compliance deadlines of one year for the public sector and two years for e-commerce providers.
This article explains Turkey's Accessibility Logo program introduced by Presidential Circular 2025/10 (Official Gazette No. 32933, June 21, 2025), covering who is obligated, the WCAG 2.2 technical requirements, the monitoring-based award process, and practical steps for achieving compliance.
This article explains how covered organizations in Türkiye must establish an internal Web Sites and Mobile Applications Accessibility Review Commission (İnceleme Komisyonu) under Presidential Circular No. 2025/10, including legal basis, obligations, WCAG 2.2 requirements, and step-by-step implementation guidance.
