sidereior/wcg-standards-adherence huggingface dataset:
Success Criterion 2.3.1 Three Flashes or Below Threshold Understanding Three Flashes or Below Threshold | How to Meet Three Flashes or Below Threshold (Level A) Web pages do not contain anything that flashes more than three times in any one second period,
      or the flash is below the general flash and red flash thresholds . Note Since any content that does not meet this success criterion can interfere with a user's
      ability to use the whole page, all content on the Web page (whether it is used to
      meet other success criteria or not) must meet this success criterion. See Conformance Requirement 5: Non-Interference . Success Criterion 2.3.2 Three Flashes Understanding Three Flashes | How to Meet Three Flashes (Level AAA) Web pages do not contain anything that flashes more than three times in any one second period. Success Criterion 2.3.3 Animation from Interactions Understanding Animation from Interactions | How to Meet Animation from Interactions (Level AAA) Motion animation triggered by interaction can be disabled, unless the animation is essential to the functionality or the information being conveyed.
Guideline 2.4 Navigable Understanding Navigable | How to Meet Navigable Provide ways to help users navigate, find content, and determine where they are. Success Criterion 2.4.1 Bypass Blocks Understanding Bypass Blocks | How to Meet Bypass Blocks (Level A) A mechanism is available to bypass blocks of content that are repeated on multiple Web pages . Success Criterion 2.4.2 Page Titled Understanding Page Titled | How to Meet Page Titled (Level A) Web pages have titles that describe topic or purpose. Success Criterion 2.4.3 Focus Order Understanding Focus Order | How to Meet Focus Order (Level A) If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive
      focus in an order that preserves meaning and operability. Success Criterion 2.4.4 Link Purpose (In Context) Understanding Link Purpose (In Context) | How to Meet Link Purpose (In Context) (Level A) The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context , except where the purpose of the link would be ambiguous to users in general .
Success Criterion 2.4.5 Multiple Ways Understanding Multiple Ways | How to Meet Multiple Ways (Level AA) More than one way is available to locate a Web page within a set of Web pages except where the Web Page is the result of, or a step in, a process . Success Criterion 2.4.6 Headings and Labels Understanding Headings and Labels | How to Meet Headings and Labels (Level AA) Headings and labels describe topic or purpose. Success Criterion 2.4.7 Focus Visible Understanding Focus Visible | How to Meet Focus Visible (Level AA) Any keyboard operable user interface has a mode of operation where the keyboard focus
      indicator is visible. Success Criterion 2.4.8 Location Understanding Location | How to Meet Location (Level AAA) Information about the user's location within a set of Web pages is available. Success Criterion 2.4.9 Link Purpose (Link Only) Understanding Link Purpose (Link Only) | How to Meet Link Purpose (Link Only) (Level AAA) A mechanism is available to allow the purpose of each link to be identified from link text alone,
      except where the purpose of the link would be ambiguous to users in general .
Success Criterion 2.4.10 Section Headings Understanding Section Headings | How to Meet Section Headings (Level AAA) Section headings are used to organize the content. Note 1 "Heading" is used in its general sense and includes titles and other ways to add a
      heading to different types of content. Note 2 This success criterion covers sections within writing, not user interface components . User interface components are covered under Success Criterion 4.1.2 . Success Criterion 2.4.11 Focus Not Obscured (Minimum) Understanding Focus Not Obscured (Minimum) | How to Meet Focus Not Obscured (Minimum) (Level AA) [New] When a user interface component receives keyboard focus, the component is not entirely hidden due to author-created content.
