Datasets:

sidereior

/

wcg-standards-adherence

like 0

See Understanding Techniques. G159: Using an author-supplied, visible focus indicator C40: Creating a two-color focus indicator to ensure sufficient contrast with all components 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) Back to top Guideline 2.5 – Input Modalities Make it easier for users to operate functionality through various inputs beyond keyboard. 2.5.1 Pointer Gestures Level A (Added in 2.1) All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gestur e is essential. Understanding 2.5.1 Show Hide techniques and failures for 2.5.1 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 2.5.1 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.

G215: Providing controls to achieve the same result as path based or multipoint gestures G216: Providing single point activation for a control slider Failures for Success Criterion 2.5.1 F105: Failure of Success Criterion 2.5.1 due to providing functionality via a path-based gesture without simple pointer alternative Back to top 2.5.2 Pointer Cancellation Level A (Added in 2.1) For functionality that can be operated using a single pointer, at least one of the following is true: No Down-Event: The down-event of the pointer is not used to execute any part of the function; Abort or Undo: Completion of the function is on the up-event, and a mechanism is available to abort the function before completion or to undo the function after completion; Up Reversal: The up-event reverses any outcome of the preceding down-event; Essential: Completing the function on the down-event is essential. Understanding 2.5.2 Show Hide techniques and failures for 2.5.2 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 2.5.2 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. G210: Ensuring that drag-and-drop actions can be cancelled G212: Using native controls to ensure functionality is triggered on the up-event. Touch events are only triggered when touch is removed from a control (Potential future technique) Failures for Success Criterion 2.5.2 F101: Failure of Success Criterion 2.5.2 due to activating a control on the down-event Back to top 2.5.3 Label in Name Level A (Added in 2.1) For user interface components with labels that include text or images of text, the name contains the text that is presented visually.

Understanding 2.5.3 Show Hide techniques and failures for 2.5.3 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 2.5.3 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. G208: Including the text of the visible label as part of the accessible name G211: Matching the accessible name to the visible label Advisory Techniques for Success Criterion 2.5.3 If an icon has no accompanying text, consider using its hover text as its accessible name (Potential future technique) Failures for Success Criterion 2.5.3 F96: Failure due to the accessible name not containing the visible label text Accessible name contains the visible label text, but the words of the visible label are not in the same order as they are in the visible label text (Potential future technique) Accessible name contains the visible label text, but one or more other words are interspersed in the label (Potential future technique) Back to top 2.5.4 Motion Actuation Level A (Added in 2.1) Functionality that can be operated by device motion or user motion can also be operated by user interface components and responding to the motion can be disabled to prevent accidental actuation, except when: Supported Interface: The motion is used to operate functionality through an accessibility supported interface; Essential: The motion is essential for the function and doing so would invalidate the activity. Understanding 2.5.4 Show Hide techniques and failures for 2.5.4 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 2.5.4 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.

G213: Provide conventional controls and an application setting for motion activated input GXXX: Supporting system level features which allow the user to disable motion actuation Failures for Success Criterion 2.5.4 F106: Failure due to inability to deactivate motion actuation FXXX: Failure of Success Criterion 2.5.4 due to disrupting or disabling system level features which allow the user to disable motion actuation Back to top 2.5.5 Target Size (Enhanced) Level AAA (Added in 2.1) The size of the target for pointer inputs is at least 44 by 44 CSS pixels except when: Equivalent: The target is available through an equivalent link or control on the same page that is at least 44 by 44 CSS pixels; Inline: The target is in a sentence or block of 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 to the information being conveyed. Understanding 2.5.5 Show Hide techniques and failures for 2.5.5 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 2.5.5 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. Ensuring that targets are at least 44 by 44 CSS pixels. Ensuring inline links provide sufficiently large activation target.

Advisory Techniques for Success Criterion 2.5.5 none documented Failures for Success Criterion 2.5.5 Failure of success criterion 2.5.5 due to target being less than 44 by 44 CSS pixels. Back to top 2.5.6 Concurrent Input Mechanisms Level AAA (Added in 2.1) Web content does not restrict use of input modalities available on a platform except where the restriction is essential, required to ensure the security of the content, or required to respect user settings. Understanding 2.5.6 Show Hide techniques and failures for 2.5.6 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 2.5.6 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. Only using high-level, input-agnostic event handlers, such as focus, blur, click, in Javascript (Potential future technique).

