Datasets:

sidereior

/

wcg-standards-adherence

like 0

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.