Note 1 Where content in a configurable interface can be repositioned by the user, then only the initial positions of user-movable content are considered for testing and conformance of this Success Criterion. Note 2 Content opened by the user may obscure the component receiving focus. If the user can reveal the focused component without advancing the keyboard focus, the component with focus is not considered hidden due to author-created content. Success Criterion 2.4.12 Focus Not Obscured (Enhanced) Understanding Focus Not Obscured (Enhanced) | How to Meet Focus Not Obscured (Enhanced) (Level AAA) [New] When a user interface component receives keyboard focus, no part of the component is hidden by author-created content. Success Criterion 2.4.13 Focus Appearance Understanding Focus Appearance | How to Meet Focus Appearance (Level AAA) [New] When the keyboard focus indicator is visible, an area of the focus indicator meets all the following: is at least as large as the area of a 2 CSS pixel thick perimeter of the unfocused component or sub-component, and has a contrast ratio of at least 3:1 between the same pixels in the focused and unfocused states.
Exceptions: The focus indicator is determined by the user agent and cannot be adjusted by the author, or The focus indicator and the indicator's background color are not modified by the author. Note 1 What is perceived as the user interface component or sub-component (to determine enclosure or size) depends on its visual presentation . The visual presentation includes the component's visible content , border, and component-specific background. It does not include shadow and glow effects outside the component's content, background, or border. Note 2 Examples of sub-components that may receive a focus indicator are menu items in an opened drop-down menu, or focusable cells in a grid.
Note 3 Contrast calculations can be based on colors defined within the technology (such as HTML, CSS and SVG). Pixels modified by user agent resolution enhancements and anti-aliasing can be ignored. Guideline 2.5 Input Modalities Understanding Input Modalities | How to Meet Input Modalities Make it easier for users to operate functionality through various inputs beyond keyboard. Success Criterion 2.5.1 Pointer Gestures Understanding Pointer Gestures | How to Meet Pointer Gestures (Level A) All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential . Note This requirement applies to web content that interprets pointer actions (i.e.
this does not apply to actions that are required to operate the user agent or assistive technology). Success Criterion 2.5.2 Pointer Cancellation Understanding Pointer Cancellation | How to Meet Pointer Cancellation (Level A) For functionality that can be operated using a single pointer , at least one of the following is true: No Down-Event The down-event of the pointer is not used to execute any part of the function; Abort or Undo Completion of the function is on the up-event , and a mechanism is available to abort the function before completion or to undo the function after completion; Up Reversal The up-event reverses any outcome of the preceding down-event; Essential Completing the function on the down-event is essential . Note 1 Functions that emulate a keyboard or numeric keypad key press are considered essential. Note 2 This requirement applies to web content that interprets pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive technology).
Success Criterion 2.5.3 Label in Name Understanding Label in Name | How to Meet Label in Name (Level A) For user interface components with labels that include text or images of text , the name contains the text that is presented visually. Note A best practice is to have  the text of the label at the start of the name. Success Criterion 2.5.4 Motion Actuation Understanding Motion Actuation | How to Meet Motion Actuation (Level A) Functionality that can be operated by device motion or user motion can also be operated by user interface components and responding to the motion can be disabled to prevent accidental actuation, except when: Supported Interface The motion is used to operate functionality through an accessibility supported interface; Essential The motion is essential for the function and doing so would invalidate the activity. Success Criterion 2.5.5 Target Size (Enhanced) Understanding Target Size (Enhanced) | How to Meet Target Size (Enhanced) (Level AAA) The size of the target for pointer inputs is at least 44 by 44 CSS pixels except when: Equivalent The target is available through an equivalent link or control on the same page that is at least 44 by 44 CSS pixels; Inline The target is in a sentence or block of text; User Agent Control The size of the target is determined by the user agent and is not modified by the author; Essential A particular presentation of the target is essential to the information being conveyed. Success Criterion 2.5.6 Concurrent Input Mechanisms Understanding Concurrent Input Mechanisms | How to Meet Concurrent Input Mechanisms (Level AAA) Web content does not restrict use of input modalities available on a platform except where the restriction is essential , required to ensure the security of the content, or required to respect user settings.
Success Criterion 2.5.7 Dragging Movements Understanding Dragging Movements | How to Meet Dragging Movements (Level AA) [New] All functionality that uses a dragging movement for operation can be achieved by a single pointer without dragging, unless dragging is essential or the functionality is determined by the user agent and not modified by the author. Note This requirement applies to web content that interprets pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive technology). Success Criterion 2.5.8 Target Size (Minimum) Understanding Target Size (Minimum) | How to Meet Target Size (Minimum) (Level AA) [New] The size of the target for pointer inputs is at least 24 by 24 CSS pixels , except where: Spacing: Undersized targets (those less than 24 by 24 CSS pixels) are positioned so that if a 24 CSS pixel diameter circle is centered on the bounding box of each, the circles do not intersect another target or the circle for another undersized target; Equivalent: The function can be achieved through a different control on the same page that meets this criterion; Inline: The target is in a sentence or its size is otherwise constrained by the line-height of non-target text; User agent control: The size of the target is determined by the user agent and is not modified by the author; Essential: A particular presentation of the target is essential or is legally required for the information being conveyed. Note 1 Targets that allow for values to be selected spatially based on position within the target are considered one target for the purpose of the success criterion.
Guideline 3.1 Readable Understanding Readable | How to Meet Readable Make text content readable and understandable. Success Criterion 3.1.1 Language of Page Understanding Language of Page | How to Meet Language of Page (Level A) The default human language of each Web page can be programmatically determined . Success Criterion 3.1.2 Language of Parts Understanding Language of Parts | How to Meet Language of Parts (Level AA) The human language of each passage or phrase in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words
      or phrases that have become part of the vernacular of the immediately surrounding
      text. Success Criterion 3.1.3 Unusual Words Understanding Unusual Words | How to Meet Unusual Words (Level AAA) A mechanism is available for identifying specific definitions of words or phrases used in an unusual or restricted way , including idioms and jargon . Success Criterion 3.1.4 Abbreviations Understanding Abbreviations | How to Meet Abbreviations (Level AAA) A mechanism for identifying the expanded form or meaning of abbreviations is available.
