[contents]
`
`Web Content Accessibility Guidelines (WCAG) 2.0
`W3C Recommendation 11 December 2008
`
`This version:
`http://www.w3.org/TR/2008/REC-WCAG20-20081211/
`Latest version:
`http://www.w3.org/TR/WCAG20/
`Previous version:
`http://www.w3.org/TR/2008/PR-WCAG20-20081103/
`Editors:
`Ben Caldwell, Trace R&D Center, University of Wisconsin-Madison
`Michael Cooper, W3C
`Loretta Guarino Reid, Google, Inc.
`Gregg Vanderheiden, Trace R&D Center, University of Wisconsin-Madison
`Previous Editors:
`Wendy Chisholm (until July 2006 while at W3C)
`John Slatin (until June 2006 while at Accessibility Institute, University of Texas at Austin)
`Jason White (until June 2005 while at University of Melbourne)
`
`Please refer to the errata for this document, which may include normative corrections.
`
`See also translations.
`
`This document is also available in non-normative formats, available from Alternate Versions of Web Content
`Accessibility Guidelines 2.0.
`
`Copyright © 2008 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use
`rules apply.
`
`Abstract
`
`Web Content Accessibility Guidelines (WCAG) 2.0 covers a wide range of recommendations for making Web
`content more accessible. Following these guidelines will make content accessible to a wider range of people with
`disabilities, including blindness and low vision, deafness and hearing loss, learning disabilities, cognitive
`limitations, limited movement, speech disabilities, photosensitivity and combinations of these. Following these
`guidelines will also often make your Web content more usable to users in general.
`
`WCAG 2.0 success criteria are written as testable statements that are not technology-specific. Guidance about
`satisfying the success criteria in specific technologies, as well as general information about interpreting the
`success criteria, is provided in separate documents. See Web Content Accessibility Guidelines (WCAG) Overview
`for an introduction and links to WCAG technical and educational material.
`
`WCAG 2.0 succeeds Web Content Accessibility Guidelines 1.0 [WCAG10], which was published as a W3C
`Recommendation May 1999. Although it is possible to conform either to WCAG 1.0 or to WCAG 2.0 (or both), the
`W3C recommends that new and updated content use WCAG 2.0. The W3C also recommends that Web
`accessibility policies reference WCAG 2.0.
`
`ACCESSIBE LTD EXHIBIT 1014
`Page 1 of 29
`
`

`

`Status of this Document
`
`This section describes the status of this document at the time of its publication. Other documents may supersede
`this document. A list of current W3C publications and the latest revision of this technical report can be found in the
`W3C technical reports index at http://www.w3.org/TR/.
`
`This is the Web Content Accessibility Guidelines (WCAG) 2.0 W3C Recommendation from the Web Content
`Accessibility Guidelines Working Group.
`
`This document has been reviewed by W3C Members, by software developers, and by other W3C groups and
`interested parties, and is endorsed by the Director as a W3C Recommendation. It is a stable document and may
`be used as reference material or cited from another document. W3C's role in making the Recommendation is to
`draw attention to the specification and to promote its widespread deployment. This enhances the functionality and
`interoperability of the Web.
`
`WCAG 2.0 is supported by the associated non-normative documents, Understanding WCAG 2.0 and Techniques
`for WCAG 2.0. Although those documents do not have the formal status that WCAG 2.0 itself has, they provide
`information important to understanding and implementing WCAG.
`
`The Working Group requests that any comments be made using the provided online comment form. If this is not
`possible, comments can also be sent to public-comments-wcag20@w3.org. The archives for the public comments
`list are publicly available. Comments received on the WCAG 2.0 Recommendation cannot result in changes to this
`version of the guidelines, but may be addressed in errata or future versions of WCAG. The Working Group does
`not plan to make formal responses to comments. Archives of the WCAG WG mailing list discussions are publicly
`available, and future work undertaken by the Working Group may address comments received on this document.
`
`This document has been produced as part of the W3C Web Accessibility Initiative (WAI). The goals of the WCAG
`Working Group are discussed in the WCAG Working Group charter. The WCAG Working Group is part of the WAI
`Technical Activity.
`
`This document was produced by a group operating under the 5 February 2004 W3C Patent Policy. W3C maintains
`a public list of any patent disclosures made in connection with the deliverables of the group; that page also
`includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the
`individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the
`W3C Patent Policy.
`
`Table of Contents
`
`Introduction
`WCAG 2.0 Layers of Guidance
`WCAG 2.0 Supporting Documents
`Important Terms in WCAG 2.0
`WCAG 2.0 Guidelines
`1 Perceivable
`1.1 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.2 Provide alternatives for time-based media.
`1.3 Create content that can be presented in different ways (for example simpler layout) without
`losing information or structure.
`1.4 Make it easier for users to see and hear content including separating foreground from
`background.
`2 Operable
`2.1 Make all functionality available from a keyboard.
`2.2 Provide users enough time to read and use content.
`2.3 Do not design content in a way that is known to cause seizures.
`2.4 Provide ways to help users navigate, find content, and determine where they are.
`3 Understandable
`3.1 Make text content readable and understandable.
`
`ACCESSIBE LTD EXHIBIT 1014
`Page 2 of 29
`
`