Failures for Success Criterion 2.5.6 F98: Failure due to interactions being limited to touch-only on touchscreen devices Back to top 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). Understanding 2.5.7 Show Hide techniques and failures for 2.5.7 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 2.5.7 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.

G219: Ensuring that an alternative is available for dragging movements that operate on content Failures for Success Criterion 2.5.7 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 Back to top 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 2.5.8 Show Hide techniques and failures for 2.5.8 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 2.5.8 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. C42: Using min-height and min-width to ensure sufficient target spacing Back to top Principle 3 – Understandable Information and the operation of the user interface must be understandable. Guideline 3.1 – Readable Make text content readable and understandable. 3.1.1 Language of Page Level A The default human language of each Web page can be programmatically determined.

Understanding 3.1.1 Show Hide techniques and failures for 3.1.1 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 3.1.1 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. H57: Using the language attribute on the HTML element PDF16: Setting the default language using the /Lang entry in the document catalog of a PDF document PDF19: Specifying the language for a passage or phrase with the Lang entry in PDF documents Advisory Techniques for Success Criterion 3.1.1 SVR5: Specifying the default language in the HTTP header Back to top 3.1.2 Language of Parts Level AA The human language of each passage or phrase in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text. Understanding 3.1.2 Show Hide techniques and failures for 3.1.2 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 3.1.2 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.

H58: Using language attributes to identify changes in the human language PDF19: Specifying the language for a passage or phrase with the Lang entry in PDF documents Back to top 3.1.3 Unusual Words Level AAA A mechanism is available for identifying specific definitions of words or phrases used in an unusual or restricted way, including idioms and jargon. Understanding 3.1.3 Show Hide techniques and failures for 3.1.3 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 3.1.3 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. Situation A: If the word or phrase has a unique meaning within the Web page: G101: Providing the definition of a word or phrase used in an unusual or restricted way G55: Linking to definitions H40: Using description lists H60: Using the link element to link to a glossary G112: Using inline definitions H54: Using the dfn element to identify the defining instance of a word G101: Providing the definition of a word or phrase used in an unusual or restricted way G55: Linking to definitions H40: Using description lists H60: Using the link element to link to a glossary G62: Providing a glossary G70: Providing a function to search an online dictionary Situation B: If the word or phrase means different things within the same Web page: G101: Providing the definition of a word or phrase used in an unusual or restricted way G55: Linking to definitions H40: Using description lists H60: Using the link element to link to a glossary G112: Using inline definitions H54: Using the dfn element to identify the defining instance of a word Back to top 3.1.4 Abbreviations Level AAA A mechanism for identifying the expanded form or meaning of abbreviations is available. Understanding 3.1.4 Show Hide techniques and failures for 3.1.4 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 3.1.4 Note: Other techniques may also be sufficient if they meet the success criterion.

See Understanding Techniques. Situation A: If the abbreviation has only one meaning within the Web page: G102: Providing the expansion or explanation of an abbreviation G97: Providing the first use of an abbreviation immediately before or after the expanded form G55: Linking to definitions H28: Providing definitions for abbreviations by using the abbr element PDF8: Providing definitions for abbreviations via an E entry for a structure element G102: Providing the expansion or explanation of an abbreviation G55: Linking to definitions G62: Providing a glossary H60: Using the link element to link to a glossary G70: Providing a function to search an online dictionary H28: Providing definitions for abbreviations by using the abbr element PDF8: Providing definitions for abbreviations via an E entry for a structure element Situation B: If the abbreviation means different things within the same Web page: G102: Providing the expansio n or explanation of an abbreviation G55: Linking to definitions H28: Providing definitions for abbreviations by using the abbr element PDF8: Providing definitions for abbreviations via an E entry for a structure element Back to top 3.1.5 Reading Level Level AAA When text requires reading ability more advanced than the lower secondary education level after removal of proper names and titles, supplemental content, or a version that does not require reading ability more advanced than the lower secondary education level, is available. Understanding 3.1.5 Show Hide techniques and failures for 3.1.5 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 3.1.5 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. G86: Providing a text summary that can be understood by people with lower secondary education level reading ability G103: Providing visual illustrations, pictures, and symbols to help explain ideas, events, and processes G79: Providing a spoken version of the text G153: Making the text easier to read G160: Providing sign language versions of information, ideas, and processes that must be understood in order to use the content Back to top 3.1.6 Pronunciation Level AAA A mechanism is available for identifying specific pronunciation of words where meaning of the words, in context, is ambiguous without knowing the pronunciation.

