WCAG 2.1, Understanding 1.1.1
Sufficient Techniques for Success Criterion 1.1.1

Note: Other techniques may also be sufficient if they meet the success criterion. See ARIA10: Using aria-labelledby to provide a text alternative for non-text content

  • H53: Using the body of the object element
  • ARIA6: Using aria-label to provide labels for objects
  • H37: Using alt attributes on img elements
  • ARIA15: Using aria-describedby to provide descriptions of images
  • H53: Using the body of the object element
    • Situation C: If non-text content is a control or accepts user input:
    Situation D: If non-text content is time-based media (including live video-only and live audio-only); a test or exercise that would be invalid if presented in text; or primarily intended to create a specific sensory experience:
    Situation F: If the non-text content should be ignored by assistive technology:
    Failures for Success Criterion 1.1.1
    Situation A: If the content is prerecorded audio-only:
    Failures for Success Criterion 1.2.1
    Sufficient Techniques for Success Criterion 1.2.4

    Note: Other techniques may also be sufficient if they meet the success criterion. See G9: Creating captions for live synchronized media AND SM12: Providing captions through synchronized text streams in SMIL 2.0 AND Understanding 1.2.5

    Sufficient Techniques for Success Criterion 1.2.5

    Note: Other techniques may also be sufficient if they meet the success criterion. See SM6: Providing audio description in SMIL 1.0

  • SM2: Adding extended audio description in SMIL 2.0
  • Using any player that supports audio and video
  • Understanding Techniques.
    • Failures for Success Criterion 1.2.8
    Situation A: The technology provides semantic structure to make information and relationships conveyed through presentation programmatically determinable:
    Situation B: The technology in use does NOT provide the semantic structure to make the information and relationships conveyed through presentation programmatically determinable:
    Advisory Techniques for Success Criterion 1.3.1
    Sufficient Techniques for Success Criterion 1.3.2

    Note: Other techniques may also be sufficient if they meet the success criterion. See H34: Using a Unicode right-to-left mark (RLM) or left-to-right mark (LRM) to mix text direction inline

  • C27: Making the DOM order match the visual order
  • F32: Failure of Success Criterion 1.3.2 due to using white space characters to control spacing within a word
  • Understanding Techniques.
    • Sufficient Techniques for Success Criterion 1.3.4

    Note: Other techniques may also be sufficient if they meet the success criterion. See F100: Failure of Success Criterion 1.3.4 due to showing a message asking to reorient device

    1.3.5 Identify Input Purpose

    Level AA(Added in 2.1)

    The purpose of each input field collecting information about the user can be programmatically determined when:

    • The input field serves a purpose identified in the Input Purposes for User Interface Components section; and

    • The content is implemented using technologies with support for identifying the expected meaning for form input data.

    F107: Failure of Success Criterion 1.3.5 due to incorrect autocomplete attribute values

    1.3.6 Identify Purpose

    Level AAA(Added in 2.1)

    In content implemented using markup languages, the purpose of user interface components, icons, and regions can be programmatically determined.

    Understanding 1.4.1
    Sufficient Techniques for Success Criterion 1.4.1

    Note: Other techniques may also be sufficient if they meet the success criterion. See G182: Ensuring that additional visual cues are available when text color differences are used to convey information

  • C15: Using CSS to change the presentation of a user interface component when it receives focus
    • Failures for Success Criterion 1.4.1
    Sufficient Techniques for Success Criterion 1.4.2

    Note: Other techniques may also be sufficient if they meet the success criterion. See G171: Playing sounds only on user request

    Failures for Success Criterion 1.4.2
    Situation A: text is less than 18 point if not bold and less than 14 point if bold
    Advisory Techniques for Success Criterion 1.4.4
    Advisory Techniques for Success Criterion 1.4.5

    1.4.7 Low or No Background Audio

    Level AAA

    For prerecorded audio-only content that (1) contains primarily speech in the foreground, (2) is not an audio CAPTCHA or audio logo, and (3) is not vocalization intended to be primarily musical expression such as singing or rapping, at least one of the following is true:

    • No Background: The audio does not contain background sounds.

    • Turn Off: The background sounds can be turned off.

    • 20 dB: The background sounds are at least 20 decibels lower than the foreground speech content, with the exception of occasional sounds that last for only one or two seconds. Per the definition of "decibel," background sound that meets this requirement will be approximately four times quieter than the foreground speech content.

    Understanding 1.4.8

    1.4.11 Non-text Contrast

    Level AA(Added in 2.1)

    The visual presentation of the following have a contrast ratio of at least 3:1 against adjacent color(s):

    • User Interface Components: Visual information required to identify user interface components and states, except for inactive components or where the appearance of the component is determined by the user agent and not modified by the author;

    • Graphical Objects: Parts of graphics required to understand the content, except when a particular presentation of graphics is essential to the information being conveyed.

    G174: Providing a control with a sufficient contrast ratio that allows users to switch to a presentation that uses sufficient contrast
    Situation B: Color is required to understand graphical content
    Sufficient Techniques for Success Criterion 1.4.12

    Note: Other techniques may also be sufficient if they meet the success criterion. See C8: Using CSS letter-spacing to control spacing within a word

  • Understanding 1.4.13
    • Sufficient Techniques for Success Criterion 1.4.13

    Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding 2.1.1

    Sufficient Techniques for Success Criterion 2.1.1

    Note: Other techniques may also be sufficient if they meet the success criterion. See PDF3: Ensuring correct tab and reading order in PDF documents

  • SCR20: Using both keyboard and other device-specific functions
  • F54: Failure of Success Criterion 2.1.1 due to using only pointing-device-specific event handlers (including gesture) for a function
  • Understanding Techniques.
    • No additional techniques exist for this Success Criterion. Follow techniques for Success Criterion 2.1.1. If that is not possible because there is a requirement for path-dependent input, then it is not possible to meet this Level AAA Success Criterion.

    2.1.4 Character Key Shortcuts

    Level A(Added in 2.1)

    If a keyboard shortcut is implemented in content using only letter (including upper- and lower-case letters), punctuation, number, or symbol characters, then at least one of the following is true:

    • Turn off: A mechanism is available to turn the shortcut off;

    • Remap: A mechanism is available to remap the shortcut to include one or more non-printable keyboard keys (e.g., Ctrl, Alt);

    • Active only on focus: The keyboard shortcut for a user interface component is only active when that component has focus.

    F99: Failure of Success Criterion 2.1.4 due to implementing character key shortcuts that cannot be turned off or remapped

    Guideline 2.2 – Enough Time

    Provide users enough time to read and use content.

    2.2.1 Timing Adjustable

    Level A

    For each time limit that is set by the content, at least one of the following is true:

    • Turn off: The user is allowed to turn off the time limit before encountering it; or

    • Adjust: The user is allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; or

    • Extend: The user is warned before time expires and given at least 20 seconds to extend the time limit with a simple action (for example, "press the space bar"), and the user is allowed to extend the time limit at least ten times; or

    • Real-time Exception: The time limit is a required part of a real-time event (for example, an auction), and no alternative to the time limit is possible; or

    • Essential Exception: The time limit is essential and extending it would invalidate the activity; or

    • 20 Hour Exception: The time limit is longer than 20 hours.

    G198: Providing a way for the user to turn the time limit off
    Situation B: If a time limit is controlled by a script on the page:
    Situation C: If there are time limits on reading:
    Failures for Success Criterion 2.2.1
    Sufficient Techniques for Success Criterion 2.2.2

    Note: Other techniques may also be sufficient if they meet the success criterion. See G11: Creating content that blinks for less than 5 seconds

  • G191: Providing a link, button, or other mechanism that reloads the page without any blinking content
    • Failures for Success Criterion 2.2.2

    2.2.4 Interruptions

    Level AAA

    Interruptions can be postponed or suppressed by the user, except interruptions involving an emergency.

    G76: Providing a mechanism to request an update of the content instead of updating automatically
  • Understanding 2.2.5
    • Sufficient Techniques for Success Criterion 2.2.5

    Note: Other techniques may also be sufficient if they meet the success criterion. See F12: Failure of Success Criterion 2.2.5 due to having a session time limit without a mechanism re-authentication

    2.2.6 Timeouts

    Level AAA(Added in 2.1)

    Users are warned of the duration of any user inactivity that could cause data loss, unless the data is preserved for more than 20 hours when the user does not take any actions.

    Understanding Techniques.
    Failures for Success Criterion 2.4.3
  • Identifying the purpose of a link using link text combined with programmatically determined link context using one of the following techniques:

    • Level AAA

    A mechanism is available to allow the purpose of each link to be identified from link text alone, except where the purpose of the link would be ambiguous to users in general.

    G91: Providing link text that describes the purpose of a link
  • SCR30: Using scripts to change the link text
  • Providing a supplemental description of the purpose of a link using one of the following techniques:
    • Sufficient Techniques for Success Criterion 2.4.10

    Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding 2.4.11

    Sufficient Techniques for Success Criterion 2.4.11

    Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding 2.4.12

    Sufficient Techniques for Success Criterion 2.4.12

    Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding 2.4.13

    Sufficient Techniques for Success Criterion 2.4.13

    Note: Other techniques may also be sufficient if they meet the success criterion. See C41: Creating a strong focus indicator within the component

    Failures for Success Criterion 2.4.13
    • Using a CSS border for inline text which can wrap (Potential future technique)

    Guideline 2.5 – Input Modalities

    Make it easier for users to operate functionality through various inputs beyond keyboard.
    Failures for Success Criterion 2.5.1
    Sufficient Techniques for Success Criterion 2.5.4

    Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding 2.5.5

    Sufficient Techniques for Success Criterion 2.5.5

    Note: Other techniques may also be sufficient if they meet the success criterion. See F98: Failure due to interactions being limited to touch-only on touchscreen devices

    2.5.7 Dragging Movements

    Level AA(Added in 2.2)

    All functionality that uses a dragging movement for operation can be achieved by a single pointer without dragging, unless dragging is essential or the functionality is determined by the user agent and not modified by the author.

    Note: This requirement applies to web content that interprets pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive technology).

    F108: Failure of Success Criterion 2.5.7 Dragging Movements due to not providing a single pointer method for the user to operate a function that does not require a dragging movement

    2.5.8 Target Size (Minimum)

    Level AA(Added in 2.2)

    The size of the target for pointer inputs is at least 24 by 24 CSS pixels, except where:

    • Spacing: Undersized targets (those less than 24 by 24 CSS pixels) are positioned so that if a 24 CSS pixel diameter circle is centered on the bounding box of each, the circles do not intersect another target or the circle for another undersized target;

    • Equivalent: The function can be achieved through a different control on the same page that meets this criterion;

    • Inline: The target is in a sentence or its size is otherwise constrained by the line-height of non-target text;

    • User agent control: The size of the target is determined by the user agent and is not modified by the author;

    • Essential: A particular presentation of the target is essential or is legally required for the information being conveyed.

    Note 1: Targets that allow for values to be selected spatially based on position within the target are considered one target for the purpose of the success criterion. Examples include sliders, color pickers displaying a gradient of colors, or editable areas where you position the cursor.

    Note 2: For inline targets the line-height should be interpreted as perpendicular to the flow of text. For example, in a language displayed vertically, the line-height would be horizontal.

    Understanding 3.1.1
    Sufficient Techniques for Success Criterion 3.1.1

    Note: Other techniques may also be sufficient if they meet the success criterion. See PDF19: Specifying the language for a passage or phrase with the Lang entry in PDF documents

    Advisory Techniques for Success Criterion 3.1.1
  • G62: Providing a glossary
  • H40: Using description lists
  • Understanding Techniques.
    • Situation A: If the abbreviation has only one meaning within the Web page:
    Sufficient Techniques for Success Criterion 3.1.5

    Note: Other techniques may also be sufficient if they meet the success criterion. See G79: Providing a spoken version of the text

  • Understanding Techniques.
    • Note: A change of content is not always a change of context. This success criterion is automatically met if changes in content are not also changes of context.
    Advisory Techniques for Success Criterion 3.2.1

    3.2.5 Change on Request

    Level AAA

    Changes of context are initiated only by user request or a mechanism is available to turn off such changes.

    SVR1: Implementing automatic redirects on the server side instead of on the client side
  • SCR24: Using progressive enhancement to open new windows on user request
    • Situation D: If using an onchange event on a select element:
    Failures for Success Criterion 3.2.6
    • Inconsistent Help Location

    Guideline 3.3 – Input Assistance

    Help users avoid and correct mistakes.

    3.3.1 Error Identification

    Level A

    If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text.

    ARIA21: Using Aria-Invalid to Indicate An Error Field
  • ARIA19: Using ARIA role=alert or Live Regions to Identify Errors
  • SCR18: Providing client-side validation and alert
  • G199: Providing success feedback when data is submitted successfully

    • 3.3.2 Labels or Instructions

    Level A

    Labels or instructions are provided when content requires user input.

    ARIA1: Using the aria-describedby property to provide a descriptive label for user interface controls
  • G184: Providing text instructions at the beginning of a form or set of fields that describes the necessary input
  • PDF5: Indicating required form controls in PDF forms
  • G167: Using an adjacent button to label the purpose of a field
    • Note: The techniques at the end of the above list should be considered “last resort” and only used when the other techniques cannot be applied to the page. The earlier techniques are preferred because they increase accessibility to a wider user group.
    • Advisory Techniques for Success Criterion 3.3.2
    Situation A: If a mandatory field contains no information:

    3.3.8 Accessible Authentication (Minimum)

    Level AA(Added in 2.2)

    A cognitive function test (such as remembering a password or solving a puzzle) is not required for any step in an authentication process unless that step provides at least one of the following:

    • Alternative: Another authentication method that does not rely on a cognitive function test.

    • Mechanism: A mechanism is available to assist the user in completing the cognitive function test.

    • Object Recognition: The cognitive function test is to recognize objects.

    • Personal Content: The cognitive function test is to identify non-text content the user provided to the Web site.

    Note 1: What is perceived as the user interface component or sub-component (to determine enclosure or size) depends on its visual presentation. The visual presentation includes the component's visible content, border, and component-specific background. It does not include shadow and glow effects outside the component's content, background, or border.

    Note 2: Examples of mechanisms that satisfy this criterion include:

    1. support for password entry by password managers to reduce memory need, and
    2. copy and paste to reduce the cognitive burden of re-typing.
    H100: Providing properly marked up email and password inputs
  • Providing WebAuthn as an alternative to username/password (Potential future technique)
  • Providing a 3rd party login using oAuth (Potential future technique)
  • Using two techniques to provide 2 factor authentication (Potential future technique)
    • Failures for Success Criterion 3.3.8

    4.1.3 Status Messages

    Level AA(Added in 2.1)

    In content implemented using markup languages, status messages can be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus.

    G199: Providing success feedback when data is submitted successfully
    Situation B: If a status message conveys a suggestion, or a warning on the existence of an error:
    Contribute

    We welcome feedback and suggestions:

    Follow Lee on X/Twitter - Father, Husband, Serial builder creating AI, crypto, games & web tools. We are friends :) AI Will Come To Life!

    Check out: eBank.nz (Art Generator) | Netwrck.com (AI Tools) | Text-Generator.io (AI API) | BitBank.nz (Crypto AI) | ReadingTime (Kids Reading) | RewordGame | BigMultiplayerChess | WebFiddle | How.nz | Helix AI Assistant