`

`3.2 Make Web pages appear and operate in predictable ways.
`3.3 Help users avoid and correct mistakes.
`4 Robust
`4.1 Maximize compatibility with current and future user agents, including assistive
`technologies.
`
`Conformance
`Conformance Requirements
`Conformance Claims (Optional)
`Statement of Partial Conformance - Third Party Content
`Statement of Partial Conformance - Language
`
`Appendices
`
`Appendix A: Glossary (Normative)
`Appendix B: Acknowledgments
`Appendix C: References
`
`Introduction
`
`This section is informative.
`
`Web Content Accessibility Guidelines (WCAG) 2.0 defines how to make Web content more accessible to people
`with disabilities. Accessibility involves a wide range of disabilities, including visual, auditory, physical, speech,
`cognitive, language, learning, and neurological disabilities. Although these guidelines cover a wide range of issues,
`they are not able to address the needs of people with all types, degrees, and combinations of disability. These
`guidelines also make Web content more usable by older individuals with changing abilities due to aging and often
`improve usability for users in general.
`
`WCAG 2.0 is developed through the W3C process in cooperation with individuals and organizations around the
`world, with a goal of providing a shared standard for Web content accessibility that meets the needs of individuals,
`organizations, and governments internationally. WCAG 2.0 builds on WCAG 1.0 [WCAG10] and is designed to
`apply broadly to different Web technologies now and in the future, and to be testable with a combination of
`automated testing and human evaluation. For an introduction to WCAG, see the Web Content Accessibility
`Guidelines (WCAG) Overview.
`
`Web accessibility depends not only on accessible content but also on accessible Web browsers and other user
`agents. Authoring tools also have an important role in Web accessibility. For an overview of how these components
`of Web development and interaction work together, see:
`
`Essential Components of Web Accessibility
`User Agent Accessibility Guidelines (UAAG) Overview
`Authoring Tool Accessibility Guidelines (ATAG) Overview
`
`WCAG 2.0 Layers of Guidance
`
`The individuals and organizations that use WCAG vary widely and include Web designers and developers, policy
`makers, purchasing agents, teachers, and students. In order to meet the varying needs of this audience, several
`layers of guidance are provided including overall principles, general guidelines, testable success criteria and a rich
`collection of sufficient techniques, advisory techniques, and documented common failures with examples, resource
`links and code.
`
`Principles - At the top are four principles that provide the foundation for Web accessibility: perceivable,
`operable, understandable, and robust. See also Understanding the Four Principles of Accessibility.
`Guidelines - Under the principles are guidelines. The 12 guidelines provide the basic goals that authors
`should work toward in order to make content more accessible to users with different disabilities. The
`guidelines are not testable, but provide the framework and overall objectives to help authors understand the
`success criteria and better implement the techniques.
`
`ACCESSIBE LTD EXHIBIT 1014
`Page 3 of 29
`
`

