Wcag 2 2 Aa
23 inlägg
WCAG 1.3.4: Orientation
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: Identify Input Purpose
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: Contrast (Minimum)
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: Resize Text
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: Images of Text
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
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: Non-text Contrast
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: Text Spacing
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: Content on Hover or Focus
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: Multiple Ways
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: Headings and Labels
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: Focus Visible
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: Focus Not Obscured (Minimum)
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: Dragging Movements
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: Target Size (Minimum)
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: Language of Parts
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: Consistent Navigation
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: Consistent Identification
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: Consistent Help
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: Error Suggestion
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: Error Prevention (Legal, Financial, Data)
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: Accessible Authentication (Minimum)
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: Status Messages
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.