Success Criterion 3.1.5 Reading Level Understanding Reading Level | How to Meet Reading Level (Level AAA) When text requires reading ability more advanced than the lower secondary education level after removal of proper names and titles, supplemental content , or a version that does not require reading ability more advanced than the lower
      secondary education level, is available. Success Criterion 3.1.6 Pronunciation Understanding Pronunciation | How to Meet Pronunciation (Level AAA) A mechanism is available for identifying specific pronunciation of words where meaning of the
      words, in context, is ambiguous without knowing the pronunciation. Guideline 3.2 Predictable Understanding Predictable | How to Meet Predictable Make Web pages appear and operate in predictable ways. Success Criterion 3.2.1 On Focus Understanding On Focus | How to Meet On Focus (Level A) When any user interface component receives focus, it does not initiate a change of context . Success Criterion 3.2.2 On Input Understanding On Input | How to Meet On Input (Level A) Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component.
Success Criterion 3.2.3 Consistent Navigation Understanding Consistent Navigation | How to Meet Consistent Navigation (Level AA) Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user. Success Criterion 3.2.4 Consistent Identification Understanding Consistent Identification | How to Meet Consistent Identification (Level AA) Components that have the same functionality within a set of Web pages are identified consistently. Success Criterion 3.2.5 Change on Request Understanding Change on Request | How to Meet Change on Request (Level AAA) Changes of context are initiated only by user request or a mechanism is available to turn off such changes. Success Criterion 3.2.6 Consistent Help Understanding Consistent Help | How to Meet Consistent Help (Level A) [New] If a Web page contains any of the following help mechanisms , and those mechanisms are repeated on multiple Web pages within a set of Web pages , they occur in the same order relative to other page content, unless a change is initiated by the user: Human contact details; Human contact mechanism; Self-help option; A fully automated contact mechanism. Note 1 Help mechanisms may be provided directly on the page, or may be provided via a direct link to a different page containing the information.
Note 2 For this Success Criterion, "the same order relative to other page content" can be thought of as how the content is ordered when the page is serialized. The visual position of a help mechanism is likely to be consistent across pages for the same page variation (e.g., CSS break-point). The user can initiate a change, such as changing the page's zoom or orientation, which may trigger a different page variation. This criterion is concerned with relative order across pages displayed in the same page variation (e.g., same zoom level and orientation). Guideline 3.3 Input Assistance Understanding Input Assistance | How to Meet Input Assistance Help users avoid and correct mistakes.
Success Criterion 3.3.1 Error Identification Understanding Error Identification | How to Meet Error Identification (Level A) If an input error is automatically detected, the item that is in error is identified and the error
      is described to the user in text. Success Criterion 3.3.2 Labels or Instructions Understanding Labels or Instructions | How to Meet Labels or Instructions (Level A) Labels or instructions are provided when content requires user input. Success Criterion 3.3.3 Error Suggestion Understanding Error Suggestion | How to Meet Error Suggestion (Level AA) If an input error is automatically detected and suggestions for correction are known, then the suggestions
      are provided to the user, unless it would jeopardize the security or purpose of the
      content. Success Criterion 3.3.4 Error Prevention (Legal, Financial, Data) Understanding Error Prevention (Legal, Financial, Data) | How to Meet Error Prevention (Legal, Financial, Data) (Level AA) For Web pages that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, at least one of
      the following is true: Reversible Submissions are reversible. Checked Data entered by the user is checked for input errors and the user is provided an opportunity to correct them.