`

`Success Criteria - For each guideline, testable success criteria are provided to allow WCAG 2.0 to be used
`where requirements and conformance testing are necessary such as in design specification, purchasing,
`regulation, and contractual agreements. In order to meet the needs of different groups and different
`situations, three levels of conformance are defined: A (lowest), AA, and AAA (highest). Additional
`information on WCAG levels can be found in Understanding Levels of Conformance.
`Sufficient and Advisory Techniques - For each of the guidelines and success criteria in the WCAG 2.0
`document itself, the working group has also documented a wide variety of techniques. The techniques are
`informative and fall into two categories: those that are sufficient for meeting the success criteria and those
`that are advisory. The advisory techniques go beyond what is required by the individual success criteria and
`allow authors to better address the guidelines. Some advisory techniques address accessibility barriers that
`are not covered by the testable success criteria. Where common failures are known, these are also
`documented. See also Sufficient and Advisory Techniques in Understanding WCAG 2.0.
`
`All of these layers of guidance (principles, guidelines, success criteria, and sufficient and advisory techniques)
`work together to provide guidance on how to make content more accessible. Authors are encouraged to view and
`apply all layers that they are able to, including the advisory techniques, in order to best address the needs of the
`widest possible range of users.
`
`Note that even content that conforms at the highest level (AAA) will not be accessible to individuals with all types,
`degrees, or combinations of disability, particularly in the cognitive language and learning areas. Authors are
`encouraged to consider the full range of techniques, including the advisory techniques, as well as to seek relevant
`advice about current best practice to ensure that Web content is accessible, as far as possible, to this community.
`Metadata may assist users in finding content most suitable for their needs.
`
`WCAG 2.0 Supporting Documents
`
`The WCAG 2.0 document is designed to meet the needs of those who need a stable, referenceable technical
`standard. Other documents, called supporting documents, are based on the WCAG 2.0 document and address
`other important purposes, including the ability to be updated to describe how WCAG would be applied with new
`technologies. Supporting documents include:
`
`1. How to Meet WCAG 2.0 - A customizable quick reference to WCAG 2.0 that includes all of the guidelines,
`success criteria, and techniques for authors to use as they are developing and evaluating Web content.
`2. Understanding WCAG 2.0 - A guide to understanding and implementing WCAG 2.0. There is a short
`"Understanding" document for each guideline and success criterion in WCAG 2.0 as well as key topics.
`3. Techniques for WCAG 2.0 - A collection of techniques and common failures, each in a separate document
`that includes a description, examples, code and tests.
`4. The WCAG 2.0 Documents - A diagram and description of how the technical documents are related and
`linked.
`
`See Web Content Accessibility Guidelines (WCAG) Overview for a description of the WCAG 2.0 supporting
`material, including education resources related to WCAG 2.0. Additional resources covering topics such as the
`business case for Web accessibility, planning implementation to improve the accessibility of Web sites, and
`accessibility policies are listed in WAI Resources.
`
`Important Terms in WCAG 2.0
`
`WCAG 2.0 includes three important terms that are different from WCAG 1.0. Each of these is introduced briefly
`below and defined more fully in the glossary.
`
`Web Page
`It is important to note that, in this standard, the term "Web page" includes much more than static HTML
`pages. It also includes the increasingly dynamic Web pages that are emerging on the Web, including
`"pages" that can present entire virtual interactive communities. For example, the term "Web page"
`includes an immersive, interactive movie-like experience found at a single URI. For more information, see
`Understanding "Web Page".
`Programmatically Determined
`
`ACCESSIBE LTD EXHIBIT 1014
`Page 4 of 29
`
`

`