Understanding 3.1.6 Show Hide techniques and failures for 3.1.6 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 3.1.6 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. G120: Providing the pronunciation immediately following the word G121: Linking to pronunciations G62: Providing a glossary G163: Using standard diacritical marks that can be turned off H62: Using the ruby element Back to top Guideline 3.2 – Predictable Make Web pages appear and operate in predictable ways. 3.2.1 On Focus Level A When any user interface component receives focus, it does not initiate a change of context. Understanding 3.2.1 Show Hide techniques and failures for 3.2.1 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 3.2.1 Note: Other techniques may also be sufficient if they meet the success criterion.

See Understanding Techniques. G107: Using "activate" rather than "focus" as a trigger for changes of context 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 G200: Opening new windows and tabs from a link only when necessary G201: Giving users advanced warning when opening a new window Failures for Success Criterion 3.2.1 F55: Failure of Success Criteria 2.1.1, 2.4.7, and 3.2.1 due to using script to remove focus when focus is received Back to top 3.2.2 On Input Level A Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component. Understanding 3.2.2 Show Hide techniques and failures for 3.2.2 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 3.2.2 Note: Other techniques may also be sufficient if they meet the success criterion.

See Understanding Techniques. G80: Providing a submit button to initiate a change of context H32: Providing submit buttons H84: Using a button with a select element to perform an action PDF15: Providing submit buttons with the submit-form action in PDF forms G13: Describing what will happen before a change to a form control that causes a change of context to occur is made SCR19: Using an onchange event on a select element without causing a change of context 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.2 G201: Giving users advanced warning when opening a new window Failures for Success Criterion 3.2.2 F36: Failure of Success Criterion 3.2.2 due to automatically submitting a form and given a value F37: Failure of Success Criterion 3.2.2 due to launching a new window without prior warning when the selection of a radio button, check box or select list is changed Back to top 3.2.3 Consistent Navigation Level AA Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user. Understanding 3.2.3 Show Hide techniques and failures for 3.2.3 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 3.2.3 Note: Other techniques may also be sufficient if they meet the success criterion.

See Understanding Techniques. G61: Presenting repeated components in the same relative order each time they appear Advisory Techniques for Success Criterion 3.2.3 PDF14: Providing running headers and footers in PDF documents PDF17: Specifying consistent page numbering for PDF documents Failures for Success Criterion 3.2.3 F66: Failure of Success Criterion 3.2.3 due to presenting navigation links in a different relative order on different pages Back to top 3.2.4 Consistent Identification Level AA Components that have the same functionality within a set of Web pages are identified consistently. Understanding 3.2.4 Show Hide techniques and failures for 3.2.4 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 3.2.4 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. G197: Using labels, names, and text alternatives consistently for content that has the same functionality Note 1: Text alternatives that are “consistent” are not always “identical.” For instance, you may have an graphical arrow at the bottom of a Web page that links to the next Web page.

The text alternative may say “Go to page 4.” Naturally, it would not be appropriate to repeat this exact text alternative on the next Web page. It would be more appropriate to say “Go to page 5”. Although these text alternatives would not be identical, they would be consistent, and therefore would satisfy this Success Criterion. Note 2: A single non-text-content-item may be used to serve different functions. In such cases, different text alternatives are necessary and should be used.

