Understandable
20 posts
WCAG 3.1.1: Language of Page
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
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
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: Error Identification
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: Labels or Instructions
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: Redundant Entry
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 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 3.1.3: Unusual Words
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: Abbreviations
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: Reading Level
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: Pronunciation
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: Change on Request
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.6: Error Prevention (All)
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: Accessible Authentication (Enhanced)
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.