Confirmed A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission. Success Criterion 3.3.5 Help Understanding Help | How to Meet Help (Level AAA) Context-sensitive help is available. Success Criterion 3.3.6 Error Prevention (All) Understanding Error Prevention (All) | How to Meet Error Prevention (All) (Level AAA) For Web pages that require the user to submit information, at least one of the following is true: Reversible Submissions are reversible. Checked Data entered by the user is checked for input errors and the user is provided an opportunity to correct them. Confirmed A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.
Success Criterion 3.3.7 Redundant Entry Understanding Redundant Entry | How to Meet Redundant Entry (Level A) [New] Information previously entered by or provided to the user that is required to be entered again in the same process is either: auto-populated, or available for the user to select. Except when: re-entering the information is essential , the information is required to ensure the security of the content, or previously entered information is no longer valid. Success Criterion 3.3.8 Accessible Authentication (Minimum) Understanding Accessible Authentication (Minimum) | How to Meet Accessible Authentication (Minimum) (Level AA) [New] A cognitive function test (such as remembering a password or solving a puzzle) is not required for any step in an authentication process unless that step provides at least one of the following: Alternative Another authentication method that does not rely on a cognitive function test. Mechanism A mechanism is available to assist the user in completing the cognitive function test. Object Recognition The cognitive function test is to recognize objects.
Personal Content The cognitive function test is to identify non-text content the user provided to the Web site. Note 1 "Object recognition" and "Personal content" may be represented by images, video, or audio. Note 2 Examples of mechanisms that satisfy this criterion include: support for password entry by password managers to reduce memory need, and copy and paste to reduce the cognitive burden of re-typing. Success Criterion 3.3.9 Accessible Authentication (Enhanced) Understanding Accessible Authentication (Enhanced) | How to Meet Accessible Authentication (Enhanced) (Level AAA) [New] A cognitive function test (such as remembering a password or solving a puzzle) is not required for any step in an authentication process unless that step provides at least one of the following: Alternative Another authentication method that does not rely on a cognitive function test. Mechanism A mechanism is available to assist the user in completing the cognitive function test.
4. Robust Content must be robust enough that it can be interpreted by a wide variety of user
            agents, including assistive technologies. Guideline 4.1 Compatible Understanding Compatible | How to Meet Compatible Maximize compatibility with current and future user agents, including assistive technologies. Success Criterion 4.1.1 Parsing (Obsolete and removed) Understanding Parsing (Obsolete and removed) | How to Meet Parsing (Obsolete and removed) Note This criterion was originally adopted to address problems that assistive technology had directly parsing HTML. Assistive technology no longer has any need to directly parse HTML.
Consequently, these problems either no longer exist or are addressed by other criteria. This criterion no longer has utility and is removed. Success Criterion 4.1.2 Name, Role, Value Understanding Name, Role, Value | How to Meet Name, Role, Value (Level A) For all user interface components (including but not limited to: form elements, links and components generated by scripts),
      the name and role can be programmatically determined ; states, properties, and values that can be set by the user can be programmatically set ; and notification of changes to these items is available to user agents , including assistive technologies . Note This success criterion is primarily for Web authors who develop or script their own
      user interface components. For example, standard HTML controls already meet this success
      criterion when used according to specification.
Success Criterion 4.1.3 Status Messages Understanding Status Messages | How to Meet Status Messages (Level AA) In content implemented using markup languages, status messages can be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus. 5. Conformance This section lists requirements for conformance to WCAG 2.2. It also gives information about how to make conformance claims, which
            are optional. Finally, it describes what it means to be accessibility supported , since only accessibility-supported ways of using technologies can be relied upon for conformance.
Understanding Conformance includes further explanation of the accessibility-supported concept. 5.1 Interpreting Normative Requirements The main content of WCAG 2.2 is normative and defines requirements that impact conformance claims. Introductory material, appendices,
               sections marked as "non-normative", diagrams, examples, and notes are informative (non-normative). Non-normative material provides advisory information to help interpret
               the guidelines but does not create requirements that impact a conformance claim. The key words MAY , MUST , MUST NOT , NOT RECOMMENDED , RECOMMENDED , SHOULD , and SHOULD NOT are to be interpreted as described in [ RFC2119 ].
5.2 Conformance Requirements In order for a Web page to conform to WCAG 2.2, all of the following conformance requirements
               must be satisfied: 5.2.1 Conformance Level One of the following levels of conformance is met in full. For Level A conformance (the minimum level of conformance), the Web page satisfies all the Level A Success Criteria, or a conforming alternate version is provided. For Level AA conformance, the Web page satisfies all the Level A and Level AA Success
                     Criteria, or a Level AA conforming alternate version is provided. For Level AAA conformance, the Web page satisfies all the Level A, Level AA and Level
                     AAA Success Criteria, or a Level AAA conforming alternate version is provided. Note 1 Although conformance can only be achieved at the stated levels, authors are encouraged
                  to report (in their claim) any progress toward meeting success criteria from all levels
                  beyond the achieved level of conformance.