Examples can be commonly found with the use of icons such as check marks, cross marks, and traffic signs. Their functions can be different depending on the context of the Web page. A check mark icon may function as “approved”, “completed”, or “included”, to name a few, depending on the situa tion. Using “check mark” as text alternative across all Web pages does not help users understand the function of the icon. Different text alternatives can be used when the same non-text content serves multiple functions.

Failures for Success Criterion 3.2.4 F31: Failure of Success Criterion 3.2.4 due to using two different labels for the same function on different Web pages within a set of Web pages Back to top 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. Understanding 3.2.5 Show Hide techniques and failures for 3.2.5 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 3.2.5 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. Situation A: If the Web page allows automatic updates: G76: Providing a mechanism to request an update of the content instead of updating automatically Situation B: If automatic redirects are possible: SVR1: Implementing automatic redirects on the server side instead of on the client side G110: Using an instant client-side redirect H76: Using meta refresh to create an instant client-side redirect Situation C: If the Web page uses pop-up windows: Including pop-up windows using one of the following techniques: H83: Using the target attribute to open a new window on user request and indicating this in link text SCR24: Using progressive enhancement to open new windows on user request Situation D: If using an onchange event on a select element: SCR19: Using an onchange event on a select element without causing a change of context Advisory Techniques for Success Criterion 3.2.5 G200: Opening new windows and tabs from a link only when necessary Failures for Success Criterion 3.2.5 F60: Failure of Success Criterion 3.2.5 due to launching a new window when a user enters text into an input field F61: Failure of Success Criterion 3.2.5 due to complete change of main content through an automatic update that the user cannot disable from within the content F9: Failure of Success Criterion 3.2.5 due to changing the context when the user removes focus from a form element F22: Failure of Success Criterion 3.2.5 due to opening windows that are not requested by the user F52: Failure of Success Criterion 3.2.1 and 3.2.5 due to opening a new window as soon as a new page is loaded F40: Failure due to using meta redirect with a time limit F41: Failure of Success Criterion 2.2.1, 2.2.4, and 3.2.5 due to using meta refresh to reload the page Back to top 3.2.6 Consistent Help Level A (Added in 2.2) If a Web page contains any of the following help mechanisms, and those mechanisms are repeated on multiple Web pages within a set of Web pages, they occur in the same order relative to other page content, unless a change is initiated by the user: Human contact details; Human contact mechanism; Self-help option; A fully automated contact mechanism. Note 1: A fully automated contact mechanism.

Note 2: For this Success Criterion, “the same order relative to other page content” can be thought of as how the content is ordered when the page is serialized. The visual position of a help mechanism is likely to be consistent across pages for the same page variation (e.g., CSS break-point). The user can initiate a change, such as changing the page’s zoom or orientation, which may trigger a different page variation. This criterion is concerned with relative order across pages displayed in the same page variation (e.g., same zoom level and orientation). Understanding 3.2.6 Show Hide techniques and failures for 3.2.6 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 3.2.6 Note: Other techniques may also be sufficient if they meet the success criterion.

See Understanding Techniques. G220: Provide a contact-us link in a consistent location Failures for Success Criterion 3.2.6 Inconsistent Help Location Back to top 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. Understanding 3.3.1 Show Hide techniques and failures for 3.3.1 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 3.3.1 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.

Situation A: If a form contains fields for which information from the user is mandatory. G83: Providing text descriptions to identify required fields that were not completed ARIA21: Using Aria-Invalid to Indicate An Error Field SCR18: Providing client-side validation and alert PDF5: Indicating required form controls in PDF forms Situation B: If information provided by the user is required to be in a specific data format or of certain values. ARIA18: Using aria-alertdialog to Identify Errors ARIA19: Using ARIA role=alert or Live Regions to Identify Errors ARIA21: Using Aria-Invalid to Indicate An Error Field G84: Providing a text description when the user provides information that is not in the list of allowed values G85: Providing a text description when user input falls outside the required format or values SCR18: Providing client-side validation and alert SCR32: Providing client-side validation and adding error text via the DOM PDF22: Indicating when user input falls outside the required format or values in PDF forms Advisory Techniques for Success Criterion 3.3.1 G139: Creating a mechanism that allows users to jump to errors G199: Providing success feedback when data is submitted successfully Back to top 3.3.2 Labels or Instructions Level A Labels or instructions are provided when content requires user input. Understanding 3.3.2 Show Hide techniques and failures for 3.3.2 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 3.3.2 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.