`Several success criteria require that content (or certain aspects of content) can be "programmatically
`determined." This means that the content is delivered in such a way that user agents, including assistive
`technologies, can extract and present this information to users in different modalities. For more
`information, see Understanding Programmatically Determined.
`Accessibility Supported
`Using a technology in a way that is accessibility supported means that it works with assistive technologies
`(AT) and the accessibility features of operating systems, browsers, and other user agents. Technology
`features can only be relied upon to conform to WCAG 2.0 success criteria if they are used in a way that is
`"accessibility supported". Technology features can be used in ways that are not accessibility supported
`(do not work with assistive technologies, etc.) as long as they are not relied upon to conform to any
`success criterion (i.e., the same information or functionality is also available another way that is
`supported).
`The definition of "accessibility supported" is provided in the Appendix A: Glossary section of these
`guidelines. For more information, see Understanding Accessibility Support.
`WCAG 2.0 Guidelines
`
`This section is normative.
`
`Principle 1: Perceivable - Information and user interface components must be
`presentable to users in ways they can perceive.
`
`Understanding Guideline 1.1
`
`How to Meet 1.1.1
`Understanding 1.1.1
`
`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: 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.
`(Level A)
`Controls, Input: If non-text content is a control or accepts user input, then it
`has a name that describes its purpose. (Refer to Guideline 4.1 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.
`
`ACCESSIBE LTD EXHIBIT 1014
`Page 5 of 29
`
`

`

`Guideline 1.2 Time-based Media: Provide alternatives for
`time-based media.
`
`Understanding Guideline 1.2
`
`1.2.1 Audio-only and Video-only (Prerecorded): 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: (Level A)
`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.
`
`How to Meet 1.2.1
`Understanding 1.2.1
`
`1.2.2 Captions (Prerecorded): 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. (Level A)
`
`How to Meet 1.2.2
`Understanding 1.2.2
`
`1.2.3 Audio Description or Media Alternative (Prerecorded): 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. (Level A)
`
`How to Meet 1.2.3
`Understanding 1.2.3
`
`1.2.4 Captions (Live): Captions are provided for all live audio content in
`synchronized media. (Level AA)
`
`1.2.5 Audio Description (Prerecorded): Audio description is provided for all
`prerecorded video content in synchronized media. (Level AA)
`
`How to Meet 1.2.4
`Understanding 1.2.4
`
`How to Meet 1.2.5
`Understanding 1.2.5
`
`1.2.6 Sign Language (Prerecorded): Sign language interpretation is provided for all
`prerecorded audio content in synchronized media. (Level AAA)
`
`How to Meet 1.2.6
`Understanding 1.2.6
`
`1.2.7 Extended Audio Description (Prerecorded): 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. (Level AAA)
`
`How to Meet 1.2.7
`Understanding 1.2.7
`
`1.2.8 Media Alternative (Prerecorded): An alternative for time-based media is
`provided for all prerecorded synchronized media and for all prerecorded video-only
`media. (Level AAA)
`
`How to Meet 1.2.8
`Understanding 1.2.8
`
`1.2.9 Audio-only (Live): An alternative for time-based media that presents
`equivalent information for live audio-only content is provided. (Level AAA)
`
`How to Meet 1.2.9
`Understanding 1.2.9
`
`Guideline 1.3 Adaptable: Create content that can be
`presented in different ways (for example simpler layout)
`without losing information or structure.
`
`Understanding Guideline 1.3
`
`1.3.1 Info and Relationships: Information, structure, and relationships conveyed
`through presentation can be programmatically determined or are available in text.
`
`How to Meet 1.3.1
`Understanding 1.3.1
`
`ACCESSIBE LTD EXHIBIT 1014
`Page 6 of 29
`
`

`

`(Level A)
`
`1.3.2 Meaningful Sequence: When the sequence in which content is presented
`affects its meaning, a correct reading sequence can be programmatically
`determined. (Level A)
`
`1.3.3 Sensory Characteristics: Instructions provided for understanding and
`operating content do not rely solely on sensory characteristics of components such
`as shape, size, visual location, orientation, or sound. (Level A)
`Note: For requirements related to color, refer to Guideline 1.4.
`
`How to Meet 1.3.2
`Understanding 1.3.2
`
`How to Meet 1.3.3
`Understanding 1.3.3
`
`Guideline 1.4 Distinguishable: Make it easier for users to see
`and hear content including separating foreground from
`background.
`
`Understanding Guideline 1.4
`
`1.4.1 Use of Color: Color is not used as the only visual means of conveying
`information, indicating an action, prompting a response, or distinguishing a visual
`element. (Level A)
`Note: This success criterion addresses color perception specifically. Other forms of
`perception are covered in Guideline 1.3 including programmatic access to color and
`other visual presentation coding.
`
`1.4.2 Audio Control: 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. (Level A)
`Note: Since any content that does not meet this success criterion can interfere with
`a user's ability to use the whole page, all content on the Web page (whether or not
`it is used to meet other success criteria) must meet this success criterion. See
`Conformance Requirement 5: Non-Interference.
`
`1.4.3 Contrast (Minimum): The visual presentation of text and images of text has a
`contrast ratio of at least 4.5:1, except for the following: (Level AA)
`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 minimum contrast
`requirement.
`
`How to Meet 1.4.1
`Understanding 1.4.1
`
`How to Meet 1.4.2
`Understanding 1.4.2
`
`How to Meet 1.4.3
`Understanding 1.4.3
`
`1.4.4 Resize text: Except for captions and images of text, text can be resized
`without assistive technology up to 200 percent without loss of content or functionality.
`(Level AA)
`
`How to Meet 1.4.4
`Understanding 1.4.4
`
`1.4.5 Images of Text: 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: (Level AA)
`Customizable: The image of text can be visually customized to the user's
`requirements;
`
`How to Meet 1.4.5
`Understanding 1.4.5
`
`ACCESSIBE LTD EXHIBIT 1014
`Page 7 of 29
`
`