Note 2 It is not recommended that Level AAA conformance be required as a general policy for
                  entire sites because it is not possible to satisfy all Level AAA Success Criteria
                  for some content. 5.2.2 Full pages Conformance (and conformance level) is for full Web page(s) only, and cannot be achieved if part of a Web page is excluded. Note 1 For the purpose of determining conformance, alternatives to part of a page's content
                  are considered part of the page when the alternatives can be obtained directly from
                  the page, e.g., a long description or an alternative presentation of a video. Note 2 Authors of Web pages that cannot conform due to content outside of the author's control
                  may consider a Statement of Partial Conformance . Note 3 A full page includes each variation of the page that is automatically presented by
                  the page for various screen sizes (e.g.
variations in a responsive Web page). Each
                  of these variations needs to conform (or needs to have a conforming alternate version)
                  in order for the entire page to conform. 5.2.3 Complete processes When a Web page is one of a series of Web pages presenting a process (i.e., a sequence of steps that need to be completed in order to accomplish an activity),
                  all Web pages in the process conform at the specified level or better. (Conformance
                  is not possible at a particular level if any page in the process does not conform
                  at that level or better.) Example An online store has a series of pages that are used to select and purchase products.
                     All pages in the series from start to finish (checkout) conform in order for any page
                     that is part of the process to conform. 5.2.4 Only Accessibility-Supported Ways of Using Technologies Only accessibility-supported ways of using technologies are relied upon to satisfy the success criteria.
Any information or functionality that is provided
                  in a way that is not accessibility supported is also available in a way that is accessibility
                  supported. (See Understanding accessibility support .) 5.2.5 Non-Interference If technologies are used in a way that is not accessibility supported , or if they are used in a non-conforming way, then they do not block the ability
                  of users to access the rest of the page. In addition, the Web page as a whole continues to meet the conformance requirements under each of the following
                  conditions: when any technology that is not relied upon is turned on in a user agent, when any technology that is not relied upon is turned off in a user agent, and when any technology that is not relied upon is not supported by a user agent In addition, the following success criteria apply to all content on the page, including
                  content that is not otherwise relied upon to meet conformance, because failure to
                  meet them could interfere with any use of the page: 1.4.2 - Audio Control , 2.1.2 - No Keyboard Trap , 2.3.1 - Three Flashes or Below Threshold , and 2.2.2 - Pause, Stop, Hide . Note If a page cannot conform (for example, a conformance test page or an example page),
                  it cannot be included in the scope of conformance or in a conformance claim. For more information, including examples, see Understanding Conformance Requirements .
5.3 Conformance Claims (Optional) Conformance is defined only for Web pages . However, a conformance claim may be made to cover one page, a series of pages, or
               multiple related Web pages. 5.3.1 Required Components of a Conformance Claim Conformance claims are not required . Authors can conform to WCAG 2.2 without making a claim. However, if a conformance
                  claim is made, then the conformance claim must include the following information: Date of the claim Guidelines title, version and URI "Web Content Accessibility Guidelines 2.2 at https://www.w3.org/TR/WCAG22/ " Conformance level satisfied: (Level A, AA or AAA) A concise description of the Web pages , such as a list of URIs for which the claim is made, including whether subdomains
                        are included in the claim.
Note 1 The Web pages may be described by list or by an expression that describes all of the
                        URIs included in the claim. Note 2 Web-based products that do not have a URI prior to installation on the customer's
                        Web site may have a statement that the product would conform when installed. A list of the Web content technologies relied upon . Note 3 If a conformance logo is used, it would constitute a claim and must be accompanied
                  by the required components of a conformance claim listed above. 5.3.2 Optional Components of a Conformance Claim In addition to the required components of a conformance claim above, consider providing
                  additional information to assist users.
Recommended additional information includes: A list of success criteria beyond the level of conformance claimed that have been
                     met. This information should be provided in a form that users can use, preferably
                     machine-readable metadata. A list of the specific technologies that are " used but not relied upon ." A list of user agents, including assistive technologies that were used to test the
                     content. A list of specific accessibility characteristics of the content, provided in machine-readable
                     metadata. Information about any additional steps taken that go beyond the success criteria to
                     enhance accessibility.
