Web Content Accessibility Guidelines (WCAG) 2.1¶
World Wide Web Consortium. (2018). Web Content Accessibility Guidelines (WCAG) 2.1.
Cited by¶
16 citations across 16 artifacts.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Color Harmony
- A common failure is either ignoring accessibility (creating beautiful designs that exclude users) or over-accommodating accessibility (creating monotonous, low-contrast designs that fail aesthetically)
This sourceW3C Recommendation. Specifies minimum color-contrast ratios (4.5:1 for normal text, 3:1 for large text and UI components at level AA) so content remains legible to users with low vision or color-vision deficiency; supports the accessibility-versus-aesthetic-intent tension. (Citation-fix: publisher corrected from 'Web Accessibility Consortium' to W3C.)
- A common failure is either ignoring accessibility (creating beautiful designs that exclude users) or over-accommodating accessibility (creating monotonous, low-contrast designs that fail aesthetically)
- Linearization-Meaning Mismatch
- In screen-reader accessibility, a richly laid-out webpage must be read aloud as a 1D stream, and the chosen linearization (DOM source order, with ARIA overrides) may or may not match the visual reading order the designer assumed — when mismatched, the page is technically complete but functionally inaccessible.
This sourceSpecifies meaningful sequence (Success Criterion 1.3.2) and info-and-relationships (1.3.1), where DOM/programmatic reading order must match the intended reading order, with ARIA used to reconcile them.
Supported in partVerified against the work's full text
WCAG 1.3.2 requires a programmatically determinable correct reading sequence where order affects meaning; it does not discuss DOM order, ARIA overrides or the mismatch failure mode.
“When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined”
- In screen-reader accessibility, a richly laid-out webpage must be read aloud as a 1D stream, and the chosen linearization (DOM source order, with ARIA overrides) may or may not match the visual reading order the designer assumed — when mismatched, the page is technically complete but functionally inaccessible.
- Minimalism
- A common failure is minimalism that treats accessibility features as excess clutter to be removed
This sourceNormative guidelines establishing redundant signaling, sufficient contrast, and explicit labels as essential, non-decorative supports — a counterweight to over-aggressive minimalist removal.
- A common failure is minimalism that treats accessibility features as excess clutter to be removed
Domain-specific¶
- Accessibility
- In HCI and web standards this is operationalized through WCAG (Web Content Accessibility Guidelines), which structures requirements around four principles — perceivable, operable, understandable, robust — and provides testable success criteria: colour contrast ratios, keyboard-navigability requirements, ARIA semantic markup for screen readers, caption requirements for video, and reading-level guidelines for text
This sourceWCAG 2.1's four principles (perceivable, operable, understandable, robust) and its testable success criteria for contrast, keyboard operation, captions and reading level. WCAG 2.1's contrast success criterion, requiring a 4.5:1 ratio for normal text at Level AA, computed from the relative luminances of the two colours. The Americans with Disabilities Act of 1990 as the national accessibility mandate the passage cites.
Supported in partVerified against a saved copy of the source
“Principles - At the top are four principles that provide the foundation for web accessibility: perceivable, operable, understandable, and robust .”
- In HCI and web standards this is operationalized through WCAG (Web Content Accessibility Guidelines), which structures requirements around four principles — perceivable, operable, understandable, robust — and provides testable success criteria: colour contrast ratios, keyboard-navigability requirements, ARIA semantic markup for screen readers, caption requirements for video, and reading-level guidelines for text
- Focus-Order Failure
- WCAG 2.4.3 (Focus Order, Level A) addresses this directly, requiring that interactive elements receive focus in an order that preserves meaning and operability
This sourceThe WCAG 2.4.3 (Focus Order, Level A) requirement that focusable components receive focus in an order that preserves meaning and operability. Distinguishes focus order from the programmatically determined reading order as two sequences that need not coincide (WCAG SC 2.4.3). W3C technique C27, a sufficient technique for SC 2.4.3, requiring the source (DOM) order to match the CSS visual presentation.
SupportedVerified against a saved copy of the source
“Focus Order (Level A)”
- WCAG 2.4.3 (Focus Order, Level A) addresses this directly, requiring that interactive elements receive focus in an order that preserves meaning and operability
- Keyboard Accessibility
- WCAG 2.x Guideline 2.1 requires that all functionality be operable from a keyboard, through Success Criteria 2.1.1 Keyboard and 2.1.2 No Keyboard Trap (both Level A) because keyboard completeness is the upstream contract on which screen readers, switch scanners, sip-and-puff devices, and voice-control software all depend: those assistive technologies drive the keyboard interface, and any action unreachable by keyboard is unreachable by all of them.
This sourceWCAG 2.1's Guideline 2.1 Keyboard Accessible, whose Success Criterion 2.1.1 (Level A) requires all functionality of the content to be operable through a keyboard interface. WCAG 2.1's account of its layers of guidance: non-testable guidelines, each with testable success criteria used for conformance. WCAG 2.1 Success Criterion 2.1.1 Keyboard, which requires all functionality of the content to be operable through a keyboard interface.
Supported in partVerified against the source
- WCAG 2.x Guideline 2.1 requires that all functionality be operable from a keyboard, through Success Criteria 2.1.1 Keyboard and 2.1.2 No Keyboard Trap (both Level A) because keyboard completeness is the upstream contract on which screen readers, switch scanners, sip-and-puff devices, and voice-control software all depend: those assistive technologies drive the keyboard interface, and any action unreachable by keyboard is unreachable by all of them.
- Motion-Triggered Harm
- Susceptible populations include people with vestibular disorders (who are harmed by large continuous motion and parallax), photosensitive epilepsy (harmed by flash above the WCAG 2.3.1 general- and red-flash limits of frequency, luminance and area, from which the stricter 2.3.2 Three Flashes rule removes the below-threshold exemption), migraine susceptibility, autism-related sensory sensitivities, and motion-sickness vulnerability
This sourceWCAG 2.1 Success Criterion 2.3.1 Three Flashes or Below Threshold, which limits flash for photosensitive users by the general-flash and red-flash luminance, area and frequency conditions (with 2.3.2 Three Flashes as the stricter no-below-threshold rule).
Supported in partVerified against the source
- Susceptible populations include people with vestibular disorders (who are harmed by large continuous motion and parallax), photosensitive epilepsy (harmed by flash above the WCAG 2.3.1 general- and red-flash limits of frequency, luminance and area, from which the stricter 2.3.2 Three Flashes rule removes the below-threshold exemption), migraine susceptibility, autism-related sensory sensitivities, and motion-sickness vulnerability
- Operable Design
- It is the second of the four WCAG accessibility principles (Perceivable, Operable, Understandable, Robust)
This sourceThe WCAG four-principle framing in its own numbering, in which Operable is principle 2, after Perceivable and before Understandable and Robust. The five WCAG 2.1 Operable guidelines - Keyboard Accessible, Enough Time, Seizures and Physical Reactions, Navigable, and Input Modalities (the last introduced in 2.1). WCAG Success Criterion 2.1.1 (Keyboard): all functionality of the content operable through a keyboard interface without requiring specific timings for individual keystrokes.
SupportedVerified against a saved copy of the source
“Principles - At the top are four principles that provide the foundation for web accessibility: perceivable, operable, understandable, and robust.”
- It is the second of the four WCAG accessibility principles (Perceivable, Operable, Understandable, Robust)
- Perceivable Design
- Perceivable design is the first of WCAG 2.x's four principles — Perceivable, Operable, Understandable, Robust — and requires that all information and user-interface components be presentable to users in ways they can perceive, meaning no essential content is locked behind a single sensory channel that some users cannot access
This sourceThe four WCAG guidelines under Principle 1 (1.1 Text Alternatives, 1.2 Time-based Media, 1.3 Adaptable, 1.4 Distinguishable) and their captioning, contrast and audio-control criteria. WCAG Success Criterion 1.1.1 Non-text Content, which requires a text alternative serving the equivalent purpose for non-text content.
SupportedVerified against the source
- Perceivable design is the first of WCAG 2.x's four principles — Perceivable, Operable, Understandable, Robust — and requires that all information and user-interface components be presentable to users in ways they can perceive, meaning no essential content is locked behind a single sensory channel that some users cannot access
- Responsive-Layout Breakage
- When a design encodes meaning through spatial proximity, adjacency, hierarchical position, or above-the-fold prominence, a transformation that preserves "the same content" while rearranging the layout can silently destroy the encoded meaning without producing any error
This sourceThat information and relationships can be conveyed through presentation and reading sequence, and that reflowed content must keep its information and functionality (SC 1.3.1, 1.3.2, 1.4.10). That magnification acts as a viewport transformation, since WCAG equates 400% zoom with a 320 CSS px viewport and requires reflow and text resizing without loss of content (SC 1.4.10, 1.4.4).
Supported in partVerified against the source
- When a design encodes meaning through spatial proximity, adjacency, hierarchical position, or above-the-fold prominence, a transformation that preserves "the same content" while rearranging the layout can silently destroy the encoded meaning without producing any error
- Screen-Reader Ambiguity
- When the accessibility tree is absent, ambiguous, or wrong relative to the visual structure, the assistive-technology user encounters an interface stripped of the organization their sighted counterpart navigates by: section headers rendered as unsemantic
<div>elements cannot be jumped between; progress indicators encoded only as styled<span>sequences carry no "current step" state; validation error messages that appear visually in red below a field but are not associated with it viaaria-describedbycannot be discovered by a user who cannot see where the visual error marker has appearedThis sourceThe requirements that structure and relationships conveyed through presentation be programmatically determinable (SC 1.3.1) and that interface components expose name, role and state to assistive technologies (SC 4.1.2).
Supported in partVerified against the source
- When the accessibility tree is absent, ambiguous, or wrong relative to the visual structure, the assistive-technology user encounters an interface stripped of the organization their sighted counterpart navigates by: section headers rendered as unsemantic
- Touch Target Size
- Platform standards codify the rule as minimums: Apple's Human Interface Guidelines specify 44pt × 44pt; Material Design specifies 48dp × 48dp; WCAG 2.5.5 (Level AAA) specifies 44 CSS pixels
This sourceWCAG 2.1 Success Criterion 2.5.5 Target Size (Level AAA), requiring pointer targets of at least 44 by 44 CSS pixels.
Supported in partVerified against a saved copy of the source
“Success Criterion 2.5.5 Target Size Understanding Target Size | How to Meet Target Size (Level AAA) The size of the target for pointer inputs is at least 44 by 44 CSS pixels except when:”
- Platform standards codify the rule as minimums: Apple's Human Interface Guidelines specify 44pt × 44pt; Material Design specifies 48dp × 48dp; WCAG 2.5.5 (Level AAA) specifies 44 CSS pixels
Mechanisms¶
- Assistive-Technology Labeling Pass
- Automated scans grant false confidence: an interface can pass every checker and remain unusable because the labels, though present, are wrong ("button button") — meeting the letter of a name-role-value requirement while failing its intent.
This sourceRequires both automated and human evaluation, programmatically determinable names and roles, and labels that accurately describe purpose, showing why mere label presence is insufficient.
- Automated scans grant false confidence: an interface can pass every checker and remain unusable because the labels, though present, are wrong ("button button") — meeting the letter of a name-role-value requirement while failing its intent.
- Platform Conformance Test Suite
- The conformance suite encodes the platform's requirements as runnable checks — every field must expose a programmatic label, keyboard navigation must reach every control, error messages must be announced, response times must stay under budget — tiered on the real WCAG conformance levels,
This sourceRequires keyboard operability and defines cumulative WCAG conformance levels A, AA, and AAA.
- The conformance suite encodes the platform's requirements as runnable checks — every field must expose a programmatic label, keyboard navigation must reach every control, error messages must be announced, response times must stay under budget — tiered on the real WCAG conformance levels,
- Redundancy Style Guide
- It operationalizes the principle behind accessibility standards like WCAG 1.4.1
This sourceWCAG 2.1 Success Criterion 1.4.1 requires a non-color means of conveying information and actions.
- It operationalizes the principle behind accessibility standards like WCAG 1.4.1
- Scroll Progression Design
- When the visual order and the source order drift apart, the meaningful sequence is lost for anyone not reading with their eyes, in direct violation of the accessibility standards that govern reading order.
This sourceRequires meaningful reading order to remain programmatically determinable for assistive technologies.
- When the visual order and the source order drift apart, the meaningful sequence is lost for anyone not reading with their eyes, in direct violation of the accessibility standards that govern reading order.
Verification¶
Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.
Does it back the claim? Read against the text for 10 of 16 citations: 3 supported, 7 supported in part. Each verdict is shown under its citation below, with what in the work backs the sentence.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Links previously used in the corpus¶
Before the registry existed this work was also linked 1 other way.
Registry ID ref:12823eb52874 · see in the full table