`

`Essential: A particular presentation of text is essential to the information being
`conveyed.
`Note: Logotypes (text that is part of a logo or brand name) are considered essential.
`
`1.4.6 Contrast (Enhanced): The visual presentation of text and images of text has a
`contrast ratio of at least 7:1, except for the following: (Level AAA)
`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 minimum contrast
`requirement.
`
`1.4.7 Low or No Background Audio: 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: (Level AAA)
`No Background: The audio does not contain background sounds.
`Turn Off: The background sounds can be turned off.
`20 dB: The background sounds are at least 20 decibels lower than the
`foreground speech content, with the exception of occasional sounds that last
`for only one or two seconds.
`Note: Per the definition of "decibel," background sound that meets this
`requirement will be approximately four times quieter than the foreground
`speech content.
`
`1.4.8 Visual Presentation: For the visual presentation of blocks of text, a
`mechanism is available to achieve the following: (Level AAA)
`1. Foreground and background colors can be selected by the user.
`2. Width is no more than 80 characters or glyphs (40 if CJK).
`3. Text is not justified (aligned to both the left and the right margins).
`4. 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.
`5. 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.
`
`How to Meet 1.4.6
`Understanding 1.4.6
`
`How to Meet 1.4.7
`Understanding 1.4.7
`
`How to Meet 1.4.8
`Understanding 1.4.8
`
`1.4.9 Images of Text (No Exception): Images of text are only used for pure
`decoration or where a particular presentation of text is essential to the information
`being conveyed. (Level AAA)
`Note: Logotypes (text that is part of a logo or brand name) are considered essential.
`
`How to Meet 1.4.9
`Understanding 1.4.9
`
`Principle 2: Operable - User interface components and navigation must be
`operable.
`
`Guideline 2.1 Keyboard Accessible: Make all functionality
`available from a keyboard.
`
`Understanding Guideline 2.1
`
`ACCESSIBE LTD EXHIBIT 1014
`Page 8 of 29
`
`

`