A machine-readable metadata version of the list of specific technologies that are relied upon . A machine-readable metadata version of the conformance claim. Note 1 Refer to Understanding Conformance Claims for more information and example conformance claims. Note 2 Refer to Understanding Metadata for more information about the use of metadata in conformance claims. 5.4 Statement of Partial Conformance - Third Party Content Web pages that will later have additional content added can use a 'statement of partial
               conformance'.
For example, an email program, a blog, an article that allows users
               to add comments, or applications supporting user-contributed content. Another example
               would be a page, such as a portal or news site, composed of content aggregated from
               multiple contributors, or sites that automatically insert content from other sources
               over time, such as when advertisements are inserted dynamically. In these cases, it is not possible to know at the time of original posting what the
               uncontrolled content of the pages will be. It is important to note that the uncontrolled
               content can affect the accessibility of the controlled content as well. Two options
               are available: A determination of conformance can be made based on best knowledge.
If a page of this
                     type is monitored and repaired (non-conforming content is removed or brought into
                     conformance) within two business days, then a determination or claim of conformance
                     can be made since, except for errors in externally contributed content which are corrected
                     or removed when encountered, the page conforms. No conformance claim can be made if
                     it is not possible to monitor or correct non-conforming content; OR A "statement of partial conformance" may be made that the page does not conform, but
                     could conform if certain parts were removed. The form of that statement would be,
                     "This page does not conform, but would conform to WCAG 2.2 at level X if the following
                     parts from uncontrolled sources were removed." In addition, the following would also
                     be true of uncontrolled content that is described in the statement of partial conformance: It is not content that is under the author's control. It is described in a way that users can identify (e.g., they cannot be described as
                        "all parts that we do not control" unless they are clearly marked as such.) 5.5 Statement of Partial Conformance - Language A "statement of partial conformance due to language" may be made when the page does
               not conform, but would conform if accessibility support existed for (all of) the language(s) used on the page. The form of that statement
               would be, "This page does not conform, but would conform to WCAG 2.2 at level X if
               accessibility support existed for the following language(s):" 5.6 Privacy Considerations This section is non-normative.
Success Criteria within this specification which the Working Group has identified
               possible implications for privacy, either by providing protections for end users or
               which are important for web site providers to take in to consideration when implementing
               features designed to protect user privacy, are listed below. This list reflects the
               current understanding of the Working Group but other Success Criteria may have privacy
               implications that the Working Group is not aware of at the time of publishing. Success Criteria within this specification that may relate to privacy are: 2.2.6 Timeouts (AAA) 3.3.7 Redundant Entry (A) 5.7 Security Considerations This section is non-normative. Success Criteria within this specification which the Working Group has identified
               possible implications for security, either by providing protections for end users
               or which are important for web site providers to take in to consideration when implementing
               features designed to protect user security, are listed below. This list reflects the
               current understanding of the Working Group but other Success Criteria may have security
               implications that the Working Group is not aware of at the time of publishing.
Success Criteria within this specification that may relate to security are: 1.1.1 Non-text Content (A) 1.3.5 Identify Input Purpose (AA) 1.4.7 Low or No Background Audio (AAA) 2.2.1 Timing Adjustable (A) 2.2.5 Re-authenticating (AAA) 2.2.6 Timeouts (AAA) 2.5.6 Concurrent Input Mechanisms (AAA) 3.3.3 Error Suggestion (AA) 3.3.7 Redundant Entry (A) 3.3.8 Accessible Authentication (Minimum) (AA) 3.3.9 Accessible Authentication (Enhanced) (AAA) 6. Glossary abbreviation shortened form of a word, phrase, or name where the abbreviation has not become part
      of the language Note 1 This includes initialisms and acronyms where: initialisms are shortened forms of a name or phrase made from the initial letters of words or
            syllables contained in that name or phrase Note 2 Not defined in all languages. Example 1 SNCF is a French initialism that contains the initial letters of the Société Nationale des Chemins de Fer , the French national railroad. Example 2 ESP is an initialism for extrasensory perception. acronyms are abbreviated forms made from the initial letters or parts of other words (in a
            name or phrase) which may be pronounced as a word Example 3 NOAA is an acronym made from the initial letters of the National Oceanic and Atmospheric
            Administration in the United States.
