data "Web Content Accessibility Guidelines (WCAG) 2.2 Web Content Accessibility Guidelines (WCAG) 2.2 W3C Recommendation 05 October 2023 More details about this document This version: https://www.w3.org/TR/2023/REC-WCAG22-20231005/ Latest published version: https://www.w3.org/TR/WCAG22/ Latest editor's draft: https://w3c.github.io/wcag/guidelines/22/ History: https://www.w3.org/standards/history/WCAG22/ Commit history Implementation report: https://www.w3.org/WAI/WCAG22/implementation-report/ Previous Recommendation: https://www.w3.org/TR/WCAG21/ Editors: Alastair Campbell ( Nomensa ) Chuck Adams ( Oracle ) Rachael Bradley Montgomery ( Library of Congress ) Michael Cooper ( W3C ) Andrew Kirkpatrick ( Adobe ) Feedback: GitHub w3c/wcag ( pull requests , new issue , open issues ) Errata: Errata exists . See also translations . Copyright © 2020-2023 World Wide Web Consortium . W3C ® liability , trademark and document use rules apply. Abstract Web Content Accessibility Guidelines (WCAG) 2.2 covers a wide range of recommendations for making Web content more accessible." "Following these guidelines will make content more accessible to a wider range of people with disabilities, including accommodations for blindness and low vision, deafness and hearing loss, limited movement, speech disabilities, photosensitivity, and combinations of these, and some accommodation for learning disabilities and cognitive limitations; but will not address every user need for people with these disabilities. These guidelines address accessibility of web content on desktops, laptops, tablets, and mobile devices. Following these guidelines will also often make Web content more usable to users in general. WCAG 2.2 success criteria are written as testable statements that are not technology-specific. Guidance about satisfying the success criteria in specific technologies, as well as general information about interpreting the success criteria, is provided in separate documents. See Web Content Accessibility Guidelines (WCAG) Overview for an introduction and links to WCAG technical and educational material." "WCAG 2.2 extends Web Content Accessibility Guidelines 2.1 [ WCAG21 ], which was published as a W3C Recommendation June 2018. Content that conforms to WCAG 2.2 also conforms to WCAG 2.0 and WCAG 2.1. The WG intends that for policies requiring conformance to WCAG 2.0 or WCAG 2.1, WCAG 2.2 can provide an alternate means of conformance. The publication of WCAG 2.2 does not deprecate or supersede WCAG 2.0 or WCAG 2.1. While WCAG 2.0 and WCAG 2.1 remain W3C Recommendations, the W3C advises the use of WCAG 2.2 to maximize future applicability of accessibility efforts." "The W3C also encourages use of the most current version of WCAG when developing or updating Web accessibility policies. Status of This Document This section describes the status of this document at the time of its publication. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at https://www.w3.org/TR/. To comment, file an issue in the W3C WCAG GitHub repository . Although the proposed Success Criteria in this document reference issues tracking discussion, the Working Group requests that public comments be filed as new issues, one issue per discrete comment. It is free to create a GitHub account to file issues. If filing issues in GitHub is not feasible, send email to public-agwg-comments@w3.org ( comment archive )." "This document was published by the Accessibility Guidelines Working Group as a Recommendation using the Recommendation track . W3C recommends the wide deployment of this specification as a standard for the Web. A W3C Recommendation is a specification that, after extensive consensus-building, is endorsed by W3C and its Members, and has commitments from Working Group members to royalty-free licensing for implementations. This document was produced by a group operating under the 1 August 2017 W3C Patent Policy . W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent." "An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy . This document is governed by the 12 June 2023 W3C Process Document . Table of Contents Abstract Status of This Document Introduction Background on WCAG 2 WCAG 2 Layers of Guidance WCAG 2.2 Supporting Documents Requirements for WCAG 2.2 Comparison with WCAG 2.1 New Features in WCAG 2.2 Numbering in WCAG 2.2 Conformance to WCAG 2.2 Later Versions of Accessibility Guidelines 1. Perceivable 1.1 Text Alternatives 1.1.1 Non-text Content 1.2 Time-based Media 1.2.1 Audio-only and Video-only (Prerecorded) 1.2.2 Captions (Prerecorded) 1.2.3 Audio Description or Media Alternative (Prerecorded) 1.2.4 Captions (Live) 1.2.5 Audio Description (Prerecorded) 1.2.6 Sign Language (Prerecorded) 1.2.7 Extended Audio Description (Prerecorded) 1.2.8 Media Alternative (Prerecorded) 1.2.9 Audio-only (Live) 1.3 Adaptable 1.3.1 Info and Relationships 1.3.2 Meaningful Sequence 1.3.3 Sensory Characteristics 1.3.4 Orientation 1.3.5 Identify Input Purpose 1.3.6 Identify Purpose 1.4 Distinguishable 1.4.1 Use of Color 1.4.2 Audio Control 1.4.3 Contrast (Minimum) 1.4.4 Resize Text 1.4.5 Images of Text 1.4.6 Contrast (Enhanced) 1.4.7 Low or No Background Audio 1.4.8 Visual Presentation 1.4.9 Images of Text (No Exception) 1.4.10 Reflow 1.4.11 Non-text Contrast 1.4.12 Text Spacing 1.4.13 Content on Hover or Focus 2. Operable 2.1 Keyboard Accessible 2.1.1 Keyboard 2.1.2 No Keyboard Trap 2.1.3 Keyboard (No Exception) 2.1.4 Character Key Shortcuts 2.2 Enough Time 2.2.1 Timing Adjustable 2.2.2 Pause, Stop, Hide 2.2.3 No Timing 2.2.4 Interruptions 2.2.5 Re-authenticating 2.2.6 Timeouts 2.3 Seizures and Physical Reactions 2.3.1 Three Flashes or Below Threshold 2.3.2 Three Flashes 2.3.3 Animation from Interactions 2.4 Navigable 2.4.1 Bypass Blocks 2.4.2 Page Titled 2.4.3 Focus Order 2.4.4 Link Purpose (In Context) 2.4.5 Multiple Ways 2.4.6 Headings and Labels 2.4.7 Focus Visible 2.4.8 Location 2.4.9 Link Purpose (Link Only) 2.4.10 Section Headings 2.4.11 Focus Not Obscured (Minimum) 2.4.12 Focus Not Obscured (Enhanced) 2.4.13 Focus Appearance 2.5 Input Modalities 2.5.1 Pointer Gestures 2.5.2 Pointer Cancellation 2.5.3 Label in Name 2.5.4 Motion Actuation 2.5.5 Target Size (Enhanced) 2.5.6 Concurrent Input Mechanisms 2.5.7 Dragging Movements 2.5.8 Target Size (Minimum) 3." "Understandable 3.1 Readable 3.1.1 Language of Page 3.1.2 Language of Parts 3.1.3 Unusual Words 3.1.4 Abbreviations 3.1.5 Reading Level 3.1.6 Pronunciation 3.2 Predictable 3.2.1 On Focus 3.2.2 On Input 3.2.3 Consistent Navigation 3.2.4 Consistent Identification 3.2.5 Change on Request 3.2.6 Consistent Help 3.3 Input Assistance 3.3.1 Error Identification 3.3.2 Labels or Instructions 3.3.3 Error Suggestion 3.3.4 Error Prevention (Legal, Financial, Data) 3.3.5 Help 3.3.6 Error Prevention (All) 3.3.7 Redundant Entry 3.3.8 Accessible Authentication (Minimum) 3.3.9 Accessible Authentication (Enhanced) 4. Robust 4.1 Compatible 4.1.1 Parsing (Obsolete and removed) 4.1.2 Name, Role, Value 4.1.3 Status Messages 5. Conformance 5.1 Interpreting Normative Requirements 5.2 Conformance Requirements 5.2.1 Conformance Level 5.2.2 Full pages 5.2.3 Complete processes 5.2.4 Only Accessibility-Supported Ways of Using Technologies 5.2.5 Non-Interference 5.3 Conformance Claims (Optional) 5.3.1 Required Components of a Conformance Claim 5.3.2 Optional Components of a Conformance Claim 5.4 Statement of Partial Conformance - Third Party Content 5.5 Statement of Partial Conformance - Language 5.6 Privacy Considerations 5.7 Security Considerations 6. Glossary 7. Input Purposes for User Interface Components A." "Change Log B. Acknowledgments B.1 Participants of the AG WG active in the development of this document: B.2 Other previously active WCAG WG participants and other contributors to WCAG 2.0, WCAG 2.1, or supporting resources B.3 Enabling funders C. References C.1 Informative references Introduction This section is non-normative. Background on WCAG 2 Web Content Accessibility Guidelines (WCAG) 2.2 defines how to make Web content more accessible to people with disabilities. Accessibility involves a wide range of disabilities, including visual, auditory, physical, speech, cognitive, language, learning, and neurological disabilities." "Although these guidelines cover a wide range of issues, they are not able to address the needs of people with all types, degrees, and combinations of disability. These guidelines also make Web content more usable by older individuals with changing abilities due to aging and often improve usability for users in general. WCAG 2.2 is developed through the W3C process in cooperation with individuals and organizations around the world, with a goal of providing a shared standard for Web content accessibility that meets the needs of individuals, organizations, and governments internationally. WCAG 2.2 builds on WCAG 2.0 [ WCAG20 ] and WCAG 2.1 [ WCAG21 ], which in turn built on WCAG 1.0 [ WAI-WEBCONTENT ] and is designed to apply broadly to different Web technologies now and in the future, and to be testable with a combination of automated testing and human evaluation. For an introduction to WCAG, see the Web Content Accessibility Guidelines (WCAG) Overview . Significant challenges were encountered in defining additional criteria to address cognitive, language, and learning disabilities, including a short timeline for development as well as challenges in reaching consensus on testability, implementability, and international considerations of proposals." "Work will carry on in this area in future versions of WCAG. We encourage authors to refer to our supplemental guidance on improving inclusion for people with disabilities, including learning and cognitive disabilities, people with low-vision, and more . Web accessibility depends not only on accessible content but also on accessible Web browsers and other user agents. Authoring tools also have an important role in Web accessibility. For an overview of how these components of Web development and interaction work together, see: Essential Components of Web Accessibility User Agent Accessibility Guidelines (UAAG) Overview Authoring Tool Accessibility Guidelines (ATAG) Overview Where this document refers to WCAG 2 it is intended to mean any and all versions of WCAG that start with 2." "WCAG 2 Layers of Guidance The individuals and organizations that use WCAG vary widely and include Web designers and developers, policy makers, purchasing agents, teachers, and students. In order to meet the varying needs of this audience, several layers of guidance are provided including overall principles , general guidelines , testable success criteria and a rich collection of sufficient techniques , advisory techniques , and documented common failures with examples, resource links and code. Principles - At the top are four principles that provide the foundation for Web accessibility: perceivable, operable, understandable, and robust . See also Understanding the Four Principles of Accessibility . Guidelines - Under the principles are guidelines." "The 13 guidelines provide the basic goals that authors should work toward in order to make content more accessible to users with different disabilities. The guidelines are not testable, but provide the framework and overall objectives to help authors understand the success criteria and better implement the techniques. Success Criteria - For each guideline, testable success criteria are provided to allow WCAG 2.2 to be used where requirements and conformance testing are necessary such as in design specification, purchasing, regulation, and contractual agreements. In order to meet the needs of different groups and different situations, three levels of conformance are defined: A (lowest), AA, and AAA (highest). Additional information on WCAG levels can be found in Understanding Levels of Conformance ." "Sufficient and Advisory Techniques - For each of the guidelines and success criteria in the WCAG 2.2 document itself, the working group has also documented a wide variety of techniques . The techniques are informative and fall into two categories: those that are sufficient for meeting the success criteria and those that are advisory . The advisory techniques go beyond what is required by the individual success criteria and allow authors to better address the guidelines. Some advisory techniques address accessibility barriers that are not covered by the testable success criteria. Where common failures are known, these are also documented." "See also Sufficient and Advisory Techniques in Understanding WCAG 2.2 . All of these layers of guidance (principles, guidelines, success criteria, and sufficient and advisory techniques) work together to provide guidance on how to make content more accessible. Authors are encouraged to view and apply all layers that they are able to, including the advisory techniques, in order to best address the needs of the widest possible range of users. Note that even content that conforms at the highest level (AAA) will not be accessible to individuals with all types, degrees, or combinations of disability, particularly in the cognitive, language, and learning areas. Authors are encouraged to consider the full range of techniques, including the advisory techniques, Making Content Usable for People with Cognitive and Learning Disabilities , as well as to seek relevant advice about current best practice to ensure that Web content is accessible, as far as possible, to this community." "Metadata may assist users in finding content most suitable for their needs. WCAG 2.2 Supporting Documents The WCAG 2.2 document is designed to meet the needs of those who need a stable, referenceable technical standard. Other documents, called supporting documents, are based on the WCAG 2.2 document and address other important purposes, including the ability to be updated to describe how WCAG would be applied with new technologies. Supporting documents include: How to Meet WCAG 2.2 - A customizable quick reference to WCAG 2.2 that includes all of the guidelines, success criteria, and techniques for authors to use as they are developing and evaluating Web content. This includes content from WCAG 2.0, 2.1 2.2 and can be filtered in many ways to help authors focus on relevant content." "Understanding WCAG 2.2 - A guide to understanding and implementing WCAG 2.2. There is a short ""Understanding"" document for each guideline and success criterion in WCAG 2.2 as well as key topics. Techniques for WCAG 2.2 - A collection of techniques and common failures, each in a separate document that includes a description, examples, code and tests. The WCAG 2 Documents - A brief introduction to the WCAG 2 supporting documents and supplemental guidance. What's New in WCAG 2.2 introduces the new success criteria with persona quotes that illustrate the accessibility issues." "See Web Content Accessibility Guidelines (WCAG) Overview for a description of the WCAG 2.2 supporting material, including education resources related to WCAG 2. Additional resources covering topics such as the business case for Web accessibility, planning implementation to improve the accessibility of Web sites, and accessibility policies are listed in WAI Resources . Requirements for WCAG 2.2 WCAG 2.2 meets a set of requirements for WCAG 2.2 which, in turn, inherit requirements from previous WCAG 2 versions. Requirements structure the overall framework of guidelines and ensure backwards compatibility. The Working Group also used a less formal set of acceptance criteria for success criteria, to help ensure success criteria are similar in style and quality to those in WCAG 2.0. These requirements constrained what could be included in WCAG 2.2." "This constraint was important to preserve its nature as a dot-release of WCAG 2. Comparison with WCAG 2.1 WCAG 2.2 was initiated with the goal to continue the work of WCAG 2.1: Improving accessibility guidance for three major groups: users with cognitive or learning disabilities, users with low vision, and users with disabilities on mobile devices. Many ways to meet these needs were proposed and evaluated, and a set of these were refined by the Working Group. Structural requirements inherited from WCAG 2.0, clarity and impact of proposals, and timeline led to the final set of success criteria included in this version. The Working Group considers that WCAG 2.2 incrementally advances web content accessibility guidance for all these areas, but underscores that not all user needs are met by these guidelines." "WCAG 2.2 builds on and is backwards compatible with WCAG 2.1, meaning web pages that conform to WCAG 2.2 are at least as accessible as pages that conform to WCAG 2.1. Requirements have been added that build on 2.1 and 2.0. WCAG 2.2 has removed one success criterion, 4.1.1 Parsing . Authors that are required by policy to conform with WCAG 2.0 or 2.1 will be able to update content to WCAG 2.2, but may need to continue to test and report 4.1.1. Authors following more than one version of the guidelines should be aware of the following additions. New Features in WCAG 2.2 WCAG 2.2 extends WCAG 2.1 by adding new success criteria, definitions to support them, and guidelines to organize the additions. This additive approach helps to make it clear that sites which conform to WCAG 2.2 also conform to WCAG 2.1." "The Accessibility Guidelines Working Group recommends that sites adopt WCAG 2.2 as their new conformance target, even if formal obligations mention previous versions, to provide improved accessibility and to anticipate future policy changes. The following success criteria are new in WCAG 2.2: 2.4.11 Focus Not Obscured (Minimum) (AA) 2.4.12 Focus Not Obscured (Enhanced) (AAA) 2.4.13 Focus Appearance (AAA) 2.5.7 Dragging Movements (AA) 2.5.8 Target Size (Minimum) (AA) 3.2.6 Consistent Help (A) 3.3.7 Redundant Entry (A) 3.3.8 Accessible Authentication (Minimum) (AA) 3.3.9 Accessible Authentication (Enhanced) (AAA) The new success criteria may reference new terms that have also been added to the glossary and form part of the normative requirements of the success criteria. WCAG 2.2 also introduces new sections detailing aspects of the specification which may impact privacy and security . Numbering in WCAG 2.2 In order to avoid confusion for implementers for whom backwards compatibility to WCAG 2 versions is important, new success criteria in WCAG 2.2 have been appended to the end of the set of success criteria within their guideline. This avoids the need to change the section number of success criteria from WCAG 2, which would be caused by inserting new success criteria between existing success criteria in the guideline, but it means success criteria in each guideline are no longer grouped by conformance level." "The order of success criteria within each guideline does not imply information about conformance level; only the conformance level indicator (A / AA / AAA) on the success criterion itself indicates this. The WCAG 2.2 Quick Reference will provide a way to view success criteria grouped by conformance level, along with many other filter and sort options. Conformance to WCAG 2.2 WCAG 2.2 uses the same conformance model as WCAG 2.0. It is intended that sites that conform to WCAG 2.2 also conform to WCAG 2.0 and WCAG 2.1, which means they meet the requirements of any policies that reference WCAG 2.0 or WCAG 2.1, while also better meeting the needs of users on the current Web. Later Versions of Accessibility Guidelines In parallel with WCAG 2.2, the Accessibility Guidelines Working Group is developing another major version of accessibility guidelines." "The result of this work is expected to be a more substantial restructuring of web accessibility guidance than would be realistic for dot-releases of WCAG 2. The work follows a research-focused, user-centered design methodology to produce the most effective and flexible outcome, including the roles of content authoring, user agent support, and authoring tool support. This is a multi-year effort, so WCAG 2.2 is needed as an interim measure to provide updated web accessibility guidance to reflect changes on the web since the publication of WCAG 2.0. The Working Group might also develop additional interim versions, continuing with WCAG 2.2, on a similar short timeline to provide additional support while the major version is completed. 1." "Perceivable Information and user interface components must be presentable to users in ways they can perceive. Guideline 1.1 Text Alternatives Understanding Text Alternatives | How to Meet Text Alternatives Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language. Success Criterion 1.1.1 Non-text Content Understanding Non-text Content | How to Meet Non-text Content (Level A) All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for the situations listed below. Controls, Input If non-text content is a control or accepts user input, then it has a name that describes its purpose. (Refer to Success Criterion 4.1.2 for additional requirements for controls and content that accepts user input.) Time-Based Media If non-text content is time-based media, then text alternatives at least provide descriptive identification of the non-text content." "(Refer to Guideline 1.2 for additional requirements for media.) Test If non-text content is a test or exercise that would be invalid if presented in text , then text alternatives at least provide descriptive identification of the non-text content. Sensory If non-text content is primarily intended to create a specific sensory experience , then text alternatives at least provide descriptive identification of the non-text content. CAPTCHA If the purpose of non-text content is to confirm that content is being accessed by a person rather than a computer, then text alternatives that identify and describe the purpose of the non-text content are provided, and alternative forms of CAPTCHA using output modes for different types of sensory perception are provided to accommodate different disabilities. Decoration, Formatting, Invisible If non-text content is pure decoration , is used only for visual formatting, or is not presented to users, then it is implemented in a way that it can be ignored by assistive technology . Guideline 1.2 Time-based Media Understanding Time-based Media | How to Meet Time-based Media Provide alternatives for time-based media." "Success Criterion 1.2.1 Audio-only and Video-only (Prerecorded) Understanding Audio-only and Video-only (Prerecorded) | How to Meet Audio-only and Video-only (Prerecorded) (Level A) For prerecorded audio-only and prerecorded video-only media, the following are true, except when the audio or video is a media alternative for text and is clearly labeled as such: Prerecorded Audio-only An alternative for time-based media is provided that presents equivalent information for prerecorded audio-only content. Prerecorded Video-only Either an alternative for time-based media or an audio track is provided that presents equivalent information for prerecorded video-only content. Success Criterion 1.2.2 Captions (Prerecorded) Understanding Captions (Prerecorded) | How to Meet Captions (Prerecorded) (Level A) Captions are provided for all prerecorded audio content in synchronized media , except when the media is a media alternative for text and is clearly labeled as such. Success Criterion 1.2.3 Audio Description or Media Alternative (Prerecorded) Understanding Audio Description or Media Alternative (Prerecorded) | How to Meet Audio Description or Media Alternative (Prerecorded) (Level A) An alternative for time-based media or audio description of the prerecorded video content is provided for synchronized media , except when the media is a media alternative for text and is clearly labeled as such. Success Criterion 1.2.4 Captions (Live) Understanding Captions (Live) | How to Meet Captions (Live) (Level AA) Captions are provided for all live audio content in synchronized media ." "Success Criterion 1.2.5 Audio Description (Prerecorded) Understanding Audio Description (Prerecorded) | How to Meet Audio Description (Prerecorded) (Level AA) Audio description is provided for all prerecorded video content in synchronized media . Success Criterion 1.2.6 Sign Language (Prerecorded) Understanding Sign Language (Prerecorded) | How to Meet Sign Language (Prerecorded) (Level AAA) Sign language interpretation is provided for all prerecorded audio content in synchronized media . Success Criterion 1.2.7 Extended Audio Description (Prerecorded) Understanding Extended Audio Description (Prerecorded) | How to Meet Extended Audio Description (Prerecorded) (Level AAA) Where pauses in foreground audio are insufficient to allow audio descriptions to convey the sense of the video, extended audio description is provided for all prerecorded video content in synchronized media . Success Criterion 1.2.8 Media Alternative (Prerecorded) Understanding Media Alternative (Prerecorded) | How to Meet Media Alternative (Prerecorded) (Level AAA) An alternative for time-based media is provided for all prerecorded synchronized media and for all prerecorded video-only media. Success Criterion 1.2.9 Audio-only (Live) Understanding Audio-only (Live) | How to Meet Audio-only (Live) (Level AAA) An alternative for time-based media that presents equivalent information for live audio-only content is provided." "Guideline 1.3 Adaptable Understanding Adaptable | How to Meet Adaptable Create content that can be presented in different ways (for example simpler layout) without losing information or structure. Success Criterion 1.3.1 Info and Relationships Understanding Info and Relationships | How to Meet Info and Relationships (Level A) Information, structure , and relationships conveyed through presentation can be programmatically determined or are available in text. Success Criterion 1.3.2 Meaningful Sequence Understanding Meaningful Sequence | How to Meet Meaningful Sequence (Level A) When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined . Success Criterion 1.3.3 Sensory Characteristics Understanding Sensory Characteristics | How to Meet Sensory Characteristics (Level A) Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, color, size, visual location, orientation, or sound. Note For requirements related to color, refer to Guideline 1.4 ." "Success Criterion 1.3.4 Orientation Understanding Orientation | How to Meet Orientation (Level AA) Content does not restrict its view and operation to a single display orientation, such as portrait or landscape, unless a specific display orientation is essential . Note Examples where a particular display orientation may be essential are a bank check, a piano application, slides for a projector or television, or virtual reality content where content is not necessarily restricted to landscape or portrait display orientation. Success Criterion 1.3.5 Identify Input Purpose Understanding Identify Input Purpose | How to Meet Identify Input Purpose (Level AA) 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. Success Criterion 1.3.6 Identify Purpose Understanding Identify Purpose | How to Meet Identify Purpose (Level AAA) In content implemented using markup languages, the purpose of user interface components , icons, and regions can be programmatically determined . Guideline 1.4 Distinguishable Understanding Distinguishable | How to Meet Distinguishable Make it easier for users to see and hear content including separating foreground from background." "Success Criterion 1.4.1 Use of Color Understanding Use of Color | How to Meet Use of Color (Level A) Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. Note This success criterion addresses color perception specifically. Other forms of perception are covered in Guideline 1.3 including programmatic access to color and other visual presentation coding. Success Criterion 1.4.2 Audio Control Understanding Audio Control | How to Meet Audio Control (Level A) If any audio on a Web page plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level. Note Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether or not it is used to meet other success criteria) must meet this success criterion." "See Conformance Requirement 5: Non-Interference . Success Criterion 1.4.3 Contrast (Minimum) Understanding Contrast (Minimum) | How to Meet Contrast (Minimum) (Level AA) The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for the following: Large Text Large-scale text and images of large-scale text have a contrast ratio of at least 3:1; Incidental Text or images of text that are part of an inactive user interface component , that are pure decoration , that are not visible to anyone, or that are part of a picture that contains significant other visual content, have no contrast requirement. Logotypes Text that is part of a logo or brand name has no contrast requirement. Success Criterion 1.4.4 Resize Text Understanding Resize Text | How to Meet Resize Text (Level AA) Except for captions and images of text , text can be resized without assistive technology up to 200 percent without loss of content or functionality. Success Criterion 1.4.5 Images of Text Understanding Images of Text | How to Meet Images of Text (Level AA) If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text except for the following: Customizable The image of text can be visually customized to the user's requirements; Essential A particular presentation of text is essential to the information being conveyed." "Note Logotypes (text that is part of a logo or brand name) are considered essential. Success Criterion 1.4.6 Contrast (Enhanced) Understanding Contrast (Enhanced) | How to Meet Contrast (Enhanced) (Level AAA) The visual presentation of text and images of text has a contrast ratio of at least 7:1, except for the following: Large Text Large-scale text and images of large-scale text have a contrast ratio of at least 4.5:1; Incidental Text or images of text that are part of an inactive user interface component , that are pure decoration , that are not visible to anyone, or that are part of a picture that contains significant other visual content, have no contrast requirement. Logotypes Text that is part of a logo or brand name has no contrast requirement. Success Criterion 1.4.7 Low or No Background Audio Understanding Low or No Background Audio | How to Meet 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. Note Per the definition of ""decibel,"" background sound that meets this requirement will be approximately four times quieter than the foreground speech content. Success Criterion 1.4.8 Visual Presentation Understanding Visual Presentation | How to Meet Visual Presentation (Level AAA) For the visual presentation of blocks of text , a mechanism is available to achieve the following: Foreground and background colors can be selected by the user. Width is no more than 80 characters or glyphs (40 if CJK). Text is not justified (aligned to both the left and the right margins)." "Line spacing (leading) is at least space-and-a-half within paragraphs, and paragraph spacing is at least 1.5 times larger than the line spacing. Text can be resized without assistive technology up to 200 percent in a way that does not require the user to scroll horizontally to read a line of text on a full-screen window . Note 1 Content is not required to use these values. The requirement is that a mechanism is available for users to change these presentation aspects. The mechanism can be provided by the browser or other user agent." "Content is not required to provide the mechanism. Note 2 Writing systems for some languages use different presentation aspects to improve readability and legibility. If a presentation aspect in this success criterion is not used in a writing system, content in that writing system does not need to use that presentation setting and can conform without it. Authors are encouraged to follow guidance for improving readability and legibility of text in their writing system. Success Criterion 1.4.9 Images of Text (No Exception) Understanding Images of Text (No Exception) | How to Meet Images of Text (No Exception) (Level AAA) Images of text are only used for pure decoration or where a particular presentation of text is essential to the information being conveyed." "Note Logotypes (text that is part of a logo or brand name) are considered essential. Success Criterion 1.4.10 Reflow Understanding Reflow | How to Meet Reflow (Level AA) Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions for: Vertical scrolling content at a width equivalent to 320 CSS pixels ; Horizontal scrolling content at a height equivalent to 256 CSS pixels . Except for parts of the content which require two-dimensional layout for usage or meaning. Note 1 320 CSS pixels is equivalent to a starting viewport width of 1280 CSS pixels wide at 400% zoom. For web content which is designed to scroll horizontally (e.g., with vertical text), 256 CSS pixels is equivalent to a starting viewport height of 1024 CSS pixels at 400% zoom." "Note 2 Examples of content which requires two-dimensional layout are images required for understanding (such as maps and diagrams), video, games, presentations, data tables (not individual cells), and interfaces where it is necessary to keep toolbars in view while manipulating content. It is acceptable to provide two-dimensional scrolling for such parts of the content. Success Criterion 1.4.11 Non-text Contrast Understanding Non-text Contrast | How to Meet Non-text Contrast (Level AA) 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. Success Criterion 1.4.12 Text Spacing Understanding Text Spacing | How to Meet Text Spacing (Level AA) In content implemented using markup languages that support the following text style properties , no loss of content or functionality occurs by setting all of the following and by changing no other style property: Line height (line spacing) to at least 1.5 times the font size; Spacing following paragraphs to at least 2 times the font size; Letter spacing (tracking) to at least 0.12 times the font size; Word spacing to at least 0.16 times the font size. Exception: Human languages and scripts that do not make use of one or more of these text style properties in written text can conform using only the properties that exist for that combination of language and script." "Note 1 Content is not required to use these text spacing values. The requirement is to ensure that when a user overrides the authored text spacing, content or functionality is not lost. Note 2 Writing systems for some languages use different text spacing settings, such as paragraph start indent. Authors are encouraged to follow locally available guidance for improving readability and legibility of text in their writing system. Success Criterion 1.4.13 Content on Hover or Focus Understanding Content on Hover or Focus | How to Meet Content on Hover or Focus (Level AA) Where receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden, the following are true: Dismissible A mechanism is available to dismiss the additional content without moving pointer hover or keyboard focus, unless the additional content communicates an input error or does not obscure or replace other content; Hoverable If pointer hover can trigger the additional content, then the pointer can be moved over the additional content without the additional content disappearing; Persistent The additional content remains visible until the hover or focus trigger is removed, the user dismisses it, or its information is no longer valid." "Exception: The visual presentation of the additional content is controlled by the user agent and is not modified by the author. Note 1 Examples of additional content controlled by the user agent include browser tooltips created through use of the HTML title attribute [ HTML ]. Note 2 Custom tooltips, sub-menus, and other nonmodal popups that display on hover and focus are examples of additional content covered by this criterion. Note 3 This criterion applies to content that appears in addition to the triggering component itself. Since hidden components that are made visible on keyboard focus (such as links used to skip to another part of a page) do not present additional content they are not covered by this criterion." "2. Operable User interface components and navigation must be operable. Guideline 2.1 Keyboard Accessible Understanding Keyboard Accessible | How to Meet Keyboard Accessible Make all functionality available from a keyboard. Success Criterion 2.1.1 Keyboard Understanding Keyboard | How to Meet Keyboard (Level A) All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints. Note 1 This exception relates to the underlying function, not the input technique." "For example, if using handwriting to enter text, the input technique (handwriting) requires path-dependent input but the underlying function (text input) does not. Note 2 This does not forbid and should not discourage providing mouse input or other input methods in addition to keyboard operation. Success Criterion 2.1.2 No Keyboard Trap Understanding No Keyboard Trap | How to Meet No Keyboard Trap (Level A) If keyboard focus can be moved to a component of the page using a keyboard interface , then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away. Note Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether it is used to meet other success criteria or not) must meet this success criterion. See Conformance Requirement 5: Non-Interference ." "Success Criterion 2.1.3 Keyboard (No Exception) Understanding Keyboard (No Exception) | How to Meet Keyboard (No Exception) (Level AAA) All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes. Success Criterion 2.1.4 Character Key Shortcuts Understanding Character Key Shortcuts | How to Meet Character Key Shortcuts (Level A) 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. Guideline 2.2 Enough Time Understanding Enough Time | How to Meet Enough Time Provide users enough time to read and use content. Success Criterion 2.2.1 Timing Adjustable Understanding Timing Adjustable | How to Meet 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. Note This success criterion helps ensure that users can complete tasks without unexpected changes in content or context that are a result of a time limit." "This success criterion should be considered in conjunction with Success Criterion 3.2.1 , which puts limits on changes of content or context as a result of user action. Success Criterion 2.2.2 Pause, Stop, Hide Understanding Pause, Stop, Hide | How to Meet Pause, Stop, Hide (Level A) For moving, blinking , scrolling, or auto-updating information, all of the following are true: Moving, blinking, scrolling For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to pause , stop, or hide it unless the movement, blinking, or scrolling is part of an activity where it is essential ; and Auto-updating For any auto-updating information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it or to control the frequency of the update unless the auto-updating is part of an activity where it is essential. Note 1 For requirements related to flickering or flashing content, refer to Guideline 2.3 . Note 2 Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether it is used to meet other success criteria or not) must meet this success criterion. See Conformance Requirement 5: Non-Interference ." "Note 3 Content that is updated periodically by software or that is streamed to the user agent is not required to preserve or present information that is generated or received between the initiation of the pause and resuming presentation, as this may not be technically possible, and in many situations could be misleading to do so. Note 4 An animation that occurs as part of a preload phase or similar situation can be considered essential if interaction cannot occur during that phase for all users and if not indicating progress could confuse users or cause them to think that content was frozen or broken. Success Criterion 2.2.3 No Timing Understanding No Timing | How to Meet No Timing (Level AAA) Timing is not an essential part of the event or activity presented by the content, except for non-interactive synchronized media and real-time events . Success Criterion 2.2.4 Interruptions Understanding Interruptions | How to Meet Interruptions (Level AAA) Interruptions can be postponed or suppressed by the user, except interruptions involving an emergency . Success Criterion 2.2.5 Re-authenticating Understanding Re-authenticating | How to Meet Re-authenticating (Level AAA) When an authenticated session expires, the user can continue the activity without loss of data after re-authenticating." "Success Criterion 2.2.6 Timeouts Understanding Timeouts | How to Meet Timeouts (Level AAA) 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. Note Privacy regulations may require explicit user consent before user identification has been authenticated and before user data is preserved. In cases where the user is a minor, explicit consent may not be solicited in most jurisdictions, countries or regions. Consultation with privacy professionals and legal counsel is advised when considering data preservation as an approach to satisfy this success criterion. Guideline 2.3 Seizures and Physical Reactions Understanding Seizures and Physical Reactions | How to Meet Seizures and Physical Reactions Do not design content in a way that is known to cause seizures or physical reactions." "Success Criterion 2.3.1 Three Flashes or Below Threshold Understanding Three Flashes or Below Threshold | How to Meet Three Flashes or Below Threshold (Level A) Web pages do not contain anything that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds . Note Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether it is used to meet other success criteria or not) must meet this success criterion. See Conformance Requirement 5: Non-Interference . Success Criterion 2.3.2 Three Flashes Understanding Three Flashes | How to Meet Three Flashes (Level AAA) Web pages do not contain anything that flashes more than three times in any one second period. Success Criterion 2.3.3 Animation from Interactions Understanding Animation from Interactions | How to Meet Animation from Interactions (Level AAA) Motion animation triggered by interaction can be disabled, unless the animation is essential to the functionality or the information being conveyed." "Guideline 2.4 Navigable Understanding Navigable | How to Meet Navigable Provide ways to help users navigate, find content, and determine where they are. Success Criterion 2.4.1 Bypass Blocks Understanding Bypass Blocks | How to Meet Bypass Blocks (Level A) A mechanism is available to bypass blocks of content that are repeated on multiple Web pages . Success Criterion 2.4.2 Page Titled Understanding Page Titled | How to Meet Page Titled (Level A) Web pages have titles that describe topic or purpose. Success Criterion 2.4.3 Focus Order Understanding Focus Order | How to Meet Focus Order (Level A) If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability. Success Criterion 2.4.4 Link Purpose (In Context) Understanding Link Purpose (In Context) | How to Meet Link Purpose (In Context) (Level A) The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context , except where the purpose of the link would be ambiguous to users in general ." "Success Criterion 2.4.5 Multiple Ways Understanding Multiple Ways | How to Meet Multiple Ways (Level AA) More than one way is available to locate a Web page within a set of Web pages except where the Web Page is the result of, or a step in, a process . Success Criterion 2.4.6 Headings and Labels Understanding Headings and Labels | How to Meet Headings and Labels (Level AA) Headings and labels describe topic or purpose. Success Criterion 2.4.7 Focus Visible Understanding Focus Visible | How to Meet Focus Visible (Level AA) Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. Success Criterion 2.4.8 Location Understanding Location | How to Meet Location (Level AAA) Information about the user's location within a set of Web pages is available. Success Criterion 2.4.9 Link Purpose (Link Only) Understanding Link Purpose (Link Only) | How to Meet Link Purpose (Link Only) (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 ." "Success Criterion 2.4.10 Section Headings Understanding Section Headings | How to Meet Section Headings (Level AAA) Section headings are used to organize the content. Note 1 ""Heading"" is used in its general sense and includes titles and other ways to add a heading to different types of content. Note 2 This success criterion covers sections within writing, not user interface components . User interface components are covered under Success Criterion 4.1.2 . Success Criterion 2.4.11 Focus Not Obscured (Minimum) Understanding Focus Not Obscured (Minimum) | How to Meet Focus Not Obscured (Minimum) (Level AA) [New] When a user interface component receives keyboard focus, the component is not entirely hidden due to author-created content." "Note 1 Where content in a configurable interface can be repositioned by the user, then only the initial positions of user-movable content are considered for testing and conformance of this Success Criterion. Note 2 Content opened by the user may obscure the component receiving focus. If the user can reveal the focused component without advancing the keyboard focus, the component with focus is not considered hidden due to author-created content. Success Criterion 2.4.12 Focus Not Obscured (Enhanced) Understanding Focus Not Obscured (Enhanced) | How to Meet Focus Not Obscured (Enhanced) (Level AAA) [New] When a user interface component receives keyboard focus, no part of the component is hidden by author-created content. Success Criterion 2.4.13 Focus Appearance Understanding Focus Appearance | How to Meet Focus Appearance (Level AAA) [New] When the keyboard focus indicator is visible, an area of the focus indicator meets all the following: is at least as large as the area of a 2 CSS pixel thick perimeter of the unfocused component or sub-component, and has a contrast ratio of at least 3:1 between the same pixels in the focused and unfocused states." "Exceptions: The focus indicator is determined by the user agent and cannot be adjusted by the author, or The focus indicator and the indicator's background color are not modified by the author. 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 sub-components that may receive a focus indicator are menu items in an opened drop-down menu, or focusable cells in a grid." "Note 3 Contrast calculations can be based on colors defined within the technology (such as HTML, CSS and SVG). Pixels modified by user agent resolution enhancements and anti-aliasing can be ignored. Guideline 2.5 Input Modalities Understanding Input Modalities | How to Meet Input Modalities Make it easier for users to operate functionality through various inputs beyond keyboard. Success Criterion 2.5.1 Pointer Gestures Understanding Pointer Gestures | How to Meet Pointer Gestures (Level A) 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 gesture is essential . 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). Success Criterion 2.5.2 Pointer Cancellation Understanding Pointer Cancellation | How to Meet Pointer Cancellation (Level A) 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 . Note 1 Functions that emulate a keyboard or numeric keypad key press are considered essential. Note 2 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)." "Success Criterion 2.5.3 Label in Name Understanding Label in Name | How to Meet Label in Name (Level A) For user interface components with labels that include text or images of text , the name contains the text that is presented visually. Note A best practice is to have the text of the label at the start of the name. Success Criterion 2.5.4 Motion Actuation Understanding Motion Actuation | How to Meet Motion Actuation (Level A) 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. Success Criterion 2.5.5 Target Size (Enhanced) Understanding Target Size (Enhanced) | How to Meet Target Size (Enhanced) (Level AAA) 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. Success Criterion 2.5.6 Concurrent Input Mechanisms Understanding Concurrent Input Mechanisms | How to Meet Concurrent Input Mechanisms (Level AAA) 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." "Success Criterion 2.5.7 Dragging Movements Understanding Dragging Movements | How to Meet Dragging Movements (Level AA) [New] 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). Success Criterion 2.5.8 Target Size (Minimum) Understanding Target Size (Minimum) | How to Meet Target Size (Minimum) (Level AA) [New] 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. 3. Understandable Information and the operation of the user interface must be understandable." "Guideline 3.1 Readable Understanding Readable | How to Meet Readable Make text content readable and understandable. Success Criterion 3.1.1 Language of Page Understanding Language of Page | How to Meet Language of Page (Level A) The default human language of each Web page can be programmatically determined . Success Criterion 3.1.2 Language of Parts Understanding Language of Parts | How to Meet 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. Success Criterion 3.1.3 Unusual Words Understanding Unusual Words | How to Meet 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 . Success Criterion 3.1.4 Abbreviations Understanding Abbreviations | How to Meet Abbreviations (Level AAA) A mechanism for identifying the expanded form or meaning of abbreviations is available." "Success Criterion 3.1.5 Reading Level Understanding Reading Level | How to Meet 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. Success Criterion 3.1.6 Pronunciation Understanding Pronunciation | How to Meet 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. Guideline 3.2 Predictable Understanding Predictable | How to Meet Predictable Make Web pages appear and operate in predictable ways. Success Criterion 3.2.1 On Focus Understanding On Focus | How to Meet On Focus (Level A) When any user interface component receives focus, it does not initiate a change of context . Success Criterion 3.2.2 On Input Understanding On Input | How to Meet 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." "Success Criterion 3.2.3 Consistent Navigation Understanding Consistent Navigation | How to Meet 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. Success Criterion 3.2.4 Consistent Identification Understanding Consistent Identification | How to Meet Consistent Identification (Level AA) Components that have the same functionality within a set of Web pages are identified consistently. Success Criterion 3.2.5 Change on Request Understanding Change on Request | How to Meet Change on Request (Level AAA) Changes of context are initiated only by user request or a mechanism is available to turn off such changes. Success Criterion 3.2.6 Consistent Help Understanding Consistent Help | How to Meet Consistent Help (Level A) [New] 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 Help mechanisms may be provided directly on the page, or may be provided via a direct link to a different page containing the information." "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). Guideline 3.3 Input Assistance Understanding Input Assistance | How to Meet Input Assistance Help users avoid and correct mistakes." "Success Criterion 3.3.1 Error Identification Understanding Error Identification | How to Meet 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. Success Criterion 3.3.2 Labels or Instructions Understanding Labels or Instructions | How to Meet Labels or Instructions (Level A) Labels or instructions are provided when content requires user input. Success Criterion 3.3.3 Error Suggestion Understanding Error Suggestion | How to Meet 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. Success Criterion 3.3.4 Error Prevention (Legal, Financial, Data) Understanding Error Prevention (Legal, Financial, Data) | How to Meet 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. Success Criterion 3.3.5 Help Understanding Help | How to Meet Help (Level AAA) Context-sensitive help is available. Success Criterion 3.3.6 Error Prevention (All) Understanding Error Prevention (All) | How to Meet 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." "Success Criterion 3.3.7 Redundant Entry Understanding Redundant Entry | How to Meet Redundant Entry (Level A) [New] 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 the content, or previously entered information is no longer valid. Success Criterion 3.3.8 Accessible Authentication (Minimum) Understanding Accessible Authentication (Minimum) | How to Meet Accessible Authentication (Minimum) (Level AA) [New] 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 ""Object recognition"" and ""Personal content"" may be represented by images, video, or audio. 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. Success Criterion 3.3.9 Accessible Authentication (Enhanced) Understanding Accessible Authentication (Enhanced) | How to Meet Accessible Authentication (Enhanced) (Level AAA) [New] 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." "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 Understanding Compatible | How to Meet Compatible Maximize compatibility with current and future user agents, including assistive technologies. Success Criterion 4.1.1 Parsing (Obsolete and removed) Understanding Parsing (Obsolete and removed) | How to Meet Parsing (Obsolete and removed) Note This criterion was originally adopted to address problems that assistive technology had directly parsing HTML. Assistive technology no longer has any need to directly parse HTML." "Consequently, these problems either no longer exist or are addressed by other criteria. This criterion no longer has utility and is removed. Success Criterion 4.1.2 Name, Role, Value Understanding Name, Role, Value | How to Meet 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 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." "Success Criterion 4.1.3 Status Messages Understanding Status Messages | How to Meet Status Messages (Level AA) 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. 5. Conformance This section lists requirements for conformance to WCAG 2.2. It also gives information about how to make conformance claims, which are optional. Finally, it describes what it means to be accessibility supported , since only accessibility-supported ways of using technologies can be relied upon for conformance." "Understanding Conformance includes further explanation of the accessibility-supported concept. 5.1 Interpreting Normative Requirements The main content of WCAG 2.2 is normative and defines requirements that impact conformance claims. Introductory material, appendices, sections marked as ""non-normative"", diagrams, examples, and notes are informative (non-normative). Non-normative material provides advisory information to help interpret the guidelines but does not create requirements that impact a conformance claim. The key words MAY , MUST , MUST NOT , NOT RECOMMENDED , RECOMMENDED , SHOULD , and SHOULD NOT are to be interpreted as described in [ RFC2119 ]." "5.2 Conformance Requirements In order for a Web page to conform to WCAG 2.2, all of the following conformance requirements must be satisfied: 5.2.1 Conformance Level One of the following levels of conformance is met in full. For Level A conformance (the minimum level of conformance), the Web page satisfies all the Level A Success Criteria, or a conforming alternate version is provided. For Level AA conformance, the Web page satisfies all the Level A and Level AA Success Criteria, or a Level AA conforming alternate version is provided. For Level AAA conformance, the Web page satisfies all the Level A, Level AA and Level AAA Success Criteria, or a Level AAA conforming alternate version is provided. Note 1 Although conformance can only be achieved at the stated levels, authors are encouraged to report (in their claim) any progress toward meeting success criteria from all levels beyond the achieved level of conformance." "Note 2 It is not recommended that Level AAA conformance be required as a general policy for entire sites because it is not possible to satisfy all Level AAA Success Criteria for some content. 5.2.2 Full pages Conformance (and conformance level) is for full Web page(s) only, and cannot be achieved if part of a Web page is excluded. Note 1 For the purpose of determining conformance, alternatives to part of a page's content are considered part of the page when the alternatives can be obtained directly from the page, e.g., a long description or an alternative presentation of a video. Note 2 Authors of Web pages that cannot conform due to content outside of the author's control may consider a Statement of Partial Conformance . Note 3 A full page includes each variation of the page that is automatically presented by the page for various screen sizes (e.g." "variations in a responsive Web page). Each of these variations needs to conform (or needs to have a conforming alternate version) in order for the entire page to conform. 5.2.3 Complete processes When a Web page is one of a series of Web pages presenting a process (i.e., a sequence of steps that need to be completed in order to accomplish an activity), all Web pages in the process conform at the specified level or better. (Conformance is not possible at a particular level if any page in the process does not conform at that level or better.) Example An online store has a series of pages that are used to select and purchase products. All pages in the series from start to finish (checkout) conform in order for any page that is part of the process to conform. 5.2.4 Only Accessibility-Supported Ways of Using Technologies Only accessibility-supported ways of using technologies are relied upon to satisfy the success criteria." "Any information or functionality that is provided in a way that is not accessibility supported is also available in a way that is accessibility supported. (See Understanding accessibility support .) 5.2.5 Non-Interference If technologies are used in a way that is not accessibility supported , or if they are used in a non-conforming way, then they do not block the ability of users to access the rest of the page. In addition, the Web page as a whole continues to meet the conformance requirements under each of the following conditions: when any technology that is not relied upon is turned on in a user agent, when any technology that is not relied upon is turned off in a user agent, and when any technology that is not relied upon is not supported by a user agent In addition, the following success criteria apply to all content on the page, including content that is not otherwise relied upon to meet conformance, because failure to meet them could interfere with any use of the page: 1.4.2 - Audio Control , 2.1.2 - No Keyboard Trap , 2.3.1 - Three Flashes or Below Threshold , and 2.2.2 - Pause, Stop, Hide . Note If a page cannot conform (for example, a conformance test page or an example page), it cannot be included in the scope of conformance or in a conformance claim. For more information, including examples, see Understanding Conformance Requirements ." "5.3 Conformance Claims (Optional) Conformance is defined only for Web pages . However, a conformance claim may be made to cover one page, a series of pages, or multiple related Web pages. 5.3.1 Required Components of a Conformance Claim Conformance claims are not required . Authors can conform to WCAG 2.2 without making a claim. However, if a conformance claim is made, then the conformance claim must include the following information: Date of the claim Guidelines title, version and URI ""Web Content Accessibility Guidelines 2.2 at https://www.w3.org/TR/WCAG22/ "" Conformance level satisfied: (Level A, AA or AAA) A concise description of the Web pages , such as a list of URIs for which the claim is made, including whether subdomains are included in the claim." "Note 1 The Web pages may be described by list or by an expression that describes all of the URIs included in the claim. Note 2 Web-based products that do not have a URI prior to installation on the customer's Web site may have a statement that the product would conform when installed. A list of the Web content technologies relied upon . Note 3 If a conformance logo is used, it would constitute a claim and must be accompanied by the required components of a conformance claim listed above. 5.3.2 Optional Components of a Conformance Claim In addition to the required components of a conformance claim above, consider providing additional information to assist users." "Recommended additional information includes: A list of success criteria beyond the level of conformance claimed that have been met. This information should be provided in a form that users can use, preferably machine-readable metadata. A list of the specific technologies that are "" used but not relied upon ."" A list of user agents, including assistive technologies that were used to test the content. A list of specific accessibility characteristics of the content, provided in machine-readable metadata. Information about any additional steps taken that go beyond the success criteria to enhance accessibility." "A machine-readable metadata version of the list of specific technologies that are relied upon . A machine-readable metadata version of the conformance claim. Note 1 Refer to Understanding Conformance Claims for more information and example conformance claims. Note 2 Refer to Understanding Metadata for more information about the use of metadata in conformance claims. 5.4 Statement of Partial Conformance - Third Party Content Web pages that will later have additional content added can use a 'statement of partial conformance'." "For example, an email program, a blog, an article that allows users to add comments, or applications supporting user-contributed content. Another example would be a page, such as a portal or news site, composed of content aggregated from multiple contributors, or sites that automatically insert content from other sources over time, such as when advertisements are inserted dynamically. In these cases, it is not possible to know at the time of original posting what the uncontrolled content of the pages will be. It is important to note that the uncontrolled content can affect the accessibility of the controlled content as well. Two options are available: A determination of conformance can be made based on best knowledge." "If a page of this type is monitored and repaired (non-conforming content is removed or brought into conformance) within two business days, then a determination or claim of conformance can be made since, except for errors in externally contributed content which are corrected or removed when encountered, the page conforms. No conformance claim can be made if it is not possible to monitor or correct non-conforming content; OR A ""statement of partial conformance"" may be made that the page does not conform, but could conform if certain parts were removed. The form of that statement would be, ""This page does not conform, but would conform to WCAG 2.2 at level X if the following parts from uncontrolled sources were removed."" In addition, the following would also be true of uncontrolled content that is described in the statement of partial conformance: It is not content that is under the author's control. It is described in a way that users can identify (e.g., they cannot be described as ""all parts that we do not control"" unless they are clearly marked as such.) 5.5 Statement of Partial Conformance - Language A ""statement of partial conformance due to language"" may be made when the page does not conform, but would conform if accessibility support existed for (all of) the language(s) used on the page. The form of that statement would be, ""This page does not conform, but would conform to WCAG 2.2 at level X if accessibility support existed for the following language(s):"" 5.6 Privacy Considerations This section is non-normative." "Success Criteria within this specification which the Working Group has identified possible implications for privacy, either by providing protections for end users or which are important for web site providers to take in to consideration when implementing features designed to protect user privacy, are listed below. This list reflects the current understanding of the Working Group but other Success Criteria may have privacy implications that the Working Group is not aware of at the time of publishing. Success Criteria within this specification that may relate to privacy are: 2.2.6 Timeouts (AAA) 3.3.7 Redundant Entry (A) 5.7 Security Considerations This section is non-normative. Success Criteria within this specification which the Working Group has identified possible implications for security, either by providing protections for end users or which are important for web site providers to take in to consideration when implementing features designed to protect user security, are listed below. This list reflects the current understanding of the Working Group but other Success Criteria may have security implications that the Working Group is not aware of at the time of publishing." "Success Criteria within this specification that may relate to security are: 1.1.1 Non-text Content (A) 1.3.5 Identify Input Purpose (AA) 1.4.7 Low or No Background Audio (AAA) 2.2.1 Timing Adjustable (A) 2.2.5 Re-authenticating (AAA) 2.2.6 Timeouts (AAA) 2.5.6 Concurrent Input Mechanisms (AAA) 3.3.3 Error Suggestion (AA) 3.3.7 Redundant Entry (A) 3.3.8 Accessible Authentication (Minimum) (AA) 3.3.9 Accessible Authentication (Enhanced) (AAA) 6. Glossary abbreviation shortened form of a word, phrase, or name where the abbreviation has not become part of the language Note 1 This includes initialisms and acronyms where: initialisms are shortened forms of a name or phrase made from the initial letters of words or syllables contained in that name or phrase Note 2 Not defined in all languages. Example 1 SNCF is a French initialism that contains the initial letters of the Société Nationale des Chemins de Fer , the French national railroad. Example 2 ESP is an initialism for extrasensory perception. acronyms are abbreviated forms made from the initial letters or parts of other words (in a name or phrase) which may be pronounced as a word Example 3 NOAA is an acronym made from the initial letters of the National Oceanic and Atmospheric Administration in the United States." "Note 3 Some companies have adopted what used to be an initialism as their company name. In these cases, the new name of the company is the letters (for example, Ecma) and the word is no longer considered an abbreviation. accessibility supported supported by users' assistive technologies as well as the accessibility features in browsers and other user agents To qualify as an accessibility-supported use of a Web content technology (or feature of a technology), both 1 and 2 must be satisfied for a Web content technology (or feature): The way that the Web content technology is used must be supported by users' assistive technology (AT). This means that the way that the technology is used has been tested for interoperability with users' assistive technology in the human language(s) of the content, AND The Web content technology must have accessibility-supported user agents that are available to users. This means that at least one of the following four statements is true: The technology is supported natively in widely-distributed user agents that are also accessibility supported (such as HTML and CSS); OR The technology is supported in a widely-distributed plug-in that is also accessibility supported; OR The content is available in a closed environment, such as a university or corporate network, where the user agent required by the technology and used by the organization is also accessibility supported; OR The user agent(s) that support the technology are accessibility supported and are available for download or purchase in a way that: does not cost a person with a disability any more than a person without a disability and is as easy to find and obtain for a person with a disability as it is for a person without disabilities." "Note 1 The Accessibility Guidelines Working Group and the W3C do not specify which or how much support by assistive technologies there must be for a particular use of a Web technology in order for it to be classified as accessibility supported. (See Level of Assistive Technology Support Needed for ""Accessibility Support"" .) Note 2 Web technologies can be used in ways that are not accessibility supported as long as they are not relied upon and the page as a whole meets the conformance requirements, including Conformance Requirement 4 and Conformance Requirement 5 . Note 3 When a Web Technology is used in a way that is ""accessibility supported,"" it does not imply that the entire technology or all uses of the technology are supported. Most technologies, including HTML, lack support for at least one feature or use. Pages conform to WCAG only if the uses of the technology that are accessibility supported can be relied upon to meet WCAG requirements." "Note 4 When citing Web content technologies that have multiple versions, the version(s) supported should be specified. Note 5 One way for authors to locate uses of a technology that are accessibility supported would be to consult compilations of uses that are documented to be accessibility supported. (See Understanding Accessibility-Supported Web Technology Uses .) Authors, companies, technology vendors, or others may document accessibility-supported ways of using Web content technologies. However, all ways of using technologies in the documentation would need to meet the definition of accessibility-supported Web content technologies above. alternative for time-based media document including correctly sequenced text descriptions of time-based visual and auditory information and providing a means for achieving the outcomes of any time-based interaction Note A screenplay used to create the synchronized media content would meet this definition only if it was corrected to accurately represent the final synchronized media after editing. ambiguous to users in general the purpose cannot be determined from the link and all information of the Web page presented to the user simultaneously with the link (i.e., readers without disabilities would not know what a link would do until they activated it) Example The word guava in the following sentence ""One of the notable exports is guava"" is a link." "The link could lead to a definition of guava, a chart listing the quantity of guava exported or a photograph of people harvesting guava. Until the link is activated, all readers are unsure and the person with a disability is not at any disadvantage. ASCII art picture created by a spatial arrangement of characters or glyphs (typically from the 95 printable characters defined by ASCII) assistive technology (as used in this document) hardware and/or software that acts as a user agent , or along with a mainstream user agent, to provide functionality to meet the requirements of users with disabilities that go beyond those offered by mainstream user agents Note 1 Functionality provided by assistive technology includes alternative presentations (e.g., as synthesized speech or magnified content), alternative input methods (e.g., voice), additional navigation or orientation mechanisms, and content transformations (e.g., to make tables more accessible). Note 2 Assistive technologies often communicate data and messages with mainstream user agents by using and monitoring APIs. Note 3 The distinction between mainstream user agents and assistive technologies is not absolute. Many mainstream user agents provide some features to assist individuals with disabilities. The basic difference is that mainstream user agents target broad and diverse audiences that usually include people with and without disabilities." "Assistive technologies target narrowly defined populations of users with specific disabilities. The assistance provided by an assistive technology is more specific and appropriate to the needs of its target users. The mainstream user agent may provide important functionality to assistive technologies like retrieving Web content from program objects or parsing markup into identifiable bundles. Example Assistive technologies that are important in the context of this document include the following: screen magnifiers, and other visual reading assistants, which are used by people with visual, perceptual and physical print disabilities to change text font, size, spacing, color, synchronization with speech, etc. in order to improve the visual readability of rendered text and images; screen readers, which are used by people who are blind to read textual information through synthesized speech or braille; text-to-speech software, which is used by some people with cognitive, language, and learning disabilities to convert text into synthetic speech; speech recognition software, which may be used by people who have some physical disabilities; alternative keyboards, which are used by people with certain physical disabilities to simulate the keyboard (including alternate keyboards that use head pointers, single switches, sip/puff and other special input devices.); alternative pointing devices, which are used by people with certain physical disabilities to simulate mouse pointing and button activations." "audio the technology of sound reproduction Note Audio can be created synthetically (including speech synthesis), recorded from real world sounds, or both. audio description narration added to the soundtrack to describe important visual details that cannot be understood from the main soundtrack alone Note 1 Audio description of video provides information about actions, characters, scene changes, on-screen text, and other visual content. Note 2 In standard audio description, narration is added during existing pauses in dialogue. (See also extended audio description .) Note 3 Where all of the video information is already provided in existing audio , no additional audio description is necessary. Note 4 Also called ""video description"" and ""descriptive narration."" audio-only a time-based presentation that contains only audio (no video and no interaction) blinking switch back and forth between two visual states in a way that is meant to draw attention Note See also flash . It is possible for something to be large enough and blink brightly enough at the right frequency to be also classified as a flash." "blocks of text more than one sentence of text CAPTCHA initialism for ""Completely Automated Public Turing test to tell Computers and Humans Apart"" Note 1 CAPTCHA tests often involve asking the user to type in text that is displayed in an obscured image or audio file. Note 2 A Turing test is any system of tests designed to differentiate a human from a computer. It is named after famed computer scientist Alan Turing. The term was coined by researchers at Carnegie Mellon University. captions synchronized visual and/or text alternative for both speech and non-speech audio information needed to understand the media content Note 1 Captions are similar to dialogue-only subtitles except captions convey not only the content of spoken dialogue, but also equivalents for non-dialogue audio information needed to understand the program content, including sound effects, music, laughter, speaker identification and location. Note 2 Closed Captions are equivalents that can be turned on and off with some players." "Note 3 Open Captions are any captions that cannot be turned off. For example, if the captions are visual equivalent images of text embedded in video . Note 4 Captions should not obscure or obstruct relevant information in the video. Note 5 In some countries, captions are called subtitles. Note 6 Audio descriptions can be, but do not need to be, captioned since they are descriptions of information that is already presented visually." "changes of context major changes that, if made without user awareness, can disorient users who are not able to view the entire page simultaneously Changes in context include changes of: user agent ; viewport ; focus; content that changes the meaning of the Web page Note A change of content is not always a change of context. Changes in content, such as an expanding outline, dynamic menu, or a tab control do not necessarily change the context, unless they also change one of the above (e.g., focus). Example Opening a new window, moving focus to a different component, going to a new page (including anything that would look to a user as if they had moved to a new page) or significantly re-arranging the content of a page are examples of changes of context. Cognitive function test [New] A task that requires the user to remember, manipulate, or transcribe information. Examples include, but are not limited to: memorization, such as remembering a username, password, set of characters, images, or patterns." "The common identifiers name, e-mail, and phone number are not considered cognitive function tests as they are personal to the user and consistent across Web sites; transcription, such as typing in characters; use of correct spelling; performance of calculations; solving of puzzles. conformance satisfying all the requirements of a given standard, guideline or specification conforming alternate version version that conforms at the designated level, and provides all of the same information and functionality in the same human language , and is as up to date as the non-conforming content, and for which at least one of the following is true: the conforming version can be reached from the non-conforming page via an accessibility-supported mechanism , or the non-conforming version can only be reached from the conforming version, or the non-conforming version can only be reached from a conforming page that also provides a mechanism to reach the conforming version Note 1 In this definition, ""can only be reached"" means that there is some mechanism, such as a conditional redirect, that prevents a user from ""reaching"" (loading) the non-conforming page unless the user had just come from the conforming version. Note 2 The alternate version does not need to be matched page for page with the original (e.g., the conforming alternate version may consist of multiple pages). Note 3 If multiple language versions are available, then conforming alternate versions are required for each language offered. Note 4 Alternate versions may be provided to accommodate different technology environments or user groups." "Each version should be as conformant as possible. One version would need to be fully conformant in order to meet conformance requirement 1 . Note 5 The conforming alternative version does not need to reside within the scope of conformance, or even on the same Web site, as long as it is as freely available as the non-conforming version. Note 6 Alternate versions should not be confused with supplementary content , which support the original page and enhance comprehension. Note 7 Setting user preferences within the content to produce a conforming version is an acceptable mechanism for reaching another version as long as the method used to set the preferences is accessibility supported." "See Understanding Conforming Alternate Versions content (Web content) information and sensory experience to be communicated to the user by means of a user agent , including code or markup that defines the content's structure , presentation , and interactions context-sensitive help help text that provides information related to the function currently being performed Note Clear labels can act as context-sensitive help. contrast ratio (L1 + 0.05) / (L2 + 0.05), where L1 is the relative luminance of the lighter of the colors, and L2 is the relative luminance of the darker of the colors. Note 1 Contrast ratios can range from 1 to 21 (commonly written 1:1 to 21:1). Note 2 Because authors do not have control over user settings as to how text is rendered (for example font smoothing or anti-aliasing), the contrast ratio for text can be evaluated with anti-aliasing turned off. Note 3 For the purpose of Success Criteria 1.4.3 and 1.4.6, contrast is measured with respect to the specified background over which the text is rendered in normal usage." "If no background color is specified, then white is assumed. Note 4 Background color is the specified color of content over which the text is to be rendered in normal usage. It is a failure if no background color is specified when the text color is specified, because the user's default background color is unknown and cannot be evaluated for sufficient contrast. For the same reason, it is a failure if no text color is specified when a background color is specified. Note 5 When there is a border around the letter, the border can add contrast and would be used in calculating the contrast between the letter and its background." "A narrow border around the letter would be used as the letter. A wide border around the letter that fills in the inner details of the letters acts as a halo and would be considered background. Note 6 WCAG conformance should be evaluated for color pairs specified in the content that an author would expect to appear adjacent in typical presentation. Authors need not consider unusual presentations, such as color changes made by the user agent, except where caused by authors' code. correct reading sequence any sequence where words and paragraphs are presented in an order that does not change the meaning of the content CSS pixel visual angle of about 0.0213 degrees A CSS pixel is the canonical unit of measure for all lengths and measurements in CSS. This unit is density-independent, and distinct from actual hardware pixels present in a display." "User agents and operating systems should ensure that a CSS pixel is set as closely as possible to the CSS Values and Units Module Level 3 reference pixel [ css3-values ], which takes into account the physical dimensions of the display and the assumed viewing distance (factors that cannot be determined by content authors). down-event platform event that occurs when the trigger stimulus of a pointer is depressed The down-event may have different names on different platforms, such as ""touchstart"" or ""mousedown"". dragging movement [New] an operation where the pointer engages with an element on the down-event and the element (or a representation of its position) follows the pointer until an up-event Note Examples of draggable elements include list items, text elements, and images. emergency a sudden, unexpected situation or occurrence that requires immediate action to preserve health, safety, or property encloses [New] solidly bounds or surrounds essential if removed, would fundamentally change the information or functionality of the content, and information and functionality cannot be achieved in another way that would conform extended audio description audio description that is added to an audiovisual presentation by pausing the video so that there is time to add additional description Note This technique is only used when the sense of the video would be lost without the additional audio description and the pauses between dialogue/narration are too short. flash a pair of opposing changes in relative luminance that can cause seizures in some people if it is large enough and in the right frequency range Note 1 See general flash and red flash thresholds for information about types of flash that are not allowed." "Note 2 See also blinking . focus indicator [New] pixels that are changed to visually indicate when a user interface component is in a focused state functionality processes and outcomes achievable through user action general flash and red flash thresholds a flash or rapidly changing image sequence is below the threshold (i.e., content passes ) if any of the following are true: there are no more than three general flashes and / or no more than three red flashes within any one-second period; or the combined area of flashes occurring concurrently occupies no more than a total of .006 steradians within any 10 degree visual field on the screen (25% of any 10 degree visual field on the screen) at typical viewing distance where: A general flash is defined as a pair of opposing changes in relative luminance of 10% or more of the maximum relative luminance (1.0) where the relative luminance of the darker image is below 0.80; and where ""a pair of opposing changes"" is an increase followed by a decrease, or a decrease followed by an increase, and A red flash is defined as any pair of opposing transitions involving a saturated red Exception: Flashing that is a fine, balanced, pattern such as white noise or an alternating checkerboard pattern with ""squares"" smaller than 0.1 degree (of visual field at typical viewing distance) on a side does not violate the thresholds. Note 1 For general software or Web content, using a 341 x 256 pixel rectangle anywhere on the displayed screen area when the content is viewed at 1024 x 768 pixels will provide a good estimate of a 10 degree visual field for standard screen sizes and viewing distances (e.g., 15-17 inch screen at 22-26 inches). This resolution of 75 - 85 ppi is known to be lower, and thus more conservative than the nominal CSS pixel resolution of 96 ppi in CSS specifications. Higher resolutions displays showing the same rendering of the content yield smaller and safer images so it is lower resolutions that are used to define the thresholds." "Note 2 A transition is the change in relative luminance (or relative luminance/color for red flashing) between adjacent peaks and valleys in a plot of relative luminance (or relative luminance/color for red flashing) measurement against time. A flash consists of two opposing transitions. Note 3 The new working definition in the field for ""pair of opposing transitions involving a saturated red"" (from WCAG 2.2) is a pair of opposing transitions where, one transition is either to or from a state with a value R/(R + G + B) that is greater than or equal to 0.8, and the difference between states is more than 0.2 (unitless) in the CIE 1976 UCS chromaticity diagram. [ ISO_9241-391 ] Note 4 Tools are available that will carry out analysis from video screen capture. However, no tool is necessary to evaluate for this condition if flashing is less than or equal to 3 flashes in any one second." "Content automatically passes (see #1 and #2 above). human language language that is spoken, written or signed (through visual or tactile means) to communicate with humans Note See also sign language . idiom phrase whose meaning cannot be deduced from the meaning of the individual words and the specific words cannot be changed without losing the meaning Note Idioms cannot be translated directly, word for word, without losing their (cultural or language-dependent) meaning. Example 1 In English, ""spilling the beans"" means ""revealing a secret."" However, ""knocking over the beans"" or ""spilling the vegetables"" does not mean the same thing. Example 2 In Japanese, the phrase "" さじを投げる "" literally translates into ""he throws a spoon,"" but it means that there is nothing he can do and finally he gives up." "Example 3 In Dutch, "" Hij ging met de kippen op stok "" literally translates into ""He went to roost with the chickens,"" but it means that he went to bed early. image of text text that has been rendered in a non-text form (e.g., an image) in order to achieve a particular visual effect Note This does not include text that is part of a picture that contains significant other visual content. Example A person's name on a nametag in a photograph. informative for information purposes and not required for conformance Note Content required for conformance is referred to as "" normative ."" input error information provided by the user that is not accepted Note This includes: Information that is required by the Web page but omitted by the user Information that is provided by the user but that falls outside the required data format or values jargon words used in a particular way by people in a particular field Example The word StickyKeys is jargon from the field of assistive technology/accessibility. keyboard interface interface used by software to obtain keystroke input Note 1 A keyboard interface allows users to provide keystroke input to programs even if the native technology does not contain a keyboard." "Example A touchscreen PDA has a keyboard interface built into its operating system as well as a connector for external keyboards. Applications on the PDA can use the interface to obtain keyboard input either from an external keyboard or from other applications that provide simulated keyboard output, such as handwriting interpreters or speech-to-text applications with ""keyboard emulation"" functionality. Note 2 Operation of the application (or parts of the application) through a keyboard-operated mouse emulator, such as MouseKeys, does not qualify as operation through a keyboard interface because operation of the program is through its pointing device interface, not through its keyboard interface. keyboard shortcut alternative means of triggering an action by the pressing of one or more keys label text or other component with a text alternative that is presented to a user to identify a component within Web content Note 1 A label is presented to all users whereas the name may be hidden and only exposed by assistive technology. In many (but not all) cases the name and the label are the same." "Note 2 The term label is not limited to the label element in HTML. large scale (text) with at least 18 point or 14 point bold or font size that would yield equivalent size for Chinese, Japanese and Korean (CJK) fonts Note 1 Fonts with extraordinarily thin strokes or unusual features and characteristics that reduce the familiarity of their letter forms are harder to read, especially at lower contrast levels. Note 2 Font size is the size when the content is delivered. It does not include resizing that may be done by a user. Note 3 The actual size of the character that a user sees is dependent both on the author-defined size and the user's display or user agent settings." "For many mainstream body text fonts, 14 and 18 point is roughly equivalent to 1.2 and 1.5 em or to 120% or 150% of the default size for body text (assuming that the body font is 100%), but authors would need to check this for the particular fonts in use. When fonts are defined in relative units, the actual point size is calculated by the user agent for display. The point size should be obtained from the user agent, or calculated based on font metrics as the user agent does, when evaluating this success criterion. Users who have low vision would be responsible for choosing appropriate settings. Note 4 When using text without specifying the font size, the smallest font size used on major browsers for unspecified text would be a reasonable size to assume for the font. If a level 1 heading is rendered in 14pt bold or higher on major browsers, then it would be reasonable to assume it is large text." "Relative scaling can be calculated from the default sizes in a similar fashion. Note 5 The 18 and 14 point sizes for roman texts are taken from the minimum size for large print (14pt) and the larger standard font size (18pt). For other fonts such as CJK languages, the ""equivalent"" sizes would be the minimum large print size used for those languages and the next larger standard large print size. legal commitments transactions where the person incurs a legally binding obligation or benefit Example A marriage license, a stock trade (financial and legal), a will, a loan, adoption, signing up for the army, a contract of any type, etc. link purpose nature of the result obtained by activating a hyperlink live information captured from a real-world event and transmitted to the receiver with no more than a broadcast delay Note 1 A broadcast delay is a short (usually automated) delay, for example used in order to give the broadcaster time to cue or censor the audio (or video) feed, but not sufficient to allow significant editing." "Note 2 If information is completely computer generated, it is not live. lower secondary education level the two or three year period of education that begins after completion of six years of school and ends nine years after the beginning of primary education Note This definition is based on the International Standard Classification of Education [ UNESCO ]. mechanism process or technique for achieving a result Note 1 The mechanism may be explicitly provided in the content, or may be relied upon to be provided by either the platform or by user agents , including assistive technologies . Note 2 The mechanism needs to meet all success criteria for the conformance level claimed. media alternative for text media that presents no more information than is already presented in text (directly or via text alternatives) Note A media alternative for text is provided for those who benefit from alternate representations of text." "Media alternatives for text may be audio-only, video-only (including sign-language video), or audio-video. motion animation addition of steps between conditions to create the illusion of movement or to give a sense of a smooth transition Example For example, an element which moves into place or changes size while appearing is considered to be animated. An element which appears instantly without transitioning is not using animation. Motion animation does not include changes of color, blurring, or opacity which do not change the perceived size, shape, or position of the element. minimum bounding box [New] the smallest enclosing rectangle aligned to the horizontal axis within which all the points of a shape lie." "For components which wrap onto multiple lines as part of a sentence or block of text (such as hypertext links), the bounding box is based on how the component would appear on a single line. name text by which software can identify a component within Web content to the user Note 1 The name may be hidden and only exposed by assistive technology, whereas a label is presented to all users. In many (but not all) cases, the label and the name are the same. Note 2 This is unrelated to the name attribute in HTML. navigated sequentially navigated in the order defined for advancing focus (from one element to the next) using a keyboard interface non-text content any content that is not a sequence of characters that can be programmatically determined or where the sequence is not expressing something in human language Note This includes ASCII Art (which is a pattern of characters), emoticons, leetspeak (which uses character substitution), and images representing text normative required for conformance Note 1 One may conform in a variety of well-defined ways to this document." "Note 2 Content identified as "" informative "" or ""non-normative"" is never required for conformance . on a full-screen window on the most common sized desktop/laptop display with the viewport maximized Note Since people generally keep their computers for several years, it is best not to rely on the latest desktop/laptop display resolutions but to consider the common desktop/laptop display resolutions over the course of several years when making this evaluation. paused stopped by user request and not resumed until requested by user perimeter [New] continuous line forming the boundary of a shape not including shared pixels, or the minimum bounding box , whichever is shortest. Example The perimeter calculation for a 2 CSS pixel perimeter around a rectangle is 4 h +4 w , where h is the height and w is the width. For a 2 CSS pixel perimeter around a circle it is 4𝜋 r ." "pointer input input from a device that can target a specific coordinate (or set of coordinates) on a screen, such as a mouse, pen, or touch contact Note See the Pointer Events definition for ""pointer"" [ pointerevents ]. prerecorded information that is not live presentation rendering of the content in a form to be perceived by users primary education level six year time period that begins between the ages of five and seven, possibly without any previous education Note This definition is based on the International Standard Classification of Education [ UNESCO ]. process series of user actions where each action is required in order to complete an activity Example 1 Successful use of a series of Web pages on a shopping site requires users to view alternative products, prices and offers, select products, submit an order, provide shipping information and provide payment information. Example 2 An account registration page requires successful completion of a Turing test before the registration form can be accessed. programmatically determined (programmatically determinable) determined by software from author-supplied data provided in a way that different user agents , including assistive technologies , can extract and present this information to users in different modalities Example 1 Determined in a markup language from elements and attributes that are accessed directly by commonly available assistive technology." "Example 2 Determined from technology-specific data structures in a non-markup language and exposed to assistive technology via an accessibility API that is supported by commonly available assistive technology. programmatically determined link context additional information that can be programmatically determined from relationships with a link, combined with the link text, and presented to users in different modalities Example In HTML, information that is programmatically determinable from a link in English includes text that is in the same paragraph, list, or table cell as the link or in a table header cell that is associated with the table cell that contains the link. Note Since screen readers interpret punctuation, they can also provide the context from the current sentence, when the focus is on a link in that sentence. programmatically set set by software using methods that are supported by user agents, including assistive technologies pure decoration serving only an aesthetic purpose, providing no information, and having no functionality Note Text is only purely decorative if the words can be rearranged or substituted without changing their purpose. Example The cover page of a dictionary has random words in very light text in the background." "real-time event event that a) occurs at the same time as the viewing and b) is not completely generated by the content Example 1 A Webcast of a live performance (occurs at the same time as the viewing and is not prerecorded). Example 2 An on-line auction with people bidding (occurs at the same time as the viewing). Example 3 Live humans interacting in a virtual world using avatars (is not completely generated by the content and occurs at the same time as the viewing). region perceivable, programmatically determined section of content Note In HTML, any area designated with a landmark role would be a region. relationships meaningful associations between distinct pieces of content relative luminance the relative brightness of any point in a colorspace, normalized to 0 for darkest black and 1 for lightest white Note 1 For the sRGB colorspace, the relative luminance of a color is defined as L = 0.2126 * R + 0.7152 * G + 0.0722 * B where R , G and B are defined as: if RsRGB <= 0.04045 then R = RsRGB/12.92 else R = ((RsRGB+0.055)/1.055) ^ 2.4 if GsRGB <= 0.04045 then G = GsRGB/12.92 else G = ((GsRGB+0.055)/1.055) ^ 2.4 if BsRGB <= 0.04045 then B = BsRGB/12.92 else B = ((BsRGB+0.055)/1.055) ^ 2.4 and RsRGB, GsRGB, and BsRGB are defined as: RsRGB = R8bit/255 GsRGB = G8bit/255 BsRGB = B8bit/255 The ""^"" character is the exponentiation operator." "(Formula taken from [ SRGB ].) Note 2 Before May 2021 the value of 0.04045 in the definition was different (0.03928). It was taken from an older version of the specification and has been updated. It has no practical effect on the calculations in the context of these guidelines. Note 3 Almost all systems used today to view Web content assume sRGB encoding. Unless it is known that another color space will be used to process and display the content, authors should evaluate using sRGB colorspace." "If using other color spaces, see Understanding Success Criterion 1.4.3 . Note 4 If dithering occurs after delivery, then the source color value is used. For colors that are dithered at the source, the average values of the colors that are dithered should be used (average R, average G, and average B). Note 5 Tools are available that automatically do the calculations when testing contrast and flash. Note 6 A separate page giving the relative luminance definition using MathML to display the formulas is available." "relied upon (technologies that are) the content would not conform if that technology is turned off or is not supported role text or number by which software can identify the function of a component within Web content Example A number that indicates whether an image functions as a hyperlink, command button, or check box. same functionality same result when used Example A submit ""search"" button on one Web page and a ""find"" button on another Web page may both have a field to enter a term and list topics in the Web site related to the term submitted. In this case, they would have the same functionality but would not be labeled consistently. same relative order same position relative to other items Note Items are considered to be in the same relative order even if other items are inserted or removed from the original order. For example, expanding navigation menus may insert an additional level of detail or a secondary navigation section may be inserted into the reading order." "satisfies a success criterion the success criterion does not evaluate to 'false' when applied to the page section a self-contained portion of written content that deals with one or more related topics or thoughts Note A section may consist of one or more paragraphs and include graphics, tables, lists and sub-sections. set of web pages collection of web pages that share a common purpose and that are created by the same author, group or organization Example Examples include: a publication which is split across multiple Web pages, where each page contains one chapter or other significant section of the work. The publication is logically a single contiguous unit, and contains navigation features that enable access to the full set of pages. an e-commerce website shows products in a set of Web pages that all share the same navigation and identification. However, when progressing to the checkout process, the template changes; the navigation and other elements are removed, so the pages in that process are functionally and visually different." "The checkout pages are not part of the set of product pages. a blog on a sub-domain (e.g. blog.example.com) which has a different navigation and is authored by a distinct set of people from the pages on the primary domain (example.com). Note Different language versions would be considered different sets of Web pages. sign language a language using combinations of movements of the hands and arms, facial expressions, or body positions to convey meaning sign language interpretation translation of one language, generally a spoken language, into a sign language Note True sign languages are independent languages that are unrelated to the spoken language(s) of the same country or region." "single pointer pointer input that operates with one point of contact with the screen, including single taps and clicks, double-taps and clicks, long presses, and path-based gestures specific sensory experience a sensory experience that is not purely decorative and does not primarily convey important information or perform a function Example Examples include a performance of a flute solo, works of visual art etc. state dynamic property expressing characteristics of a user interface component that may change in response to user action or automated processes States do not affect the nature of the component, but represent data associated with the component or user interaction possibilities. Examples include focus, hover, select, press, check, visited/unvisited, and expand/collapse. status message change in content that is not a change of context , and that provides information to the user on the success or results of an action, on the waiting state of an application, on the progress of a process, or on the existence of errors structure The way the parts of a Web page are organized in relation to each other; and The way a collection of Web pages is organized style property property whose value determines the presentation (e.g. font, color, size, location, padding, volume, synthesized speech prosody) of content elements as they are rendered (e.g." "onscreen, via loudspeaker, via braille display) by user agents Style properties can have several origins: User agent default styles: The default style property values applied in the absence of any author or user styles. Some web content technologies specify a default rendering, others do not; Author styles: Style property values that are set by the author as part of the content (e.g. in-line styles, author style sheets); User styles: Style property values that are set by the user (e.g. via user agent interface settings, user style sheets) supplemental content additional content that illustrates or clarifies the primary content Example 1 An audio version of a Web page . Example 2 An illustration of a complex process ." "Example 3 A paragraph summarizing the major outcomes and recommendations made in a research study. synchronized media audio or video synchronized with another format for presenting information and/or with time-based interactive components, unless the media is a media alternative for text that is clearly labeled as such target region of the display that will accept a pointer action, such as the interactive area of a user interface component Note If two or more targets are overlapping, the overlapping area should not be included in the measurement of the target size, except when the overlapping targets perform the same action or open the same page. technology (Web content) mechanism for encoding instructions to be rendered, played or executed by user agents Note 1 As used in these guidelines ""Web Technology"" and the word ""technology"" (when used alone) both refer to Web Content Technologies. Note 2 Web content technologies may include markup languages, data formats, or programming languages that authors may use alone or in combination to create end-user experiences that range from static Web pages to synchronized media presentations to dynamic Web applications. Example Some common examples of Web content technologies include HTML, CSS, SVG, PNG, PDF, Flash, and JavaScript." "text sequence of characters that can be programmatically determined , where the sequence is expressing something in human language text alternative Text that is programmatically associated with non-text content or referred to from text that is programmatically associated with non-text content. Programmatically associated text is text whose location can be programmatically determined from the non-text content. Example An image of a chart is described in text in the paragraph after the chart. The short text alternative for the chart indicates that a description follows. Note Refer to Understanding Text Alternatives for more information. up-event platform event that occurs when the trigger stimulus of a pointer is released The up-event may have different names on different platforms, such as ""touchend"" or ""mouseup""." "used in an unusual or restricted way words used in such a way that requires users to know exactly which definition to apply in order to understand the content correctly Example The term ""gig"" means something different if it occurs in a discussion of music concerts than it does in article about computer hard drive space, but the appropriate definition can be determined from context. By contrast, the word ""text"" is used in a very specific way in WCAG 2.1, so a definition is supplied in the glossary. user agent any software that retrieves and presents Web content for users Example Web browsers, media players, plug-ins, and other programs — including assistive technologies — that help in retrieving, rendering, and interacting with Web content. user-controllable data that is intended to be accessed by users Note This does not refer to such things as Internet logs and search engine monitoring data. Example Name and address fields for a user's account." "user interface component a part of the content that is perceived by users as a single control for a distinct function Note 1 Multiple user interface components may be implemented as a single programmatic element. ""Components"" here is not tied to programming techniques, but rather to what the user perceives as separate controls. Note 2 User interface components include form elements and links as well as components generated by scripts. Note 3 What is meant by ""component"" or ""user interface component"" here is also sometimes called ""user interface element"". Example An applet has a ""control"" that can be used to move through content by line or page or random access. Since each of these would need to have a name and be settable independently, they would each be a ""user interface component."" user inactivity any continuous period of time where no user actions occur The method of tracking will be determined by the web site or application." "video the technology of moving or sequenced pictures or images Note Video can be made up of animated or photographic images, or both. video-only a time-based presentation that contains only video (no audio and no interaction) viewport object in which the user agent presents content Note 1 The user agent presents content through one or more viewports. Viewports include windows, frames, loudspeakers, and virtual magnifying glasses. A viewport may contain another viewport (e.g., nested frames). Interface components created by the user agent such as prompts, menus, and alerts are not viewports." "Note 2 This definition is based on User Agent Accessibility Guidelines 1.0 Glossary [ UAAG10 ]. visually customized the font, size, color, and background can be set Web page a non-embedded resource obtained from a single URI using HTTP plus any other resources that are used in the rendering or intended to be rendered together with it by a user agent Note 1 Although any ""other resources"" would be rendered together with the primary resource, they would not necessarily be rendered simultaneously with each other. Note 2 For the purposes of conformance with these guidelines, a resource must be ""non-embedded"" within the scope of conformance to be considered a Web page. Example 1 A Web resource including all embedded images and media. Example 2 A Web mail program built using Asynchronous JavaScript and XML (AJAX)." "The program lives entirely at http://example.com/mail, but includes an inbox, a contacts area and a calendar. Links or buttons are provided that cause the inbox, contacts, or calendar to display, but do not change the URI of the page as a whole. Example 3 A customizable portal site, where users can choose content to display from a set of different content modules. Example 4 When you enter ""http://shopping.example.com/"" in your browser, you enter a movie-like interactive shopping environment where you visually move around in a store dragging products off of the shelves around you and into a visual shopping cart in front of you. Clicking on a product causes it to be demonstrated with a specification sheet floating alongside." "This might be a single-page Web site or just one page within a Web site. 7. Input Purposes for User Interface Components This section contains a listing of common user interface component input purposes. The terms below are not keywords that must be used, but instead represent purposes that must be captured in the taxonomy adopted by a webpage. Where applicable, authors mark up controls with the chosen taxonomy to indicate the semantic purpose." "This provides the potential for user agents and assistive technologies to apply personalized presentations that can enable more people to understand and use the content. Note The list of input type purposes is based on the control purposes defined in the HTML specification's Autofill section , but it is important to understand that a different technology may have some or all of the same concepts defined in its specification and only the concepts that are mapped to the meanings below are required. The following input control purposes are intended to relate to the user of the content and pertain only to information related to that individual. name - Full name honorific-prefix - Prefix or title (e.g., ""Mr."", ""Ms."", ""Dr."", ""M lle "") given-name - Given name (in some Western cultures, also known as the first name ) additional-name - Additional names (in some Western cultures, also known as middle names , forenames other than the first name) family-name - Family name (in some Western cultures, also known as the last name or surname ) honorific-suffix - Suffix (e.g., ""Jr."", ""B.Sc."", ""MBASW"", ""II"") nickname - Nickname, screen name, handle: a typically short name used instead of the full name organization-title - Job title (e.g., ""Software Engineer"", ""Senior Vice President"", ""Deputy Managing Director"") username - A username new-password - A new password (e.g., when creating an account or changing a password) current-password - The current password for the account identified by the username field (e.g., when logging in) organization - Company name corresponding to the person, address, or contact information in the other fields associated with this field street-address - Street address (multiple lines, newlines preserved) address-line1 - Street address (one line per field, line 1) address-line2 - Street address (one line per field, line 2) address-line3 - Street address (one line per field, line 3) address-level4 - The most fine-grained administrative level, in addresses with four administrative levels address-level3 - The third administrative level, in addresses with three or more administrative levels address-level2 - The second administrative level, in addresses with two or more administrative levels; in the countries with two administrative levels, this would typically be the city, town, village, or other locality within which the relevant street address is found address-level1 - The broadest administrative level in the address, i.e., the province within which the locality is found; for example, in the US, this would be the state; in Switzerland it would be the canton; in the UK, the post town country - Country code country-name - Country name postal-code - Postal code, post code, ZIP code, CEDEX code (if CEDEX, append ""CEDEX"", and the dissement , if relevant, to the address-level2 field) cc-name - Full name as given on the payment instrument cc-given-name - Given name as given on the payment instrument (in some Western cultures, also known as the first name ) cc-additional-name - Additional names given on the payment instrument (in some Western cultures, also known as middle names , forenames other than the first name) cc-family-name - Family name given on the payment instrument (in some Western cultures, also known as the last name or surname ) cc-number - Code identifying the payment instrument (e.g., the credit card number) cc-exp - Expiration date of the payment instrument cc-exp-month - Month component of the expiration date of the payment instrument cc-exp-year - Year component of the expiration date of the payment instrument cc-csc - Security code for the payment instrument (also known as the card security code (CSC), card validation code (CVC), card verification value (CVV), signature panel code (SPC), credit card ID (CCID), etc) cc-type - Type of payment instrument transaction-currency - The currency that the user would prefer the transaction to use transaction-amount - The amount that the user would like for the transaction (e.g., when entering a bid or sale price) language - Preferred language bday - Birthday bday-day - Day component of birthday bday-month - Month component of birthday bday-year - Year component of birthday sex - Gender identity (e.g., Female, Fa’afafine ) url - Home page or other Web page corresponding to the company, person, address, or contact information in the other fields associated with this field photo - Photograph, icon, or other image corresponding to the company, person, address, or contact information in the other fields associated with this field tel - Full telephone number, including country code tel-country-code - Country code component of the telephone number tel-national - Telephone number without the country code component, with a country-internal prefix applied if applicable tel-area-code - Area code component of the telephone number, with a country-internal prefix applied if applicable tel-local - Telephone number without the country code and area code components tel-local-prefix - First part of the component of the telephone number that follows the area code, when that component is split into two components tel-local-suffix - Second part of the component of the telephone number that follows the area code, when that component is split into two components tel-extension - Telephone number internal extension code email - E-mail address impp - URL representing an instant messaging protocol endpoint (for example, "" aim:goim?screenname=example "" or "" xmpp:fred@example.net "") A. Change Log This section shows substantive changes made in WCAG 2.2 since WCAG 2.1." "Errata fixes to WCAG 2.1 have also been incorporated into WCAG 2.2. The full commit history to WCAG 2.2 is available. 2019-11-10: Promoted Focus Visible from Level AA to Level A. 2020-01-14: Added Focus Visible (Enhanced) , later renamed to Focus Appearance (Enhanced), later removed. 2020-03-10: Renamed Pointer Target Spacing to Target Size (Minimum) 2020-03-30: Added Accessible Authentication (Minimum) ." "2020-05-27: Added Dragging (later renamed Dragging Movements ). 2020-07-19: Added Findable Help (later renamed to Consistent Help ), Fixed Reference Points (Page Break Navigation), Hidden Controls (later renamed Visible Controls), Pointer Target Spacing (later renamed Target Size (Minimum) ), Redundant Entry . 2020-08-04: Added Focus Appearance (Minimum) (later renamed to Focus Appearance ) and renamed Focus Visible (Enhanced) to Focus Appearance (Enhanced) . 2020-11-02: Renamed Dragging to Dragging Movements . 2020-12-08: Renamed Hidden Controls to Visible Controls." 2021-09-21: Added Accessible Authentication (No Exception) . 2022-03-22: Added Focus Not Obscured (Minimum) . 2022-05-13: Removed Visible Controls. 2022-05-30: Added Focus Not Obscured (Enhanced) . 2022-07-15: Removed Page Break Navigation. "2023-06-05: Added privacy and security sections within conformance. B. Acknowledgments This section is non-normative. Additional information about participation in the Accessibility Guidelines Working Group (AG WG) can be found on the Working Group home page . B.1 Participants of the AG WG active in the development of this document: Jake Abma (Invited Expert) Shadi Abou-Zahra (Amazon) Chuck Adams (Oracle Corporation) Amani Ali (Nomensa) Jim Allan (Invited Expert) Jon Avila (Level Access) Bruce Bailey (U.S." "Access Board) Renaldo Bernard (University of Southampton) Dan Bjorge (Deque Systems, Inc.) Peter Bossley (Thomson Reuters) Rachael Bradley Montgomery (Library of Congress) Judy Brewer ( W3C ) Shari Butler (Pearson plc) Thaddeus Cambron (Invited Expert) Alastair Campbell (Nomensa) Laura Carlson (Invited Expert) Sukriti Chadha (Invited Expert) Rafal Charlampowicz (AccessibilityOZ) Michael Cooper ( W3C ) Jennifer Delisi (Invited Expert) Wayne Dick (Knowbility, Inc) Kim Dirks (Thomson Reuters) E.A. Draffan (University of Southampton) Eric Eggert ( W3C ) Michael Elledge (Invited Expert) Steve Faulkner (TPGi) David Fazio (Invited Expert) Wilco Fiers (Deque Systems, Inc.) Detlev Fischer (Invited Expert) John Foliot (Invited Expert) Matt Garrish (DAISY Consortium) Alistair Garrison (Level Access) Jaunita George (Navy Federal Credit Union) Michael Gower (IBM Corporation) Markku Hakkinen (Educational Testing Service) Charles Hall (Invited Expert) Katie Haritos-Shea (Knowbility, Inc) Dan Harper-Wain (HM Government) Shawn Henry ( W3C ) Sarah Horton (Invited Expert) Abi James (University of Southampton) Marc Johlic (IBM Corporation) Oliver Keim (SAP SE) Andrew Kirkpatrick (Adobe) John Kirkwood (Invited Expert) JaEun Jemma Ku (University of Illinois Chicago) Patrick H. Lauke (TetraLogical) Shawn Lauriat (Google, Inc.) Steve Lee (Invited Expert) Chris Loiselle (Invited Expert) David MacDonald (Invited Expert) Jan McSorley (Pearson plc) Rain Breaw Michaels (Google LLC) Neil Milliken (Unify Software and Solutions) Mary Jo Mueller (IBM Corporation) Jay Mullen (College Board) Brooks Newton (Thomson Reuters) Gundula Niemann (SAP SE) James Nurthen (Oracle Corporation) Lori Oakley (Oracle Corporation) Joshue O Connor (Invited Expert) Scott O'Hara (Microsoft) Sailesh Panchang (Deque Systems, Inc.) Kim Patch (Invited Expert) Melanie Philipp (Deque Systems, Inc.) Mike Pluke (Invited Expert) Ian Pouncey (TetraLogical) Ruoxi Ran ( W3C ) Stephen Repsher (Invited Expert) John Rochford (Invited Expert) Stefan Schnabel (SAP SE) Ayelet Seeman (Invited Expert) Lisa Seeman-Kestenbaum (Invited Expert) Glenda Sims (Deque Systems, Inc.) Avneesh Singh (DAISY Consortium) David Sloan (TPGi) Andrew Somers (Invited Expert) Jeanne Spellman (TetraLogical) Francis Storr (Intel) Poornima Badhan Subramanian (Invited Expert) Ben Tillyer (Invited Expert) Makoto Ueki (Invited Expert) Gregg Vanderheiden (Raising the Floor) Kathleen Wahlbin (Invited Expert) Léonie Watson (TetraLogical) Jason White (Educational Testing Service) White, Kevin ( W3C Staff) Mark Wilcock (Unify Software and Solutions) B.2 Other previously active WCAG WG participants and other contributors to WCAG 2.0, WCAG 2.1, or supporting resources Paul Adam, Jenae Andershonis, Wilhelm Joys Andersen, Andrew Arch, Avi Arditti, Aries Arditi, Tom Babinszki, Mark Barratt, Mike Barta, Sandy Bartell, Kynn Bartlett, Chris Beer, Charles Belov, Marco Bertoni, Harvey Bingham, Chris Blouch, Paul Bohman, Frederick Boland, Denis Boudreau, Patrice Bourlon, Andy Brown, Dick Brown, Doyle Burnett, Raven Calais, Ben Caldwell, Tomas Caspers, Roberto Castaldo, Sofia Celic-Li, Sambhavi Chandrashekar, Mike Cherim, Jonathan Chetwynd, Wendy Chisholm, Alan Chuter, David M Clark, Joe Clark, Darcy Clarke, James Coltham, Earl Cousins, James Craig, Tom Croucher, Pierce Crowell, Nir Dagan, Daniel Dardailler, Geoff Deering, Sébastien Delorme, Pete DeVasto, Iyad Abu Doush, Sylvie Duchateau, Cherie Eckholm, Roberto Ellero, Don Evans, Gavin Evans, Neal Ewers, Steve Faulkner, Bengt Farre, Lainey Feingold, Wilco Fiers, Michel Fitos, Alan J. Flavell, Nikolaos Floratos, Kentarou Fukuda, Miguel Garcia, P.J. Gardner, Alistair Garrison, Greg Gay, Becky Gibson, Al Gilman, Kerstin Goldsmith, Michael Grade, Karl Groves, Loretta Guarino Reid, Jon Gunderson, Emmanuelle Gutiérrez y Restrepo, Brian Hardy, Eric Hansen, Benjamin Hawkes-Lewis, Sean Hayes, Shawn Henry, Hans Hillen, Donovan Hipke, Bjoern Hoehrmann, Allen Hoffman, Chris Hofstader, Yvette Hoitink, Martijn Houtepen, Carlos Iglesias, Richard Ishida, Jonas Jacek, Ian Jacobs, Phill Jenkins, Barry Johnson, Duff Johnson, Jyotsna Kaki, Shilpi Kapoor, Leonard R." "Kasday, Kazuhito Kidachi, Ken Kipness, Johannes Koch, Marja-Riitta Koivunen, Maureen Kraft, Preety Kumar, Kristjan Kure, Andrew LaHart, Gez Lemon, Chuck Letourneau, Aurélien Levy, Harry Loots, Scott Luebking, Tim Lacy, Jim Ley, Alex Li, William Loughborough, N Maffeo, Mark Magennis, Erich Manser, Kapsi Maria, Luca Mascaro, Matt May, Sheena McCullagh, Liam McGee, Jens Oliver Meiert, Niqui Merret, Jonathan Metz, Alessandro Miele, Steven Miller, Mathew J Mirabella, Matt May, Marti McCuller, Sorcha Moore, Charles F. Munat, Robert Neff, Charles Nevile, Liddy Nevile, Dylan Nicholson, Bruno von Niman, Tim Noonan, Sebastiano Nutarelli, Graham Oliver, Sean B. Palmer, Charu Pandhi, evarshi Pant, Nigel Peck, Anne Pemberton, David Poehlman, Ian Pouncey, Charles Pritchard, Kerstin Probiesch, W Reagan, Adam Victor Reed, Chris Reeve, Chris Ridpath, Lee Roberts, Mark Rogers, Raph de Rooij, Gregory J. Rosmaita, Matthew Ross, Sharron Rush, Joel Sanda, Janina Sajka, Roberto Scano, Gordon Schantz, Tim van Schie, Wolf Schmidt, Stefan Schnabel, Cynthia Shelly, Glenda Sims, John Slatin, Becky Smith, Jared Smith, Andi Snow-Weaver, Neil Soiffer, Mike Squillace, Michael Stenitzer, Diane Stottlemyer, Christophe Strobbe, Sarah J Swierenga, Jim Thatcher, Terry Thompson, Justin Thorp, David Todd, Mary Utt, Jean Vanderdonckt, Carlos A Velasco, Eric Velleman, Gijs Veyfeyken, Dena Wainwright, Paul Walsch, Daman Wandke, Richard Warren, Elle Waters, Takayuki Watanabe, Gian Wild, David Wooley, Wu Wei, Kenny Zhang, Leona Zumbo. B.3 Enabling funders This publication has been funded in part with U.S." "Federal funds from the Health and Human Services, National Institute on Disability, Independent Living, and Rehabilitation Research (NIDILRR), initially under contract number ED-OSE-10-C-0067, then under contract number HHSP23301500054C, and now under HHS75P00120P00168. The content of this publication does not necessarily reflect the views or policies of the U.S. Department of Health and Human Services or the U.S. Department of Education, nor does mention of trade names, commercial products, or organizations imply endorsement by the U.S. Government." C. References C.1 Informative references [css3-values] CSS Values and Units Module Level 3 . Tab Atkins Jr.; Elika Etemad. W3C. 1 December 2022. W3C Candidate Recommendation. URL: https://www.w3.org/TR/css-values-3/ [HTML] HTML Standard . Anne van Kesteren; Domenic Denicola; Ian Hickson; Philip Jägenstedt; Simon Pieters. WHATWG. Living Standard. "URL: https://html.spec.whatwg.org/multipage/ [ISO_9241-391] Ergonomics of human-system interaction—Part 391: Requirements, analysis and compliance test methods for the reduction of photosensitive seizures . International Standards Organization. URL: https://www.iso.org/standard/56350.html [pointerevents] Pointer Events . Jacob Rossi; Matt Brubeck. W3C." 4 April 2019. W3C Recommendation. URL: https://www.w3.org/TR/pointerevents/ [RFC2119] Key words for use in RFCs to Indicate Requirement Levels . S. Bradner. IETF. March 1997. Best Current Practice. URL: https://www.rfc-editor.org/rfc/rfc2119 [SRGB] Multimedia systems and equipment - Colour measurement and management - Part 2-1: Colour management - Default RGB colour space - sRGB . IEC. URL: https://webstore.iec.ch/publication/6169 [UAAG10] User Agent Accessibility Guidelines 1.0 . Ian Jacobs; Jon Gunderson; Eric Hansen. W3C. 17 December 2002. W3C Recommendation. URL: https://www.w3.org/TR/UAAG10/ [UNESCO] International Standard Classification of Education . 2011. URL: https://unesdoc.unesco.org/ark:/48223/pf0000219109 [WAI-WEBCONTENT] Web Content Accessibility Guidelines 1.0 . Wendy Chisholm; Gregg Vanderheiden; Ian Jacobs. W3C. 5 May 1999. W3C Recommendation. URL: https://www.w3.org/TR/WAI-WEBCONTENT/ [WCAG20] Web Content Accessibility Guidelines (WCAG) 2.0 . Ben Caldwell; Michael Cooper; Loretta Guarino Reid; Gregg Vanderheiden et al. W3C. 11 December 2008. W3C Recommendation. URL: https://www.w3.org/TR/WCAG20/ [WCAG21] Web Content Accessibility Guidelines (WCAG) 2.1 . Michael Cooper; Andrew Kirkpatrick; Joshue O'Connor; Alastair Campbell. W3C. 21 September 2023. W3C Recommendation. URL: https://www.w3.org/TR/WCAG21/ ↑ Permalink Referenced in: § 3.1.4 Abbreviations Permalink Referenced in: § 2.5.4 Motion Actuation § 5. Conformance § 5.2.4 Only Accessibility-Supported Ways of Using Technologies § 5.2.5 Non-Interference § 5.5 Statement of Partial Conformance - Language § 6. Glossary Permalink Referenced in: § 1.2.1 Audio-only and Video-only (Prerecorded) § 1.2.3 Audio Description or Media Alternative (Prerecorded) § 1.2.8 Media Alternative (Prerecorded) § 1.2.9 Audio-only (Live) Permalink Referenced in: § 2.4.4 Link Purpose (In Context) § 2.4.9 Link Purpose (Link Only) Permalink Referenced in: § 6. "Glossary Permalink Referenced in: § 1.1.1 Non-text Content § 1.4.4 Resize Text § 4.1.2 Name, Role, Value § 4.1.3 Status Messages § 6. Glossary (2) (3) (4) Permalink Referenced in: § 1.2.2 Captions (Prerecorded) § 1.2.4 Captions (Live) § 1.2.6 Sign Language (Prerecorded) § 6. Glossary (2) (3) (4) Permalink Referenced in: § 1.2.3 Audio Description or Media Alternative (Prerecorded) § 1.2.5 Audio Description (Prerecorded) § 1.2.7 Extended Audio Description (Prerecorded) § 6. Glossary (2) Permalink Referenced in: § 1.2.1 Audio-only and Video-only (Prerecorded) § 1.2.9 Audio-only (Live) § 1.4.7 Low or No Background Audio Permalink Referenced in: § 2.2.2 Pause, Stop, Hide § 6. Glossary Permalink Referenced in: § 1.4.8 Visual Presentation Permalink Referenced in: § 1.1.1 Non-text Content § 1.4.7 Low or No Background Audio Permalink Referenced in: § 1.2.2 Captions (Prerecorded) § 1.2.4 Captions (Live) § 1.4.4 Resize Text Permalink Referenced in: § 3.2.1 On Focus § 3.2.2 On Input § 3.2.5 Change on Request § 6." Glossary Permalink Referenced in: § 3.3.8 Accessible Authentication (Minimum) § 3.3.9 Accessible Authentication (Enhanced) Permalink Referenced in: § 5. Conformance § 5.2.2 Full pages § 6. Glossary (2) (3) Permalink Referenced in: § 5.2.1 Conformance Level Permalink Referenced in: § 2.4.13 Focus Appearance § 6. Glossary (2) (3) (4) Permalink Referenced in: § 3.3.5 Help Permalink Referenced in: § 1.4.3 Contrast (Minimum) § 1.4.6 Contrast (Enhanced) § 1.4.11 Non-text Contrast Permalink Referenced in: § 1.3.2 Meaningful Sequence Permalink Referenced in: § 1.4.10 Reflow (2) § 2.4.13 Focus Appearance § 2.5.5 Target Size (Enhanced) § 2.5.8 Target Size (Minimum) Permalink Referenced in: § 2.5.2 Pointer Cancellation § 6. Glossary Permalink Referenced in: § 2.5.7 Dragging Movements Permalink Referenced in: § 2.2.4 Interruptions Permalink Referenced in: Not referenced in this document. "Permalink Referenced in: § 1.3.4 Orientation § 1.4.5 Images of Text § 1.4.9 Images of Text (No Exception) § 1.4.11 Non-text Contrast § 2.2.1 Timing Adjustable § 2.2.2 Pause, Stop, Hide § 2.2.3 No Timing § 2.3.3 Animation from Interactions § 2.5.1 Pointer Gestures § 2.5.2 Pointer Cancellation § 2.5.4 Motion Actuation § 2.5.5 Target Size (Enhanced) § 2.5.6 Concurrent Input Mechanisms § 2.5.7 Dragging Movements § 2.5.8 Target Size (Minimum) § 3.3.7 Redundant Entry Permalink Referenced in: § 1.2.7 Extended Audio Description (Prerecorded) § 6. Glossary Permalink Referenced in: § 2.3.1 Three Flashes or Below Threshold § 2.3.2 Three Flashes § 6. Glossary (2) Permalink Referenced in: § 2.4.13 Focus Appearance Permalink Referenced in: § 2.1.1 Keyboard § 2.1.3 Keyboard (No Exception) § 2.5.1 Pointer Gestures § 2.5.2 Pointer Cancellation § 2.5.4 Motion Actuation § 2.5.7 Dragging Movements § 6. Glossary Permalink Referenced in: § 2.3.1 Three Flashes or Below Threshold § 6. Glossary Permalink Referenced in: § 3.1.1 Language of Page § 3.1.2 Language of Parts § 6." "Glossary (2) (3) (4) Permalink Referenced in: § 3.1.3 Unusual Words Permalink Referenced in: § 1.4.3 Contrast (Minimum) § 1.4.4 Resize Text § 1.4.5 Images of Text § 1.4.6 Contrast (Enhanced) § 1.4.9 Images of Text (No Exception) § 2.5.3 Label in Name § 6. Glossary Permalink Referenced in: § 5.1 Interpreting Normative Requirements § 6. Glossary Permalink Referenced in: § 1.4.13 Content on Hover or Focus § 3.3.1 Error Identification § 3.3.3 Error Suggestion Permalink Referenced in: § 3.1.3 Unusual Words Permalink Referenced in: § 2.1.1 Keyboard § 2.1.2 No Keyboard Trap § 2.1.3 Keyboard (No Exception) § 6. Glossary Permalink Referenced in: § 2.1.4 Character Key Shortcuts Permalink Referenced in: § 2.4.6 Headings and Labels § 2.5.3 Label in Name § 3.3.2 Labels or Instructions § 6. Glossary Permalink Referenced in: § 1.4.3 Contrast (Minimum) § 1.4.6 Contrast (Enhanced) Permalink Referenced in: § 3.3.4 Error Prevention (Legal, Financial, Data) Permalink Referenced in: § 2.4.4 Link Purpose (In Context) Permalink Referenced in: § 1.2.4 Captions (Live) § 1.2.9 Audio-only (Live) § 6." "Glossary Permalink Referenced in: § 3.1.5 Reading Level Permalink Referenced in: § 1.4.2 Audio Control § 1.4.8 Visual Presentation § 1.4.13 Content on Hover or Focus § 2.1.4 Character Key Shortcuts § 2.4.1 Bypass Blocks § 2.4.9 Link Purpose (Link Only) § 2.5.2 Pointer Cancellation § 3.1.3 Unusual Words § 3.1.4 Abbreviations § 3.1.6 Pronunciation § 3.2.5 Change on Request § 3.2.6 Consistent Help § 3.3.8 Accessible Authentication (Minimum) § 3.3.9 Accessible Authentication (Enhanced) § 6. Glossary (2) Permalink Referenced in: § 1.2.1 Audio-only and Video-only (Prerecorded) § 1.2.2 Captions (Prerecorded) § 1.2.3 Audio Description or Media Alternative (Prerecorded) § 6. Glossary Permalink Referenced in: § 2.3.3 Animation from Interactions Permalink Referenced in: § 2.5.8 Target Size (Minimum) § 6. Glossary Permalink Referenced in: § 1.1.1 Non-text Content § 2.5.3 Label in Name § 4.1.2 Name, Role, Value § 6. Glossary Permalink Referenced in: § 2.4.3 Focus Order Permalink Referenced in: § 1.1.1 Non-text Content § 3.3.8 Accessible Authentication (Minimum) § 6." "Glossary Permalink Referenced in: § 5.1 Interpreting Normative Requirements § 6. Glossary Permalink Referenced in: § 1.4.8 Visual Presentation Permalink Referenced in: § 2.2.2 Pause, Stop, Hide Permalink Referenced in: § 2.4.13 Focus Appearance Permalink Referenced in: § 2.5.5 Target Size (Enhanced) § 2.5.8 Target Size (Minimum) Permalink Referenced in: § 1.2.1 Audio-only and Video-only (Prerecorded) § 1.2.2 Captions (Prerecorded) § 1.2.3 Audio Description or Media Alternative (Prerecorded) § 1.2.5 Audio Description (Prerecorded) § 1.2.6 Sign Language (Prerecorded) § 1.2.7 Extended Audio Description (Prerecorded) § 1.2.8 Media Alternative (Prerecorded) § 1.4.7 Low or No Background Audio Permalink Referenced in: § 1.3.1 Info and Relationships § 1.4.11 Non-text Contrast § 2.4.13 Focus Appearance § 2.5.8 Target Size (Minimum) § 6. Glossary Permalink Referenced in: § 6. Glossary Permalink Referenced in: § 2.4.5 Multiple Ways § 3.3.7 Redundant Entry § 3.3.8 Accessible Authentication (Minimum) § 3.3.9 Accessible Authentication (Enhanced) § 5.2.3 Complete processes § 6. Glossary (2) (3) Permalink Referenced in: § 1.3.1 Info and Relationships § 1.3.2 Meaningful Sequence § 1.3.5 Identify Input Purpose § 1.3.6 Identify Purpose § 3.1.1 Language of Page § 3.1.2 Language of Parts § 4.1.2 Name, Role, Value § 4.1.3 Status Messages § 6." "Glossary (2) (3) Permalink Referenced in: § 2.4.4 Link Purpose (In Context) Permalink Referenced in: § 4.1.2 Name, Role, Value Permalink Referenced in: § 1.1.1 Non-text Content § 1.4.3 Contrast (Minimum) § 1.4.6 Contrast (Enhanced) § 1.4.9 Images of Text (No Exception) Permalink Referenced in: § 2.2.3 No Timing Permalink Referenced in: § 1.3.6 Identify Purpose Permalink Referenced in: § 1.3.1 Info and Relationships § 6. Glossary Permalink Referenced in: § 6. Glossary (2) (3) (4) Permalink Referenced in: § 5. Conformance § 5.2.4 Only Accessibility-Supported Ways of Using Technologies § 5.2.5 Non-Interference § 5.3.1 Required Components of a Conformance Claim § 5.3.2 Optional Components of a Conformance Claim (2) § 6. Glossary (2) Permalink Referenced in: § 4.1.2 Name, Role, Value § 4.1.3 Status Messages Permalink Referenced in: § 3.2.4 Consistent Identification Permalink Referenced in: § 3.2.3 Consistent Navigation Permalink Referenced in: § 5.2.1 Conformance Level Permalink Referenced in: § 2.4.10 Section Headings Permalink Referenced in: § 2.4.5 Multiple Ways § 2.4.8 Location § 3.2.3 Consistent Navigation § 3.2.4 Consistent Identification § 3.2.6 Consistent Help Permalink Referenced in: § 6." Glossary (2) Permalink Referenced in: § 1.2.6 Sign Language (Prerecorded) Permalink Referenced in: § 2.5.1 Pointer Gestures § 2.5.2 Pointer Cancellation § 2.5.7 Dragging Movements Permalink Referenced in: § 1.1.1 Non-text Content Permalink Referenced in: § 1.4.11 Non-text Contrast § 6. Glossary Permalink Referenced in: § 4.1.3 Status Messages Permalink Referenced in: § 1.3.1 Info and Relationships § 6. Glossary Permalink Referenced in: § 1.4.12 Text Spacing Permalink Referenced in: § 3.1.5 Reading Level § 6. Glossary Permalink Referenced in: § 1.2.2 Captions (Prerecorded) § 1.2.3 Audio Description or Media Alternative (Prerecorded) § 1.2.4 Captions (Live) § 1.2.5 Audio Description (Prerecorded) § 1.2.6 Sign Language (Prerecorded) § 1.2.7 Extended Audio Description (Prerecorded) § 1.2.8 Media Alternative (Prerecorded) § 2.2.3 No Timing Permalink Referenced in: § 2.5.5 Target Size (Enhanced) § 2.5.8 Target Size (Minimum) Permalink Referenced in: § 2.4.13 Focus Appearance § 5.2.4 Only Accessibility-Supported Ways of Using Technologies § 5.2.5 Non-Interference § 5.3.1 Required Components of a Conformance Claim § 6. Glossary (2) (3) Permalink Referenced in: § 1.1.1 Non-text Content § 1.4.3 Contrast (Minimum) § 1.4.4 Resize Text § 1.4.5 Images of Text § 1.4.6 Contrast (Enhanced) § 1.4.9 Images of Text (No Exception) § 1.4.12 Text Spacing § 2.5.3 Label in Name § 6. "Glossary (2) (3) Permalink Referenced in: § 1.1.1 Non-text Content § 6. Glossary (2) Permalink Referenced in: § 2.5.2 Pointer Cancellation § 6. Glossary Permalink Referenced in: § 3.1.3 Unusual Words Permalink Referenced in: § 2.4.13 Focus Appearance § 2.5.7 Dragging Movements § 2.5.8 Target Size (Minimum) § 4.1.2 Name, Role, Value § 6. Glossary (2) (3) (4) (5) (6) (7) (8) (9) Permalink Referenced in: § 3.3.4 Error Prevention (Legal, Financial, Data) Permalink Referenced in: § 1.3.6 Identify Purpose § 1.4.3 Contrast (Minimum) § 1.4.6 Contrast (Enhanced) § 1.4.11 Non-text Contrast § 2.1.4 Character Key Shortcuts § 2.4.10 Section Headings § 2.4.11 Focus Not Obscured (Minimum) § 2.4.12 Focus Not Obscured (Enhanced) § 2.5.3 Label in Name § 2.5.4 Motion Actuation § 3.2.1 On Focus § 3.2.2 On Input § 4.1.2 Name, Role, Value § 6. Glossary § 7." "Input Purposes for User Interface Components Permalink Referenced in: § 2.2.6 Timeouts Permalink Referenced in: § 1.2.3 Audio Description or Media Alternative (Prerecorded) § 1.2.5 Audio Description (Prerecorded) § 1.2.7 Extended Audio Description (Prerecorded) § 6. Glossary (2) (3) (4) (5) (6) (7) (8) Permalink Referenced in: § 1.2.1 Audio-only and Video-only (Prerecorded) § 1.2.8 Media Alternative (Prerecorded) Permalink Referenced in: § 6. Glossary Permalink Referenced in: § 1.4.5 Images of Text Permalink Referenced in: § 2.3.1 Three Flashes or Below Threshold § 2.3.2 Three Flashes § 2.4.1 Bypass Blocks § 2.4.2 Page Titled § 2.4.3 Focus Order § 2.4.5 Multiple Ways § 3.1.1 Language of Page § 3.2.3 Consistent Navigation § 3.2.6 Consistent Help § 3.3.4 Error Prevention (Legal, Financial, Data) § 3.3.6 Error Prevention (All) § 5.2.1 Conformance Level § 5.2.2 Full pages § 5.2.3 Complete processes § 5.2.5 Non-Interference § 5.3 Conformance Claims (Optional) § 6. Glossary (2) (3) (4) (5) (6) How to Meet WCAG (Quickref Reference) How to Meet WCAG (Quick Reference) A customizable quick reference to Web Content Accessibility Guidelines (WCAG) 2 requirements (success criteria) and techniques. Show Hide About & How to Use About This tool provides a customizable view of WCAG 2 resources: Web Content Accessibility Guidelines web standard — WCAG 2.2 , WCAG 2.1 , WCAG 2.0 Techniques for WCAG 2 implementation guidance Understanding WCAG 2 supporting information Background on these resources is provided in the WCAG Overview and The WCAG 2 documents ." "For important information about techniques, see Understanding Techniques for WCAG Success Criteria . How to Use Select the “Filter” tab in the main menu to customize: Tags: Shows only success criteria associated with the selected tags. Levels: Shows only success criteria for the selected levels. Technologies: Shows only techniques for the selected technologies. Techniques: Shows only the types of techniques and/or failures selected." "The Share this view button provides a link to this tool with the filters you have set. The SHARE buttons provide links to individual success criteria. Show Hide in-page navigation and filter options Hide Contents Filter 1. Perceivable 1.1 Text Alternatives 1.1.1 Non-text Content 1.2 Time-based Media 1.2.1 Audio-only and Video-only (Prerecorded) 1.2.2 Captions (Prerecorded) 1.2.3 Audio Description or Media Alternative (Prerecorded) 1.2.4 Captions (Live) 1.2.5 Audio Description (Prerecorded) 1.2.6 Sign Language (Prerecorded) 1.2.7 Extended Audio Description (Prerecorded) 1.2.8 Media Alternative (Prerecorded) 1.2.9 Audio-only (Live) 1.3 Adaptable 1.3.1 Info and Relationships 1.3.2 Meaningful Sequence 1.3.3 Sensory Characteristics 1.3.4 Orientation 1.3.5 Identify Input Purpose 1.3.6 Identify Purpose 1.4 Distinguishable 1.4.1 Use of C olor 1.4.2 Audio Control 1.4.3 Contrast (Minimum) 1.4.4 Resize Text 1.4.5 Images of Text 1.4.6 Contrast (Enhanced) 1.4.7 Low or No Background Audio 1.4.8 Visual Presentation 1.4.9 Images of Text (No Exception) 1.4.10 Reflow 1.4.11 Non-text Contrast 1.4.12 Text Spacing 1.4.13 Content on Hover or Focus 2. Operable 2.1 Keyboard Accessible 2.1.1 Keyboard 2.1.2 No Keyboard Trap 2.1.3 Keyboard (No Exception) 2.1.4 Character Key Shortcuts 2.2 Enough Time 2.2.1 Timing Adjustable 2.2.2 Pause, Stop, Hide 2.2.3 No Timing 2.2.4 Interruptions 2.2.5 Re-authenticating 2.2.6 Timeouts 2.3 Seizures and Physical Reactions 2.3.1 Three Flashes or Below Threshold 2.3.2 Three Flashes 2.3.3 Animation from Interactions 2.4 Navigable 2.4.1 Bypass Blocks 2.4.2 Page Titled 2.4.3 Focus Order 2.4.4 Link Purpose (In Context) 2.4.5 Multiple Ways 2.4.6 Headings and Labels 2.4.7 Focus Visible 2.4.8 Location 2.4.9 Link Purpose (Link Only) 2.4.10 Section Headings 2.4.11 Focus Not Obscured (Minimum) 2.4.12 Focus Not Obscured (Enhanced) 2.4.13 Focus Appearance 2.5 Input Modalities 2.5.1 Pointer Gestures 2.5.2 Pointer Cancellation 2.5.3 Label in Name 2.5.4 Motion Actuation 2.5.5 Target Size (Enhanced) 2.5.6 Concurrent Input Mechanisms 2.5.7 Dragging Movements 2.5.8 Target Size (Minimum) 3." "Understandable 3.1 Readable 3.1.1 Language of Page 3.1.2 Language of Parts 3.1.3 Unusual Words 3.1.4 Abbreviations 3.1.5 Reading Level 3.1.6 Pronunciation 3.2 Predictable 3.2.1 On Focus 3.2.2 On Input 3.2.3 Consistent Navigation 3.2.4 Consistent Identification 3.2.5 Change on Request 3.2.6 Consistent Help 3.3 Input Assistance 3.3.1 Error Identification 3.3.2 Labels or Instructions 3.3.3 Error Suggestion 3.3.4 Error Prevention (Legal, Financial, Data) 3.3.5 Help 3.3.6 Error Prevention (All) 3.3.7 Redundant Entry 3.3.8 Accessible Authentication (Minimum) 3.3.9 Accessible Authentication (Enhanced) 4. Robust 4.1 Compatible 4.1.1 Parsing 4.1.2 Name, Role, Value 4.1.3 Status Messages Changing filters will change the listed Success Criteria and Techniques. WCAG Version WCAG 2.2 WCAG 2.1 WCAG 2.0 Only 2.2 Added Success Criteria Only 2.1 Added Success Criteria Note: Clear Filters will not change the selected version. Tags Clear tags Developing only Interaction Design only Content Creation only Visual Design only animation audio auto complete autoplay blinking buttons captcha captions carousels changing content color components consistent experience content contrast controls drag and drop errors events fixed flashing focus forms graphical objects headings help hidden content hover icons iframes images images of text interaction keyboard labels language layout links live stream logins markup media queries menus messaging meta tag mobile modals moving content navigation notifications orientation page title pop up positioning progress steps readability reflow regions screen size skip to content sticky streaming structure tab order tables text text alternatives time limits user interface video viewport visual cues zoom Show all tags Levels Select all Level A only Level AA only Level AAA only Techniques Select all Sufficient Techniques only Advisory Techniques only Failures only Technologies Select all HTML only CSS only ARIA only Client-side Scripting only Server-side Scripting only SMIL only PDF only Show Sidebar Loading Loaded Selected Filters: WCAG 2.2: all success criteria and all techniques. (What did the filter remove?) Clear filters Expand all sections Share Link to this view, with the filters you have selected: Shortcut to copy the link: ctrl + C or ⌘ C Close Principle 1 – Perceivable Information and user interface components must be presentable to users in ways they can perceive." "Guideline 1.1 – Text Alternatives Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language. 1.1.1 Non-text Content Level A All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for the situations listed below. Controls, Input: If non-text content is a control or accepts user input, then it has a name that describes its purpose. (Refer to Success Criterion 4.1.2 for additional requirements for controls and content that accepts user input.) Time-Based Media: If non-text content is time-based media, then text alternatives at least provide descriptive identification of the non-text content. (Refer to Guideline 1.2 for additional requirements for media.) Test: If non-text content is a test or exercise that would be invalid if presented in text, then text alternatives at least provide descriptive identification of the non-text content." "Sensory: If non-text content is primarily intended to create a specific sensory experience, then text alternatives at least provide descriptive identification of the non-text content. CAPTCHA: If the purpose of non-text content is to confirm that content is being accessed by a person rather than a computer, then text alternatives that identify and describe the purpose of the non-text content are provided, and alternative forms of CAPTCHA using output modes for different types of sensory perception are provided to accommodate different disabilities. Decoration, Formatting, Invisible: If non-text content is pure decoration, is used only for visual formatting, or is not presented to users, then it is implemented in a way that it can be ignored by assistive technology. Understanding 1.1.1 Show Hide techniques and failures for 1.1.1 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 1.1.1 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques." "Situation A: If a short description can serve the same purpose and present the same information as the non-text content: G94: Providing short text alternative for non-text content that serves the same purpose and presents the same information as the non-text content Short text alternative techniques for Situation A: ARIA6: Using aria-label to provide labels for objects ARIA10: Using aria-labelledby to provide a text alternative for non-text content G196: Using a text alternative on one item within a group of images that describes all items in the group H2: Combining adjacent image and text links for the same resource H35: Providing text alternatives on applet elements H37: Using alt attributes on img elements H53: Using the body of the object element H86: Providing text alternatives for ASCII art, emoticons, and leetspeak PDF1: Applying text alternatives to images with the Alt entry in PDF documents Situation B: If a short description can not serve the same purpose and present the same information as the non-text content (e.g., a chart or diagram): G95: Providing short text alternatives that provide a brief description of the non-text content Short text alternative techniques for Situation B: ARIA6: Using aria-label to provide labels for objects ARIA10: Using aria-labelledby to provide a text alternative for non-text content G196: Using a text alternative on one item within a group of images that describes all items in the group H2: Combining adjacent image and text links for the same resource H35: Providing text alternatives on applet elements H37: Using alt attributes on img elements H53: Using the body of the object element H86: Providing text alternatives for ASCII art, emoticons, and leetspeak PDF1: Applying text alternatives to images with the Alt entry in PDF documents Long text alternative techniques for Situation B: ARIA15: Using aria-describedby to provide descriptions of images G73: Providing a long description in another location with a link to it that is immediately adjacent to the non-text content G74: Providing a long description in text near the non-text content, with a reference to the location of the long description in the short description G92: Providing long description for non-text content that serves the same purpose and presents the same information H45: Using longdesc H53: Using the body of the object element Situation C: If non-text content is a control or accepts user input: G82: Providing a text alternative that identifies the purpose of the non-text content Text alternative techniques for controls and input for Situation C: ARIA6: Using aria-label to provide labels for objects ARIA9: Using aria-labelledby to concatenate a label from several text nodes H24: Providing text alternatives for the area elements of image maps H30: Providing link text that describes the purpose of a link for anchor elements H36: Using alt attributes on images used as submit buttons H44: Using label elements to associate text labels with form controls H65: Using the title attribute to identify form controls when the label element cannot be used 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: Providing a descriptive label Short text alternative techniques for Situation D: ARIA6: Using aria-label to provide labels for objects ARIA10: Using aria-labelledby to provide a text alternative for non-text content G196: Using a text alternative on one item within a group of images that describes all items in the group H2: Combining adjacent image and text links for the same resource H35: Providing text alternatives on applet elements H37: Using alt attributes on img elements H53: Using the body of the object element H86: Providing text alternative s for ASCII art, emoticons, and leetspeak PDF1: Applying text alternatives to images with the Alt entry in PDF documents G68: Providing a short text alternative that describes the purpose of live audio-only and live video-only content Short text alternative techniques for Situation D: ARIA6: Using aria-label to provide labels for objects ARIA10: Using aria-labelledby to provide a text alternative for non-text content G196: Using a text alternative on one item within a group of images that describes all items in the group H2: Combining adjacent image and text links for the same resource H35: Providing text alternatives on applet elements H37: Using alt attributes on img elements H53: Using the body of the object element H86: Providing text alternatives for ASCII art, emoticons, and leetspeak PDF1: Applying text alternatives to images with the Alt entry in PDF documents G100: Providing a short text alternative which is the accepted name or a descriptive name of the non-text content Short text alternative techniques for Situation D: ARIA6: Using aria-label to provide labels for objects ARIA10: Using aria-labelledby to provide a text alternative for non-text content G196: Using a text alternative on one item within a group of images that describes all items in the group H2: Combining adjacent image and text links for the same resource H35: Providing text alternatives on applet elements H37: Using alt attributes on img elements H53: Using the body of the object element H86: Providing text alternatives for ASCII art, emoticons, and leetspeak PDF1: Applying text alternatives to images with the Alt entry in PDF documents Situation E: If non-text content is a CAPTCHA: G143: Providing a text alternative that describes the purpose of the CAPTCHA AND G144: Ensuring that the Web Page contains another CAPTCHA serving the same purpose using a different modality Situation F: If the non-text content should be ignored by assistive technology: Implementing or marking the non-text content so that it will be ignored by assistive technology using one of the following techniques: Techniques to indicate that text alternatives are not required for Situation F: C9: Using CSS to include decorative images H67: Using null alt text and no title attribute on img elements for images that AT should ignore PDF4: Hiding decorative images with the Artifact tag in PDF documents Advisory Techniques for Success Criterion 1.1.1 C18: Using CSS margin and padding rules instead of spacer images for layout design Failures for Success Criterion 1.1.1 F3: Failure of Success Criterion 1.1.1 due to using CSS to include images that convey important information F13: Failure of Success Criterion 1.1.1 and 1.4.1 due to having a text alternative that does not include information that is conveyed by color differences in the image 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 F30: Failure of Success Criterion 1.1.1 and 1.2.1 due to using text alternatives that are not alternatives (e.g., filenames or placeholder text) F38: Failure of Success Criterion 1.1.1 due to not marking up decorative images in HTML in a way that allows assistive technology to ignore them F39: Failure of Success Criterion 1.1.1 due to providing a text alternative that is not null (e.g., alt=""spacer"" or alt=""image"") for images that should be ignored by assistive technology F65: Failure of Success Criterion 1.1.1 due to omitting the alt attribute or text alternative on img elements, area elements, and input elements of type ""image"" F67: Failure of Success Criterion 1.1.1 and 1.2.1 due to providing long descriptions for non-text content that does not serve the same purpose or does not present the same information F71: Failure of Success Criterion 1.1.1 due to using text look-alikes to represent text without providing a text alternative F72: Failure of Success Criterion 1.1.1 due to using ASCII art without providing a text alternative Back to top Guideline 1.2 – Time-based Media Provide alternatives for time-based media. 1.2.1 Audio-only and Video-only (Prerecorded) Level A For prerecorded audio-only and prerecorded video-only media, the following are true, except when the audio or video is a media alternative for text and is clearly labeled as such: Prerecorded Audio-only: An alternative for time-based media is provided that presents equivalent information for prerecorded audio-only content. Prerecorded Video-only: Either an alternative for time-based media or an audio track is provided that presents equivalent information for prerecorded video-only content. Understanding 1.2.1 Show Hide techniques and failures for 1.2.1 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 1.2.1 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques." "Situation A: If the content is prerecorded audio-only: G158: Providing an alternative for time-based media for audio-only content Situation B: If the content is prerecorded video-only: G159: Providing an alternative for time-based media for video-only content G166: Providing audio that describes the important video content and describing it as such Advisory Techniques for Success Criterion 1.2.1 H96: Using the track element to provide audio descriptions Failures for Success Criterion 1.2.1 F30: Failure of Success Criterion 1.1.1 and 1.2.1 due to using text alternatives that are not alternatives (e.g., filenames or placeholder text) F67: Failure of Success Criterion 1.1.1 and 1.2.1 due to providing long descriptions for non-text content that does not serve the same purpose or does not present the same information Back to top 1.2.2 Captions (Prerecorded) Level A Captions are provided for all prerecorded audio content in synchronized media, except when the media is a media alternative for text and is clearly labeled as such. Understanding 1.2.2 Show Hide techniques and failures for 1.2.2 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 1.2.2 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. G93: Providing open (always visible) captions G87: Providing closed captions using any readily available media format that has a video player that supports closed captioning G87: Providing closed captions using any of the technology-specific techniques below SM11: Providing captions through synchronized text streams in SMIL 1.0 SM12: Providing captions through synchronized text streams in SMIL 2.0 H95: Using the track element to provide captions Failures for Success Criterion 1.2.2 F8: Failure of Success Criterion 1.2.2 due to captions omitting some dialogue or important sound effects F75: Failure of Success Criterion 1.2.2 by providing synchronized media without captions when the synchronized media presents more information than is presented on the page F74: Failure of Success Criterion 1.2.2 and 1.2.8 due to not labeling a synchronized media alternative to text as an alternative Back to top 1.2.3 Audio Description or Media Alternative (Prerecorded) Level A An alternative for time-based media or audio description of the prerecorded video content is provided for synchronized media, except when the media is a media alternative for text and is clearly labeled as such. Understanding 1.2.3 Show Hide techniques and failures for 1.2.3 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 1.2.3 Note: Other techniques may also be sufficient if they meet the success criterion." "See Understanding Techniques. G69: Providing an alternative for time based media using one of the following techniques G58: Placing a link to the alternative for time-based media immediately next to the non-text content Linking to the alternative for time-based media using one of the following techniques H53: Using the body of the object element G78: Providing a second, user-selectable, audio track that includes audio descriptions G173: Providing a version of a movie with audio descriptions SM6: Providing audio description in SMIL 1.0 SM7: Providing audio description in SMIL 2.0 Using any player that supports audio and video G8: Providing a movie with extended audio descriptions SM1: Adding extended audio description in SMIL 1.0 SM2: Adding extended audio description in SMIL 2.0 Using any player that supports audio and video G203: Using a static text alternative to describe a talking head video Advisory Techniques for Success Criterion 1.2.3 H96: Using the track element to provide audio descriptions Back to top 1.2.4 Captions (Live) Level AA Captions are provided for all live audio content in synchronized media. Understanding 1.2.4 Show Hide techniques and failures for 1.2.4 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 1.2.4 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. G9: Creating captions for live synchronized media AND G93: Providing open (always visible) captions G9: Creating captions for live synchronized media AND G87: Providing closed captions G9: Creating captions for live synchronized media SM11: Providing captions through synchronized text streams in SMIL 1.0 SM12: Providing captions through synchronized text streams in SMIL 2.0 AND G87: Providing closed captions SM11: Providing captions through synchronized text streams in SMIL 1.0 SM12: Providing captions through synchronized text streams in SMIL 2.0 Back to top 1.2.5 Audio Description (Prerecorded) Level AA Audio description is provided for all prerecorded video content in synchronized media." "Understanding 1.2.5 Show Hide techniques and failures for 1.2.5 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 1.2.5 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. G78: Providing a second, user-selectable, audio track that includes audio descriptions G173: Providing a version of a movie with audio descriptions SM6: Providing audio description in SMIL 1.0 SM7: Providing audio description in SMIL 2.0 Using any player that supports audio and video G8: Providing a movie with extended audio descriptions SM1: Adding extended audio description in SMIL 1.0 SM2: Adding extended audio description in SMIL 2.0 Using any player that supports audio and video G203: Using a static text alternative to describe a talking head video Advisory Techniques for Success Criterion 1.2.5 H96: Using the track element to provide audio descriptions Back to top 1.2.6 Sign Language (Prerecorded) Level AAA Sign language interpretation is provided for all prerecorded audio content in synchronized media. Understanding 1.2.6 Show Hide techniques and failures for 1.2.6 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 1.2.6 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques." "G54: Including a sign language interpreter in the video stream G81: Providing a synchronized video of the sign language interpreter that can be displayed in a different viewport or overlaid on the image by the player SM13: Providing sign language interpretation through synchronized video streams in SMIL 1.0 SM14: Providing sign language interpretation through synchronized video streams in SMIL 2.0 Back to top 1.2.7 Extended Audio Description (Prerecorded) Level AAA Where pauses in foreground audio are insufficient to allow audio descriptions to convey the sense of the video, extended audio description is provided for all prerecorded video content in synchronized media. Understanding 1.2.7 Show Hide techniques and failures for 1.2.7 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 1.2.7 Note: Other techniques may also be sufficient if they meet the success criterion. See Under standing Techniques. G8: Providing a movie with extended audio descriptions SM1: Adding extended audio description in SMIL 1.0 SM2: Adding extended audio description in SMIL 2.0 Using any player that supports audio and video Advisory Techniques for Success Criterion 1.2.7 H96: Using the track element to provide audio descriptions Back to top 1.2.8 Media Alternative (Prerecorded) Level AAA An alternative for time-based media is provided for all prerecorded synchronized media and for all prerecorded video-only media. Understanding 1.2.8 Show Hide techniques and failures for 1.2.8 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 1.2.8 Note: Other techniques may also be sufficient if they meet the success criterion." See Understanding Techniques. Situation A: If the content is prerecorded synchronized media: G69: Providing an alternative for time based media G58: Placing a link to the alternative for time-based media immediately next to the non-text content Linking to the alternative for time-based media using one of the following techniques H53: Using the body of the object element Situation B: If the content is prerecorded video-only: G159: Providing an alternative for time-based media for video-only content Advisory Techniques for Success Criterion 1.2.8 H46: Using noembed with embed Failures for Success Criterion 1.2.8 F74: Failure of Success Criterion 1.2.2 and 1.2.8 due to not labeling a synchronized media alternative to text as an alternative Back to top 1.2.9 Audio-only (Live) Level AAA An alternative for time-based media that presents equivalent information for live audio-only content is provided. Understanding 1.2.9 Show Hide techniques and failures for 1.2.9 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 1.2.9 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. G151: Providing a link to a text transcript of a prepared statement or script if the script is followed G150: Providing text based alternatives for live audio-only content G157: Incorporating a live audio captioning service into a Web page Back to top Guideline 1.3 – Adaptable Create content that can be presented in different ways (for example simpler layout) without losing information or structure. "1.3.1 Info and Relationships Level A Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. Understanding 1.3.1 Show Hide techniques and failures for 1.3.1 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 1.3.1 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. Situation A: The technology provides semantic structure to make information and relationships conveyed through presentation programmatically determinable: ARIA11: Using ARIA landmarks to identify regions of a page ARIA12: Using role=heading to identify headings ARIA13: Using aria-labelledby to name regions and landmarks ARIA16: Using aria-labelledby to provide a name for user interface controls ARIA17: Using grouping roles to identify related form controls ARIA20: Using the region role to identify a region of the page G115: Using semantic elements to mark up structure AND H49: Using semantic markup to mark emphasized or special text G117: Using text to convey information that is conveyed by variations in presentation of text G140: Separating information and structure from presentation to enable different presentations ARIA24: Semantically identifying a font icon with role=""img"" Making information and relationships conveyed through presentation programmatically determinable using the following techniques: G138: Using semantic markup whenever color cues are used H51: Using table markup to present tabular information PDF6: Using table elements for table markup in PDF Documents PDF20: Using Adobe Acrobat Pro's Table Editor to repair mistagged tables H39: Using caption elements to associate data table captions with data tables H73: Using the summary attribute of the table element to give an overview of data tables H63: Using the scope attribute to associate header cells and data cells in data tables H43: Using id and headers attributes to associate data cells with header cells in data tables H44: Using label elements to associate text labels with form controls H65: Using the title attribute to identify form controls when the label element cannot be used PDF10: Providing labels for interactive form controls in PDF documents PDF12: Providing name, role, value information for form fields in PDF documents H71: Providing a description for groups of form controls using fieldset and legend elements H85: Using OPTGROUP to group OPTION elements inside a SELECT H48: Using ol, ul and dl for lists or groups of links H42: Using h1-h6 to identify headings PDF9: Providing headings by marking content with heading tags in PDF documents SCR21: Using functions of the Document Object Model (DOM) to add content to a page PDF11: Providing links and link text using the Link annotation and the /Link structure element in PDF documents PDF17: Specifying consistent page numbering for PDF documents PDF21: Using List tags for lists in PDF documents H97: Grouping related links using the nav element Situation B: The technology in use does NOT provide the semantic structure to make the information and relationships conveyed through presentation programmatically determinable: G117: Using text to convey information that is conveyed by variations in presentation of text Making information and relationships conveyed through presentation programmatically determinable or available in text using the following techniques: T1: Using standard text formatting conventions for paragraphs T2: Using standard text formatting conventions for lists T3: Using standard text formatting conventions for headings Advisory Techniques for Success Criterion 1.3.1 C22: Using CSS to control visual presentation of text G162: Positioning labels to maximize predictability of relationships ARIA1: Using the aria-describedby property to provide a descriptive label for user interface controls ARIA2: Identifying a required field with the aria-required property G141: Organizing a page using headings Failures for Success Criterion 1.3.1 F2: Failure of Success Criterion 1.3.1 due to using changes in text presentation to convey information without using the appropriate markup or text F33: Failure of Success Criterion 1.3.1 and 1.3.2 due to using white space characters to create multiple columns in plain text content F34: Failure of Success Criterion 1.3.1 and 1.3.2 due to using white space characters to format tables in plain text content F42: Failure of Success Criteria 1.3.1, 2.1.1, 2.1.3, or 4.1.2 when emulating links F43: Failure of Success Criterion 1.3.1 due to using structural markup in a way that does not represent relationships in the content F46: Failure of Success Criterion 1.3.1 due to using th elements, layout tables F48: Failure of Success Criterion 1.3.1 due to using the pre element to markup tabular information F87: Failure of Success Criterion 1.3.1 due to inserting non-decorative content by using ::before and ::after pseudo-elements and the 'content' property in CSS F90: Failure of Success Criterion 1.3.1 for incorrectly associating table headers and content via the headers and id attributes F91: Failure of Success Criterion 1.3.1 for not correctly marking up table headers F92: Failure of Success Criterion 1.3.1 due to the use of role presentation on content which conveys semantic information Back to top 1.3.2 Meaningful Sequence Level A When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined. Understanding 1.3.2 Show Hide techniques and failures for 1.3.2 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 1.3.2 Note: Other techniques may also be sufficient if they meet the success criterion." "See Understanding Techniques. G57: Ordering the content in a meaningful sequence G57: Ordering the content in a meaningful sequence H34: Using a Unicode right-to-left mark (RLM) or left-to-right mark (LRM) to mix text direction inline H56: Using the dir attribute on an inline element to resolve problems with nested directional runs C6: Positioning content based on structural markup C8: Using CSS letter-spacing to control spacing within a word C27: Making the DOM order match the visual order PDF3: Ensuring correct tab and reading order in PDF documents Failures for Success Criterion 1.3.2 F34: Failure of Success Criterion 1.3.1 and 1.3.2 due to using white space characters to format tables in plain text content F33: Failure of Success Criterion 1.3.1 and 1.3.2 due to using white space characters to create multiple columns in plain text content F32: Failure of Success Criterion 1.3.2 due to using white space characters to control spacing within a word F49: Failure of Success Criterion 1.3.2 due to using an HTML layout table that does not make sense when linearized F1: Failure of Success Criterion 1.3.2 due to changing the meaning of content by positioning information with CSS Back to top 1.3.3 Sensory Characteristics Level A Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, color, size, visual location, orientation, or sound. Note 1: For requirements related to color, refer to Guideline 1.4. Understanding 1.3.3 Show Hide techniques and failures for 1.3.3 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 1.3.3 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques." "G96: Providing textual ident ification of items that otherwise rely only on sensory information to be understood Failures for Success Criterion 1.3.3 F14: Failure of Success Criterion 1.3.3 due to identifying content only by its shape or location F26: Failure of Success Criterion 1.3.3 due to using a graphical symbol alone to convey information Back to top 1.3.4 Orientation Level AA (Added in 2.1) Content does not restrict its view and operation to a single display orientation, such as portrait or landscape, unless a specific display orientation is essential. Understanding 1.3.4 Show Hide techniques and failures for 1.3.4 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 1.3.4 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. G214: Using a control to allow access to content in different orientations which is otherwise restricted Failures for Success Criterion 1.3.4 F97: Failure due to locking the orientation to landscape or portrait view F100: Failure of Success Criterion 1.3.4 due to showing a message asking to reorient device Back to top 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. Understanding 1.3.5 Back to top 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.3.6 Show Hide techniques and failures for 1.3.6 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 1.3.6 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. Programmatically indicating the purpose of icons, regions and user interface components ARIA11: Using ARIA landmarks to identify regions of a page Using microdata to markup user interface components (future link) Advisory Techniques for Success Criterion 1.3.6 Enabling user agents to find the version of the content that best fits their needs Using semantics to identify important features (e.g., coga-simplification=""simplest"") Using aria-invalid and aria-required Back to top Guideline 1.4 – Distinguishable Make it easier for users to see and hear content including separating foreground from background. 1.4.1 Use of Color Level A Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. Note 1: This success criterion addresses color perception specifically." "Other forms of perception are covered in Guideline 1.3 including programmatic access to color and other visual presentation coding. Understanding 1.4.1 Show Hide techniques and failures for 1.4.1 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 1.4.1 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. Situation A: If the color of particular words, backgrounds, or other content is used to indicate information: G14: Ensuring that information conveyed by color differences is also available in text G205: Including a text cue for colored form control labels G182: Ensuring that additional visual cues are available when text color differences are used to convey information G183: Using a contrast ratio of 3:1 with surrounding text and providing additional visual cues on hover for links or controls where color alone is used to identify them Situation B: If color is used within an image to convey information: G111: Using color and pattern G14: Ensuring that information conveyed by color differences is also available in text Advisory Techniques for Success Criterion 1.4.1 C15: Using CSS to change the presentation of a user interface component when it receives focus Failures for Success Criterion 1.4.1 F13: Failure of Success Criterion 1.1.1 and 1.4.1 due to having a text alternative that does not include information that is conveyed by color differences in the image F73: Failure of Success Criterion 1.4.1 due to creating links that are not visually evident without color vision F81: Failure of Success Criterion 1.4.1 due to identifying required or error fields using color differences only Back to top 1.4.2 Audio Control Level A If any audio on a Web page plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level. Understanding 1.4.2 Show Hide techniques and failures for 1.4.2 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 1.4.2 Note: Other techniques may also be sufficient if they meet the success criterion." "See Understanding Techniques. G60: Playing a sound that turns off automatically within three seconds G170: Providing a control near the beginning of the Web page that turns off sounds that play automatically G171: Playing sounds only on user request Failures for Success Criterion 1.4.2 F23: Failure of 1.4.2 due to playing a sound longer than 3 seconds where there is no mechanism to turn it off F93: Failure of Success Criterion 1.4.2 for absence of a way to pause or stop an HTML5 media element that autoplays Back to top 1.4.3 Contrast (Minimum) Level AA The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for the following: Large Text: Large-scale text and images of large-scale text have a contrast ratio of at least 3:1; Incidental: Text or images of text that are part of an inactive user interface component, that are pure decoration, that are not visible to anyone, or that are part of a picture that contains significant other visual content, have no contrast requirement. Logotypes: Text that is part of a logo or brand name has no contrast requirement. Understanding 1.4.3 Show Hide techniques and failures for 1.4.3 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 1.4.3 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques." "Situation A: text is less than 18 point if not bold and less than 14 point if bold G18: Ensuring that a contrast ratio of at least 4.5:1 exists between text (and images of text) and background behind the text G148: Not specifying background color, not specifying text color, and not using technology features that change those defaults G174: Providing a control with a sufficient contrast ratio that allows users to switch to a presentation that uses sufficient contrast Situation B: text is at least 18 point if not bold and at least 14 point if bold G145: Ensuring that a contrast ratio of at least 3:1 exists between text (and images of text) and background behind the text G148: Not specifying background color, not specifying text color, and not using technology features that change those defaults G174: Providing a control with a sufficient contrast ratio that allows users to switch to a presentation that uses sufficient contrast Advisory Techniques for Success Criterion 1.4.3 G156: Using a technology that has commonly-available user agents that can change the foreground and background of blocks of text Failures for Success Criterion 1.4.3 F24: Failure of Success Criterion 1.4.3, 1.4.6 and 1.4.8 due to specifying foreground colors without specifying background colors or vice versa F83: Failure of Success Criterion 1.4.3 and 1.4.6 due to using background images that do not provide sufficient contrast with foreground text (or images of text) Back to top 1.4.4 Resize Text Level AA Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality. Understanding 1.4.4 Show Hide techniques and failures for 1.4.4 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 1.4.4 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. G142: Using a technology that has commonly-available user agents that support zoom Ensuring that text containers resize when the text resizes AND using measurements that are relative to other measurements in the content by using one or more of the following techniques: C28: Specifying the size of text containers using em units Techniques for relative measurements C12: Using percent for font sizes C13: Using named font sizes C14: Using em units for font sizes Techniques for text container resizing SCR34: Calculating size and position in a way that scales with text size G146: Using liquid layout G178: Providing controls on the Web page that allow users to incrementally change the size of all text on the page up to 200 percent G179: Ensuring that there is no loss of content or functionality when the text resizes and text containers do not change their width Advisory Techniques for Success Criterion 1.4.4 C17: Scaling form elements which contain text C20: Using relative measurements to set column widths so that lines can average 80 characters or less when the browser is resized C22: Using CSS to control visual presentation of text Failures for Success Criterion 1.4.4 F69: Failure of Success Criterion 1.4.4 when resizing visually rendered text up to 200 percent causes the text, image or controls to be clipped, truncated or obscured F80: Failure of Success Criterion 1.4.4 when text-based form controls do not resize when visually rendered text is resized up to 200% F94: Failure of Success Criterion 1.4.4 due to incorrect use of viewport units to resize text Back to top 1.4.5 Images of Text Level AA If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text except for the following: Customizable: The image of text can be visually customized to the user's requirements; Essential: A particular presentation of text is essential to the information being conveyed. Note 1: Logotypes (text that is part of a logo or brand name) are considered essential." "Understanding 1.4.5 Show Hide techniques and failures for 1.4.5 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 1.4.5 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. C22: Using CSS to control visual presentation of text C30: Using CSS to replace text with images of text and providing user interface controls to switch G140: Separating information and structure from presentation to enable different presentations PDF7: Performing OCR on a scanned PDF document to provide actual text Advisory Techniques for Success Criterion 1.4.5 C12: Using percent for font sizes C13: Using named font sizes C14: Using em units for font sizes C8: Using CSS letter-spacing to control spacing within a word C6: Positioning content based on structural markup Back to top 1.4.6 Contrast (Enhanced) Level AAA The visual presentation of text and images of text has a contrast ratio of at least 7:1, except for the following: Large Text: Large-scale text and images of large-scale text have a contrast ratio of at least 4.5:1; Incidental: Text or images of text that are part of an inactive user interface component, that are pure decoration, that are not visible to anyone, or that are part of a picture that contains significant other visual content, have no contrast requirement. Logotypes: Text that is part of a logo or brand name has no contrast requirement. Understanding 1.4.6 Show Hide techniques and failures for 1.4.6 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 1.4.6 Note: Other techniques may also be sufficient if they meet the success criterion." "See Understanding Techniques. Situation A: text is less than 18 point if not bold and less than 14 point if bold G17: Ensuring that a contrast ratio of at least 7:1 exists between text (and images of text) and background behind the text G148: Not specifying background color, not specifying text color, and not using technology features that change those defaults G174: Providing a control with a sufficient contrast ratio that allows users to switch to a presentation that uses sufficient contrast Situation B: text is as least 18 point if not bold and at least 14 point if bold G18: Ensuring that a contrast ratio of at least 4.5:1 exists between text (and images of text) and background behind the text G148: Not specifying background color, not specifying text color, and not using technology features that change those defaults G174: Providing a control with a sufficient contrast ratio that allows users to switch to a presentation that uses sufficient contrast Advisory Techniques for Success Criterion 1.4.6 G156: Using a technology that has commonly-available user agents that can change the foreground and background of blocks of text Failures for Success Criterion 1.4.6 F24: Failure of Success Criterion 1.4.3, 1.4.6 and 1.4.8 due to specifying foreground colors without specifying background colors or vice versa F83: Failure of Success Criterion 1.4.3 and 1.4.6 due to using background images that do not provide sufficient contrast with foreground text (or images of text) Back to top 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.7 Show Hide techniques and failures for 1.4.7 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 1.4.7 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. G56: Mixing audio files so that non-speech sounds are at least 20 decibels lower than the speech audio content Back to top 1.4.8 Visual Presentation Level AAA For the visual presentation of blocks of text, a mechanism is available to achieve the following: Foreground and background colors can be selected by the user. Width is no more than 80 characters or glyphs (40 if CJK). Text is not justified (aligned to both the left and the right margins)." "Line spacing (leading) is at least space-and-a-half within paragraphs, and paragraph spacing is at least 1.5 times larger than the line spacing. Text can be resized without assistive technology up to 200 percent in a way that does not require the user to scroll horizontally to read a line of text on a full-screen window. Understanding 1.4.8 Show Hide techniques and failures for 1.4.8 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 1.4.8 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. First Requirement: Techniques to ensure foreground and background colors can be selected by the user C23: Specifying text and background colors of secondary content such as banners, features and navigation in CSS while not specifying text and background colors of the main content OR C25: Specifying borders and layout in CSS to delineate areas of a Web page while not specifying text and text-background colors OR G156: Using a technology that has commonly-available user agents that can change the foreground and background of blocks of text OR G148: Not specifying background color, not specifying text color, and not using technology features that change those defaults OR G175: Providing a multi color selection tool on the page for foreground and background colors OR Second Requirement: Techniques to ensure width is no more than 80 characters or glyphs (40 if CJK) G204: Not interfering with the user agent's reflow of text as the viewing window is narrowed OR C20: Using relative measurements to set column widths so that lines can average 80 characters or less when the browser is resized Third Requirement: Techniques to ensure text is not justified (aligned to both the left and the right margins) C19: Specifying alignment either to the left OR right in CSS OR G172: Providing a mechanism to remove full justification of text OR G169: Aligning text on only one side Fourth Requirement: Techniques to ensure line spacing (leading) is at least space-and-a-half within paragraphs, and paragraph spacing is at least 1.5 times larger than the line spacing G188: Providing a button on the page to increase line spaces and paragraph spaces OR C21: Specifying line spacing in CSS Fifth Requirement: Techniques to ensure text can be resized without assistive technology up to 200 percent in a way that does not require the user to scroll horizontally to read a line of text on a full-screen window Not interfering with the user agent's reflow of text as the viewing window is narrowed G146: Using liquid layout AND using measurements that are relative to other measurements in the content by C12: Using percent for font sizes OR C13: Using named font sizes OR C14: Using em units for font sizes OR C24: Using percentage values in CSS for container sizes OR SCR34: Calculating size and position in a way that scales with text size G206: Providing options within the content to switch to a layout that does not require the user to scroll horizontally to read a line of text Failures for Success Criterion 1.4.8 F24: Failure of Success Criterion 1.4.3, 1.4.6 and 1.4.8 due to specifying foreground colors without specifying background colors or vice versa F88: Failure of Success Criterion 1.4.8 due to using text that is justified (aligned to both the left and the right margins) Back to top 1.4.9 Images of Text (No Exception) Level AAA Images of text are only used for pure decoration or where a particular presentation of text is essential to the information being conveyed." "Note 1: Logotypes (text that is part of a logo or brand name) are considered essential. Understanding 1.4.9 Show Hide techniques and failures for 1.4.9 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 1.4.9 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. C22: Using CSS to control visual presentation of text C30: Using CSS to replace text with images of text and providing user interface controls to switch G140: Separating information and structure from presentation to enable different presentations PDF7: Performing OCR on a scanned PDF document to provide actual text Advisory Techniques for Success Criterion 1.4.9 C12: Using percent for font sizes C13: Using named font sizes C14: Using em units for font sizes C8: Using CSS letter-spacing to control spacing within a word C6: Positioning content based on structural markup Back to top 1.4.10 Reflow Level AA (Added in 2.1) Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions for: Vertical scrolling content at a width equivalent to 320 CSS pixels; Horizontal scrolling content at a height equivalent to 256 CSS pixels; Except for parts of the content which require two-dimensional layout for usage or meaning. Understanding 1.4.10 Show Hide techniques and failures for 1.4.10 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 1.4.10 Note: Other techniques may also be sufficient if they meet the success criterion." "See Understanding Techniques. C32: Using media queries and grid CSS to reflow columns C31: Using CSS Flexbox to reflow content C33: Allowing for Reflow with Long URLs and Strings of Text C38: Using CSS width, max-width and flexbox to fit labels and inputs SCR34: Calculating size and position in a way that scales with text size G206: Providing options within the content to switch to a layout that does not require the user to scroll horizontally to read a line of text Using PDF/UA when creating PDFs (Potential future technique) Advisory Techniques for Success Criterion 1.4.10 C34: Using media queries to un-fixing sticky headers / footers C37: Using CSS max-width and height to fit images CSS, Reflowing simple data tables (Potential future technique) CSS, Fitting data cells within the width of the viewport (Potential future technique) Mechanism to allow mobile view at any time (Potential future technique) Failures for Success Criterion 1.4.10 F102: Failure of Success Criterion 1.4.10 due to content disappearing and not being available when content has reflowed Back to top 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. Understanding 1.4.11 Show Hide techniques and failures for 1.4.11 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 1.4.11 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. Situation B: Color is required to understand graphical content G207: Ensuring that a contrast ratio of 3:1 is provided for icons G209: Provide sufficient contrast at the boundaries between adjoining colors Text in or over graphics @@ Include labels and values with the graphic (TBD) G18: Ensuring that a contrast ratio of at least 4.5:1 exists between text (and images of text) and background behind the text G145: Ensuring that a contrast ratio of at least 3:1 exists between text (and images of text) and background behind the text G174: Providing a control with a sufficient contrast ratio that allows users to switch to a presentation that uses sufficient contrast Failures for Success Criterion 1.4.11 F78: Failure of Success Criterion 2.4.7 due to styling element outlines and borders in a way that removes or renders non-visible the visual focus indica tor Back to top 1.4.12 Text Spacing Level AA (Added in 2.1) In content implemented using markup languages that support the following text style properties, no loss of content or functionality occurs by setting all of the following and by changing no other style property: Line height (line spacing) to at least 1.5 times the font size; Spacing following paragraphs to at least 2 times the font size; Letter spacing (tracking) to at least 0.12 times the font size; Word spacing to at least 0.16 times the font size." "Exception: Human languages and scripts that do not make use of one or more of these text style properties in written text can conform using only the properties that exist for that combination of language and script. Understanding 1.4.12 Show Hide techniques and failures for 1.4.12 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 1.4.12 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. C36: Allowing for text spacing override C35: Allowing for text spacing without wrapping Advisory Techniques for Success Criterion 1.4.12 C8: Using CSS letter-spacing to control spacing within a word C21: Specifying line spacing in CSS C28: Specifying the size of text containers using em units Failures for Success Criterion 1.4.12 F104: Failure of Success Criterion 1.4.12 due to clipped or overlapped content when text spacing is adjusted Back to top 1.4.13 Content on Hover or Focus Level AA (Added in 2.1) Where receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden, the following are true: Dismissible: A mechanism is available to dismiss the additional content without moving pointer hover or keyboard focus, unless the additional content communicates an input error or does not obscure or replace other content; Hoverable: If pointer hover can trigger the additional content, then the pointer can be moved over the additional content without the additional content disappearing; Persistent: The additional content remains visible until the hover or focus trigger is removed, the user dismisses it, or its information is no longer valid. Exception: The visual presentation of the additional content is controlled by the user agent and is not modified by the author." "Understanding 1.4.13 Show Hide techniques and failures for 1.4.13 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 1.4.13 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. SCR39: Making content on focus or hover hoverable, dismissible, and persistent ARIA: Using role=""tooltip"" (Potential future technique) CSS: Using hover and focus pseudo classes (Potential future technique) Failures for Success Criterion 1.4.13 F95: Failure of Success Criterion 1.4.13 due to content shown on hover not being hoverable Failure to make content dismissable without moving pointer hover or keyboard focus (Potential future technique) Failure to meet by content on hover or focus not remaining visible until dismissed or invalid (Potential future technique) Back to top Principle 2 – Operable User interface components and navigation must be operable. Guideline 2.1 – Keyboard Accessible Make all functionality available from a keyboard. 2.1.1 Keyboard Level A All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints." "Note 1: This exception relates to the underlying function, not the input technique. For example, if using handwriting to enter text, the input technique (handwriting) requires path-dependent input but the underlying function (text input) does not. Note 2: This does not forbid and should not discourage providing mouse input or other input methods in addition to keyboard operation. Understanding 2.1.1 Show Hide techniques and failures for 2.1.1 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 2.1.1 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques." "G202: Ensuring keyboard control for all functionality Ensuring keyboard control by using one of the following techniques. H91: Using HTML form controls and links PDF3: Ensuring correct tab and reading order in PDF documents PDF11: Providing links and link text using the Link annotation and the /Link structure element in PDF documents PDF23: Providing interactive form controls in PDF documents G90: Providing keyboard-triggered event handlers SCR20: Using both keyboard and other device-specific functions SCR35: Making actions keyboard accessible by using the onclick event of anchors and buttons SCR2: Using redundant keyboard and mouse event handlers Advisory Techniques for Success Criterion 2.1.1 SCR29: Adding keyboard-accessible actions to static HTML elements Failures for Success Criterion 2.1.1 F54: Failure of Success Criterion 2.1.1 due to using only pointing-device-specific event handlers (including gesture) for a function 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 F42: Failure of Success Criteria 1.3.1, 2.1.1, 2.1.3, or 4.1.2 when emulating links Back to top 2.1.2 No Keyboard Trap Level A If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away. Note 1: Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether it is used to meet other success criteria or not) must meet this success criterion. See Conformance Requirement 5: Non-Interference. Understanding 2.1.2 Show Hide techniques and failures for 2.1.2 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 2.1.2 Note: Other techniques may also be sufficient if they meet the success criterion." "See Understanding Techniques. G21: Ensuring that users are not trapped in content Failures for Success Criterion 2.1.2 F10: Failure of Success Criterion 2.1.2 and Conformance Requirement 5 due to combining multiple content formats in a way that traps users inside one format type Back to top 2.1.3 Keyboard (No Exception) Level AAA All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes. Understanding 2.1.3 Back to top 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. Understanding 2.1.4 Show Hide techniques and failures for 2.1.4 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 2.1.4 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques." "G217: Providing a mechanism to allow users to remap or turn off character key shortcuts Failures for Success Criterion 2.1.4 F99: Failure of Success Criterion 2.1.4 due to implementing character key shortcuts that cannot be turned off or remapped Back to top 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 i s 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. Understanding 2.2.1 Show Hide techniques and failures for 2.2.1 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 2.2.1 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. Situation A: If there are session time limits: G133: Providing a checkbox on the first page of a multipart form that allows users to ask for longer session time limit or no session time limit 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: G198: Providing a way for the user to turn the time limit off G180: Providing the user with a means to set the time limit to 10 times the default time limit SCR16: Providing a script that warns the user a time limit is about to expire AND SCR1: Allowing the user to extend the default time limit Situation C: If there are time limits on reading: G4: Allowing the content to be paused and restarted from where it was paused G198: Providing a way for the user to turn the time limit off SCR33: Using script to scroll content, and providing a mechanism to pause it SCR36: Providing a mechanism to allow users to display moving, scrolling, or auto-updating text in a static window or area Failures for Success Criterion 2.2.1 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 F58: Failure of Success Criterion 2.2.1 due to using server-side techniques to automatically redirect pages after a time-out Back to top 2.2.2 Pause, Stop, Hide Level A For moving, blinking, scrolling, or auto-updating information, all of the following are true: Moving, blinking, scrolling: For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it unless the movement, blinking, or scrolling is part of an activity where it is essential; and Auto-updating: For any auto-updating information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it or to control the frequency of the update unless the auto-updating is part of an activity where it is essential." "Note 1: For requirements related to flickering or flashing content, refer to Guideline 2.3. Note 2: Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether it is used to meet other success criteria or not) must meet this success criterion. See Conformance Requirement 5: Non-Interference. Note 3: Content that is updated periodically by software or that is streamed to the user agent is not required to preserve or present information that is generated or received between the initiation of the pause and resuming presentation, as this may not be technically possible, and in many situations could be misleading to do so. Note 4: An animation that occurs as part of a preload phase or similar situation can be considered essential if interaction cannot occur during that phase for all users and if not indicating progress could confuse users or cause them to think that content was frozen or broken." "Understanding 2.2.2 Show Hide techniques and failures for 2.2.2 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 2.2.2 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. G4: Allowing the content to be paused and restarted from where it was paused SCR33: Using script to scroll content, and providing a mechanism to pause it G11: Creating content that blinks for less than 5 seconds G187: Using a technology to include blinking content that can be turned off via the user agent G152: Setting animated gif images to stop blinking after n cycles (within 5 seconds) SCR22: Using scripts to control blinking and stop it in five seconds or less G186: Using a control in the Web page that stops moving, blinking, or auto-updating content G191: Providing a link, button, or other mechanism that reloads the page without any blinking content Failures for Success Criterion 2.2.2 F16: Failure of Success Criterion 2.2.2 due to including scrolling content where movement is not essential to the activity without also including a mechanism to pause and restart the content F47: Failure of Success Criterion 2.2.2 due to using the blink element F4: Failure of Success Criterion 2.2.2 due to using text-decoration:blink without a mechanism to stop it in less than five seconds F50: Failure of Success Criterion 2.2.2 due to a script that causes a blink effect without a mechanism to stop the blinking at 5 seconds or less F7: Failure of Success Criterion 2.2.2 due to an object or applet for more than five seconds Back to top 2.2.3 No Timing Level AAA Timing is not an essential part of the event or activity presented by the content, except for non-interactive synchronized media and real-time events. Understanding 2.2.3 Show Hide techniques and failures for 2.2.3 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 2.2.3 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques." "G5: Allowing users to complete an activity without any time limit Back to top 2.2.4 Interruptions Level AAA Interruptions can be postponed or suppressed by the user, except interruptions involving an emergency. Understanding 2.2.4 Show Hide techniques and failures for 2.2.4 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 2.2.4 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. G75: Providing a mechanism to postpone any updating of content G76: Providing a mechanism to request an update of the content instead of updating automatically SCR14: Using scripts to make nonessential alerts optional Failures for Success Criterion 2.2.4 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 2.2.5 Re-authenticating Level AAA When an authenticated session expires, the user can continue the activity without loss of data after re-authenticating. Understanding 2.2.5 Show Hide techniques and failures for 2.2.5 Sufficient Advisory< /span> Failures Sufficient Techniques for Success Criterion 2.2.5 Note: Other techniques may also be sufficient if they meet the success criterion." "See Understanding Techniques. Providing options to continue without loss of data using one of the following techniques: G105: Saving data so that it can be used after a user re-authenticates G181: Encoding user data as hidden or encrypted data in a re-authorization page Failures for Success Criterion 2.2.5 F12: Failure of Success Criterion 2.2.5 due to having a session time limit without a mechanism re-authentication Back to top 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 2.2.6 Show Hide techniques and failures for 2.2.6 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 2.2.6 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. Setting a session timeout to occur following at least 20 hours of inactivity." "Store user data for more than 20 hours. Provide a warning of the duration of user inactivity at the start of a process. Back to top Guideline 2.3 – Seizures and Physical Reactions Do not design content in a way that is known to cause seizures or physical reactions. 2.3.1 Three Flashes or Below Threshold Level A Web pages do not contain anything that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds. Note 1: Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether it is used to meet other success criteria or not) must meet this success criterion." See Conformance Requirement 5: Non-Interference. Understanding 2.3.1 Show Hide techniques and failures for 2.3.1 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 2.3.1 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. G19: Ensuring that no component of the content flashes more than three times in any 1-second period G176: Keeping the flashing area small enough G15: Using a tool to ensure that content does not violate the general flash threshold or red flash threshold Back to top 2.3.2 Three Flashes Level AAA Web pages do not contain anything that flashes more than three times in any one second period. Understanding 2.3.2 Show Hide techniques and failures for 2.3.2 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 2.3.2 Note: Other techniques may also be sufficient if they meet the success criterion. "See Understanding Techniques. G19: Ensuring that no component of the content flashes more than three times in any 1-second period Back to top 2.3.3 Animation from Interactions Level AAA (Added in 2.1) Motion animation triggered by interaction can be disabled, unless the animation is essential to the functionality or the information being conveyed. Understanding 2.3.3 Show Hide techniques and failures for 2.3.3 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 2.3.3 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. C39: Using the CSS reduce-motion query to prevent motion Gx: Allowing users to set a preference that prevents animation." "Back to top Guideline 2.4 – Navigable Provide ways to help users navigate, find content, and determine where they are. 2.4.1 Bypass Blocks Level A A mechanism is available to bypass blocks of content that are repeated on multiple Web pages. Understanding 2.4.1 Show Hide techniques and failures for 2.4.1 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 2.4.1 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. Creating links to skip blocks of repeated material using one of the following techniques: G1: Adding a link at the top of each page that goes directly to the main content area G123: Adding a link at the beginning of a block of repeated content to go to the end of the b lock G124: Adding links at the top of the page to each area of the content Grouping blocks of repeated material in a way that can be skipped, using one of the following techniques: ARIA11: Using ARIA landmarks to identify regions of a page H69: Providing heading elements at the beginning of each section of content PDF9: Providing headings by marking content with heading tags in PDF documents H70: Using frame elements to group blocks of repeated material AND H64: Using the title attribute of the frame and iframe elements SCR28: Using an expandable and collapsible menu to bypass block of content Advisory Techniques for Success Criterion 2.4.1 C6: Positioning content based on structural markup H97: Grouping related links using the nav element Back to top 2.4.2 Page Titled Level A Web pages have titles that describe topic or purpose." "Understanding 2.4.2 Show Hide techniques and failures for 2.4.2 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 2.4.2 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. G88: Providing descriptive titles for Web pages H25: Providing a title using the title element PDF18: Specifying the document title using the Title entry in the document information dictionary of a PDF document Advisory Techniques for Success Criterion 2.4.2 G127: Identifying a Web page's relationship to a larger collection of Web pages Failures for Success Criterion 2.4.2 F25: Failure of Success Criterion 2.4.2 due to the title of a Web page not identifying the contents Back to top 2.4.3 Focus Order Level A If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability. Understanding 2.4.3 Show Hide techniques and failures for 2.4.3 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 2.4.3 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques." "G59: Placing the interactive elements in an order that follows sequences and relationships within the content Giving focus to elements in an order that follows sequences and relationships within the content using one of the following techniques: C27: Making the DOM order match the visual order PDF3: Ensuring correct tab and reading order in PDF documents Changing a Web page dynamically using one of the following techniques: SCR26: Inserting dynamic content into the Document Object Model immediately following its trigger element SCR37: Creating Custom Dialogs in a Device Independent Way SCR27: Reordering page sections using the Document Object Model Failures for Success Criterion 2.4.3 F44: Failure of Success Criterion 2.4.3 due to using tabindex to create a tab order that does not preserve meaning and operability F85: Failure of Success Criterion 2.4.3 due to using dialogs or menus that are not adjacent to their trigger control in the sequential navigation order Back to top 2.4.4 Link Purpose (In Context) Level A The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general. Understanding 2.4.4 Show Hide techniques and failures for 2.4.4 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 2.4.4 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. G91: Providing link text that describes the purpose of a link H30: Providing link text that describes the purpose of a link for anchor elements H24: Providing text alternatives for the area elements of image maps Allowing the user to choose short or long link text using one of the techniques below: G189: Providing a control near the beginning of the Web page that changes the link text SCR30: Using scripts to change the link text G53: Identifying the purpose of a link using link text combined with the text of the enclosing sentence Providing a supplemental description of the purpose of a link using one of the following techniques: H33: Supplementing link text with the title attribute C7: Using CSS to hide a portion of the link text Identifying the purpose of a link using link text combined with programmatically determined link context using one of the following techniques: ARIA7: Using aria-labelledby for link purpose ARIA8: Using aria-label for link purpose H77: Identifying the purpose of a link using link text combined with its enclosing list item H78: Identifying the purpose of a link using link text combined with its enclosing paragraph H79: Identifying the purpose of a link in a data table using the link text combined with its enclosing table cell and associated table header cells H81: Identifying the purpose of a link in a nested list using link text combined with the parent list item under which the list is nested G91: Providing link text that describes the purpose of a link PDF11: Providing links and link text using the Link annotation and the /Link structure element in PDF documents PDF13: Providing replacement text using the /Alt entry for links in PDF documents Advisory Techniques for Success Criterion 2.4.4 H2: Combining adjacent image and text links for the same resource H80: Identifying the purpose of a link using link text combined with the preceding heading element Failures for Success Criterion 2.4.4 F63: Failure of Success Criterion 2.4.4 due to providing link context only in content that is not related to the link 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 2.4.5 Multiple Ways Level AA More than one way is available to locate a Web page within a set of Web pages except where the Web Page is the result of, or a step in, a process. Understanding 2.4.5 Show Hide techniques and failures for 2.4.5 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 2.4.5 Note: Other techniques may also be sufficient if they meet the success criterion." "See Understanding Techniques. Using two or more of the following techniques: G125: Providing links to navigate to related Web pages G64: Providing a Table of Contents G63: Providing a site map G161: Providing a search function to help users find content G126: Providing a list of links to all other Web pages G185: Linking to all of the pages on the site from the home page Advisory Techniques for Success Criterion 2.4.5 H59: Using the link element and navigation tools PDF2: Creating bookmarks in PDF documents Back to top 2.4.6 Headings and Labels Level AA Headings and labels describe topic or purpose. Understanding 2.4.6 Show Hide techniques and failures for 2.4.6 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 2.4.6 Note: Other techniques may al so be sufficient if they meet the success criterion. See Understanding Techniques. G130: Providing descriptive headings G131: Providing descriptive labels Back to top 2.4.7 Focus Visible Level AA Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible." "Understanding 2.4.7 Show Hide techniques and failures for 2.4.7 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 2.4.7 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. G149: Using user interface components that are highlighted by the user agent when they receive focus C15: Using CSS to change the presentation of a user interface component when it receives focus G165: Using the default focus indicator for the platform so that high visibility default focus indicators will carry over G195: Using an author-supplied, visible focus indicator C40: Creating a two-color focus indicator to ensure sufficient contrast with all components SCR31: Using script to change the background color or border of the element with focus Failures for Success Criterion 2.4.7 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 F78: Failure of Success Criterion 2.4.7 due to styling element outlines and borders in a way that removes or renders non-visible the visual focus indicator Back to top 2.4.8 Location Level AAA Information about the user's location within a set of Web pages is available. Understanding 2.4.8 Show Hide techniques and failures for 2.4.8 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 2.4.8 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques." "G65: Providing a breadcrumb trail G63: Providing a site map G128: Indicating current location within navigation bars G127: Identifying a Web page's relationship to a larger collection of Web pages H59: Using the link element and navigation tools Advisory Techniques for Success Criterion 2.4.8 PDF14: Providing running headers and footers in PDF documents PDF17: Specifying consistent page numbering for PDF documents Back to top 2.4.9 Link Purpose (Link Only) 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. Understanding 2.4.9 Show Hide techniques and failures for 2.4.9 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 2.4.9 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. ARIA8: Using aria-label for link purpose G91: Providing link text that describes the purpose of a link H30: Providing link text that describes the purpose of a link for anchor elements H24: Providing text alternatives for the area elements of image maps Allowing the user to choose short or long link text using one of the techniques below: G189: Providing a control near the beginning of the Web page that changes the link text SCR30: Using scripts to change the link text Providing a supplemental description of the purpose of a link using one of the following techniques: C7: Using CSS to hide a portion of the link text Semantically indicating links using one of the following techniques: PDF11: Providing links and link text using the Link annotation and the /Link structure element in PDF documents PDF13: Providing replacement text using the /Alt entry for links in PDF documents Advisory Techniques for Success Criterion 2.4.9 H2: Combining adjacent image and text links for the same resource H33: Supplementing link text with the title attribute Failures for Success Criterion 2.4.9 F84: Failure of Success Criterion 2.4.9 due to using a non-specific link such as ""click here"" or ""more"" without a mechanism to change the link text to specific text. 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 2.4.10 Section Headings Level AAA Section headings are used to organize the content." "Note 1: ""Heading"" is used in its general sense and includes titles and other ways to add a heading to different types of content. Note 2: This success criterion covers sections within writing, not user interface components. User Interface components are covered under Success Criterion 4.1.2. Understanding 2.4.10 Back to top 2.4.11 Focus Not Obscured (Minimum) Level AA (Added in 2.2) When a user interface component receives keyboard focus, the component is not entirely hidden due to author-created content. Note 1: Where content in a configurable interface can be repositioned by the user, then only the initial positions of user-movable content are considered for testing and conformance of this Success Criterion." "Note 2: Content opened by the user may obscure the component receiving focus. If the user can reveal the focused component without advancing the keyboard focus, the component with focus is not considered hidden due to author-created content. Understanding 2.4.11 Show Hide techniques and failures for 2.4.11 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 2.4.11 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. C43: Using CSS scroll-padding to un- obscure content Failures for Success Criterion 2.4.11 F110: Failure of Success Criterion 2.4.12 Focus Not Obscured (Minimum) due to a sticky footer or header completely hiding focused elements Back to top 2.4.12 Focus Not Obscured (Enhanced) Level AAA (Added in 2.2) When a user interface component receives keyboard focus, no part of the component is hidden by author-created content." "Understanding 2.4.12 Show Hide techniques and failures for 2.4.12 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 2.4.12 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. C43: Using CSS scroll-padding to un-obscure content Failures for Success Criterion 2.4.12 An interaction that causes content to appear over the component with keyboard focus, visually covering part of the focus indicator. This behavior might be encountered with advertising or promotional material meant to provide more information about a product as the user navigates through a catalogue. A page has a sticky footer (attached to the bottom of the viewport)." "When tabbing down the page, a focused item is partially hidden by the footer because content in the viewport scrolls without sufficient scroll padding . Back to top 2.4.13 Focus Appearance Level AAA (Added in 2.2) When the keyboard focus indicator is visible, an area of the focus indicator meets all the following: is at least as large as the area of a 2 CSS pixel thick perimeter of the unfocused component or sub-component, and has a contrast ratio of at least 3:1 between the same pixels in the focused and unfocused states. Exceptions: The focus indicator is determined by the user agent and cannot be adjusted by the author, or The focus indicator and the indicator’s background color are not modified by the author. 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 sub-components that may receive a focus indicator are menu items in an opened drop-down menu, or focusable cells in a grid. Note 3: Contrast calculations can be based on colors defined within the technology (such as HTML, CSS and SVG). Pixels modified by user agent resolution enhancements and anti-aliasing can be ignored. Understanding 2.4.13 Show Hide techniques and failures for 2.4.13 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 2.4.13 Note: Other techniques may also be sufficient if they meet the success criterion." "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 wai-eo-editors@w3.org (a publicly archived list) or wai@w3.org (a WAI staff-only list). Copyright © 2023 W3C ® ( MIT , ERCIM , Keio , Beihang ) Usage policies apply ."