G131: Providing descriptive labels ARIA1: Using the aria-describedby property to provide a descriptive label for user interface controls ARIA9: Using aria-labelledby to concatenate a label from several text nodes ARIA17: Using grouping roles to identify related form controls G89: Providing expected data format and example G184: Providing text instructions at the beginning of a form or set of fields that describes the necessary input G162: Positioning labels to maximize predictability of relationships G83: Providing text descriptions to identify required fields that were not completed H90: Indicating required form controls using label or legend PDF5: Indicating required form controls in PDF forms H44: Using label elements to associate text labels with form controls PDF10: Providing labels for interactive form controls in PDF documents H71: Providing a description for groups of form controls using fieldset and legend elements 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 G13: Describing what will happen before a change to a form control that causes a change of context to occur is made Failures for Success Criterion 3.3.2 F82: Failure of Success Criterion 3.3.2 by visually formatting a set of phone number fields but not including a text label Back to top 3.3.3 Error Suggestion Level AA If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content. Understanding 3.3.3 Show Hide techniques and failures for 3.3.3 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 3.3.3 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.

Situation A: If a mandatory field contains no information: G83: Providing text descriptions to identify required fields that were not completed ARIA2: Identifying a required field with the aria-required property PDF5: Indicating required form controls in PDF forms Situation B: If information for a field is required to be in a specific data format: ARIA18: Using aria-alertdialog to Identify Errors G85: Providing a text description when user input falls outside the required format or values G177: Providing suggested correction text SCR18: Providing client-side validation and alert SCR32: Providing client-side validation and adding error text via the DOM PDF22: Indicating when user input falls outside the required format or values in PDF forms Situation C: Information provided by the user is required to be one of a limited set of values: ARIA18: Using aria-alertdialog to Identify Errors G84: Providing a text description when the user provides information that is not in the list of allowed values G177: Providing suggested correction text SCR18: Providing client-side validation and alert SCR32: Providing client-side validation and adding error text via the DOM PDF22: Indicating when user input falls outside the required format or values in PDF forms Advisory Techniques for Success Criterion 3.3.3 G139: Creating a mechanism that allows users to jump to errors G199: Providing success feedback when data is submitted successfully Back to top 3.3.4 Error Prevention (Legal, Financial, Data) Level AA For Web pages that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, at least one of the following is true: Reversible: Submissions are reversible. Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them. Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission. Understanding 3.3.4 Show Hide techniques and failures for 3.3.4 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 3.3.4 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.

Situation A: If an application causes a legal transaction to occur, such as making a purchase or submitting an income tax return: G164: Providing a stated time within which an online request (or transaction) may be amended or canceled by the user after making the request G98: Providing the ability for the user to review and correct answers before submitting G155: Providing a checkbox in addition to a submit button Situation B: If an action causes information to be deleted: G99: Providing the ability to recover deleted information G168: Requesting confirmation to continue with selected action G155: Providing a checkbox in addition to a submit button Situation C: If the Web page includes a testing application: G98: Providing the ability for the user to review and correct answers before submitting G168: Requesting confirmation to continue with selected action Advisory Techniques for Success Criterion 3.3.4 SCR18: Providing client-side validation and alert G199: Providing success feedback when data is submitted successfully Back to top 3.3.5 Help Level AAA Context-sensitive help is available. Understanding 3.3.5 Show Hide techniques and failures for 3.3.5 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 3.3.5 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. Situation A: If a form requires text input: G71: Providing a help link on every Web page G193: Providing help by an assistant in the Web page G194: Providing spell checking and suggestions for text input G184: Providing text instructions at the beginning of a form or set of fields that describes the necessary input Situation B: If a form requires text input in an expected data format: G89: Providing expected data format and example G184: Providing text instructions at the beginning of a form or set of fields that describes the necessary input Advisory Techniques for Success Criterion 3.3.5 H89: Using the title attribute to provide context-sensitive help Back to top 3.3.6 Error Prevention (All) Level AAA For Web pages that require the user to submit information, at least one of the following is true: Reversible: Submissions are reversible. Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them.

Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission. Understanding 3.3.6 Back to top 3.3.7 Redundant Entry Level A (Added in 2.2) Information previously entered by or provided to the user that is required to be entered again in the same process is either: auto-populated, or available for the user to select. Except when: re-entering the information is essential, the information is required to ensure the security of th e content, or previously entered information is no longer valid. Understanding 3.3.7 Show Hide techniques and failures for 3.3.7 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 3.3.7 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.