Note 3 Some companies have adopted what used to be an initialism as their company name. In
      these cases, the new name of the company is the letters (for example, Ecma) and the
      word is no longer considered an abbreviation. accessibility supported supported by users' assistive technologies as well as the accessibility features in browsers and other user agents To qualify as an accessibility-supported use of a Web content technology (or feature
      of a technology), both 1 and 2 must be satisfied for a Web content technology (or
      feature): The way that the Web content technology is used must be supported by users' assistive technology (AT). This means that the way that the technology is used has been tested for interoperability
            with users' assistive technology in the human language(s) of the content, AND The Web content technology must have accessibility-supported user agents that are
               available to users. This means that at least one of the following four statements is true: The technology is supported natively in widely-distributed user agents that are also
                  accessibility supported (such as HTML and CSS); OR The technology is supported in a widely-distributed plug-in that is also accessibility
                  supported; OR The content is available in a closed environment, such as a university or corporate
                  network, where the user agent required by the technology and used by the organization
                  is also accessibility supported; OR The user agent(s) that support the technology are accessibility supported and are
                  available for download or purchase in a way that: does not cost a person with a disability any more than a person without a disability and is as easy to find and obtain for a person with a disability as it is for a person
                     without disabilities.
Note 1 The Accessibility Guidelines Working Group and the W3C do not specify which or how much support by assistive
      technologies there must be for a particular use of a Web technology in order for it
      to be classified as accessibility supported. (See Level of Assistive Technology Support Needed for "Accessibility Support" .) Note 2 Web technologies can be used in ways that are not accessibility supported as long
      as they are not relied upon and the page as a whole meets the conformance requirements, including Conformance Requirement 4 and Conformance Requirement 5 . Note 3 When a Web Technology is used in a way that is "accessibility supported," it does not imply that the entire
      technology or all uses of the technology are supported. Most technologies, including
      HTML, lack support for at least one feature or use. Pages conform to WCAG only if
      the uses of the technology that are accessibility supported can be relied upon to
      meet WCAG requirements.
Note 4 When citing Web content technologies that have multiple versions, the version(s) supported
      should be specified. Note 5 One way for authors to locate uses of a technology that are accessibility supported
      would be to consult compilations of uses that are documented to be accessibility supported.
      (See Understanding Accessibility-Supported Web Technology Uses .) Authors, companies, technology vendors, or others may document accessibility-supported
      ways of using Web content technologies. However, all ways of using technologies in
      the documentation would need to meet the definition of accessibility-supported Web
      content technologies above. alternative for time-based media document including correctly sequenced text descriptions of time-based visual and
      auditory information and providing a means for achieving the outcomes of any time-based
      interaction Note A screenplay used to create the synchronized media content would meet this definition
      only if it was corrected to accurately represent the final synchronized media after
      editing. ambiguous to users in general the purpose cannot be determined from the link and all information of the Web page
      presented to the user simultaneously with the link (i.e., readers without disabilities
      would not know what a link would do until they activated it) Example The word guava in the following sentence "One of the notable exports is guava" is
      a link.
The link could lead to a definition of guava, a chart listing the quantity
      of guava exported or a photograph of people harvesting guava. Until the link is activated,
      all readers are unsure and the person with a disability is not at any disadvantage. ASCII art picture created by a spatial arrangement of characters or glyphs (typically from the
      95 printable characters defined by ASCII) assistive technology (as used in this document) hardware and/or software that acts as a user agent , or along with a mainstream user agent, to provide functionality to meet the requirements
      of users with disabilities that go beyond those offered by mainstream user agents Note 1 Functionality provided by assistive technology includes alternative presentations
      (e.g., as synthesized speech or magnified content), alternative input methods (e.g.,
      voice), additional navigation or orientation mechanisms, and content transformations
      (e.g., to make tables more accessible). Note 2 Assistive technologies often communicate data and messages with mainstream user agents
      by using and monitoring APIs. Note 3 The distinction between mainstream user agents and assistive technologies is not absolute.
      Many mainstream user agents provide some features to assist individuals with disabilities.
      The basic difference is that mainstream user agents target broad and diverse audiences
      that usually include people with and without disabilities.