`2.1.1 Keyboard: 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. (Level A)
`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.
`
`2.1.2 No Keyboard Trap: 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. (Level A)
`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.
`
`How to Meet 2.1.1
`Understanding 2.1.1
`
`How to Meet 2.1.2
`Understanding 2.1.2
`
`2.1.3 Keyboard (No Exception): All functionality of the content is operable through
`a keyboard interface without requiring specific timings for individual keystrokes.
`(Level AAA)
`
`How to Meet 2.1.3
`Understanding 2.1.3
`
`Guideline 2.2 Enough Time: Provide users enough time to
`read and use content.
`
`Understanding Guideline 2.2
`
`How to Meet 2.2.1
`Understanding 2.2.1
`
`2.2.1 Timing Adjustable: For each time limit that is set by the content, at least one
`of the following is true: (Level A)
`Turn off: The user is allowed to turn off the time limit before encountering it; or
`Adjust: The user is allowed to adjust the time limit before encountering it over
`a wide range that is at least ten times the length of the default setting; or
`Extend: The user is warned before time expires and given at least 20 seconds
`to extend the time limit with a simple action (for example, "press the space
`bar"), and the user is allowed to extend the time limit at least ten times; or
`Real-time Exception: The time limit is a required part of a real-time event (for
`example, an auction), and no alternative to the time limit is possible; or
`Essential Exception: The time limit is essential and extending it would
`invalidate the activity; or
`20 Hour Exception: The time limit is longer than 20 hours.
`Note: This success criterion helps ensure that users can complete tasks without
`unexpected changes in content or context that are a result of a time limit. This
`success criterion should be considered in conjunction with Success Criterion 3.2.1,
`which puts limits on changes of content or context as a result of user action.
`
`2.2.2 Pause, Stop, Hide: For moving, blinking, scrolling, or auto-updating
`information, all of the following are true: (Level A)
`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
`
`How to Meet 2.2.2
`Understanding 2.2.2
`
`ACCESSIBE LTD EXHIBIT 1014
`Page 9 of 29
`
`

`

`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.
`
`2.2.3 No Timing: 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.
`(Level AAA)
`
`How to Meet 2.2.3
`Understanding 2.2.3
`
`2.2.4 Interruptions: Interruptions can be postponed or suppressed by the user,
`except interruptions involving an emergency. (Level AAA)
`
`2.2.5 Re-authenticating: When an authenticated session expires, the user can
`continue the activity without loss of data after re-authenticating. (Level AAA)
`
`How to Meet 2.2.4
`Understanding 2.2.4
`
`How to Meet 2.2.5
`Understanding 2.2.5
`
`Guideline 2.3 Seizures: Do not design content in a way that is
`known to cause seizures.
`
`Understanding Guideline 2.3
`
`2.3.1 Three Flashes or Below Threshold: 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. (Level A)
`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.
`
`How to Meet 2.3.1
`Understanding 2.3.1
`
`2.3.2 Three Flashes: Web pages do not contain anything that flashes more than
`three times in any one second period. (Level AAA)
`
`How to Meet 2.3.2
`Understanding 2.3.2
`
`Guideline 2.4 Navigable: Provide ways to help users
`navigate, find content, and determine where they are.
`
`Understanding Guideline 2.4
`
`ACCESSIBE LTD EXHIBIT 1014
`Page 10 of 29
`
`

`

`2.4.1 Bypass Blocks: A mechanism is available to bypass blocks of content that are
`repeated on multiple Web pages. (Level A)
`
`How to Meet 2.4.1
`Understanding 2.4.1
`
`2.4.2 Page Titled: Web pages have titles that describe topic or purpose. (Level A)
`
`2.4.3 Focus Order: 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. (Level A)
`
`2.4.4 Link Purpose (In Context): 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. (Level A)
`
`How to Meet 2.4.2
`Understanding 2.4.2
`
`How to Meet 2.4.3
`Understanding 2.4.3
`
`