G221: Provide data from a previous step in a process Not requesting the same information twice (Potential future technique) Back to top 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: support for password entry by password managers to reduce memory need, and copy and paste to reduce the cognitive burden of re-typing. Understanding 3.3.8 Show Hide techniques and failures for 3.3.8 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 3.3.8 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.

G218: Email link authentication 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 F109: Failure of Success Criterion 3.3.8 and 3.3.9 due to preventing password or code re-entry in the same format Back to top 3.3.9 Accessible Authentication (Enhanced) Level AAA (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. Understanding 3.3.9 Show Hide techniques and failures for 3.3.9 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 3.3.9 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. G218: Email link authentication 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.9 F109: Failure of Success Criterion 3.3.8 and 3.3.9 due to preventing password or code re-entry in the same format Back to top Principle 4 – Robust Content must be robust enough that it can be interpreted by a wide variety of user agents, including assistive technologies.

Guideline 4.1 – Compatible Maximize compatibility with current and future user agents, including assistive technologies. 4.1.1 Parsing Level A In content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features. Note 1: This Success Criterion should be considered as always satisfied for any content using HTML or XML. Note 2: Since this criterion was written, the HTML Living Standard has adopted specific requirements governing how user agents must handle incomplete tags, incorrect element nesting, duplicate attributes, and non-unique IDs. [HTML] Although the HTML Standard treats some of these cases as non-conforming for authors, it is considered to “allow these features” for the purposes of this Success Criterion because the specification requires that user agents support handling these cases consistently.

In practice, this criterion no longer provides any benefit to people with disabilities in itself. Issues such as missing roles due to inappropriately nested elements or incorrect states or names due to a duplicate ID are covered by different Success Criteria and should be reported under those criteria rather than as issues with 4.1.1. Understanding 4.1.1 Show Hide techniques and failures for 4.1.1 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 4.1.1 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. G134: Validating Web pages G192: Fully conforming to specifications H88: Using HTML according to spec Ensuring that Web pages can be parsed by using one of the following techniques: H74: Ensuring that opening and closing tags are used according to specification AND H93: Ensuring that id attributes are unique on a Web page AND H94: Ensuring that elements do not contain duplicate attributes H75: Ensuring that Web pages are well-formed Failures for Success Criterion 4.1.1 F70: Failure of Success Criterion 4.1.1 due to incorrect use of start and end tags or attribute markup F77: Failure of Success Criterion 4.1.1 due to duplicate values of type ID Back to top 4.1.2 Name, Role, Value Level A For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies.

Note 1: This success criterion is primarily for Web authors who develop or script their own user interface components. For example, standard HTML controls already meet this success criterion when used according to specification. Understanding 4.1.2 Show Hide techniques and failures for 4.1.2 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 4.1.2 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. Situation A: If using a standard user interface component in a markup language (e.g., HTML): ARIA14: Using aria-label to provide an invisible label where a visible label cannot be used ARIA16: Using aria-labelledby to provide a name for user interface controls G108: Using markup features to expose the name and role, allow user-settable properties to be directly set, and provide notification of changes H91: Using HTML form controls and links H44: Using label elements to associate text labels with form controls H64: Using the title attribute of the frame and iframe elements H65: Using the title attribute to identify form controls when the label element cannot be used H88: Using HTML according to spec Situation B: If using script or code to re-purpose a standard user interface component in a markup language: Exposing the names and roles, allowing user-settable properties to be directly set, and providing notification of changes using one of the following techniques: ARIA16: Using aria-labelledby to provide a name for user interface controls Situation C: If using a standard user interface component in a programming technology: G135: Using the accessibility API features of a technology to expose names and notification of changes PDF10: Providing labels for interactive form controls in PDF documents PDF12: Providing name, role, value information for form fields in PDF documents Situation D: If creating your own user interface component in a programming language: G10: Creating components using a technology that supports the accessibility notification of changes ARIA4: Using a WAI-ARIA role to expose the role of a user interface component ARIA5: Using WAI-ARIA state and property attributes to expose the state of a user interface component ARIA16: Using aria-labelledby to provide a name for user interface controls Failures for Success Criterion 4.1.2 F59: Failure of Success Criterion 4.1.2 due to using script to make div or span a user interface control in HTML without providing a role for the control F15: Failure of Success Criterion 4.1.2 due to implementing custom controls that do not use an accessibility API for the technology, or do so incompletely F20: Failure of Success Criterion 1.1.1 and 4.1.2 due to not updating text alternatives when changes to non-text content occur F68: Failure of Success Criterion 4.1.2 due to a user interface control not having a programmatically determined name F79: Failure of Success Criterion 4.1.2 due to the focus state of a user interface component not being programmatically determinable or no notification of change of focus state available F86: Failure of Success Criterion 4.1.2 due to not providing names for each part of a multi-part form field, such as a US telephone number F89: Failure of Success Criteria 2.4.4, 2.4.9 and 4.1.2 due to not providing an accessible name for an image which is the only content in a link Back to top 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.

Understanding 4.1.3 Show Hide techniques and failures for 4.1.3 Suffici ent Advisory Failures Sufficient Techniques for Success Criterion 4.1.3 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. Situation A: If a status message advises on the success or results of an action, or the state of an application: ARIA22: Using role=status to present status messages 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: ARIA19: Using ARIA role=alert or Live Regions to Identify Errors G83: Providing text descriptions to identify required fields that were not completed G84: Providing a text description when the user provides information that is not in the list of allowed values G85: Providing a text description when user input falls outside the required format or values G177: Providing suggested correction text G194: Providing spell checking and suggestions for text input Situation C: If a status message conveys information on the progress of a process: ARIA23: Using role=log to identify sequential information updates Using role="progressbar" (future link) ARIA22: Using role=status to present status messages AND G193: Providing help by an assistant in the Web page Advisory Techniques for Success Criterion 4.1.3 Using aria-live regions with chat clients (future link) Using role="marquee" (future link) Using role="timer" (future link) ARIA18: Using aria-alertdialog to Identify Errors SCR14: Using scripts to make nonessential alerts optional Failures for Success Criterion 4.1.3 F103: Failure of Success Criterion 4.1.3 due to providing status messages that cannot be programmatically determined through role or properties Using role="alert" or aria-live="assertive" on content which is not important and time-sensitive (future link) Back to top Contribute We welcome feedback and suggestions: This resource — report bugs and contribute directly to the Github repository Techniques — contribute new WCAG techniques Other — contribute corrections, updates, or new information related to techniques, failures, or other WCAG documentation, per the instructions for commenting Document Information Status: Updated 12 Nov 2023. Version 3.5.1. Lead Developer: Eric Eggert (W3C).

Project Lead: Shadi Abou-Zahra (W3C). Previous editors and developers: Gregg Vanderheiden, Loretta Guarino Reid, Ben Caldwell, Shawn Lawton Henry , Gez Lemon. The 2023 redesign was developed by the Education and Outreach Working Group ( EOWG ) and the Web Content Accessibility Guidelines Working Group ( WCAG WG ), with support from the WAI-DEV project , a project of the European Commission IST Programme. WAI Site Map Help with WAI Website Search Contacting WAI Feedback welcome to [email protected] (a publicly archived list) or [email protected] (a WAI staff-only list). Copyright © 2023 W3C ® ( MIT , ERCIM , Keio , Beihang ) Usage policies apply .