Assistive technologies
      target narrowly defined populations of users with specific disabilities. The assistance
      provided by an assistive technology is more specific and appropriate to the needs
      of its target users. The mainstream user agent may provide important functionality
      to assistive technologies like retrieving Web content from program objects or parsing
      markup into identifiable bundles. Example Assistive technologies that are important in the context of this document include
      the following: screen magnifiers, and other visual reading assistants, which are used by people with
         visual, perceptual and physical print disabilities to change text font, size, spacing,
         color, synchronization with speech, etc. in order to improve the visual readability
         of rendered text and images; screen readers, which are used by people who are blind to read textual information
         through synthesized speech or braille; text-to-speech software, which is used by some people with cognitive, language, and
         learning disabilities to convert text into synthetic speech; speech recognition software, which may be used by people who have some physical disabilities; alternative keyboards, which are used by people with certain physical disabilities
         to simulate the keyboard (including alternate keyboards that use head pointers, single
         switches, sip/puff and other special input devices.); alternative pointing devices, which are used by people with certain physical disabilities
         to simulate mouse pointing and button activations.
audio the technology of sound reproduction Note Audio can be created synthetically (including speech synthesis), recorded from real
      world sounds, or both. audio description narration added to the soundtrack to describe important visual details that cannot
      be understood from the main soundtrack alone Note 1 Audio description of video provides information about actions, characters, scene changes, on-screen text, and
      other visual content. Note 2 In standard audio description, narration is added during existing pauses in dialogue.
      (See also extended audio description .) Note 3 Where all of the video information is already provided in existing audio , no additional audio description is necessary. Note 4 Also called "video description" and "descriptive narration." audio-only a time-based presentation that contains only audio (no video and no interaction) blinking switch back and forth between two visual states in a way that is meant to draw attention Note See also flash . It is possible for something to be large enough and blink brightly enough at the
      right frequency to be also classified as a flash.
blocks of text more than one sentence of text CAPTCHA initialism for "Completely Automated Public Turing test to tell Computers and Humans
      Apart" Note 1 CAPTCHA tests often involve asking the user to type in text that is displayed in an
      obscured image or audio file. Note 2 A Turing test is any system of tests designed to differentiate a human from a computer.
      It is named after famed computer scientist Alan Turing. The term was coined by researchers
      at Carnegie Mellon University. captions synchronized visual and/or text alternative for both speech and non-speech audio information needed to understand the media content Note 1 Captions are similar to dialogue-only subtitles except captions convey not only the
      content of spoken dialogue, but also equivalents for non-dialogue audio information
      needed to understand the program content, including sound effects, music, laughter,
      speaker identification and location. Note 2 Closed Captions are equivalents that can be turned on and off with some players.
Note 3 Open Captions are any captions that cannot be turned off. For example, if the captions
      are visual equivalent images of text embedded in video . Note 4 Captions should not obscure or obstruct relevant information in the video. Note 5 In some countries, captions are called subtitles. Note 6 Audio descriptions can be, but do not need to be, captioned since they are descriptions of information
      that is already presented visually.
changes of context major changes that, if made without user awareness, can disorient users who are not able to view
      the entire page simultaneously Changes in context include changes of: user agent ; viewport ; focus; content that changes the meaning of the Web page Note A change of content is not always a change of context. Changes in content, such as
      an expanding outline, dynamic menu, or a tab control do not necessarily change the
      context, unless they also change one of the above (e.g., focus). Example Opening a new window, moving focus to a different component, going to a new page (including
      anything that would look to a user as if they had moved to a new page) or significantly
      re-arranging the content of a page are examples of changes of context. Cognitive function test [New] A task that requires the user to remember, manipulate, or transcribe information. Examples include, but are not limited to: memorization, such as remembering a username, password, set of characters, images, or patterns.
The common identifiers name, e-mail, and phone number are not considered cognitive function tests as they are personal to the user and consistent across Web sites; transcription, such as typing in characters; use of correct spelling; performance of calculations; solving of puzzles. conformance satisfying all the requirements of a given standard, guideline or specification conforming alternate version version that conforms at the designated level, and provides all of the same information and functionality in the same human language , and is as up to date as the non-conforming content, and for which at least one of the following is true: the conforming version can be reached from the non-conforming page via an accessibility-supported mechanism , or the non-conforming version can only be reached from the conforming version, or the non-conforming version can only be reached from a conforming page that also provides
               a mechanism to reach the conforming version Note 1 In this definition, "can only be reached" means that there is some mechanism, such
      as a conditional redirect, that prevents a user from "reaching" (loading) the non-conforming
      page unless the user had just come from the conforming version. Note 2 The alternate version does not need to be matched page for page with the original
      (e.g., the conforming alternate version may consist of multiple pages). Note 3 If multiple language versions are available, then conforming alternate versions are
      required for each language offered. Note 4 Alternate versions may be provided to accommodate different technology environments
      or user groups.