FrenchDocumentAccessibility.html

<div>
    <h1>
        <a name="_Bureau_de_l’accessibilité"></a>
        Bureau de l’accessibilité de la TI
    </h1>
</div>
<p>
    Le bureau de l'accessibilité de la technologie de l'information (BATI)
    continue d’être un fournisseur de la technologie adaptative et un partisan
    de l’inclusion des personnes ayant un handicap en milieu de travail. Nous
    sommes des chefs démontrés, engagés dans notre mandat d’accessibilité,
continuant d’offrir un soutien aux employés handicapés. Conformément à la    <em>Loi canadienne sur l'accessibilité</em>, et en collaboration avec nos
    partenaires des agences centraux, nous recommandons les normes, les lignes
    directrices et les pratiques exemplaires reconnues à l'échelle
    internationale.
</p>
<p>
    L'étendue de nos services comprend l'approvisionnement, la formation, la
    sensibilisation l'évaluation de produits ainsi que des conseils d’experts
    Accessibilité en Technologie de l’information et des communications (TIC)..
</p>
<p>
    Qu’est-ce que l’accessibilitéL’accessibilité est un terme qui décrit sides
    personnes de toutes capacités ou ayant un handicap peuvent utilisés un
    produit (par exemple un site Web, un site mobile ou une application)..Le
    contexte d’un produit réfère à de l’information telle que :
</p>
<p>
    · Texte, image ou son;
</p>
<p>
    · Code ou balisage qui définit une structure, la présentation, etc.; ou,
</p>
<p>
    · L’organisation de l’information en forme d’interfaces et d’expérience
    d’usager.
</p>
<h2>
    Coordonnées
</h2>
<p>
· Bureau de l’accessibilité des TI :    <a>edsc.ti-it.a11y.esdc@hrsdc-rhdcc.gc.ca</a>
</p>
<ul>
    <li>
        Téléphone : 819-654-1071
    </li>
</ul>
<div>
    <h1>
        Liste de vérification de conformité à l'accessibilité
    </h1>
</div>
<p>
    Ce document est une liste de vérification préliminaire qui doit être
    complétée afin de déterminer si des exigences en accessibilité s’appliquent
    pour votre projet. L'objectif de ce document est de faciliter
    l’identification des exigences en accessibilité. Il agit également à titre
    de premier point de contact pour les gestionnaires et le Bureau de
    l'accessibilité de la technologie de l'information (BATI).
</p>
<div>
    <h1>
        Guide du document
    </h1>
</div>
<p>
    Pour une utilisation optimale du document, suivez chaqueétape en ordre
    etconsultez la section
    <a
        href="file:///C:/Users/18192/Desktop/EPMO%20Accessibility%20Compliance%20Checklist%20FR%20(1).docx#_Outil_et_ressources"
    >
        Outils et ressources
    </a>
    pour des renseignement additionnels sur l’accessibilité.s. Si vous
rencontrez des problèmes avec ce document, veuillez contacter l’    <a>équipe Stratégie et Sensibilisation en Accessibilité</a>.
</p>
<div>
    <h1>
        Pour commencer
    </h1>
</div>
<table
    width="744"
    title="Getting Started Checklist"
    border="0"
    cellspacing="0"
    cellpadding="0"
    summary="1. Contact Accessibility Compliance Project Team [1] for initial consultation
2. Review Accessibility Standards [2] and Policy [3]
3. Generate Accessibility Requirements [4] and Develop Self-Assessments
4. Review Training Opportunities
"
>
    <thead>
        <tr>
            <td width="7">
            </td>
            <td width="66" valign="top" colspan="2">
                <p align="center">
                    <strong>Cocher</strong>
                    <strong></strong>
                </p>
            </td>
            <td width="671" valign="top" colspan="2">
                <p align="center">
                    <strong>À faire</strong>
                    <strong></strong>
                </p>
            </td>
        </tr>
    </thead>
    <tbody>
        <tr>
            <td width="66" valign="top" colspan="2">
                <p align="center">
                    ☐
                </p>
            </td>
            <td width="671" valign="top" colspan="2">
                <p>
                    <strong>Complétez</strong>
                    le
                    <a
                        href="file:///C:/Users/18192/Desktop/EPMO%20Accessibility%20Compliance%20Checklist%20FR%20(1).docx#_Questionnaire_sur_l’accessibilité"
                    >
                        questionnaire sur l’accessibilité
                    </a>
                    dans la section suivante. Si l’une des questions s’applique
                    à votre projet, procéder à la prochaine étape.
                </p>
                <p>
                    <strong> </strong>
                </p>
            </td>
            <td width="7">
            </td>
        </tr>
        <tr>
            <td width="66" valign="top" colspan="2">
                <p align="center">
                    ☐
                </p>
            </td>
            <td width="671" valign="top" colspan="2">
                <p>
                    <strong>Examinez</strong>
                    les
                    <a
                        href="file:///C:/Users/18192/Desktop/EPMO%20Accessibility%20Compliance%20Checklist%20FR%20(1).docx#_Outils_et_ressources"
                    >
                        Outils et ressource
                    </a>
                    sur les normes et les politiques de l’accessibilité.
                </p>
            </td>
            <td width="7">
            </td>
        </tr>
        <tr>
            <td width="66" valign="top" colspan="2">
                <p align="center">
                    ☐
                </p>
            </td>
            <td width="671" valign="top" colspan="2">
                <p>
                    <a>
                        <strong>
                            Contactez Bureau de l’accessibilité des TI
                        </strong>
                    </a>
                    <strong><u> -nous</u></strong>
                    pour vous inscrire à une séance de coaching sur
                    l’accessibilité ou pour initier une consultation sur
                    l’accessibilité pour votre projet.
                </p>
                <p>
                    <strong> </strong>
                </p>
            </td>
            <td width="7">
            </td>
        </tr>
        <tr height="0">
            <td width="7">
            </td>
            <td width="59">
            </td>
            <td width="7">
            </td>
            <td width="664">
            </td>
            <td width="7">
            </td>
        </tr>
    </tbody>
</table>
<p>
    <a name="_Questionnaire_sur_l’accessibilité"></a>
</p>
<h2>
    Questionnaire sur l’accessibilité
</h2>



<section><fieldset><legend>Does the <abbr title="Information Communication Technology">ICT</abbr> procurement provide...</legend>
<div>
<div>
<div><label for="hardware"><input name="hardware" type="checkbox" />User-facing physical (hardware) components</label></div>
<div><label for="integrated"><input name="integrated" type="checkbox" />User-facing hardware that is integrated into the environment (eg. permanently installed self-service kiosk or large, immovable photocopier)</label></div>
<div><label for="web"><input name="web" type="checkbox" />Websites, web applications, or HTML documents</label></div>
<div><label for="non-web-docs"><input name="non-web-docs" type="checkbox" />Documents that are not HTML</label></div>
<div><label for="platform"><input name="platform" type="checkbox" />Platform software (eg. an operating system)</label></div>
<div><label for="ui"><input name="ui" type="checkbox" />Software that provides a user interface outside of the browser</label></div>
<div><label for="at"><input name="at" type="checkbox" />Adaptive (assistive) technology software</label></div>
<div><label for="documentation"><input name="documentation" type="checkbox" />Product documentation</label></div>
<div><label for="support"><input name="support" type="checkbox" />Support services</label></div>
<div><label for="a11y"><input name="a11y" type="checkbox" />Documented accessibility features</label></div>
<div><label for="comm"><input name="comm" type="checkbox" />Two-way communication (any medium)</label></div>
<div><label for="voice-comm"><input name="voice-comm" type="checkbox" />Two-way voice communication</label></div>
<div><label for="video-comm"><input name="video-comm" type="checkbox" />Two-way video communication</label></div>
<div><label for="bio"><input name="bio" type="checkbox" />Biometric authentication or control</label></div>
</div>
<div>
<div><label for="closed"><input name="closed" type="checkbox" />Functionality that is closed to adaptive technologies (eg. a system where no screen-reader software can be installed)</label></div>
<div><label for="conversion"><input name="conversion" type="checkbox" />Conversion of information between electronic formats</label></div>
<div><label for="video-sync"><input name="video-sync" type="checkbox" />Video playback, transmission, conversion, or recording (with synchronized audio)</label></div>
<div><label for="speech-output"><input name="speech-output" type="checkbox" />Hardware with speech output</label></div>
<div><label for="relay"><input name="relay" type="checkbox" />Relay services (eg. captioned telephony service)</label></div>
<div><label for="authoring"><input name="authoring" type="checkbox" />Authoring tools (eg. a word processor or web <abbr title="Content Management System">CMS</abbr>)</label></div>
<div><label for="t-coil"><input name="t-coil" type="checkbox" />Fixed-line communication device which is normally held to the ear and carries the "T" symbol</label></div>
<div><label for="mobile-phone"><input name="mobile-phone" type="checkbox" />Wireless communication device which is normally held to the ear</label></div>
<div><label for="shared"><input name="shared" type="checkbox" />Functionality designed for shared use</label></div>
<div><label for="keys"><input name="keys" type="checkbox" />Provisioning keys, tickets or fare cards, where their orientation is important for further use</label></div>
<div><label for="video-player"><input name="video-player" type="checkbox" />Primary functionality of displaying materials containing video with associated audio content</label></div>
</div>
</div>
</fieldset></section>
<p>&nbsp;</p>



<section><fieldset><legend>Refine clause selection</legend> 
<div>

<div><label for="5d94c4763a40e40aa4645eca"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645eca" aria-hidden="true" data-number="5" />5 Generic requirements</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645ecb"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645ecb" aria-hidden="true" data-number="5.1" />5.1 Closed functionality</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645ecc"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645ecc" aria-hidden="true" data-number="5.1.1" />5.1.1 Introduction (informative)</label>
<div>
<p>ICT has closed functionality for many reasons, including design or policy. Some of the functionality of products can be closed because the product is self-contained and users are precluded from adding peripherals or software in order to access that functionality.</p>
<p>ICT may have closed functionality in practice even though the ICT was not designed, developed or supplied to be closed.</p>
<p>Computers that do not allow end-users to adjust settings or install software are functionally closed.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645ecd"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645ecd" aria-hidden="true" data-number="5.1.2" />5.1.2 General</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645ece"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645ece" aria-hidden="true" data-number="5.1.2.1" />5.1.2.1 Closed functionality</label>
<div>
<p>Where ICT has closed functionality, it shall meet the requirements set out in clauses 5.2 to 13, as applicable.</p>
<p>NOTE 1: ICT may close some, but not all, of its functionalities. Only the closed functionalities have to conform to the requirements of clause 5.1.</p>
<p>NOTE 2: The provisions within this clause are requirements for the closed functionality of ICT that replace those requirements in clauses 5.2 to 13 that specifically state that they do not apply to closed functionality. This may be because they relate to compatibility with assistive technology or to the ability for the user to adjust system accessibility settings in products with closed functionality (e.g. products that prevent access to the system settings control panel).</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645ecf"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645ecf" aria-hidden="true" data-number="5.1.2.2" />5.1.2.2 Assistive technology</label>
<div>
<p>Where ICT has closed functionality, that closed functionality shall be operable without requiring the user to attach, connect or install assistive technology and shall conform to the generic requirements of clauses 5.1.3 to 5.1.6 as applicable. Personal headsets and induction loops shall not be classed as assistive technology for the purpose of this clause.</p>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645ed0"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645ed0" aria-hidden="true" data-number="5.1.3" />5.1.3 Non-visual access</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645ed1"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645ed1" aria-hidden="true" data-number="5.1.3.1" />5.1.3.1 General</label>
<div>
<p>Where visual information is needed to enable the use of those functions of ICT that are closed to assistive technologies for screen reading, ICT shall provide at least one mode of operation using non-visual access to enable the use of those functions.</p>
<p>NOTE 1: Non-visual access may be in an audio form, including speech, or a tactile form.</p>
<p>NOTE 2: The visual information needed to enable use of some functions may include operating instructions and orientation, transaction prompts, user input verification, error messages and non-text content.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645ed2"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645ed2" aria-hidden="true" data-number="5.1.3.2" />5.1.3.2 Auditory output delivery including speech</label>
<div>
<p>Where auditory output is provided as non-visual access to closed functionality, the auditory output shall be delivered:</p>
<ol>
<li>either directly by a mechanism included in or provided with the ICT; or</li>
<li>by a personal headset that can be connected through a 3,5 mm audio jack, or an industry standard connection, without requiring the use of vision.</li>
</ol>
<p>NOTE 1: Mechanisms included in or provided with ICT may be, but are not limited to, a loudspeaker, a built-in handset/headset, or other industry standard coupled peripheral.</p>
<p>NOTE 2: An industry standard connection could be a wireless connection.</p>
<p>NOTE 3: Some users may benefit from the provision of an inductive loop.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645ed3"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645ed3" aria-hidden="true" data-number="5.1.3.3" />5.1.3.3 Auditory output correlation</label>
<div>
<p>Where auditory output is provided as non-visual access to closed functionality, and where information is displayed on the screen, the ICT should provide auditory information that allows the user to correlate the audio with the information displayed on the screen.</p>
<p>NOTE 1: Many people who are legally blind still have visual ability, and use aspects of the visual display even if it cannot be fully comprehended. An audio alternative that is both complete and complementary includes all visual information such as focus or highlighting, so that the audio can be correlated with information that is visible on the screen at any point in time.</p>
<p>NOTE 2: Examples of auditory information that allows the user to correlate the audio with the information displayed on the screen include structure and relationships conveyed through presentation.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645ed4"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645ed4" aria-hidden="true" data-number="5.1.3.4" />5.1.3.4 Speech output user control</label>
<div>
<p>Where speech output is provided as non-visual access to closed functionality, the speech output shall be capable of being interrupted and repeated when requested by the user, where permitted by security requirements.</p>
<p>NOTE 1: It is best practice to allow the user to pause speech output rather than just allowing them to interrupt it.</p>
<p>NOTE 2: It is best practice to allow the user to repeat only the most recent portion rather than requiring play to start from the beginning.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645ed5"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645ed5" aria-hidden="true" data-number="5.1.3.5" />5.1.3.5 Speech output automatic interruption</label>
<div>
<p>Where speech output is provided as non-visual access to closed functionality, the ICT shall interrupt current speech output when a user action occurs and when new speech output begins.</p>
<p>NOTE: Where it is essential that the user hears the entire message, e.g. a safety instruction or warning, the ICT may need to block all user action so that speech is not interrupted.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645ed6"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645ed6" aria-hidden="true" data-number="5.1.3.6" />5.1.3.6 Speech output for non-text content</label>
<div>
<p>Where ICT presents non-text content, the alternative for non-text content shall be presented to users via speech output unless the non-text content is pure decoration or is used only for visual formatting. The speech output for non-text content shall follow the guidance for "text alternative" described in <a href="http://www.w3.org/TR/WCAG21/#non-text-content">WCAG 2.1 Success Criterion 1.1.1 Non-text content</a>.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645ed7"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645ed7" aria-hidden="true" data-number="5.1.3.7" />5.1.3.7 Speech output for video information</label>
<div>
<p>Where pre-recorded video content is needed to enable the use of closed functions of ICT and where speech output is provided as non-visual access to closed functionality, the speech output shall present equivalent information for the pre-recorded video content.</p>
<p>NOTE: This speech output can take the form of an audio description or an auditory transcript of the video content.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645ed8"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645ed8" aria-hidden="true" data-number="5.1.3.8" />5.1.3.8 Masked entry</label>
<div>
<p>Where auditory output is provided as non-visual access to closed functionality, and the characters displayed are masking characters, the auditory output shall not be a spoken version of the characters entered unless the auditory output is known to be delivered only to a mechanism for private listening, or the user explicitly chooses to allow non-private auditory output.</p>
<p>NOTE 1: Masking characters are usually displayed for security purposes and include, but are not limited to asterisks representing personal identification numbers.</p>
<p>NOTE 2: Unmasked character output might be preferred when closed functionality is used, for example, in the privacy of the user's home. A warning highlighting privacy concerns might be appropriate to ensure that the user has made an informed choice.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645ed9"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645ed9" aria-hidden="true" data-number="5.1.3.9" />5.1.3.9 Private access to personal data</label>
<div>
<p>Where auditory output is provided as non-visual access to closed functionality, and the output contains data that is considered to be private according to the applicable privacy policy, the corresponding auditory output shall only be delivered through a mechanism for private listening that can be connected without requiring the use of vision, or through any other mechanism explicitly chosen by the user.</p>
<p>NOTE 1: This requirement does not apply in cases where data is not defined as being private according to the applicable privacy policy or where there is no applicable privacy policy.</p>
<p>NOTE 2: Non-private output might be preferred when closed functionality is used, for example, in the privacy of the user's home. A warning highlighting privacy concerns might be appropriate to ensure that the user has made an informed choice.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645eda"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645eda" aria-hidden="true" data-number="5.1.3.10" />5.1.3.10 Non-interfering audio output</label>
<div>
<p>Where auditory output is provided as non-visual access to closed functionality, the ICT shall not automatically play, at the same time, any interfering audible output that lasts longer than three seconds.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645edb"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645edb" aria-hidden="true" data-number="5.1.3.11" />5.1.3.11 Private listening volume</label>
<div>
<p>Where auditory output is provided as non-visual access to closed functionality and is delivered through a mechanism for private listening, ICT shall provide at least one non-visual mode of operation for controlling the volume.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645edc"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645edc" aria-hidden="true" data-number="5.1.3.12" />5.1.3.12 Speaker volume</label>
<div>
<p>Where auditory output is provided as non-visual access to closed functionality and is delivered through speakers on ICT, a non-visual incremental volume control shall be provided with output amplification up to a level of at least 65 dBA (-29 dBPaA).</p>
<p>NOTE: For noisy environments, 65 dBA may not be sufficient.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645edd"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645edd" aria-hidden="true" data-number="5.1.3.13" />5.1.3.13 Volume reset</label>
<div>
<p>Where auditory output is provided as non-visual access to closed functionality, a function that resets the volume to be at a level of 65 dBA or less after every use, shall be provided, unless the ICT is dedicated to a single user.</p>
<p>NOTE: A feature to disable the volume reset function may be provided in order to enable the single-user exception to be met.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645ede"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645ede" aria-hidden="true" data-number="5.1.3.14" />5.1.3.14 Spoken languages</label>
<div>
<p>Where speech output is provided as non-visual access to closed functionality, speech output shall be in the same human language as the displayed content provided, except:</p>
<ol>
<li>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;</li>
<li>where the content is generated externally and not under the control of the ICT vendor, clause 5.1.3.14 shall not be required to apply for languages not supported by the ICT's speech synthesizer;</li>
<li>for displayed languages that cannot be selected using non-visual access;</li>
<li>where the user explicitly selects a speech language that is different from the language of the displayed content.</li>
</ol>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645edf"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645edf" aria-hidden="true" data-number="5.1.3.15" />5.1.3.15 Non-visual error identification</label>
<div>
<p>Where speech output is provided as non-visual access to closed functionality and an input error is automatically detected, speech output shall identify and describe the item that is in error.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645ee0"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645ee0" aria-hidden="true" data-number="5.1.3.16" />5.1.3.16 Receipts, tickets, and transactional outputs</label>
<div>
<p>Where ICT is closed to visual access and provides receipts, tickets or other outputs as a result of a self-service transaction, speech output shall be provided which shall include all information necessary to complete or verify the transaction. In the case of ticketing machines, printed copies of itineraries and maps shall not be required to be audible.</p>
<p>NOTE: The speech output may be provided by any element of the total ICT system.</p>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645ee1"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645ee1" aria-hidden="true" data-number="5.1.4" />5.1.4 Functionality closed to text enlargement</label>
<div>
<p>Where any functionality of ICT is closed to the text enlargement features of platform or assistive technology, the ICT shall provide a mode of operation where the text and images of text necessary for all functionality is displayed in such a way that a non-accented capital "H" subtends an angle of at least 0,7 degrees at a viewing distance specified by the supplier.</p>
<p>The subtended angle, in degrees, may be calculated from:</p>
<p>&Psi; = (180 x H) / (&pi; x D)</p>
<p>Where:</p>
<ul>
<li>&psi; is the subtended angle in degrees</li>
<li>H is the height of the text</li>
<li>D is the viewing distance</li>
<li>D and H are expressed in the same units</li>
</ul>
<p>NOTE 1: The intent is to provide a mode of operation where text is large enough to be used by most users with low vision.</p>
<p>NOTE 2: Table 5.1 and Figure 1 illustrate the relationship between the maximum viewing distance and minimum character height at the specified minimum subtended angle.</p>
<p>(See Table 5.1 and Figure 1)</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645eed"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645eed" aria-hidden="true" data-number="5.1.5" />5.1.5 Visual output for auditory information</label>
<div>
<p>Where pre-recorded auditory information is needed to enable the use of closed functions of ICT, the ICT shall provide visual information that is equivalent to the pre-recorded auditory output.</p>
<p>NOTE: This visual information can take the form of captions or text transcripts</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645eee"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645eee" aria-hidden="true" data-number="5.1.6" />5.1.6 Operation without keyboard interface</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645eef"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645eef" aria-hidden="true" data-number="5.1.6.1" />5.1.6.1 Closed functionality</label>
<div>
<p>Where ICT functionality is closed to keyboards or keyboard interfaces, all functionality shall be operable without vision as required by clause 5.1.3.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645ef0"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645ef0" aria-hidden="true" data-number="5.1.6.2" />5.1.6.2 Input focus</label>
<div>
<p>Where ICT functionality is closed to keyboards or keyboard interfaces and where input focus can be moved to a user interface element, it shall be possible to move the input focus away from that element using the same mechanism, in order to avoid trapping the input focus.</p>
</div>
</div>
</li>
</ul>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645ef1"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645ef1" aria-hidden="true" data-number="5.2" />5.2 Activation of accessibility features</label>
<div>
<p>Where ICT has documented accessibility features, it shall be possible to activate those documented accessibility features that are required to meet a specific need without relying on a method that does not support that need.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645ef2"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645ef2" aria-hidden="true" data-number="5.3" />5.3 Biometrics</label>
<div>
<p>Where ICT uses biological characteristics, it shall not rely on the use of a particular biological characteristic as the only means of user identification or for control of ICT.</p>
<p>NOTE 1: Alternative means of user identification or for control of ICT could be non-biometric or biometric.</p>
<p>NOTE 2: Biometric methods based on dissimilar biological characteristics increase the likelihood that individuals with disabilities possess at least one of the specified biological characteristics. Examples of dissimilar biological characteristics are fingerprints, eye retinal patterns, voice, and face.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645ef3"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645ef3" aria-hidden="true" data-number="5.4" />5.4 Preservation of accessibility information during conversion</label>
<div>
<p>Where ICT converts information or communication it shall preserve all documented non-proprietary information that is provided for accessibility, to the extent that such information can be contained in or supported by the destination format.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645ef4"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645ef4" aria-hidden="true" data-number="5.5" />5.5 Operable parts</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645ef5"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645ef5" aria-hidden="true" data-number="5.5.1" />5.5.1 Means of operation</label>
<div>
<p>Where ICT has operable parts that require grasping, pinching, or twisting of the wrist to operate, an accessible alternative means of operation that does not require these actions shall be provided.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645ef6"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645ef6" aria-hidden="true" data-number="5.5.2" />5.5.2 Operable parts discernibility</label>
<div>
<p>Where ICT has operable parts, it shall provide a means to discern each operable part, without requiring vision and without performing the action associated with the operable part.</p>
<p>NOTE: One way of meeting this requirement is by making the operable parts tactilely discernible.</p>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645ef7"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645ef7" aria-hidden="true" data-number="5.6" />5.6 Locking or toggle controls</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645ef8"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645ef8" aria-hidden="true" data-number="5.6.1" />5.6.1 Tactile or auditory status</label>
<div>
<p>Where ICT has a locking or toggle control and that control is visually presented to the user, the ICT shall provide at least one mode of operation where the status of the control can be determined either through touch or sound without operating the control.</p>
<p>NOTE 1: Locking or toggle controls are those controls that can only have two or three states and that keep their state while being used.</p>
<p>NOTE 2: An example of a locking or toggle control is the "Caps Lock" key found on most keyboards. Another example is the volume button on a pay telephone, which can be set at normal, loud, or extra loud volume.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645ef9"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645ef9" aria-hidden="true" data-number="5.6.2" />5.6.2 Visual status</label>
<div>
<p>Where ICT has a locking or toggle control and the control is non-visually presented to the user, the ICT shall provide at least one mode of operation where the status of the control can be visually determined when the control is presented.</p>
<p>NOTE 1: Locking or toggle controls are those controls that can only have two or three states and that keep their state while being used.</p>
<p>NOTE 2: An example of a locking or toggle control is the "Caps Lock" key found on most keyboards. An example of making the status of a control determinable is a visual status indicator on a keyboard.</p>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645efa"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645efa" aria-hidden="true" data-number="5.7" />5.7 Key repeat</label>
<div>
<p>Where ICT has a key repeat function that cannot be turned off:</p>
<ol>
<li>the delay before the key repeat shall be adjustable to at least 2 seconds; and</li>
<li>the key repeat rate shall be adjustable down to one character per 2 seconds.</li>
</ol>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645efb"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645efb" aria-hidden="true" data-number="5.8" />5.8 Double-strike key acceptance</label>
<div>
<p>Where ICT has a keyboard or keypad, the delay after any keystroke, during which an additional key-press will not be accepted if it is identical to the previous keystroke, shall be adjustable up to at least 0,5 seconds</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645efc"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645efc" aria-hidden="true" data-number="5.9" />5.9 Simultaneous user actions</label>
<div>
<p>Where ICT uses simultaneous user actions for its operation, such ICT shall provide at least one mode of operation that does not require simultaneous user actions to operate the ICT.</p>
<p>NOTE: Having to use both hands to open the lid of a laptop, having to press two or more keys at the same time or having to touch a surface with more than one finger are examples of simultaneous user actions.</p>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645efd"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645efd" aria-hidden="true" data-number="6" />6 ICT with two-way voice communication</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645efe"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645efe" aria-hidden="true" data-number="6.1" />6.1 Audio bandwidth for speech</label>
<div>
<p>Where ICT provides two-way voice communication, in order to provide good audio quality, that ICT shall be able to encode and decode two-way voice communication with a frequency range with an upper limit of at least 7 000 Hz.</p>
<p>NOTE 1: For the purposes of interoperability, support of Recommendation ITU-T G.722 [i.21] is widely used.</p>
<p>NOTE 2: Where codec negotiation is implemented, other standardized codecs such as Recommendation ITU-T G.722.2 [i.22] are sometimes used so as to avoid transcoding.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645eff"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645eff" aria-hidden="true" data-number="6.2" />6.2 Real-time text (RTT) functionality</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f00"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f00" aria-hidden="true" data-number="6.2.1" />6.2.1 RTT provision</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f01"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f01" aria-hidden="true" data-number="6.2.1.1" />6.2.1.1 RTT communication</label>
<div>
<p>Where ICT supports two-way voice communication in a specified context of use, the ICT shall allow a user to communicate with another user by RTT.</p>
<p>NOTE 1: The RTT capability can be provided as a factory default or added later.</p>
<p>NOTE 2: Provision of RTT may require additional service provision, additional hardware and/or software which may be provided separately or together.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f02"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f02" aria-hidden="true" data-number="6.2.1.2" />6.2.1.2 Concurrent voice and text</label>
<div>
<p>Where ICT supports two-way voice communication in a specified context of use, and enables a user to communicate with another user by RTT, it shall provide a mechanism to select a mode of operation which allows concurrent voice and text.</p>
<p>NOTE: The availability of voice and RTT running concurrently can allow the RTT to replace or support voice and transfer additional information such as numbers, currency amounts and spelling of names.</p>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f03"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f03" aria-hidden="true" data-number="6.2.2" />6.2.2 Display of Real-time Text</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f04"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f04" aria-hidden="true" data-number="6.2.2.1" />6.2.2.1 Visually distinguishable display</label>
<div>
<p>Where ICT has RTT send and receive capabilities, displayed sent text shall be visually differentiated from and separated from received text.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f05"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f05" aria-hidden="true" data-number="6.2.2.2" />6.2.2.2 Programmatically determinable send and receive direction</label>
<div>
<p>Where ICT has RTT send and receive capabilities, the send/receive direction of transmitted text shall be programmatically determinable, unless the RTT has closed functionality.</p>
<p>NOTE: The intent of this clause is to enable screen readers to be able to distinguish between incoming text and outgoing text when used with RTT functionality.</p>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f06"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f06" aria-hidden="true" data-number="6.2.3" />6.2.3 Interoperability</label>
<div>
<p>Where ICT with RTT functionality interoperates with other ICT with RTT functionality (as required by clause 6.2.1.1) they shall support at least one of the four RTT interoperability mechanisms described below:</p>
<ol>
<li>ICT interoperating over the Public Switched Telephone Network (PSTN), with other ICT that directly connects to the PSTN as described in Recommendation ITU-T V.18 [i.23] or any of its annexes for text telephony signals at the PSTN interface;</li>
<li>ICT interoperating with other ICT using VOIP with Session Initiation Protocol (SIP) and using real-time text that conforms to IETF RFC 4103 [i.13];</li>
<li>ICT interoperating with other ICT using RTT that conforms with the IP Multimedia Sub-System (IMS) set of protocols specified in ETSI TS 126 114 [i.10], ETSI TS 122 173 [i.11] and ETSI TS 134 229 [i.12];</li>
<li>ICT interoperating with other ICT using a relevant and applicable common specification for RTT exchange that is published and available. This common specification shall include a method for indicating loss or corruption of characters.</li>
</ol>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f07"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f07" aria-hidden="true" data-number="6.2.4" />6.2.4 Real-time text responsiveness</label>
<div>
<p>Where ICT utilises RTT input, that RTT input shall be transmitted to the ICT network supporting RTT within 1 second of the input entry.</p>
<p>NOTE 1: Input entry is considered to have occurred when sufficient user input has occurred for the ICT to establish which character(s) to send.</p>
<p>NOTE 2: Input entry will differ between systems where text is entered on a word-by-word basis (e.g. speech-to-text and predictive-text based systems) and systems where each character is separately generated.</p>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f08"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f08" aria-hidden="true" data-number="6.3" />6.3 Caller ID</label>
<div>
<p>Where ICT provides caller identification or similar telecommunications functions are provided, the caller identification and similar telecommunications functions shall be available in text form and in at least one other modality.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f09"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f09" aria-hidden="true" data-number="6.4" />6.4 Alternatives to voice-based services</label>
<div>
<p>Where ICT provides real-time voice-based communication and also provides voice mail, auto-attendant, or interactive voice response facilities, the ICT should offer users a means to access the information and carry out the tasks provided by the ICT without the use of hearing or speech.</p>
<p>NOTE: Solutions capable of handling audio, real-time text and video media could satisfy the above requirement.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f0a"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f0a" aria-hidden="true" data-number="6.5" />6.5 Video communication</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f0b"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f0b" aria-hidden="true" data-number="6.5.1" />6.5.1 General (informative)</label>
<div>
<p>Clause 6.5 (Video communications) provides performance requirements that support users who communicate using sign language and lip-reading. For these users, good usability is achieved with Common Intermediate Format (CIF) resolution, a frame rate of 20 frames per second and over, with a time difference between speech audio and video that does not exceed 100 ms.</p>
<p>When the resolution is reduced to Quarter Common Intermediate Format (QCIF) and the frame rate drops to 12 frames per second the communication is still usable with some restrictions.</p>
<p>A lower resolution causes less disturbance to the perception of sign language and lip-reading than that caused by a lower frame rate.</p>
<p>Delay can be a problem in video communication. Overall delay values below 0,4 s are preferred, with an increase in preference down to 0,1 s. Values over 0,8 s are felt to hinder a good sign conversation. Overall delay depends on multiple factors, including e.g. network delay and video processing. For this reason a testable requirement on minimum values for overall delay cannot be produced.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f0c"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f0c" aria-hidden="true" data-number="6.5.2" />6.5.2 Resolution</label>
<div>
<p>Where ICT that provides two-way voice communication includes real-time video functionality, the ICT:</p>
<ol>
<li>shall support at least QCIF resolution;</li>
<li>should preferably support at least CIF resolution.</li>
</ol>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f0d"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f0d" aria-hidden="true" data-number="6.5.3" />6.5.3 Frame rate</label>
<div>
<p>Where ICT that provides two-way voice communication includes real-time video functionality, the ICT:</p>
<ol>
<li>shall support a frame rate of at least 12 frames per second (FPS);</li>
<li>should preferably support a frame rate of at least 20 frames per second (FPS) with or without sign language in the video stream.</li>
</ol>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f0e"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f0e" aria-hidden="true" data-number="6.5.4" />6.5.4 Synchronization between audio and video</label>
<div>
<p>Where ICT that provides two-way voice communication includes real-time video functionality, the ICT should ensure a maximum time difference of 100 ms between the speech and video presented to the user.</p>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f0f"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f0f" aria-hidden="true" data-number="6.6" />6.6 Alternatives to video-based services</label>
<div>
<p>Where ICT provides real-time video-based communication and also provides answering machine, auto attendant or interactive response facilities, the ICT should offer users a means to access the information and carry out the tasks related to these facilities:</p>
<ol>
<li>for audible information, without the use of hearing;</li>
<li>for spoken commands, without the use of speech;</li>
<li>for visual information, without the use of vision.</li>
</ol>
<p>NOTE: Solutions capable of generating real-time captions or handling real-time text could satisfy the above requirement.</p>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f10"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f10" aria-hidden="true" data-number="7" />7 ICT with video capabilities</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f11"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f11" aria-hidden="true" data-number="7.1" />7.1 Caption processing technology</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f12"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f12" aria-hidden="true" data-number="7.1.1" />7.1.1 Captioning playback</label>
<div>
<p>Where ICT displays video with synchronized audio, it shall have a mode of operation to display the available captions. Where closed captions are provided as part of the content, the ICT shall allow the user to choose to display the captions.</p>
<p>NOTE: Captions may contain information about timing, colour and positioning. This caption data is important for caption users. Timing is used for caption synchronization. Colour can be used for speaker identification. Position can be used to avoid obscuring important information.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f13"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f13" aria-hidden="true" data-number="7.1.2" />7.1.2 Captioning synchronization</label>
<div>
<p>Where ICT displays captions, the mechanism to display captions shall preserve synchronization between the audio and the corresponding captions.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f14"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f14" aria-hidden="true" data-number="7.1.3" />7.1.3 Preservation of captioning</label>
<div>
<p>Where ICT transmits, converts or records video with synchronized audio, it shall preserve caption data such that it can be displayed in a manner consistent with clauses 7.1.1 and 7.1.2.</p>
<p>Additional presentational aspects of the text such as screen position, text colours, text style and text fonts may convey meaning, based on regional conventions. Altering these presentational aspects could change the meaning and should be avoided wherever possible.</p>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f15"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f15" aria-hidden="true" data-number="7.2" />7.2 Audio description technology</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f16"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f16" aria-hidden="true" data-number="7.2.1" />7.2.1 Audio description playback</label>
<div>
<p>Where ICT displays video with synchronized audio, it shall provide a mechanism to select and play available audio description to the default audio channel.</p>
<p>Where video technologies do not have explicit and separate mechanisms for audio description, an ICT is deemed to satisfy this requirement if the ICT enables the user to select and play several audio tracks.</p>
<p>NOTE 1: In such cases, the video content can include the audio description as one of the available audio tracks.</p>
<p>NOTE 2: Audio descriptions in digital media sometimes include information to allow descriptions that are longer than the gaps between dialogue. Support in digital media players for this "extended audio description" feature is useful, especially for digital media that is viewed personally.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f17"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f17" aria-hidden="true" data-number="7.2.2" />7.2.2 Audio description synchronization</label>
<div>
<p>Where ICT has a mechanism to play audio description, it shall preserve the synchronization between the audio/visual content and the corresponding audio description.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f18"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f18" aria-hidden="true" data-number="7.2.3" />7.2.3 Preservation of audio description</label>
<div>
<p>Where ICT transmits, converts, or records video with synchronized audio, it shall preserve audio description data such that it can be played in a manner consistent with clauses 7.2.1 and 7.2.2.</p>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f19"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f19" aria-hidden="true" data-number="7.3" />7.3 User controls for captions and audio description</label>
<div>
<p>Where ICT primarily displays materials containing video with associated audio content, user controls to activate subtitling and audio description shall be provided to the user at the same level of interaction (i.e. the number of steps to complete the task) as the primary media controls.</p>
<p>NOTE 1: Primary media controls are the set of controls that the user most commonly uses to control media.</p>
<p>NOTE 2: Products that have a general hardware volume control, such as a telephone, or a laptop which can be configured to display video through software but which is not its primary purpose, would not need dedicated hardware controls for captions and descriptions; however software controls, or hardware controls mapped through software, would need to be at the same level of interaction.</p>
<p>NOTE 3: It is best practice for ICT to include additional controls enabling the user to select whether captions and audio description are turned on or off by default.</p>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f1a"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f1a" aria-hidden="true" data-number="8" />8 Hardware</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f1b"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f1b" aria-hidden="true" data-number="8.1" />8.1 General</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f1c"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f1c" aria-hidden="true" data-number="8.1.1" />8.1.1 Generic requirements</label>
<div>
<p>The "generic requirements" of clause 5 also apply to ICT that is hardware.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f1d"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f1d" aria-hidden="true" data-number="8.1.2" />8.1.2 Standard connections</label>
<div>
<p>Where an ICT provides user input or output device connection points, the ICT shall provide at least one input and/or output connection that conforms to an industry standard non-proprietary format, directly or through the use of commercially available adapters.</p>
<p>NOTE 1: The intent of this requirement is to ensure compatibility with assistive technologies by requiring the use of standard connections on ICT.</p>
<p>NOTE 2: The word connection applies to both physical and wireless connections.</p>
<p>NOTE 3: Current examples of industry standard non-proprietary formats are USB and Bluetooth.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f1e"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f1e" aria-hidden="true" data-number="8.1.3" />8.1.3 Colour</label>
<div>
<p>Where the ICT has hardware aspects that use colour, colour shall not be used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.</p>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f1f"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f1f" aria-hidden="true" data-number="8.2" />8.2 Hardware products with speech output</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f20"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f20" aria-hidden="true" data-number="8.2.1" />8.2.1 Speech volume gain</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f21"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f21" aria-hidden="true" data-number="8.2.1.1" />8.2.1.1 Speech volume range</label>
<div>
<p>Where ICT hardware has speech output, it shall provide a means to adjust the speech output volume level over a range of at least 18 dB.</p>
<p>NOTE: Fixed-line handsets and headsets fulfilling the requirements of ANSI/TIA-4965 [i.2] are deemed to comply with this requirement.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f22"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f22" aria-hidden="true" data-number="8.2.1.2" />8.2.1.2 Incremental volume control</label>
<div>
<p>Where ICT hardware has speech output and its volume control is incremental, it shall provide at least one intermediate step of 12 dB gain above the lowest volume setting.</p>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f23"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f23" aria-hidden="true" data-number="8.2.2" />8.2.2 Magnetic coupling</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f24"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f24" aria-hidden="true" data-number="8.2.2.1" />8.2.2.1 Fixed-line devices</label>
<div>
<p>Where ICT hardware is a fixed-line communication device with speech output and which is normally held to the ear and which carries the "T" symbol specified in ETSI ETS 300 381 [1], it shall provide a means of magnetic coupling which meets the requirements of ETSI ES 200 381-1 [2].</p>
<p>NOTE: ICT fulfilling the requirements of TIA-1083-A [i.24] is deemed to comply with the requirements of this clause.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f25"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f25" aria-hidden="true" data-number="8.2.2.2" />8.2.2.2 Wireless communication devices</label>
<div>
<p>Where ICT hardware is a wireless communication device with speech output which is normally held to the ear, it shall provide a means of magnetic coupling to hearing technologies which meets the requirements of ETSI ES 200 381-2 [3].</p>
<p>NOTE: ICT fulfilling the requirements of ANSI/IEEE C63.19 [i.1] is deemed to comply with the requirements of this clause.</p>
</div>
</div>
</li>
</ul>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f26"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f26" aria-hidden="true" data-number="8.3" />8.3 Physical access to ICT</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f27"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f27" aria-hidden="true" data-number="8.3.1" />8.3.1 General (informative)</label>
<div>
<p>Clauses 8.3.2 to 8.3.4 describe recommendations on those dimensions that are integral to the ICT (e.g. integral shelves, or integral cabins that may restrict access to the operable parts of the ICT).</p>
<p>When ICT is installed, the dimensions of the surrounding space combined with the dimensions of the ICT might affect the physical access to the ICT. Accessible physical access of the ICT would be achieved if the installation instructions referred to in clause 8.3.5 are followed.</p>
<p>It may not be possible to apply all recommendations of clause 8.3 to all aspects of maintenance, repair, or occasional monitoring of equipment in all circumstances. Nevertheless, it is best practice to apply the recommendations in clause 8.3, where feasible and safe to do so.</p>
<p>NOTE 1: The dimensions set out in clause 8.3 are identical to those given in the American 2010 ADA standards for accessible design [i.25].</p>
<p>NOTE 2: Physical access to ICT is dependent on the dimensions of both the ICT and the environment in which it is installed and operated. Clause 8.3 does not apply to the accessibility of the physical environment external to the ICT.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f28"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f28" aria-hidden="true" data-number="8.3.2" />8.3.2 Clear floor or ground space</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f29"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f29" aria-hidden="true" data-number="8.3.2.1" />8.3.2.1 Change in level</label>
<div>
<p>Where there is a change in floor level that is integral to the ICT then it should be ramped with a slope no steeper than 1:48.</p>
<p>Exceptions:</p>
<ol>
<li>If the change in floor level is less than or equal to 6,4 mm (&frac14; inch) the change may be vertical as shown in Figure 2.</li>
<li>If the change in floor level is less than or equal to 13 mm (&frac12; inch) the change may have a slope not steeper than 1:2 as shown in Figure 3.</li>
</ol>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f2a"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f2a" aria-hidden="true" data-number="8.3.2.2" />8.3.2.2 Clear floor or ground space</label>
<div>
<p>Where the operating area is integral to the ICT, it should provide a clear floor area that has the minimum dimensions of 760 mm (30 inches) by 1 220 mm (48 inches) from which to operate the ICT. This is shown in Figure 4.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f2b"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f2b" aria-hidden="true" data-number="8.3.2.3" />8.3.2.3 Approach</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f2c"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f2c" aria-hidden="true" data-number="8.3.2.3.1" />8.3.2.3.1 General</label>
<div>
<p>Where the access space is integral to the ICT, at least one full side of the space should be unobstructed.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f2d"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f2d" aria-hidden="true" data-number="8.3.2.3.2" />8.3.2.3.2 Forward approach</label>
<div>
<p>Where the operating area is inside an alcove integral to the ICT, the alcove is deeper than 610 mm (24 inches), and where a forward approach is necessary, the dimension of the access space should be a minimum of 915 mm (36 inches) wide. This is shown in Figure 5.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f2e"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f2e" aria-hidden="true" data-number="8.3.2.3.3" />8.3.2.3.3 Parallel approach</label>
<div>
<p>Where the operating area is inside an alcove integral to the ICT, the alcove is deeper than 380 mm (15 inches), and where a parallel approach is possible, the dimension of the access space should be a minimum of 1 525 mm (60 inches) wide. This is shown in Figure 6.</p>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f2f"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f2f" aria-hidden="true" data-number="8.3.2.4" />8.3.2.4 Knee and toe clearance width</label>
<div>
<p>Where the space under an obstacle that is integral to the ICT is part of access space, the clearance should be at least 760 mm (30 inches) wide.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f30"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f30" aria-hidden="true" data-number="8.3.2.5" />8.3.2.5 Toe clearance</label>
<div>
<p>Where an obstacle is integral to the ICT, a space under the obstacle that is less than 230 mm (9 inches) above the floor is considered toe clearance and should:</p>
<ol>
<li>extend 635 mm (25 inches) maximum under the whole obstacle;</li>
<li>provide a space at least 430 mm (17 inches) deep and 230 mm (9 inches) above the floor under the obstacle;</li>
<li>extend no more than 150 mm (6 inches) beyond any obstruction at 230 mm (9 inches) above the floor.</li>
</ol>
<p>This is shown in Figure 7.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f31"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f31" aria-hidden="true" data-number="8.3.2.6" />8.3.2.6 Knee clearance</label>
<div>
<p>Where an obstacle is integral to the ICT, the space under the obstacle that is between 230 mm (9 inches) and 685 mm (27 inches) above the floor is considered knee clearance and should:</p>
<ol>
<li>extend no more than 635 mm (25 inches) under the obstacle at a height of 230 mm (9 inches) above the floor;</li>
<li>extend at least 280 mm (11 inches) under the obstacle at a height of 230 mm (9 inches) above the floor;</li>
<li>extend at least 205 mm (8 inches) under the obstacle at a height of 685 mm (27 inches) above the floor;</li>
<li>be permitted to be reduced in depth at a rate of 25 mm (1 inch) for each 150 mm (6 inches) in height.</li>
</ol>
<p>This is shown in Figure 8.</p>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f32"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f32" aria-hidden="true" data-number="8.3.3" />8.3.3 Reach range for ICT</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f33"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f33" aria-hidden="true" data-number="8.3.3.1" />8.3.3.1 Forward reach</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f34"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f34" aria-hidden="true" data-number="8.3.3.1.1" />8.3.3.1.1 Unobstructed high forward reach</label>
<div>
<p>Where the access space is integral to the ICT and the forward reach is unobstructed, the essential controls should be located no higher than 1 220 mm (48 inches) above the floor of the access space. This is shown in Figure 9.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f35"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f35" aria-hidden="true" data-number="8.3.3.1.2" />8.3.3.1.2 Unobstructed low forward reach</label>
<div>
<p>Where the access space is integral to the ICT and the forward reach is unobstructed, the essential controls should be located no lower than 380 mm (15 inches) above the floor of the access space. This is shown in Figure 9.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f36"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f36" aria-hidden="true" data-number="8.3.3.1.3" />8.3.3.1.3 Obstructed reach</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f37"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f37" aria-hidden="true" data-number="8.3.3.1.3.1" />8.3.3.1.3.1 Clear floor space</label>
<div>
<p>Where the access space is integral to the ICT and has an obstruction which is integral to the ICT which hinders the access to any essential controls, the ICT should provide a clear floor space which extends beneath the obstructing element for a distance not less than the required reach depth over the obstruction.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f38"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f38" aria-hidden="true" data-number="8.3.3.1.3.2" />8.3.3.1.3.2 Obstructed (&lt; 510 mm) forward reach</label>
<div>
<p>Where the access space is integral to the ICT and has an obstruction which is integral to the ICT and which is less than 510 mm (20 inches), the forward reach to all essential controls should be no higher than 1 220 mm (48 inches) above the floor contact of the ICT. This is shown in Figure 10 (a).</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f39"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f39" aria-hidden="true" data-number="8.3.3.1.3.3" />8.3.3.1.3.3 Obstructed (&lt; 635 mm) forward reach</label>
<div>
<p>Where the access space is integral to the ICT and has an obstruction which is integral to the ICT and which is greater than 510 mm (20 inches) and less than 635 mm (25 inches) maximum, the forward reach to all essential controls should be no higher than 1 120 mm (44 inches) above the floor contact of the ICT. This is shown in Figure 10 (b).</p>
</div>
</div>
</li>
</ul>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f3a"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f3a" aria-hidden="true" data-number="8.3.3.2" />8.3.3.2 Side reach</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f3b"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f3b" aria-hidden="true" data-number="8.3.3.2.1" />8.3.3.2.1 Unobstructed high side reach</label>
<div>
<p>Where the access space is integral to the ICT, allows a parallel approach, and the side reach is unobstructed or obstructed by an element integral to the ICT which is less than 255 mm (10 inches), all essential controls should be within a high side reach which is less than or equal to 1 220 mm (48 inches) above the floor of the access space. This is shown in Figure 11.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f3c"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f3c" aria-hidden="true" data-number="8.3.3.2.2" />8.3.3.2.2 Unobstructed low side reach</label>
<div>
<p>Where the access space is integral to the ICT, allows a parallel approach, and the side reach is unobstructed or obstructed by an element integral to the ICT which is less than 255 mm (10 inches), all essential controls should be within a low side reach which is greater than or equal to 380 mm (15 inches) above the floor of the access space. This is shown in Figure 11.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f3d"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f3d" aria-hidden="true" data-number="8.3.3.2.3" />8.3.3.2.3 Obstructed side reach</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f3e"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f3e" aria-hidden="true" data-number="8.3.3.2.3.1" />8.3.3.2.3.1 Obstructed (&le; 255 mm) side reach</label>
<div>
<p>Where the access space is integral to the ICT, allows a parallel approach and has an obstruction which is integral to the ICT, the height of the obstruction should be less than 865 mm (34 inches). Where the depth of the obstruction is less than or equal to 255 mm (10 inches), the high side reach to all essential controls should be no higher than 1 220 mm (48 inches) above the floor of the access space. This is shown in Figure 12 (a).</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f3f"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f3f" aria-hidden="true" data-number="8.3.3.2.3.2" />8.3.3.2.3.2 Obstructed (&le; 610 mm) side reach</label>
<div>
<p>Where the access space is integral to the ICT, allows a parallel approach and has an obstruction which is integral to the ICT, the height of the obstruction should be less than 865 mm (34 inches). Where the depth of the obstruction is greater than 255 mm (10 inches) with a maximum depth of 610 mm (24 inches), the high side reach to all essential controls should be no higher than 1 170 mm (46 inches) above the floor of the access space. This is shown in Figure 12 (b).</p>
</div>
</div>
</li>
</ul>
</li>
</ul>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f40"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f40" aria-hidden="true" data-number="8.3.4" />8.3.4 Visibility</label>
<div>
<p>Where the operating area is integral to the ICT, and a display screen is provided, information on the screen should be legible from a point located 1 015 mm (40 inches) above the centre of the floor of the operating area (as defined in clause 8.3.2.2).</p>
<p>NOTE: The intent of this provision is that the information on the screen can be read by users with normal vision and appropriate language skills, when seated in a wheelchair.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f41"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f41" aria-hidden="true" data-number="8.3.5" />8.3.5 Installation instructions</label>
<div>
<p>Where an ICT is intended to be installed, instructions should be made available which outline a method to install the ICT in a manner that ensures that the dimensions of the integral spaces of the ICT conform to clauses 8.3.2 to 8.3.4.</p>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f42"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f42" aria-hidden="true" data-number="8.4" />8.4 Mechanically operable parts</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f43"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f43" aria-hidden="true" data-number="8.4.1" />8.4.1 Numeric keys</label>
<div>
<p>Where provided, physical numeric keys arranged in a rectangular keypad layout shall have the number five key tactilely distinct from the other keys of the keypad.</p>
<p>NOTE: Recommendation ITU-T E.161 [i.20] describes the 12-key telephone keypad layout and provides further details of the form of tactile markers.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f44"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f44" aria-hidden="true" data-number="8.4.2" />8.4.2 Operation of mechanical parts</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f45"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f45" aria-hidden="true" data-number="8.4.2.1" />8.4.2.1 Means of operation of mechanical parts</label>
<div>
<p>Where a control requires grasping, pinching, or twisting of the wrist to operate it, an accessible alternative means of operation that does not require these actions shall be provided.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f46"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f46" aria-hidden="true" data-number="8.4.2.2" />8.4.2.2 Force of operation of mechanical parts</label>
<div>
<p>Where a control requires a force greater than 22,2 N to operate it, an accessible alternative means of operation that requires a force less than 22,2 N shall be provided.</p>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f47"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f47" aria-hidden="true" data-number="8.4.3" />8.4.3 Keys, tickets and fare cards</label>
<div>
<p>Where ICT provides keys, tickets or fare cards, and their orientation is important for further use, they shall have an orientation that is tactilely discernible.</p>
<p>NOTE: ETSI ETS 300 767 [i.6] defines suitable tactile indications for plastic cards.</p>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f48"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f48" aria-hidden="true" data-number="8.5" />8.5 Tactile indication of speech mode</label>
<div>
<p>Where ICT is designed for shared use and speech output is available, a tactile indication of the means to initiate the speech mode of operation shall be provided.</p>
<p>NOTE: The tactile indication could include Braille instructions.</p>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f49"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f49" aria-hidden="true" data-number="9" />9 Web</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f4a"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f4a" aria-hidden="true" data-number="9.0" />9.0 General (informative)</label>
<div>
<p>Requirements in clause 9 apply to web pages (as defined in clause 3.1) including:</p>
<ul>
<li>Conformance with WCAG 2.0 Level AA is equivalent to conforming with clauses 9.1.1, 9.1.2, 9.1.3.1 to 9.1.3.3, 9.1.4.1 to 9.1.4.5, 9.2.1.1, 9.2.1.2, 9.2.1.4, 9.2.1.1, 9.2.1.2, 9.2.2, 9.2.3, 9.2.4, 9.3, 9.4.1.1, 9.4.1.2 and the conformance requirements of clause 9.5 of the present document.</li>
<li>Conformance with WCAG 2.1 Level AA is equivalent to conforming with all of clauses 9.1 to 9.4 and the conformance requirements of clause 9.5 of the present document.</li>
<li>Requirements for other documents and software are provided in clauses 10 and 11 respectively.</li>
</ul>
<p>NOTE 1: When evaluating web sites they are evaluated as individual web pages. Web applications, mobile web applications etc. are covered under the definition of web page which is quite broad and covers all web content types.</p>
<p>The web content requirements in clauses 9.1 to 9.4 set out all of the Level A and Level AA Success Criteria from the</p>
<p>W3C Web Content Accessibility Guidelines (WCAG 2.1) [5]:</p>
<ul>
<li>Web Pages conforming to WCAG 2.0 Level A and AA also conform to clauses 9.1.1.1 to 9.1.3.3, 9.1.4.1 to 9.1.4.5, 9.2.1.1, 9.2.1.2, 9.2.2.1 to 9.2.4.7, 9.3.1.1 to 9.4.1.2 and the conformance requirements of clause 9.5.</li>
<li>Web Pages that conform to WCAG 2.1 Level AA conform to all of clauses 9.1 to 9.4 and the conformance requirements of clause 9.5.</li>
<li>Web Pages conforming to clauses 9.1.1.1 to 9.1.3.3, 9.1.4.1 to 9.1.4.5, 9.2.1.1, 9.2.1.2, 9.2.2.1 to 9.2.4.7, 9.3.1.1 to 9.4.1.2, and the conformance requirements of clause 9.5, also conform to WCAG 2.0 Level AA.</li>
<li>Web Pages that conform to all of clauses 9.1 to 9.4, and the conformance requirements of clause 9.5, conform to WCAG 2.1 Level AA.</li>
</ul>
<p>NOTE 2: WCAG 2.0 is identical to ISO/IEC 40500 (2012): "Information technology - W3C Web Content Accessibility Guidelines (WCAG) 2.0" [4].</p>
<p>The requirements in clauses 9.1 to 9.4 are written using the concept of satisfying success criteria (defined in clause 3.1).</p>
<p>A web page satisfies a WCAG success criterion when the success criterion does not evaluate to false when applied to the web page. This implies that if the success criterion puts conditions on a specific feature and that specific feature does not occur in the web page, then the web page satisfies the success criterion.</p>
<p>NOTE 3: For example, a web page that does not contain pre-recorded audio content in synchronized media will automatically satisfy WCAG success criterion 1.2.2 (captions - pre-recorded) and, in consequence, will also conform to clause 9.1.2.2.</p>
<p>In addition to Level AA success criteria, the Web Content Accessibility Guidelines also include success criteria for Level AAA.</p>
<p>NOTE 4: The body of the present document does not include the Level AAA success criteria, both to avoid confusion with the Level A and Level AA based requirements and for harmonisation with other procurement standards.</p>
<p>Web authors and procurement accessibility specialists are encouraged to improve accessibility beyond the requirements of the present document and should therefore consider whether any of the WCAG Level AAA success criteria offer suggestions that may be applicable and relevant to their project, as well as potentially beneficial to some users.</p>
<p>NOTE 5: The W3C states that "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".</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f4b"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f4b" aria-hidden="true" data-number="9.1" />9.1 Perceivable</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f4c"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f4c" aria-hidden="true" data-number="9.1.1" />9.1.1 Text alternatives</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f4d"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f4d" aria-hidden="true" data-number="9.1.1.1" />9.1.1.1 Non-text content</label>
<div>
<p>Where ICT is a web page, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#non-text-content">WCAG 2.1 Success Criterion 1.1.1 Non-text content</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 1.1.1 Non-text content</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/non-text-content.html">Understanding Non-text Content</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#non-text-content">How to Meet Non-text Content</a></p>
<p>(Level A)</p>
<p>All <a href="http://www.w3.org/TR/WCAG21/#dfn-non-text-content">non-text content</a> that is presented to the user has a <a href="http://www.w3.org/TR/WCAG21/#dfn-text-alternative">text alternative</a> that serves the equivalent purpose, except for the situations listed below.</p>
<ul>
<li>Controls, Input: If non-text content is a control or accepts user input, then it has a <a href="http://www.w3.org/TR/WCAG21/#dfn-name">name</a> that describes its purpose. (Refer to <a href="http://www.w3.org/TR/WCAG21/#name-role-value">Success Criterion 4.1.2</a> for additional requirements for controls and content that accepts user input.)</li>
<li>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 <a href="http://www.w3.org/TR/WCAG21/#time-based-media">Guideline 1.2</a> for additional requirements for media.)</li>
<li>Test: If non-text content is a test or exercise that would be invalid if presented in <a href="http://www.w3.org/TR/WCAG21/#dfn-text">text</a>, then text alternatives at least provide descriptive identification of the non-text content.</li>
<li>Sensory: If non-text content is primarily intended to create a <a href="http://www.w3.org/TR/WCAG21/#dfn-specific-sensory-experience">specific sensory experience,</a> then text alternatives at least provide descriptive identification of the non-text content.</li>
<li><a href="http://www.w3.org/TR/WCAG21/#dfn-captcha">CAPTCHA</a>: 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.</li>
<li>Decoration, Formatting, Invisible: If non-text content is <a href="http://www.w3.org/TR/WCAG21/#dfn-pure-decoration">pure decoration,</a> 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 <a href="http://www.w3.org/TR/WCAG21/#dfn-assistive-technologies">assistive technology</a>.</li>
</ul>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f4e"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f4e" aria-hidden="true" data-number="9.1.2" />9.1.2 Time-based media</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f4f"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f4f" aria-hidden="true" data-number="9.1.2.1" />9.1.2.1 Audio-only and video-only (prerecorded)</label>
<div>
<p>Where ICT is a web page, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#audio-only-and-video-only-prerecorded">WCAG 2.1 Success Criterion 1.2.1 Audio-only and Video-only (Prerecorded)</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 1.2.1 Audio-only and Video-only (Prerecorded)</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/audio-only-and-video-only-prerecorded.html">Understanding Audio-only and Video-only (Prerecorded)</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#audio-only-and-video-only-prerecorded">How to Meet Audio-only and Video-only (Prerecorded)</a></p>
<p>(Level A)</p>
<p>For <a href="http://www.w3.org/TR/WCAG21/#dfn-prerecorded">prerecorded</a><a href="https://www.w3.org/TR/WCAG21/#dfn-audio-only">audio-only</a> and prerecorded <a href="http://www.w3.org/TR/WCAG21/#dfn-video-only">video-only</a> media, the following are true, except when the audio or video is a <a href="http://www.w3.org/TR/WCAG21/#dfn-media-alternative-for-text">media alternative for text</a> and is clearly labeled as such:</p>
<ul>
<li>Prerecorded Audio-only: An <a href="http://www.w3.org/TR/WCAG21/#dfn-alternative-for-time-based-media">alternative for time-based media</a> is provided that presents equivalent information for prerecorded audio-only content.</li>
<li>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.</li>
</ul>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f50"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f50" aria-hidden="true" data-number="9.1.2.2" />9.1.2.2 Captions (prerecorded)</label>
<div>
<p>Where ICT is a web page, it shall satisfy the <a href="http://www.w3.org/TR/WCAG21/#captions-prerecorded">WCAG 2.1 Success Criterion 1.2.2 Captions (Prerecorded)</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 1.2.2 Captions (Prerecorded)</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/captions-prerecorded.html">Understanding Captions (Prerecorded)</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#captions-prerecorded">How to Meet Captions (Prerecorded)</a></p>
<p>(Level A)</p>
<p><a href="http://www.w3.org/TR/WCAG21/#dfn-captions">Captions</a> are provided for all <a href="http://www.w3.org/TR/WCAG21/#dfn-prerecorded">prerecorded</a><a href="http://www.w3.org/TR/WCAG21/#dfn-audio">audio</a> content in <a href="http://www.w3.org/TR/WCAG21/#dfn-synchronized-media">synchronized media</a>, except when the media is a <a href="http://www.w3.org/TR/WCAG21/#dfn-media-alternative-for-text">media alternative for text</a> and is clearly labeled as such.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f51"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f51" aria-hidden="true" data-number="9.1.2.3" />9.1.2.3 Audio description or media alternative (prerecorded)</label>
<div>
<p>Where ICT is a web page, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#audio-description-or-media-alternative-prerecorded">WCAG 2.1 Success Criterion 1.2.3 Audio Description or Media Alternative (Prerecorded)</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 1.2.3 Audio Description or Media Alternative (Prerecorded)</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/audio-description-or-media-alternative-prerecorded.html">Understanding Audio Description or Media Alternative (Prerecorded)</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#audio-description-or-media-alternative-prerecorded">How to Meet Audio Description or Media Alternative (Prerecorded)</a></p>
<p>(Level A)</p>
<p>An <a href="http://www.w3.org/TR/WCAG21/#dfn-alternative-for-time-based-media">alternative for time-based media</a> or audio description of the <a href="http://www.w3.org/TR/WCAG21/#dfn-prerecorded">prerecorded</a> video content is provided for <a href="http://www.w3.org/TR/WCAG21/#dfn-synchronized-media">synchronized media</a>, except when the media is a <a href="http://www.w3.org/TR/WCAG21/#dfn-media-alternative-for-text">media alternative for text</a> and is clearly labeled as such.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f52"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f52" aria-hidden="true" data-number="9.1.2.4" />9.1.2.4 Captions (live)</label>
<div>
<p>Where ICT is a web page, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#captions-live">WCAG 2.1 Success Criterion 1.2.4 Captions (Live)</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 1.2.4 Captions (Live)</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/captions-live.html">Understanding Captions (Live)</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#captions-live">How to Meet Captions (Live)</a></p>
<p>(Level AA)</p>
<p><a href="http://www.w3.org/TR/WCAG21/#dfn-captions">Captions</a> are provided for all <a href="http://www.w3.org/TR/WCAG21/#dfn-live">live</a><a href="http://www.w3.org/TR/WCAG21/#dfn-audio">audio</a> content in <a href="http://www.w3.org/TR/WCAG21/#dfn-synchronized-media">synchronized media</a>.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f53"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f53" aria-hidden="true" data-number="9.1.2.5" />9.1.2.5 Audio description (prerecorded)</label>
<div>
<p>Where ICT is a web page, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#audio-description-prerecorded">WCAG 2.1 Success Criterion 1.2.5 Audio Description (Prerecorded)</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 1.2.5 Audio Description (Prerecorded).</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/audio-description-prerecorded.html">Understanding Audio Description (Prerecorded)</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#audio-description-prerecorded">How to Meet Audio Description (Prerecorded)</a></p>
<p>(Level AA)</p>
<p><a href="http://www.w3.org/TR/WCAG21/#dfn-audio-descriptions">Audio description</a> is provided for all <a href="http://www.w3.org/TR/WCAG21/#dfn-prerecorded">prerecorded</a><a href="http://www.w3.org/TR/WCAG21/#dfn-video">video</a> content in <a href="http://www.w3.org/TR/WCAG21/#dfn-synchronized-media">synchronized media</a>.</p>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f54"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f54" aria-hidden="true" data-number="9.1.3" />9.1.3 Adaptable</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f55"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f55" aria-hidden="true" data-number="9.1.3.1" />9.1.3.1 Info and relationships</label>
<div>
<p>Where ICT is a web page, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#info-and-relationships">WCAG 2.1 Success Criterion 1.3.1 Info and Relationships</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 1.3.1 Info and Relationships</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/info-and-relationships.html">Understanding Info and Relationships</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#info-and-relationships">How to Meet Info and Relationships</a></p>
<p>(Level A)</p>
<p>Information, <a href="http://www.w3.org/TR/WCAG21/#dfn-structure">structure</a>, and <a href="http://www.w3.org/TR/WCAG21/#dfn-relationships">relationships</a> conveyed through <a href="http://www.w3.org/TR/WCAG21/#dfn-presentation">presentation</a> can be <a href="http://www.w3.org/TR/WCAG21/#dfn-programmatically-determinable">programmatically determined</a> or are available in text.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f56"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f56" aria-hidden="true" data-number="9.1.3.2" />9.1.3.2 Meaningful sequence</label>
<div>
<p>Where ICT is a web page, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#meaningful-sequence">WCAG 2.1 Success Criterion 1.3.2 Meaningful Sequence</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 1.3.2 Meaningful Sequence</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/meaningful-sequence.html">Understanding Meaningful Sequence</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#meaningful-sequence">How to Meet Meaningful Sequence</a></p>
<p>(Level A)</p>
<p>When the sequence in which content is presented affects its meaning, a <a href="http://www.w3.org/TR/WCAG21/#dfn-correct-reading-sequence">correct reading sequence</a> can be <a href="http://www.w3.org/TR/WCAG21/#dfn-programmatically-determinable">programmatically determined</a>.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f57"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f57" aria-hidden="true" data-number="9.1.3.3" />9.1.3.3 Sensory characteristics</label>
<div>
<p>Where ICT is a web page, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#sensory-characteristics">WCAG 2.1 Success Criterion 1.3.3 Sensory Characteristics</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 1.3.3 Sensory Characteristics</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/sensory-characteristics.html">Understanding Sensory Characteristics</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#sensory-characteristics">How to Meet Sensory Characteristics</a></p>
<p>(Level A)</p>
<p>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.</p>
<p>Note: For requirements related to color, refer to <a href="http://www.w3.org/TR/WCAG21/#distinguishable">Guideline 1.4</a>.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f58"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f58" aria-hidden="true" data-number="9.1.3.4" />9.1.3.4 Orientation</label>
<div>
<p>Where ICT is a web page, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#orientation">WCAG 2.1 Success Criterion 1.3.4 Orientation</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 1.3.4 Orientation</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/orientation.html">Understanding Orientation</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#orientation">How to Meet Orientation</a></p>
<p>(Level AA)</p>
<p>Content does not restrict its view and operation to a single display orientation, such as portrait or landscape, unless a specific display orientation is <a href="http://www.w3.org/TR/WCAG21/#dfn-essential">essential</a>.</p>
<p>Note: Examples where a particular display orientation may be essential are a bank check, a piano application, slides for a projector or television, or virtual reality content where binary display orientation is not applicable.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f59"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f59" aria-hidden="true" data-number="9.1.3.5" />9.1.3.5 Identify input purpose</label>
<div>
<p>Where ICT is a web page, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#identify-input-purpose">WCAG 2.1 Success Criterion 1.3.5 Identify Input Purpose</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 1.3.5 Identify Input Purpose</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/identify-input-purpose.html">Understanding Identify Input Purpose</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#identify-input-purpose">How to Meet Identify Input Purpose</a></p>
<p>(Level AA)</p>
<p>The purpose of each input field collecting information about the user can be <a href="http://www.w3.org/TR/WCAG21/#dfn-programmatically-determinable">programmatically determined</a> when:</p>
<ul>
<li>The input field serves a purpose identified in the <a href="http://www.w3.org/TR/WCAG21/#input-purposes">Input Purposes for User Interface Components</a> section; and</li>
<li>The content is implemented using technologies with support for identifying the expected meaning for form input data.</li>
</ul>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f5a"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f5a" aria-hidden="true" data-number="9.1.4" />9.1.4 Distinguishable</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f5b"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f5b" aria-hidden="true" data-number="9.1.4.1" />9.1.4.1 Use of colour</label>
<div>
<p>Where ICT is a web page, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#use-of-color">WCAG 2.1 Success Criterion 1.4.1 Use of Color</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 1.4.1 Use of Color</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/use-of-color.html">Understanding Use of Color</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#use-of-color">How to Meet Use of Color</a></p>
<p>(Level A)</p>
<p>Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.</p>
<p>Note: This success criterion addresses color perception specifically. Other forms of perception are covered in <a href="http://www.w3.org/TR/WCAG21/#adaptable">Guideline 1.3</a> including programmatic access to color and other visual presentation coding.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f5c"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f5c" aria-hidden="true" data-number="9.1.4.2" />9.1.4.2 Audio control</label>
<div>
<p>Where ICT is a web page, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#audio-control">WCAG 2.1 Success Criterion 1.4.2 Audio Control</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 1.4.2 Audio Control</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/audio-control.html">Understanding Audio Control</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#audio-control">How to Meet Audio Control</a></p>
<p>(Level A)</p>
<p>If any audio on a Web page plays automatically for more than 3 seconds, either a <a href="http://www.w3.org/TR/WCAG21/#dfn-mechanism">mechanism</a> is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level.</p>
<p>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 <a href="http://www.w3.org/TR/WCAG21/#cc5">Conformance Requirement 5: Non-Interference</a>.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f5d"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f5d" aria-hidden="true" data-number="9.1.4.3" />9.1.4.3 Contrast (minimum)</label>
<div>
<p>Where ICT is a web page, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#contrast-minimum">WCAG 2.1 Success Criterion 1.4.3 Contrast (Minimum)</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 1.4.3 Contrast (Minimum)</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/contrast-minimum.html">Understanding Contrast (Minimum)</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#contrast-minimum">How to Meet Contrast (Minimum)</a></p>
<p>(Level AA)</p>
<p>The visual presentation of <a href="http://www.w3.org/TR/WCAG21/#dfn-text">text</a> and <a href="http://www.w3.org/TR/WCAG21/#dfn-images-of-text">images of text</a> has a <a href="http://www.w3.org/TR/WCAG21/#dfn-contrast-ratio">contrast ratio</a> of at least 4.5:1, except for the following:</p>
<ul>
<li>Large Text: <a href="http://www.w3.org/TR/WCAG21/#dfn-large-scale">Large-scale text</a> and images of large-scale text have a contrast ratio of at least 3:1;</li>
<li>Incidental: Text or images of text that are part of an inactive <a href="http://www.w3.org/TR/WCAG21/#dfn-user-interface-components">user interface component</a>, that are <a href="http://www.w3.org/TR/WCAG21/#dfn-pure-decoration">pure decoration</a>, that are not visible to anyone, or that are part of a picture that contains significant other visual content, have no contrast requirement.</li>
<li>Logotypes: Text that is part of a logo or brand name has no contrast requirement.</li>
</ul>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f5e"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f5e" aria-hidden="true" data-number="9.1.4.4" />9.1.4.4 Resize text</label>
<div>
<p>Where ICT is a web page, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#resize-text">WCAG 2.1 Success Criterion 1.4.4 Resize text</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 1.4.4 Resize text</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/resize-text.html">Understanding Resize text</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#resize-text">How to Meet Resize text</a></p>
<p>(Level AA)</p>
<p>Except for <a href="http://www.w3.org/TR/WCAG21/#dfn-captions">captions</a> and <a href="http://www.w3.org/TR/WCAG21/#dfn-images-of-text">images of text</a>, <a href="http://www.w3.org/TR/WCAG21/#dfn-text">text</a> can be resized without <a href="http://www.w3.org/TR/WCAG21/#dfn-assistive-technologies">assistive technology</a> up to 200 percent without loss of content or functionality.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f5f"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f5f" aria-hidden="true" data-number="9.1.4.5" />9.1.4.5 Images of text</label>
<div>
<p>Where ICT is a web page, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#images-of-text">WCAG 2.1 Success Criterion 1.4.5 Images of Text</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 1.4.5 Images of Text.</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/images-of-text.html">Understanding Images of Text</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#images-of-text">How to Meet Images of Text</a></p>
<p>(Level AA)</p>
<p>If the technologies being used can achieve the visual presentation, <a href="http://www.w3.org/TR/WCAG21/#dfn-text">text</a> is used to convey information rather than <a href="http://www.w3.org/TR/WCAG21/#dfn-images-of-text">images of text</a> except for the following:</p>
<ul>
<li>Customizable: The image of text can be <a href="http://www.w3.org/TR/WCAG21/#dfn-visually-customized">visually customized</a> to the user's requirements;</li>
<li>Essential: A particular presentation of text is <a href="http://www.w3.org/TR/WCAG21/#dfn-essential">essential</a> to the information being conveyed.</li>
</ul>
<p>Note: Logotypes (text that is part of a logo or brand name) are considered essential.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f60"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f60" aria-hidden="true" data-number="9.1.4.10" />9.1.4.10 Reflow</label>
<div>
<p>Where ICT is a web page, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#reflow">WCAG 2.1 Success Criterion 1.4.10 Reflow</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 1.4.10 Reflow</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/reflow.html">Understanding Reflow</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#reflow">How to Meet Reflow</a></p>
<p>(Level AA)</p>
<p>Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions for:</p>
<ul>
<li>Vertical scrolling content at a width equivalent to 320 <a href="http://www.w3.org/TR/WCAG21/#dfn-css-pixels">CSS pixels</a>;</li>
<li>Horizontal scrolling content at a height equivalent to 256 <a href="http://www.w3.org/TR/WCAG21/#dfn-css-pixels">CSS pixels</a>.</li>
</ul>
<p>Except for parts of the content which require two-dimensional layout for usage or meaning.</p>
<p>Note: 320 CSS pixels is equivalent to a starting viewport width of 1280 CSS pixels wide at 400% zoom. For web content which are designed to scroll horizontally (e.g. with vertical text), the 256 CSS pixels is equivalent to a starting viewport height of 1024px at 400% zoom.</p>
<p>Note: Examples of content which require two-dimensional layout are images, maps, diagrams, video, games, presentations, data tables, and interfaces where it is necessary to keep toolbars in view while manipulating content.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f61"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f61" aria-hidden="true" data-number="9.1.4.11" />9.1.4.11 Non-text contrast</label>
<div>
<p>Where ICT is a web page, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#non-text-contrast">WCAG 2.1 Success Criterion 1.4.11 Non-text Contrast</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 1.4.11 Non-text Contrast</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/non-text-contrast.html">Understanding Non-text Contrast</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#non-text-contrast">How to Meet Non-text Contrast</a></p>
<p>(Level AA)</p>
<p>The visual <a href="http://www.w3.org/TR/WCAG21/#dfn-presentation">presentation</a> of the following have a <a href="http://www.w3.org/TR/WCAG21/#dfn-contrast-ratio">contrast ratio</a> of at least 3:1 against adjacent color(s):</p>
<ul>
<li>User Interface Components: Visual information required to identify <a href="http://www.w3.org/TR/WCAG21/#dfn-user-interface-components">user interface components</a> and <a href="http://www.w3.org/TR/WCAG21/#dfn-states">states</a>, except for inactive components or where the appearance of the component is determined by the user agent and not modified by the author;</li>
<li>Graphical Objects: Parts of graphics required to understand the content, except when a particular presentation of graphics is <a href="http://www.w3.org/TR/WCAG21/#dfn-essential">essential</a> to the information being conveyed.</li>
</ul>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f62"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f62" aria-hidden="true" data-number="9.1.4.12" />9.1.4.12 Text spacing</label>
<div>
<p>Where ICT is a web page, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#text-spacing">WCAG 2.1 Success Criterion 1.4.12 Text spacing</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 1.4.12 Text spacing</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/text-spacing.html">Understanding Text Spacing</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#text-spacing">How to Meet Text Spacing</a></p>
<p>(Level AA)</p>
<p>In content implemented using markup languages that support the following <a href="http://www.w3.org/TR/WCAG21/#dfn-text">text</a><a href="http://www.w3.org/TR/WCAG21/#dfn-style-properties">style properties</a>, no loss of content or functionality occurs by setting all of the following and by changing no other style property:</p>
<ul>
<li>Line height (line spacing) to at least 1.5 times the font size;</li>
<li>Spacing following paragraphs to at least 2 times the font size;</li>
<li>Letter spacing (tracking) to at least 0.12 times the font size;</li>
<li>Word spacing to at least 0.16 times the font size.</li>
</ul>
<p>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.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f63"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f63" aria-hidden="true" data-number="9.1.4.13" />9.1.4.13 Content on hover or focus</label>
<div>
<p>Where ICT is a web page, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#content-on-hover-or-focus">WCAG 2.1 Success Criterion 1.4.13 Content on Hover or Focus</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 1.4.13 Content on Hover or Focus</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/content-on-hover-or-focus.html">Understanding Content on Hover or Focus</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#content-on-hover-or-focus">How to Meet Content on Hover or Focus</a></p>
<p>(Level AA)</p>
<p>Where receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden, the following are true:</p>
<ul>
<li>Dismissable: A <a href="http://www.w3.org/TR/WCAG21/#dfn-mechanism">mechanism</a> is available to dismiss the additional content without moving pointer hover or keyboard focus, unless the additional content communicates an <a href="http://www.w3.org/TR/WCAG21/#dfn-input-error">input error</a> or does not obscure or replace other content;</li>
<li>Hoverable: If pointer hover can trigger the additional content, then the pointer can be moved over the additional content without the additional content disappearing;</li>
<li>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.</li>
</ul>
<p>Exception: The visual presentation of the additional content is controlled by the user agent and is not modified by the author.</p>
<p>Note: Examples of additional content controlled by the user agent include browser tooltips created through use of the HTML <a href="http://www.w3.org/TR/html/dom.html#the-title-attribute">title attribute</a>.</p>
<p>Note: Custom tooltips, sub-menus, and other non-modal popups that display on hover and focus are examples of additional content covered by this criterion.</p>
</div>
</div>
</li>
</ul>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f64"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f64" aria-hidden="true" data-number="9.2" />9.2 Operable</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f65"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f65" aria-hidden="true" data-number="9.2.1" />9.2.1 Keyboard accessible</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f66"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f66" aria-hidden="true" data-number="9.2.1.1" />9.2.1.1 Keyboard</label>
<div>
<p>Where ICT is a web page, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#keyboard">WCAG 2.1 Success Criterion 2.1.1 Keyboard</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 2.1.1 Keyboard</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/keyboard.html">Understanding Keyboard</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#keyboard">How to Meet Keyboard</a></p>
<p>(Level A)</p>
<p>All <a href="http://www.w3.org/TR/WCAG21/#dfn-functionality">functionality</a> of the content is operable through a <a href="http://www.w3.org/TR/WCAG21/#dfn-keyboard-interface">keyboard interface</a> 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.</p>
<p>Note: 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.</p>
<p>Note: This does not forbid and should not discourage providing mouse input or other input methods in addition to keyboard operation.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f67"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f67" aria-hidden="true" data-number="9.2.1.2" />9.2.1.2 No keyboard trap</label>
<div>
<p>Where ICT is a web page, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#no-keyboard-trap">WCAG 2.1 Success Criterion 2.1.2 No Keyboard Trap</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 2.1.2 No Keyboard Trap</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/no-keyboard-trap.html">Understanding No Keyboard Trap</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#no-keyboard-trap">How to Meet No Keyboard Trap</a></p>
<p>(Level A)</p>
<p>If keyboard focus can be moved to a component of the page using a <a href="http://www.w3.org/TR/WCAG21/#dfn-keyboard-interface">keyboard interface</a>, 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.</p>
<p>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 <a href="http://www.w3.org/TR/WCAG21/#cc5">Conformance Requirement 5: Non-Interference</a>.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f68"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f68" aria-hidden="true" data-number="9.2.1.4" />9.2.1.4 Character key shortcuts</label>
<div>
<p>Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion <a href="http://www.w3.org/TR/WCAG21/#character-key-shortcuts">2.1.4 Character Key Shortcuts</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 2.1.4 Character Key Shortcuts</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/character-key-shortcuts.html">Understanding Character Key Shortcuts</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#character-key-shortcuts">How to Meet Character Key Shortcuts</a></p>
<p>(Level A)</p>
<p>If a <a href="http://www.w3.org/TR/WCAG21/#dfn-keyboard-shortcuts">keyboard shortcut</a> 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:</p>
<ul>
<li>Turn off: A <a href="http://www.w3.org/TR/WCAG21/#dfn-mechanism">mechanism</a> is available to turn the shortcut off;</li>
<li>Remap: A mechanism is available to remap the shortcut to use one or more non-printable keyboard characters (e.g. Ctrl, Alt, etc.);</li>
<li>Active only on focus: The keyboard shortcut for a <a href="http://www.w3.org/TR/WCAG21/#dfn-user-interface-components">user interface component</a> is only active when that component has focus.</li>
</ul>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f69"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f69" aria-hidden="true" data-number="9.2.2" />9.2.2 Enough time</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f6a"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f6a" aria-hidden="true" data-number="9.2.2.1" />9.2.2.1 Timing adjustable</label>
<div>
<p>Where ICT is a web page, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#timing-adjustable">WCAG 2.1 Success Criterion 2.2.1 Timing Adjustable</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 2.2.1 Timing Adjustable</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/timing-adjustable.html">Understanding Timing Adjustable</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#timing-adjustable">How to Meet Timing Adjustable</a></p>
<p>(Level A)</p>
<p>For each time limit that is set by the content, at least one of the following is true:</p>
<ul>
<li>Turn off: The user is allowed to turn off the time limit before encountering it; or</li>
<li>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</li>
<li>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</li>
<li>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</li>
<li>Essential Exception: The time limit is <a href="http://www.w3.org/TR/WCAG21/#dfn-essential">essential</a> and extending it would invalidate the activity; or</li>
<li>20 Hour Exception: The time limit is longer than 20 hours.</li>
</ul>
<p>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 <a href="http://www.w3.org/TR/WCAG21/#on-focus">Success Criterion 3.2.1,</a> which puts limits on changes of content or context as a result of user action.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f6b"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f6b" aria-hidden="true" data-number="9.2.2.2" />9.2.2.2 Pause, stop, hide</label>
<div>
<p>Where ICT is a web page, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#pause-stop-hide">WCAG 2.1 Success Criterion 2.2.2 Pause, Stop, Hide</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 2.2.2 Pause, Stop, Hide</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/pause-stop-hide.html">Understanding Pause, Stop, Hide</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#pause-stop-hide">How to Meet Pause, Stop, Hide</a></p>
<p>(Level A)</p>
<p>For moving, <a href="http://www.w3.org/TR/WCAG21/#dfn-blinking">blinking</a>, scrolling, or auto-updating information, all of the following are true:</p>
<ul>
<li>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 <a href="http://www.w3.org/TR/WCAG21/#dfn-pause">pause</a>, stop, or hide it unless the movement, blinking, or scrolling is part of an activity where it is <a href="http://www.w3.org/TR/WCAG21/#dfn-essential">essential;</a> and</li>
<li>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.</li>
</ul>
<p>Note: For requirements related to flickering or flashing content, refer to <a href="http://www.w3.org/TR/WCAG21/#seizures-and-physical-reactions">Guideline 2.3</a>.</p>
<p>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 <a href="http://www.w3.org/TR/WCAG21/#cc5">Conformance Requirement 5: Non-Interference</a>.</p>
<p>Note: 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.</p>
<p>Note: 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.</p>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f6c"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f6c" aria-hidden="true" data-number="9.2.3" />9.2.3 Seizures and physical reactions</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f6d"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f6d" aria-hidden="true" data-number="9.2.3.1" />9.2.3.1 Three flashes or below threshold</label>
<div>
<p>Where ICT is a web page, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#three-flashes-or-below-threshold">WCAG 2.1 Success Criterion 2.3.1 Three Flashes or Below Threshold</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 2.3.1 Three Flashes or Below Threshold</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/three-flashes-or-below-threshold.html">Understanding Three Flashes or Below Threshold</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#three-flashes-or-below-threshold">How to Meet Three Flashes or Below Threshold</a></p>
<p>(Level A)</p>
<p><a href="http://www.w3.org/TR/WCAG21/#dfn-web-page-s">Web pages</a> do not contain anything that flashes more than three times in any one second period, or the <a href="http://www.w3.org/TR/WCAG21/#dfn-flashes">flash</a> is below the <a href="http://www.w3.org/TR/WCAG21/#dfn-general-flash-and-red-flash-thresholds">general flash and red flash thresholds</a>.</p>
<p>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 <a href="http://www.w3.org/TR/WCAG21/#cc5">Conformance Requirement 5: Non-Interference</a>.</p>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f6e"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f6e" aria-hidden="true" data-number="9.2.4" />9.2.4 Navigable</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f6f"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f6f" aria-hidden="true" data-number="9.2.4.1" />9.2.4.1 Bypass blocks</label>
<div>
<p>Where ICT is a web page, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#bypass-blocks">WCAG 2.1 Success Criterion 2.4.1 Bypass Blocks</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 2.4.1 Bypass Blocks</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/bypass-blocks.html">Understanding Bypass Blocks</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#bypass-blocks">How to Meet Bypass Blocks</a></p>
<p>(Level A)</p>
<p>A <a href="http://www.w3.org/TR/WCAG21/#dfn-mechanism">mechanism</a> is available to bypass blocks of content that are repeated on multiple <a href="http://www.w3.org/TR/WCAG21/#dfn-web-page-s">Web pages</a>.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f70"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f70" aria-hidden="true" data-number="9.2.4.2" />9.2.4.2 Page titled</label>
<div>
<p>Where ICT is a web page, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#page-titled">WCAG 2.1 Success Criterion 2.4.2 Page Titled</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 2.4.2 Page Titled</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/page-titled.html">Understanding Page Titled</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#page-titled">How to Meet Page Titled</a></p>
<p>(Level A)</p>
<p><a href="http://www.w3.org/TR/WCAG21/#dfn-web-page-s">Web pages</a> have titles that describe topic or purpose.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f71"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f71" aria-hidden="true" data-number="9.2.4.3" />9.2.4.3 Focus Order</label>
<div>
<p>Where ICT is a web page, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#focus-order">WCAG 2.1 Success Criterion 2.4.3 Focus Order</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 2.4.3 Focus Order</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/focus-order.html">Understanding Focus Order</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#focus-order">How to Meet Focus Order</a></p>
<p>(Level A)</p>
<p>If a <a href="http://www.w3.org/TR/WCAG21/#dfn-web-page-s">Web page</a> can be <a href="http://www.w3.org/TR/WCAG21/#dfn-navigated-sequentially">navigated sequentially</a> and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f72"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f72" aria-hidden="true" data-number="9.2.4.4" />9.2.4.4 Link purpose (in context)</label>
<div>
<p>Where ICT is a web page, it shall satisfy <a href="https://www.w3.org/TR/WCAG21/#link-purpose-in-context">WCAG 2.1 Success Criterion 2.4.4 Link Purpose (In Context)</a>-</p>
<p><strong>WCAG 2.1 Success Criterion 2.4.4 Link Purpose (In Context)</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/link-purpose-in-context.html">Understanding Link Purpose (In Context)</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#link-purpose-in-context">How to Meet Link Purpose (In Context)</a></p>
<p>(Level A)</p>
<p>The <a href="http://www.w3.org/TR/WCAG21/#dfn-purpose-of-each-link">purpose of each link</a> can be determined from the link text alone or from the link text together with its <a href="http://www.w3.org/TR/WCAG21/#dfn-programmatically-determined-link-context">programmatically determined link context</a>, except where the purpose of the link would be <a href="http://www.w3.org/TR/WCAG21/#dfn-ambiguous-to-users-in-general">ambiguous to users in general</a>.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f73"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f73" aria-hidden="true" data-number="9.2.4.5" />9.2.4.5 Multiple ways</label>
<div>
<p>Where ICT is a web page, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#multiple-ways">WCAG 2.1 Success Criterion 2.4.5 Multiple Ways</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 2.4.5 Multiple Ways</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/multiple-ways.html">Understanding Multiple Ways</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#multiple-ways">How to Meet Multiple Ways</a></p>
<p>(Level AA)</p>
<p>More than one way is available to locate a <a href="http://www.w3.org/TR/WCAG21/#dfn-web-page-s">Web page</a> within a <a href="http://www.w3.org/TR/WCAG21/#dfn-set-of-web-pages">set of Web pages</a> except where the Web Page is the result of, or a step in, a <a href="http://www.w3.org/TR/WCAG21/#dfn-processes">process</a>.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f74"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f74" aria-hidden="true" data-number="9.2.4.6" />9.2.4.6 Headings and labels</label>
<div>
<p>Where ICT is a web page, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#headings-and-labels">WCAG 2.1 Success Criterion 2.4.6 Headings and Labels</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 2.4.6 Headings and Labels</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/headings-and-labels.html">Understanding Headings and Labels</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#headings-and-labels">How to Meet Headings and Labels</a></p>
<p>(Level AA)</p>
<p>Headings and <a href="http://www.w3.org/TR/WCAG21/#dfn-labels">labels</a> describe topic or purpose.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f75"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f75" aria-hidden="true" data-number="9.2.4.7" />9.2.4.7 Focus visible</label>
<div>
<p>Where ICT is a web page, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#focus-visible">WCAG 2.1 Success Criterion 2.4.7 Focus Visible</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 2.4.7 Focus Visible</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/focus-visible.html">Understanding Focus Visible</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#focus-visible">How to Meet Focus Visible</a></p>
<p>(Level AA)</p>
<p>Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible.</p>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f76"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f76" aria-hidden="true" data-number="9.2.5" />9.2.5 Input modalities</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f77"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f77" aria-hidden="true" data-number="9.2.5.1" />9.2.5.1 Pointer gestures</label>
<div>
<p>Where ICT is a web page, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#pointer-gestures">WCAG 2.1 Success Criterion 2.5.1 Pointer Gestures</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 2.5.1 Pointer Gestures</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/pointer-gestures.html">Understanding Pointer Gestures</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#pointer-gestures">How to Meet Pointer Gestures</a></p>
<p>(Level A)</p>
<p>All <a href="http://www.w3.org/TR/WCAG21/#dfn-functionality">functionality</a> that uses multipoint or path-based gestures for operation can be operated with a <a href="http://www.w3.org/TR/WCAG21/#dfn-single-pointer">single pointer</a> without a path-based gesture, unless a multipoint or path-based gesture is <a href="http://www.w3.org/TR/WCAG21/#dfn-essential">essential</a>.</p>
<p>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).</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f78"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f78" aria-hidden="true" data-number="9.2.5.2" />9.2.5.2 Pointer cancellation</label>
<div>
<p>Where ICT is a web page, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#pointer-cancellation">WCAG 2.1 Success Criterion 2.5.2 Pointer Cancellation</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 2.5.2 Pointer Cancellation</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/pointer-cancellation.html">Understanding Pointer Cancellation</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#pointer-cancellation">How to Meet Pointer Cancellation</a></p>
<p>(Level A)</p>
<p>For <a href="http://www.w3.org/TR/WCAG21/#dfn-functionality">functionality</a> that can be operated using a <a href="http://www.w3.org/TR/WCAG21/#dfn-single-pointer">single pointer</a>, at least one of the following is true:</p>
<ul>
<li>No Down-Event: The <a href="http://www.w3.org/TR/WCAG21/#dfn-down-event">down-event</a> of the pointer is not used to execute any part of the function;</li>
<li>Abort or Undo: Completion of the function is on the <a href="http://www.w3.org/TR/WCAG21/#dfn-up-event">up-event,</a> and a <a href="http://www.w3.org/TR/WCAG21/#dfn-mechanism">mechanism</a> is available to abort the function before completion or to undo the function after completion;</li>
<li>Up Reversal: The up-event reverses any outcome of the preceding down-event;</li>
<li>Essential: Completing the function on the down-event is <a href="http://www.w3.org/TR/WCAG21/#dfn-essential">essential</a>.</li>
</ul>
<p>Note: Functions that emulate a keyboard or numeric keypad key press are considered essential.</p>
<p>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).</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f79"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f79" aria-hidden="true" data-number="9.2.5.3" />9.2.5.3 Label in name</label>
<div>
<p>Where ICT is a web page, it shall satisfy <a href="https://www.w3.org/TR/WCAG21/#label-in-name">WCAG 2.1 Success Criterion 2.5.3 Label in Name</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 2.5.3 Label in Name</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/label-in-name.html">Understanding Label in Name</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#label-in-name">How to Meet Label in Name</a></p>
<p>(Level A)</p>
<p>For user <a href="http://www.w3.org/TR/WCAG21/#dfn-user-interface-components">interface components</a> with <a href="http://www.w3.org/TR/WCAG21/#dfn-labels">labels</a> that include <a href="http://www.w3.org/TR/WCAG21/#dfn-text">text</a> or <a href="http://www.w3.org/TR/WCAG21/#dfn-images-of-text">images of text</a>, the <a href="http://www.w3.org/TR/WCAG21/#dfn-name">name</a> contains the text that is presented visually.</p>
<p>Note: A best practice is to have the text of the label at the start of the name.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f7a"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f7a" aria-hidden="true" data-number="9.2.5.4" />9.2.5.4 Motion actuation</label>
<div>
<p>Where ICT is a web page, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#motion-actuation">WCAG 2.1 Success Criterion 2.5.4 Motion Actuation</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 2.5.4 Motion Actuation</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/motion-actuation.html">Understanding Motion Actuation</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#motion-actuation">How to Meet Motion Actuation</a></p>
<p>(Level A)</p>
<p><a href="http://www.w3.org/TR/WCAG21/#dfn-functionality">Functionality</a> that can be operated by device motion or user motion can also be operated by <a href="http://www.w3.org/TR/WCAG21/#dfn-user-interface-components">user interface components</a> and responding to the motion can be disabled to prevent accidental actuation, except when:</p>
<ul>
<li>Supported Interface: The motion is used to operate functionality through an <a href="http://www.w3.org/TR/WCAG21/#dfn-accessibility-supported">accessibility supported</a> interface;</li>
<li>Essential: The motion is <a href="http://www.w3.org/TR/WCAG21/#dfn-essential">essential</a> for the function and doing so would invalidate the activity.</li>
</ul>
</div>
</div>
</li>
</ul>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f7b"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f7b" aria-hidden="true" data-number="9.3" />9.3 Understandable</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f7c"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f7c" aria-hidden="true" data-number="9.3.1" />9.3.1 Readable</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f7d"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f7d" aria-hidden="true" data-number="9.3.1.1" />9.3.1.1 Language of page</label>
<div>
<p>Where ICT is a web page, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#language-of-page">WCAG 2.1 Success Criterion 3.1.1 Language of Page</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 3.1.1 Language of Page</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/language-of-page.html">Understanding Language of Page</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#language-of-page">How to Meet Language of Page</a></p>
<p>(Level A)</p>
<p>The default <a href="http://www.w3.org/TR/WCAG21/#dfn-human-language-s">human language</a> of each <a href="http://www.w3.org/TR/WCAG21/#dfn-web-page-s">Web page</a> can be <a href="http://www.w3.org/TR/WCAG21/#dfn-programmatically-determinable">programmatically determined</a>.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f7e"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f7e" aria-hidden="true" data-number="9.3.1.2" />9.3.1.2 Language of parts</label>
<div>
<p>Where ICT is a web page, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#language-of-parts">WCAG 2.1 Success Criterion 3.1.2 Language of Parts</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 3.1.2 Language of Parts</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/language-of-parts.html">Understanding Language of Parts</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#language-of-parts">How to Meet Language of Parts</a></p>
<p>(Level AA)</p>
<p>The <a href="http://www.w3.org/TR/WCAG21/#dfn-human-language-s">human language</a> of each passage or phrase in the content can be <a href="http://www.w3.org/TR/WCAG21/#dfn-programmatically-determinable">programmatically determined</a> 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.</p>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f7f"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f7f" aria-hidden="true" data-number="9.3.2" />9.3.2 Predictable</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f80"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f80" aria-hidden="true" data-number="9.3.2.1" />9.3.2.1 On focus</label>
<div>
<p>Where ICT is a web page, it shall satisfy <a href="https://www.w3.org/TR/WCAG21/#on-focus">WCAG 2.1 Success Criterion 3.2.1 On Focus</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 3.2.1 On Focus</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/on-focus.html">Understanding On Focus</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#on-focus">How to Meet On Focus</a></p>
<p>(Level A)</p>
<p>When any <a href="http://www.w3.org/TR/WCAG21/#dfn-user-interface-components">user interface component</a> receives focus, it does not initiate a <a href="http://www.w3.org/TR/WCAG21/#dfn-change-of-context">change of context</a>.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f81"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f81" aria-hidden="true" data-number="9.3.2.2" />9.3.2.2 On input</label>
<div>
<p>Where ICT is a web page, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#on-input">WCAG 2.1 Success Criterion 3.2.2 On Input</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 3.2.2 On Input</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/on-input.html">Understanding On Input</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#on-input">How to Meet On Input</a></p>
<p>(Level A)</p>
<p>Changing the setting of any <a href="http://www.w3.org/TR/WCAG21/#dfn-user-interface-components">user interface component</a> does not automatically cause a <a href="http://www.w3.org/TR/WCAG21/#dfn-change-of-context">change of context</a> unless the user has been advised of the behavior before using the component.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f82"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f82" aria-hidden="true" data-number="9.3.2.3" />9.3.2.3 Consistent navigation</label>
<div>
<p>Where ICT is a web page, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#consistent-navigation">WCAG 2.1 Success Criterion 3.2.3 Consistent Navigation</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 3.2.3 Consistent Navigation</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/consistent-navigation.html">Understanding Consistent Navigation</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#consistent-navigation">How to Meet Consistent Navigation</a></p>
<p>(Level AA)</p>
<p>Navigational mechanisms that are repeated on multiple <a href="http://www.w3.org/TR/WCAG21/#dfn-web-page-s">Web pages</a> within a <a href="http://www.w3.org/TR/WCAG21/#dfn-set-of-web-pages">set of Web pages</a> occur in the <a href="http://www.w3.org/TR/WCAG21/#dfn-same-relative-order">same relative order</a> each time they are repeated, unless a change is initiated by the user.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f83"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f83" aria-hidden="true" data-number="9.3.2.4" />9.3.2.4 Consistent identification</label>
<div>
<p>Where ICT is a web page, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#consistent-identification">WCAG 2.1 Success Criterion 3.2.4 Consistent Identification</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 3.2.4 Consistent Identification</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/consistent-identification.html">Understanding Consistent Identification</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#consistent-identification">How to Meet Consistent Identification</a></p>
<p>(Level AA)</p>
<p>Components that have the <a href="http://www.w3.org/TR/WCAG21/#dfn-same-functionality">same functionality</a> within a <a href="http://www.w3.org/TR/WCAG21/#dfn-set-of-web-pages">set of Web pages</a> are identified consistently.</p>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f84"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f84" aria-hidden="true" data-number="9.3.3" />9.3.3 Input assistance</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f85"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f85" aria-hidden="true" data-number="9.3.3.1" />9.3.3.1 Error identification</label>
<div>
<p>Where ICT is a web page, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#error-identification">WCAG 2.1 Success Criterion 3.3.1 Error Identification</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 3.3.1 Error Identification</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/error-identification.html">Understanding Error Identification</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#error-identification">How to Meet Error Identification</a></p>
<p>(Level A)</p>
<p>If an <a href="http://www.w3.org/TR/WCAG21/#dfn-input-error">input error</a> is automatically detected, the item that is in error is identified and the error is described to the user in text.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f86"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f86" aria-hidden="true" data-number="9.3.3.2" />9.3.3.2 Labels or instructions</label>
<div>
<p>Where ICT is a web page, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#labels-or-instructions">WCAG 2.1 Success Criterion 3.3.2 Labels or Instructions</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 3.3.2 Labels or Instructions</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/labels-or-instructions.html">Understanding Labels or Instructions</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#labels-or-instructions">How to Meet Labels or Instructions</a></p>
<p>(Level A)</p>
<p><a href="http://www.w3.org/TR/WCAG21/#dfn-labels">Labels</a> or instructions are provided when content requires user input.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f87"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f87" aria-hidden="true" data-number="9.3.3.3" />9.3.3.3 Error suggestion</label>
<div>
<p>Where ICT is a web page, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#error-suggestion">WCAG 2.1 Success Criterion 3.3.3 Error Suggestion</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 3.3.3 Error Suggestion</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/error-suggestion.html">Understanding Error Suggestion</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#error-suggestion">How to Meet Error Suggestion</a></p>
<p>(Level AA)</p>
<p>If an <a href="http://www.w3.org/TR/WCAG21/#dfn-input-error">input error</a> 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.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f88"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f88" aria-hidden="true" data-number="9.3.3.4" />9.3.3.4 Error prevention (legal, financial, data)</label>
<div>
<p>Where ICT is a web page, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#error-prevention-legal-financial-data">WCAG 2.1 Success Criterion 3.3.4 Error Prevention (Legal, Financial, Data)</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 3.3.4 Error Prevention (Legal, Financial, Data)</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/error-prevention-legal-financial-data.html">Understanding Error Prevention (Legal, Financial, Data)</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#error-prevention-legal-financial-data">How to Meet Error Prevention (Legal, Financial, Data)</a></p>
<p>(Level AA)</p>
<p>For <a href="http://www.w3.org/TR/WCAG21/#dfn-web-page-s">Web pages</a> that cause <a href="http://www.w3.org/TR/WCAG21/#dfn-legal-commitments">legal commitments</a> or financial transactions for the user to occur, that modify or delete <a href="http://www.w3.org/TR/WCAG21/#dfn-user-controllable">user-controllable</a> data in data storage systems, or that submit user test responses, at least one of the following is true:</p>
<ul>
<li>Reversible: Submissions are reversible.</li>
<li>Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them.</li>
<li>Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.</li>
</ul>
</div>
</div>
</li>
</ul>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f89"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f89" aria-hidden="true" data-number="9.4" />9.4 Robust</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f8a"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f8a" aria-hidden="true" data-number="9.4.1" />9.4.1 Compatible</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f8b"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f8b" aria-hidden="true" data-number="9.4.1.1" />9.4.1.1 Parsing</label>
<div>
<p>Where ICT is a web page, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#parsing">WCAG 2.1 Success Criterion 4.1.1 Parsing</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 4.1.1 Parsing</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/parsing.html">Understanding Parsing</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#parsing">How to Meet Parsing</a></p>
<p>(Level A)</p>
<p>In content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features.</p>
<p>Note: Start and end tags that are missing a critical character in their formation, such as a closing angle bracket or a mismatched attribute value quotation mark are not complete.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f8c"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f8c" aria-hidden="true" data-number="9.4.1.2" />9.4.1.2 Name, role, value</label>
<div>
<p>Where ICT is a web page, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#name-role-value">WCAG 2.1 Success Criterion 4.1.2 Name, Role, Value</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 4.1.2 Name, Role, Value</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/name-role-value.html">Understanding Name, Role, Value</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#name-role-value">How to Meet Name, Role, Value</a></p>
<p>(Level A)</p>
<p>For all <a href="http://www.w3.org/TR/WCAG21/#dfn-user-interface-components">user interface components</a> (including but not limited to: form elements, links and components generated by scripts), the <a href="http://www.w3.org/TR/WCAG21/#dfn-name">name</a> and <a href="http://www.w3.org/TR/WCAG21/#dfn-role">role</a> can be <a href="http://www.w3.org/TR/WCAG21/#dfn-programmatically-determinable">programmatically determined</a>; states, properties, and values that can be set by the user can be <a href="http://www.w3.org/TR/WCAG21/#dfn-programmatically-set">programmatically set</a>; and notification of changes to these items is available to <a href="http://www.w3.org/TR/WCAG21/#dfn-user-agents">user agents</a>, including <a href="http://www.w3.org/TR/WCAG21/#dfn-assistive-technologies">assistive technologies</a>.</p>
<p>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.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f8d"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f8d" aria-hidden="true" data-number="9.4.1.3" />9.4.1.3 Status messages</label>
<div>
<p>Where ICT is a web page, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#status-messages">WCAG 2.1 Success Criterion 4.1.3 Status Messages</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 4.1.3 Status Messages</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/status-messages.html">Understanding Status Messages</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#status-messages">How to Meet Status Messages</a></p>
<p>(Level AA)</p>
<p>In content implemented using markup languages, <a href="http://www.w3.org/TR/WCAG21/#dfn-status-messages">status messages</a> can be <a href="http://www.w3.org/TR/WCAG21/#dfn-programmatically-determinable">programmatically determined</a> through <a href="http://www.w3.org/TR/WCAG21/#dfn-role">role</a> or properties such that they can be presented to the user by <a href="http://www.w3.org/TR/WCAG21/#dfn-assistive-technologies">assistive technologies</a> without receiving focus.</p>
</div>
</div>
</li>
</ul>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f8e"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f8e" aria-hidden="true" data-number="9.5" />9.5 WCAG conformance requirements</label>
<div>
<p>Where ICT is a web page, it shall satisfy all the following five WCAG 2.1 conformance requirements at Level AA [5].</p>
<ol>
<li>Conformance level</li>
<li>Full pages</li>
<li>Complete processes</li>
<li>Only Accessibility-Supported Ways of Using Technologies</li>
<li>Non-interference</li>
</ol>
<p>NOTE 1: A Web page that meets all of requirements 9.1 to 9.4, or where a Level AA conforming alternate version (as defined in WCAG 2.1 [5]) is provided, will meet conformance requirement 1.</p>
<p>NOTE 2: According to W3C: "WCAG 2.1 extends Web Content Accessibility Guidelines 2.0 [4], which was published as a W3C Recommendation December 2008. Content that conforms to WCAG 2.1 also conforms to WCAG 2.0, and therefore to policies that reference WCAG 2.0" [4].</p>
<p>NOTE 3: Conformance requirement 5 states that all content on the page, including content that is not otherwise relied upon to meet conformance, meets clauses 9.1.4.2, 9.2.1.2, 9.2.2.2 and 9.2.3.1.</p>
<p>WCAG 2.1 conformance requirements at Level AA [5]</p>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f8f"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f8f" aria-hidden="true" data-number="10" />10 Non-web documents</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f90"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f90" aria-hidden="true" data-number="10.0" />10.0 General (informative)</label>
<div>
<p>Requirements in clause 10 apply to documents:</p>
<ul>
<li>that are not web pages;</li>
<li>that are not embedded in web pages;</li>
<li>that are embedded in web pages and that are not used in the rendering and that are not intended to be rendered together with the web page in which they are embedded.</li>
</ul>
<p>Clause 9 provides requirements for documents that are in web pages or that are embedded in web pages and that are used in the rendering or that are intended to be rendered together with the web page in which they are embedded.</p>
<p>NOTE 1: Some examples of documents are letters, spreadsheets, emails, books, pictures, presentations, and movies that have an associated user agent such as a document reader, editor or media player.</p>
<p>NOTE 2: A single document may be composed of multiple files such as the video content, closed caption text, etc. This fact is not usually apparent to the end-user consuming the document/content.</p>
<p>NOTE 3: Documents require a user agent in order for the content to be presented to users. The requirements for user agents can be found in clause 11.</p>
<p>NOTE 4: The requirements for content that is part of software, can be found in clause 11.</p>
<p>NOTE 5: The success criteria set out in clause 10 are intended to harmonize with the Working Group Note [i.26] produced by the W3C's <a href="http://www.w3.org/WAI/GL/WCAG2ICT-TF/">WCAG2ICT Task Force</a>.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f91"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f91" aria-hidden="true" data-number="10.1" />10.1 Perceivable</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f92"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f92" aria-hidden="true" data-number="10.1.1" />10.1.1 Text alternatives</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f93"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f93" aria-hidden="true" data-number="10.1.1.1" />10.1.1.1 Non-text content</label>
<div>
<p>Where ICT is a non-web document, it shall satisfy the <a href="http://www.w3.org/TR/WCAG21/#non-text-content">WCAG 2.1 Success Criterion 1.1.1 Non-text Content</a>.</p>
<p>NOTE: CAPTCHAs do not currently appear outside of the Web. However, if they do appear, this guidance is accurate.</p>
<p><strong>WCAG 2.1 Success Criterion 1.1.1 Non-text Content</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/non-text-content.html">Understanding Non-text Content</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#non-text-content">How to Meet Non-text Content</a></p>
<p>(Level A)</p>
<p>All <a href="http://www.w3.org/TR/WCAG21/#dfn-non-text-content">non-text content</a> that is presented to the user has a <a href="http://www.w3.org/TR/WCAG21/#dfn-text-alternative">text alternative</a> that serves the equivalent purpose, except for the situations listed below.</p>
<ul>
<li>Controls, Input: If non-text content is a control or accepts user input, then it has a <a href="http://www.w3.org/TR/WCAG21/#dfn-name">name</a> that describes its purpose. (Refer to <a href="http://www.w3.org/TR/WCAG21/#name-role-value">Success Criterion 4.1.2</a> for additional requirements for controls and content that accepts user input.)</li>
<li>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 <a href="http://www.w3.org/TR/WCAG21/#time-based-media">to Guideline 1.2</a> for additional requirements for media.)</li>
<li>Test: If non-text content is a test or exercise that would be invalid if presented in <a href="http://www.w3.org/TR/WCAG21/#dfn-text">text</a>, then text alternatives at least provide descriptive identification of the non-text content.</li>
<li>Sensory: If non-text content is primarily intended to create a <a href="http://www.w3.org/TR/WCAG21/#dfn-specific-sensory-experience">specific sensory experience</a>, then text alternatives at least provide descriptive identification of the non-text content.</li>
<li><a href="http://www.w3.org/TR/WCAG21/#dfn-captcha">CAPTCHA</a>: 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.</li>
<li>Decoration, Formatting, Invisible: If non-text content is <a href="http://www.w3.org/TR/WCAG21/#dfn-pure-decoration">pure decoration</a>, 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 <a href="http://www.w3.org/TR/WCAG21/#dfn-assistive-technologies">assistive technology</a>.</li>
</ul>
</div>
</div>
</li>
</ul>
</li>
</ul>
</li>
</ul>
</li>
</ul>


<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f94"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f94" aria-hidden="true" data-number="10.1.2" />10.1.2 Time-based media</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f95"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f95" aria-hidden="true" data-number="10.1.2.1" />10.1.2.1 Audio-only and video-only (prerecorded)</label>
<div>
<p>Where ICT is a non-web document, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#audio-only-and-video-only-prerecorded">WCAG 2.1 Success Criterion 1.2.1 Audio-only and Video-only (Prerecorded)</a>.</p>
<p>NOTE: The alternative can be provided directly in the document - or provided in an alternate version that meets the success criterion.</p>
<p><strong>Success Criterion 1.2.1 Audio-only and Video-only (Prerecorded)</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/audio-only-and-video-only-prerecorded.html">Understanding Audio-only and Video-only (Prerecorded)</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#audio-only-and-video-only-prerecorded">How to Meet Audio-only and Video-only (Prerecorded)</a></p>
<p>(Level A)</p>
<p>For <a href="http://www.w3.org/TR/WCAG21/#dfn-prerecorded">prerecorded audio-only</a> and prerecorded <a href="http://www.w3.org/TR/WCAG21/#dfn-video-only">video-only</a> media, the following are true, except when the audio or video is a <a href="http://www.w3.org/TR/WCAG21/#dfn-media-alternative-for-text">media alternative for text</a> and is clearly labeled as such:</p>
<ul>
<li>Prerecorded Audio-only: An <a href="http://www.w3.org/TR/WCAG21/#dfn-alternative-for-time-based-media">alternative for time-based media</a> is provided that presents equivalent information for prerecorded audio-only content.</li>
<li>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.</li>
</ul>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f96"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f96" aria-hidden="true" data-number="10.1.2.2" />10.1.2.2 Captions (prerecorded)</label>
<div>
<p>Where ICT is a non-web document, it shall satisfy the <a href="http://www.w3.org/TR/WCAG21/#captions-prerecorded">WCAG 2.1 Success Criterion 1.2.2 Captions (Prerecorded)</a>.</p>
<p>NOTE: The WCAG 2.1 definition of "captions" notes that "in some countries, captions are called subtitles". They are also sometimes referred to as "subtitles for the hearing impaired". Per the definition in WCAG 2.1, to meet this success criterion, whether called captions or subtitles, they would have to provide "synchronized visual and / or text alternative for both speech and non-speech audio information needed to understand the media content" where non-speech information includes "sound effects, music, laughter, speaker identification and location".</p>
<p><strong>WCAG 2.1 Success Criterion 1.2.2 Captions (Prerecorded).</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/captions-prerecorded.html">Understanding Captions (Prerecorded)</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#captions-prerecorded">How to Meet Captions (Prerecorded)</a></p>
<p>(Level A)</p>
<p><a href="http://www.w3.org/TR/WCAG21/#dfn-captions">Captions</a> are provided for all <a href="http://www.w3.org/TR/WCAG21/#dfn-prerecorded">prerecorded</a> audio content in <a href="http://www.w3.org/TR/WCAG21/#dfn-synchronized-media">synchronized media</a>, except when the media is a <a href="http://www.w3.org/TR/WCAG21/#dfn-media-alternative-for-text">media alternative for text</a> and is clearly labeled as such.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f97"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f97" aria-hidden="true" data-number="10.1.2.3" />10.1.2.3 Audio description or media alternative (prerecorded)</label>
<div>
<p>Where ICT is a non-web document, it shall satisfy the <a href="http://www.w3.org/TR/WCAG21/#audio-description-or-media-alternative-prerecorded">WCAG 2.1 Success Criterion 1.2.3 Audio Description or Media Alternative (Prerecorded)</a>.</p>
<p>NOTE 1: The WCAG 2.1 definition of "audio description" says that "audio description" is "Also called 'video description' and 'descriptive narration'".</p>
<p>NOTE 2: Secondary or alternate audio tracks are commonly used for this purpose.</p>
<p><strong>WCAG 2.1 Success Criterion 1.2.3 Audio Description or Media Alternative (Prerecorded).</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/audio-description-or-media-alternative-prerecorded.html">Understanding Audio Description or Media Alternative (Prerecorded)</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#audio-description-or-media-alternative-prerecorded">How to Meet Audio Description or Media Alternative (Prerecorded)</a></p>
<p>(Level A)</p>
<p>An <a href="http://www.w3.org/TR/WCAG21/#dfn-alternative-for-time-based-media">alternative for time-based media</a> or <a href="http://www.w3.org/TR/WCAG21/#dfn-audio-descriptions">audio description</a> of the <a href="http://www.w3.org/TR/WCAG21/#dfn-prerecorded">prerecorded</a><a href="http://www.w3.org/TR/WCAG21/#dfn-video">video</a> content is provided for <a href="http://www.w3.org/TR/WCAG21/#dfn-synchronized-media">synchronized media</a>, except when the media is a <a href="http://www.w3.org/TR/WCAG21/#dfn-media-alternative-for-text">media alternative for text</a> and is clearly labeled as such.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f98"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f98" aria-hidden="true" data-number="10.1.2.4" />10.1.2.4 Captions (live)</label>
<div>
<p>Where ICT is a non-web document, it shall satisfy the <a href="http://www.w3.org/TR/WCAG21/#captions-live">WCAG 2.1 Success Criterion 1.2.4 Captions (Live)</a>.</p>
<p>NOTE: The WCAG 2.1 definition of "captions" notes that "in some countries, captions are called subtitles". They are also sometimes referred to as "subtitles for the hearing impaired". Per the definition in WCAG 2.1, to meet this success criterion, whether called captions or subtitles, they would have to provide "synchronized visual and / or text alternative for both speech and non-speech audio information needed to understand the media content" where non-speech information includes "sound effects, music, laughter, speaker identification and location".</p>
<p><strong>WCAG 2.1 Success Criterion 1.2.4 Captions (Live)</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/captions-live.html">Understanding Captions (Live)</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#audio-description-or-media-alternative-prerecorded">How to Meet Captions (Live)</a></p>
<p>(Level AA)</p>
<p><a href="http://www.w3.org/TR/WCAG21/#dfn-captions">Captions</a> are provided for all <a href="http://www.w3.org/TR/WCAG21/#dfn-live">live</a><a href="http://www.w3.org/TR/WCAG21/#dfn-audio">audio</a> content in <a href="http://www.w3.org/TR/WCAG21/#dfn-synchronized-media">synchronized media</a>.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f99"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f99" aria-hidden="true" data-number="10.1.2.5" />10.1.2.5 Audio description (prerecorded)</label>
<div>
<p>Where ICT is a non-web document, it shall satisfy the <a href="http://www.w3.org/TR/WCAG21/#audio-description-prerecorded">WCAG 2.1 Success Criterion 1.2.5 Audio Description (Prerecorded)</a>.</p>
<p>NOTE 1: The WCAG 2.1 definition of "audio description" says that audio description is "Also called 'video description' and 'descriptive narration'".</p>
<p>NOTE 2: Secondary or alternate audio tracks are commonly used for this purpose.</p>
<p><strong>WCAG 2.1 Success Criterion 1.2.5 Audio Description (Prerecorded)</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/audio-description-prerecorded.html">Understanding Audio Description (Prerecorded)</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#audio-description-prerecorded">How to Meet Audio Description (Prerecorded)</a></p>
<p>(Level AA)</p>
<p><a href="http://www.w3.org/TR/WCAG21/#dfn-audio-descriptions">Audio description</a> is provided for all <a href="http://www.w3.org/TR/WCAG21/#dfn-prerecorded">prerecorded</a><a href="http://www.w3.org/TR/WCAG21/#dfn-video">video</a> content in <a href="http://www.w3.org/TR/WCAG21/#dfn-synchronized-media">synchronized media</a>.</p>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f9a"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f9a" aria-hidden="true" data-number="10.1.3" />10.1.3 Adaptable</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f9b"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f9b" aria-hidden="true" data-number="10.1.3.1" />10.1.3.1 Info and relationships</label>
<div>
<p>Where ICT is a non-web document, it shall satisfy the <a href="http://www.w3.org/TR/WCAG21/#info-and-relationships">WCAG 2.1 Success Criterion 1.3.1 Info and Relationships</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 1.3.1 Info and Relationships</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/info-and-relationships.html">Understanding Info and Relationships</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#info-and-relationships">How to Meet Info and Relationships</a></p>
<p>(Level A)</p>
<p>Information, <a href="http://www.w3.org/TR/WCAG21/#dfn-structure">structure</a>, and <a href="http://www.w3.org/TR/WCAG21/#dfn-relationships">relationships</a> conveyed through <a href="http://www.w3.org/TR/WCAG21/#dfn-presentation">presentation</a> can be <a href="http://www.w3.org/TR/WCAG21/#dfn-programmatically-determinable">programmatically determined</a> or are available in text.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f9c"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f9c" aria-hidden="true" data-number="10.1.3.2" />10.1.3.2 Meaningful sequence</label>
<div>
<p>Where ICT is a non-web document, it shall satisfy the <a href="http://www.w3.org/TR/WCAG21/#meaningful-sequence">WCAG 2.1 Success Criterion 1.3.2 Meaningful Sequence</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 1.3.2 Meaningful Sequence</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/meaningful-sequence.html">Understanding Meaningful Sequence</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#meaningful-sequence">How to Meet Meaningful Sequence</a></p>
<p>(Level A)</p>
<p>When the sequence in which content is presented affects its meaning, a <a href="http://www.w3.org/TR/WCAG21/#dfn-correct-reading-sequence">correct reading sequence</a> can be <a href="http://www.w3.org/TR/WCAG21/#dfn-programmatically-determinable">programmatically determined</a>.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f9d"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f9d" aria-hidden="true" data-number="10.1.3.3" />10.1.3.3 Sensory characteristics</label>
<div>
<p>Where ICT is a non-web document, it shall satisfy the <a href="http://www.w3.org/TR/WCAG21/#sensory-characteristics">WCAG 2.1 Success Criterion 1.3.3 Sensory Characteristics</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 1.3.3 Sensory Characteristics.</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/sensory-characteristics.html">Understanding Sensory Characteristics</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#sensory-characteristics">How to Meet Sensory Characteristics</a></p>
<p>(Level A)</p>
<p>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.</p>
<p>Note: For requirements related to color, refer to WCAG 2.1 - <a href="http://www.w3.org/TR/WCAG21/#distinguishable">Guideline 1.4</a>.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f9e"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f9e" aria-hidden="true" data-number="10.1.3.4" />10.1.3.4 Orientation</label>
<div>
<p>Where ICT is a non-web document, it shall satisfy the <a href="http://www.w3.org/TR/WCAG21/#orientation">WCAG 2.1 Success Criterion 1.3.4 Orientation</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 1.3.4 Orientation</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/orientation.html">Understanding Orientation</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#orientation">How to Meet Orientation</a></p>
<p>(Level AA)</p>
<p>Content does not restrict its view and operation to a single display orientation, such as portrait or landscape, unless a specific display orientation is <a href="http://www.w3.org/TR/WCAG21/#dfn-essential">essential</a>.</p>
<p>Note: Examples where a particular display orientation may be essential are a bank check, a piano application, slides for a projector or television, or virtual reality content where binary display orientation is not applicable.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645f9f"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645f9f" aria-hidden="true" data-number="10.1.3.5" />10.1.3.5 Identify input purpose</label>
<div>
<p>Where ICT is a non-web document, it shall satisfy the <a href="http://www.w3.org/TR/WCAG21/#identify-input-purpose">WCAG 2.1 Success Criterion 1.3.5 Identify Input Purpose</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 1.3.5 Identify Input Purpose</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/identify-input-purpose.html">Understanding Identify Input Purpose</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#identify-input-purpose">How to Meet Identify Input Purpose</a></p>
<p>(Level AA)</p>
<p>The purpose of each input field collecting information about the user can be <a href="http://www.w3.org/TR/WCAG21/#dfn-programmatically-determinable">programmatically determined</a> when:</p>
<ul>
<li>The input field serves a purpose identified in the <a href="http://www.w3.org/TR/WCAG21/#input-purposes">Input Purposes for User Interface Components</a> section; and</li>
<li>The content is implemented using technologies with support for identifying the expected meaning for form input data.</li>
</ul>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fa0"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fa0" aria-hidden="true" data-number="10.1.4" />10.1.4 Distinguishable</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fa1"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fa1" aria-hidden="true" data-number="10.1.4.1" />10.1.4.1 Use of colour</label>
<div>
<p>Where ICT is a non-web document, it shall satisfy the <a href="http://www.w3.org/TR/WCAG21/#use-of-color">WCAG 2.1 Success Criterion 1.4.1 Use of Color</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 1.4.1 Use of Color.</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/use-of-color.html">Understanding Use of Color</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#use-of-color">How to Meet Use of Color</a></p>
<p>(Level A)</p>
<p>Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.</p>
<p>Note: This success criterion addresses color perception specifically. Other forms of perception are covered in <a href="http://www.w3.org/TR/WCAG21/#adaptable">Guideline 1.3</a> including programmatic access to color and other visual presentation coding.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fa2"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fa2" aria-hidden="true" data-number="10.1.4.2" />10.1.4.2 Audio control</label>
<div>
<p>Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.1.</p>
<p><strong>Table 10.1: Document success criterion: Audio control</strong></p>
<p>If any audio in a document plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a <a href="http://www.w3.org/TR/WCAG21/#dfn-mechanism">mechanism</a> is available to control audio volume independently from the overall system volume level.</p>
<p>NOTE 1: Since any part of a document that does not meet this success criterion can interfere with a user's ability to use the whole document, all content in the document (whether or not it is used to meet other success criteria) shall meet this success criterion.</p>
<p>NOTE 2: This success criterion is identical to the <a href="http://www.w3.org/TR/WCAG21/#audio-control">WCAG 2.1 Success Criterion 1.4.2 Audio Control</a>, replacing "on a Web page" with "in a document" "any content" with "any part of a document", "whole page" with "whole document", "on the Web page" with "in the document", removing "See Conformance Requirement 5: Non-Interference" and adding note 1.</p>
<p><strong>WCAG 2.1 Success Criterion 1.4.2 Audio Control</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/audio-control.html">Understanding Audio Control</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#audio-control">How to Meet Audio Control</a></p>
<p>(Level A)</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fa3"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fa3" aria-hidden="true" data-number="10.1.4.3" />10.1.4.3 Contrast (minimum)</label>
<div>
<p>Where ICT is a non-web document, it shall satisfy the <a href="http://www.w3.org/TR/WCAG21/#contrast-minimum">WCAG 2.1 Success Criterion 1.4.3 Contrast (Minimum)</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 1.4.3 Contrast (Minimum)</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/contrast-minimum.html">Understanding Contrast (Minimum)</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#contrast-minimum">How to Meet Contrast (Minimum)</a></p>
<p>(Level AA)</p>
<p>The visual presentation of <a href="http://www.w3.org/TR/WCAG21/#dfn-text">text</a> and <a href="http://www.w3.org/TR/WCAG21/#dfn-images-of-text">images of text</a> has a <a href="http://www.w3.org/TR/WCAG21/#dfn-contrast-ratio">contrast ratio</a> of at least 4.5:1, except for the following:</p>
<ul>
<li>Large Text: <a href="http://www.w3.org/TR/WCAG21/#dfn-large-scale">Large-scale</a> text and images of large-scale text have a contrast ratio of at least 3:1;</li>
<li>Incidental: Text or images of text that are part of an inactive <a href="http://www.w3.org/TR/WCAG21/#dfn-user-interface-components">user interface component</a>, that are <a href="http://www.w3.org/TR/WCAG21/#dfn-pure-decoration">pure decoration</a>, that are not visible to anyone, or that are part of a picture that contains significant other visual content, have no contrast requirement.</li>
<li>Logotypes: Text that is part of a logo or brand name has no contrast requirement.</li>
</ul>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fa4"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fa4" aria-hidden="true" data-number="10.1.4.4" />10.1.4.4 Resize text</label>
<div>
<p>Where ICT is a non-web document, it shall satisfy the <a href="http://www.w3.org/TR/WCAG21/#resize-text">WCAG 2.1 Success Criterion 1.4.4 Resize Text</a>.</p>
<p>NOTE 1: Content for which there are software players, viewers or editors with a 200 percent zoom feature would automatically meet this success criterion when used with such players, unless the content will not work with zoom.</p>
<p>NOTE 2: This success criterion is about the ability to allow users to enlarge the text on screen at least up to 200 % without needing to use assistive technologies. This means that the application provides some means for enlarging the text 200 % (zoom or otherwise) without loss of content or functionality or that the application works with the platform features that meet this requirement.</p>
<p><strong>WCAG 2.1 Success Criterion 1.4.4 Resize Text</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/resize-text.html">Understanding Resize text</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#resize-text">How to Meet Resize text</a></p>
<p>(Level AA)</p>
<p>Except for <a href="http://www.w3.org/TR/WCAG21/#dfn-captions">captions</a> and <a href="http://www.w3.org/TR/WCAG21/#dfn-images-of-text">images of text</a>, <a href="http://www.w3.org/TR/WCAG21/#dfn-text">text</a> can be resized without <a href="http://www.w3.org/TR/WCAG21/#dfn-assistive-technologies">assistive technology</a> up to 200 percent without loss of content or functionality.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fa5"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fa5" aria-hidden="true" data-number="10.1.4.5" />10.1.4.5 Images of text</label>
<div>
<p>Where ICT is a non-web document, it shall satisfy the <a href="http://www.w3.org/TR/WCAG21/#images-of-text">WCAG 2.1 Success Criterion 1.4.5 Images of Text</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 1.4.5 Images of Text</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/images-of-text.html">Understanding Images of Text</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#images-of-text">How to Meet Images of Text</a></p>
<p>(Level AA)</p>
<p>If the technologies being used can achieve the visual presentation, <a href="http://www.w3.org/TR/WCAG21/#dfn-text">text</a> is used to convey information rather than <a href="http://www.w3.org/TR/WCAG21/#dfn-images-of-text">images of text</a> except for the following:</p>
<ul>
<li>Customizable: The image of text can be <a href="http://www.w3.org/TR/WCAG21/#dfn-visually-customized">visually customized</a> to the user's requirements;</li>
<li>Essential: A particular presentation of text is <a href="http://www.w3.org/TR/WCAG21/#dfn-essential">essential</a> to the information being conveyed.</li>
</ul>
<p>Note: Logotypes (text that is part of a logo or brand name) are considered essential.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fa6"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fa6" aria-hidden="true" data-number="10.1.4.10" />10.1.4.10 Reflow</label>
<div>
<p>Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.2.</p>
<p><strong>Table 10.2: Document success criterion: Reflow</strong></p>
<p>Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions for:</p>
<ul>
<li>Vertical scrolling content at a width equivalent to 320 <a href="http://www.w3.org/TR/WCAG21/#dfn-css-pixels">CSS pixels</a>;</li>
<li>Horizontal scrolling content at a height equivalent to 256 <a href="http://www.w3.org/TR/WCAG21/#dfn-css-pixels">CSS pixels</a>.</li>
</ul>
<p>Except for parts of the content which require two-dimensional layout for usage or meaning.</p>
<p>NOTE 1: 320 CSS pixels is equivalent to a starting viewport width of 1280 CSS pixels wide at 400% zoom. For documents which are designed to scroll horizontally (e.g. with vertical text), the 256 CSS pixels is equivalent to a starting viewport height of 1024px at 400% zoom.</p>
<p>NOTE 2: Examples of content which require two-dimensional layout are images, maps, diagrams, video, games, presentations, data tables, and interfaces where it is necessary to keep toolbars in view while manipulating content.</p>
<p>NOTE 3: This success criterion is identical to the <a href="http://www.w3.org/TR/WCAG21/#reflow">WCAG 2.1 Success Criterion 1.4.10 Reflow</a> replacing the original WCAG 2.1 notes with notes 1 and 2, above.</p>
<p><strong>WCAG 2.1 Success Criterion 1.4.10 Reflow</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/reflow.html">Understanding Reflow</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#reflow">How to Meet Reflow</a></p>
<p>(Level AA)</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fa7"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fa7" aria-hidden="true" data-number="10.1.4.11" />10.1.4.11 Non-text contrast</label>
<div>
<p>Where ICT is a non-web document, it shall satisfy <a href="https://www.w3.org/TR/WCAG21/#non-text-contrast">WCAG 2.1 Success Criterion 1.4.11 Non-text Contrast</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 1.4.11 Non-text Contrast.</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/non-text-contrast.html">Understanding Non-text Contrast</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#non-text-contrast">How to Meet Non-text Contrast</a></p>
<p>(Level AA)</p>
<p>The visual <a href="http://www.w3.org/TR/WCAG21/#dfn-presentation">presentation</a> of the following have a <a href="http://www.w3.org/TR/WCAG21/#dfn-contrast-ratio">contrast ratio</a> of at least 3:1 against adjacent color(s):</p>
<ul>
<li>User Interface Components: Visual information required to identify <a href="http://www.w3.org/TR/WCAG21/#dfn-user-interface-components">user interface components</a> and <a href="http://www.w3.org/TR/WCAG21/#dfn-states">states</a>, except for inactive components or where the appearance of the component is determined by the user agent and not modified by the author;</li>
<li>Graphical Objects: Parts of graphics required to understand the content, except when a particular presentation of graphics is <a href="http://www.w3.org/TR/WCAG21/#dfn-essential">essential</a> to the information being conveyed.</li>
</ul>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fa8"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fa8" aria-hidden="true" data-number="10.1.4.12" />10.1.4.12 Text spacing</label>
<div>
<p>Where ICT is a non-web document that does not have a fixed size content layout area that is essential to the information being conveyed, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#text-spacing">WCAG 2.1 Success Criterion 1.4.12 Text spacing</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 1.4.12 Text spacing</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/text-spacing.html">Understanding Text Spacing</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#text-spacing">How to Meet Text Spacing</a></p>
<p>(Level AA)</p>
<p>In content implemented using markup languages that support the following <a href="http://www.w3.org/TR/WCAG21/#dfn-text">text</a><a href="http://www.w3.org/TR/WCAG21/#dfn-style-properties">style properties</a>, no loss of content or functionality occurs by setting all of the following and by changing no other style property:</p>
<ul>
<li>Line height (line spacing) to at least 1.5 times the font size;</li>
<li>Spacing following paragraphs to at least 2 times the font size;</li>
<li>Letter spacing (tracking) to at least 0.12 times the font size;</li>
<li>Word spacing to at least 0.16 times the font size.</li>
</ul>
<p>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.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fa9"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fa9" aria-hidden="true" data-number="10.1.4.13" />10.1.4.13 Content on hover or focus</label>
<div>
<p>Where ICT is a non-web document, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#content-on-hover-or-focus">WCAG 2.1 Success Criterion 1.4.13 Content on Hover or Focus</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 1.4.13 Content on Hover or Focus.</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/content-on-hover-or-focus.html">Understanding Content on Hover or Focus</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#content-on-hover-or-focus">How to Meet Content on Hover or Focus</a></p>
<p>(Level AA)</p>
<p>Where receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden, the following are true:</p>
<ul>
<li>Dismissable: A <a href="http://www.w3.org/TR/WCAG21/#dfn-mechanism">mechanism</a> is available to dismiss the additional content without moving pointer hover or keyboard focus, unless the additional content communicates an <a href="http://www.w3.org/TR/WCAG21/#dfn-input-error">input error</a> or does not obscure or replace other content;</li>
<li>Hoverable: If pointer hover can trigger the additional content, then the pointer can be moved over the additional content without the additional content disappearing;</li>
<li>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.</li>
</ul>
<p>Exception: The visual presentation of the additional content is controlled by the user agent and is not modified by the author.</p>
<p>Note: Examples of additional content controlled by the user agent include browser tooltips created through use of the HTML <a href="http://www.w3.org/TR/html/dom.html#the-title-attribute">title attribute</a>.</p>
<p>Note: Custom tooltips, sub-menus, and other nonmodal popups that display on hover and focus are examples of additional content covered by this criterion.</p>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645faa"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645faa" aria-hidden="true" data-number="10.2" />10.2 Operable</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fab"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fab" aria-hidden="true" data-number="10.2.1" />10.2.1 Keyboard accessible</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fac"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fac" aria-hidden="true" data-number="10.2.1.1" />10.2.1.1 Keyboard</label>
<div>
<p>Where ICT is a non-web document, it shall satisfy the <a href="http://www.w3.org/TR/WCAG21/#keyboard">WCAG 2.1 Success Criterion 2.1.1 Keyboard</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 2.1.1 Keyboard</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/keyboard.html">Understanding Keyboard</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#keyboard">How to Meet Keyboard</a></p>
<p>(Level A)</p>
<p>All <a href="http://www.w3.org/TR/WCAG21/#dfn-functionality">functionality</a> of the content is operable through a <a href="http://www.w3.org/TR/WCAG21/#dfn-keyboard-interface">keyboard interface</a> 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.</p>
<p>Note: 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.</p>
<p>Note: This does not forbid and should not discourage providing mouse input or other input methods in addition to keyboard operation.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fad"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fad" aria-hidden="true" data-number="10.2.1.2" />10.2.1.2 No keyboard trap</label>
<div>
<p>Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.3.</p>
<p><strong>Table 10.3: Document success criterion: No keyboard trap</strong></p>
<p>If keyboard focus can be moved to a component of the document using a <a href="http://www.w3.org/TR/WCAG21/#dfn-keyboard-interface">keyboard interface</a>, 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.</p>
<p>NOTE 1: Since any part of a document that does not meet this success criterion can interfere with a user's ability to use the whole document, it is necessary for all content in the document (whether or not it is used to meet other success criteria) to meet this success criterion.</p>
<p>NOTE 2: Standard exit methods may vary by platform. For example, on many desktop platforms, the Escape key is a standard method for exiting.</p>
<p>NOTE 3: This success criterion is identical to the <a href="http://www.w3.org/TR/WCAG21/#no-keyboard-trap">WCAG 2.1 Success Criterion 2.1.2 No Keyboard Trap</a> replacing "page" and "Web page" with "document", removing "See Conformance Requirement 5: Non-Interference" and with the addition of note 2 above and with note 1 above re-drafted to avoid the use of the word "must".</p>
<p><strong>WCAG 2.1 Success Criterion 2.1.2 No Keyboard Trap</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/no-keyboard-trap.html">Understanding No Keyboard Trap</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#no-keyboard-trap">How to Meet No Keyboard Trap</a></p>
<p>(Level A)</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fae"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fae" aria-hidden="true" data-number="10.2.1.4" />10.2.1.4 Character key shortcuts</label>
<div>
<p>Where ICT is a non-web document, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#character-key-shortcuts">WCAG 2.1 Success Criterion 2.1.4 Character Key Shortcuts</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 2.1.4 Character Key Shortcuts</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/character-key-shortcuts.html">Understanding Character Key Shortcuts</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#character-key-shortcuts">How to Meet Character Key Shortcuts</a></p>
<p>(Level A)</p>
<p>If a <a href="http://www.w3.org/TR/WCAG21/#dfn-keyboard-shortcuts">keyboard shortcut</a> 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:</p>
<ul>
<li>Turn off: A <a href="http://www.w3.org/TR/WCAG21/#dfn-mechanism">mechanism</a> is available to turn the shortcut off;</li>
<li>Remap: A mechanism is available to remap the shortcut to use one or more non-printable keyboard characters (e.g. Ctrl, Alt, etc.);</li>
<li>Active only on focus: The keyboard shortcut for a <a href="http://www.w3.org/TR/WCAG21/#dfn-user-interface-components">user interface component</a> is only active when that component has focus.</li>
</ul>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645faf"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645faf" aria-hidden="true" data-number="10.2.2" />10.2.2 Enough time</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fb0"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fb0" aria-hidden="true" data-number="10.2.2.1" />10.2.2.1 Timing adjustable</label>
<div>
<p>Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.4.</p>
<p><strong>Table 10.4: Document success criterion: Timing adjustable</strong></p>
<p>For each time limit that is set by the document, at least one of the following is true:</p>
<ul>
<li>Turn off: The user is allowed to turn off the time limit before encountering it; or</li>
<li>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</li>
<li>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</li>
<li>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</li>
<li>Essential Exception: The time limit is <a href="http://www.w3.org/TR/WCAG21/#dfn-essential">essential</a> and extending it would invalidate the activity; or</li>
<li>20 Hour Exception: The time limit is longer than 20 hours.</li>
</ul>
<p>NOTE 1: 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 <a href="http://www.w3.org/TR/WCAG21/#on-focus">WCAG 2.1 Success Criterion 3.2.1</a>, which puts limits on changes of content or context as a result of user action.</p>
<p>NOTE 2: This success criterion is identical to the <a href="http://www.w3.org/TR/WCAG21/#timing-adjustable">WCAG 2.1 Success Criterion 2.2.1 Timing Adjustable</a> replacing "the content" with "documents" and with the words "WCAG 2.1" added before the word "Success Criterion" in note 1 above.</p>
<p><strong>WCAG 2.1 Success Criterion 2.2.1 Timing Adjustable</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/timing-adjustable.html">Understanding Timing Adjustable</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#timing-adjustable">How to Meet Timing Adjustable</a></p>
<p>(Level A)</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fb1"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fb1" aria-hidden="true" data-number="10.2.2.2" />10.2.2.2 Pause, stop, hide</label>
<div>
<p>Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.5.</p>
<p><strong>Table 10.5: Document success criterion: Pause, stop, hide</strong></p>
<p>For moving, <a href="http://www.w3.org/TR/WCAG21/#dfn-blinking">blinking</a>, scrolling, or auto-updating information, all of the following are true:</p>
<ul>
<li>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 <a href="http://www.w3.org/TR/WCAG21/#dfn-pause">pause</a>, stop, or hide it unless the movement, blinking, or scrolling is part of an activity where it is <a href="http://www.w3.org/TR/WCAG21/#dfn-essential">essential</a>; and</li>
<li>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.</li>
</ul>
<p>NOTE 1: For requirements related to flickering or flashing content, refer to <a href="https://www.w3.org/TR/WCAG21/#seizures-and-physical-reactions">WCAG 2.1 Guideline 2.3</a>.</p>
<p>NOTE 2: Since any part of a document that does not meet this success criterion can interfere with a user's ability to use the whole document, it is necessary for all content in the document (whether it is used to meet other success criteria or not) to meet this success criterion.</p>
<p>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.</p>
<p>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.</p>
<p>NOTE 5: This success criterion is identical to the <a href="http://www.w3.org/TR/WCAG21/#pause-stop-hide">WCAG 2.1 Success Criterion 2.2.2 Pause, Stop, Hide</a> replacing "page" and "Web page" with "document", removing "See Conformance Requirement 5: Non-Interference" in note 2 of the success criterion, with the words "WCAG 2.1" added before the word "Guideline" in note 1 above and with note 2 above re-drafted to avoid the use of the word "must".</p>
<p><strong>Guideline 2.3 Seizures and Physical Reactions</strong></p>
<p><strong>Do not design content in a way that is known to cause seizures or physical reactions.</strong></p>
<p><strong>WCAG 2.1 Success Criterion 2.2.2 Pause, Stop, Hide</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/pause-stop-hide.html">Understanding Pause, Stop, Hide</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#pause-stop-hide">How to Meet Pause, Stop, Hide</a></p>
<p>(Level A)</p>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fb2"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fb2" aria-hidden="true" data-number="10.2.3" />10.2.3 Seizures and physical reactions</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fb3"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fb3" aria-hidden="true" data-number="10.2.3.1" />10.2.3.1 Three flashes or below threshold</label>
<div>
<p>Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.6.</p>
<p><strong>Table 10.6: Document success criterion: Three flashes or below threshold</strong></p>
<p>Documents do not contain anything that flashes more than three times in any one second period, or the <a href="http://www.w3.org/TR/WCAG21/#dfn-flashes">flash</a> is below the <a href="http://www.w3.org/TR/WCAG21/#dfn-general-flash-and-red-flash-thresholds">general flash and red flash thresholds</a>.</p>
<p>NOTE 1: Since any part of a document that does not meet this success criterion can interfere with a user's ability to use the whole document, it is necessary for all content in the document (whether it is used to meet other success criteria or not) to meet this success criterion.</p>
<p>NOTE 2: This success criterion is identical to the <a href="http://www.w3.org/TR/WCAG21/#three-flashes-or-below-threshold">WCAG 2.1 Success Criterion 2.3.1 Three Flashes or Below Threshold</a> replacing "Web pages" with "documents", "the whole page" with "the whole document", "the Web page" with "the document" and removing "See Conformance Requirement 5: Non-Interference" and with note 1 above re-drafted to avoid the use of the word "must".</p>
<p><strong>WCAG 2.1 Success Criterion 2.3.1 Three Flashes or Below Threshold</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/three-flashes-or-below-threshold.html">Understanding Three Flashes or Below Threshold</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#three-flashes-or-below-threshold">How to Meet Three Flashes or Below Threshold</a></p>
<p>(Level A)</p>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fb4"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fb4" aria-hidden="true" data-number="10.2.4" />10.2.4 Navigable</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fb5"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fb5" aria-hidden="true" data-number="10.2.4.2" />10.2.4.2 Document titled</label>
<div>
<p>Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.7.</p>
<p><strong>Table 10.7: Document success criterion: Document titled</strong></p>
<p>Documents have titles that describe topic or purpose.</p>
<p>NOTE 1: The name of a document (e.g. document, media file) is a sufficient title if it describes the topic or purpose.</p>
<p>NOTE 2: This success criterion is identical to the <a href="http://www.w3.org/TR/WCAG21/#page-titled">WCAG 2.1 Success Criterion 2.4.2 Page Titled</a> replacing "Web pages" with "documents" and with the addition of note 1 above.</p>
<p><strong>WCAG 2.1 Success Criterion 2.4.2 Page Titled</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/page-titled.html">Understanding Page Titled</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#page-titled">How to Meet Page Titled</a></p>
<p>(Level A)</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fb6"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fb6" aria-hidden="true" data-number="10.2.4.3" />10.2.4.3 Focus Order</label>
<div>
<p>Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.8.</p>
<p><strong>Table 10.8: Document success criterion: Focus order</strong></p>
<p>If a document can be <a href="http://www.w3.org/TR/WCAG21/#dfn-navigated-sequentially">navigated sequentially</a> and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability.</p>
<p>NOTE: This success criterion is identical to the <a href="http://www.w3.org/TR/WCAG21/#focus-order">WCAG 2.1 Success Criterion 2.4.3 Focus Order</a> replacing "Web page" with "document".</p>
<p><strong>WCAG 2.1 Success Criterion 2.4.3 Focus Order</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/focus-order.html">Understanding Focus Order</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#focus-order">How to Meet Focus Order</a></p>
<p>(Level A)</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fb7"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fb7" aria-hidden="true" data-number="10.2.4.4" />10.2.4.4 Link purpose (in context)</label>
<div>
<p>Where ICT is a non-web document, it shall satisfy the <a href="http://www.w3.org/TR/WCAG21/#link-purpose-in-context">WCAG 2.1 Success Criterion 2.4.4 Link Purpose (In Context)</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 2.4.4 Link Purpose (In Context)</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/link-purpose-in-context.html">Understanding Link Purpose (In Context</a>)</p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#link-purpose-in-context">How to Meet Link Purpose (In Context)</a></p>
<p>(Level A)</p>
<p>The <a href="http://www.w3.org/TR/WCAG21/#dfn-purpose-of-each-link">purpose of each link</a> can be determined from the link text alone or from the link text together with its <a href="http://www.w3.org/TR/WCAG21/#dfn-programmatically-determined-link-context">programmatically determined link context</a>, except where the purpose of the link would be <a href="http://www.w3.org/TR/WCAG21/#dfn-ambiguous-to-users-in-general">ambiguous to users in general</a>.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fb8"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fb8" aria-hidden="true" data-number="10.2.4.6" />10.2.4.6 Headings and labels</label>
<div>
<p>Where ICT is a non-web document, it shall satisfy the <a href="http://www.w3.org/TR/WCAG21/#headings-and-labels">WCAG 2.1 Success Criterion 2.4.6 Headings and Labels</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 2.4.6 Headings and Labels</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/headings-and-labels.html">Understanding Headings and Labels</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#headings-and-labels">How to Meet Headings and Labels</a></p>
<p>(Level AA)</p>
<p>Headings and <a href="http://www.w3.org/TR/WCAG21/#dfn-labels">labels</a> describe topic or purpose</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fb9"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fb9" aria-hidden="true" data-number="10.2.4.7" />10.2.4.7 Focus visible</label>
<div>
<p>Where ICT is a non-web document, it shall satisfy the <a href="http://www.w3.org/TR/WCAG21/#focus-visible">WCAG 2.1 Success Criterion 2.4.7 Focus Visible</a></p>
<p><strong>WCAG 2.1 Success Criterion 2.4.7 Focus Visible</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/focus-visible.html">Understanding Focus Visible</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#focus-visible">How to Meet Focus Visible</a></p>
<p>(Level AA)</p>
<p>Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible.</p>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fba"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fba" aria-hidden="true" data-number="10.2.5" />10.2.5 Input modalities</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fbb"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fbb" aria-hidden="true" data-number="10.2.5.1" />10.2.5.1 Pointer gestures</label>
<div>
<p>Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.9.</p>
<p><strong>Table 10.9: Document success criterion: Pointer gestures</strong></p>
<p>All <a href="http://www.w3.org/TR/WCAG21/#dfn-functionality">functionality</a> that uses multipoint or path-based gestures for operation can be operated with a <a href="http://www.w3.org/TR/WCAG21/#dfn-single-pointer">single pointer</a> without a path-based gesture, unless a multipoint or path-based gesture is <a href="http://www.w3.org/TR/WCAG21/#dfn-essential">essential</a>.</p>
<p>NOTE 1: This requirement applies to documents that interpret pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive technology).</p>
<p>NOTE 2: This success criterion is identical to the <a href="http://www.w3.org/TR/WCAG21/#pointer-gestures">WCAG 2.1 Success Criterion 2.5.1 Pointer Gestures</a> replacing the original WCAG 2.1 note with note 1 above.</p>
<p><strong>WCAG 2.1 Success Criterion 2.5.1 Pointer Gestures</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/pointer-gestures.html">Understanding Pointer Gestures</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#pointer-gestures">How to Meet Pointer Gestures</a></p>
<p>(Level A)</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fbc"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fbc" aria-hidden="true" data-number="10.2.5.2" />10.2.5.2 Pointer cancellation</label>
<div>
<p>Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.10.</p>
<p><strong>Table 10.10: Document success criterion: Pointer cancellation</strong></p>
<p>For <a href="http://www.w3.org/TR/WCAG21/#dfn-functionality">functionality</a> that can be operated using a <a href="http://www.w3.org/TR/WCAG21/#dfn-single-pointer">single pointer</a>, at least one of the following is true:</p>
<ul>
<li>No Down-Event: The <a href="http://www.w3.org/TR/WCAG21/#dfn-down-event">down-event</a> of the pointer is not used to execute any part of the function;</li>
<li>Abort or Undo: Completion of the function is on the <a href="http://www.w3.org/TR/WCAG21/#dfn-up-event">up-event,</a> and a <a href="http://www.w3.org/TR/WCAG21/#dfn-mechanism">mechanism</a> is available to abort the function before completion or to undo the function after completion;</li>
<li>Up Reversal: The up-event reverses any outcome of the preceding down-event;</li>
<li>Essential: Completing the function on the down-event is <a href="http://www.w3.org/TR/WCAG21/#dfn-essential">essential</a>.</li>
</ul>
<p>NOTE 1: Functions that emulate a keyboard or numeric keypad key press are considered essential.</p>
<p>NOTE 2: This requirement applies to a document that interprets pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive technology).</p>
<p>NOTE 3: This success criterion is identical to the <a href="http://www.w3.org/TR/WCAG21/#pointer-cancellation">WCAG 2.1 Success Criterion 2.5.2 Pointer Cancellation</a> replacing the original WCAG 2.1 note with notes 1 and 2 above.</p>
<p><strong>WCAG 2.1 Success Criterion 2.5.2 Pointer Cancellation</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/pointer-cancellation.html">Understanding Pointer Cancellation</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#pointer-cancellation">How to Meet Pointer Cancellation</a></p>
<p>(Level A)</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fbd"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fbd" aria-hidden="true" data-number="10.2.5.3" />10.2.5.3 Label in name</label>
<div>
<p>Where ICT is a non-web document, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#label-in-name">WCAG 2.1 Success Criterion 2.5.3 Label in Name</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 2.5.3 Label in Name</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/label-in-name.html">Understanding Label in Name</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#label-in-name">How to Meet Label in Name</a></p>
<p>(Level A)</p>
<p>For <a href="http://www.w3.org/TR/WCAG21/#dfn-user-interface-components">user interface components</a> with <a href="http://www.w3.org/TR/WCAG21/#dfn-labels">labels</a> that include <a href="http://www.w3.org/TR/WCAG21/#dfn-text">text</a> or <a href="http://www.w3.org/TR/WCAG21/#dfn-images-of-text">images of text,</a> the <a href="http://www.w3.org/TR/WCAG21/#dfn-name">name</a> contains the text that is presented visually.</p>
<p>Note: A best practice is to have the text of the label at the start of the name.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fbe"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fbe" aria-hidden="true" data-number="10.2.5.4" />10.2.5.4 Motion actuation</label>
<div>
<p>Where ICT is a non-web document, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#motion-actuation">WCAG 2.1 Success Criterion 2.5.4 Motion Actuation</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 2.5.4 Motion Actuation</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/motion-actuation.html">Understanding Motion Actuation</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#motion-actuation">How to Meet Motion Actuation</a></p>
<p>(Level A)</p>
<p><a href="http://www.w3.org/TR/WCAG21/#dfn-functionality">Functionality</a> that can be operated by device motion or user motion can also be operated by <a href="http://www.w3.org/TR/WCAG21/#dfn-user-interface-components">user interface components</a> and responding to the motion can be disabled to prevent accidental actuation, except when:</p>
<ul>
<li>Supported Interface: The motion is used to operate functionality through an <a href="http://www.w3.org/TR/WCAG21/#dfn-accessibility-supported">accessibility supported</a> interface;</li>
<li>Essential: The motion is <a href="http://www.w3.org/TR/WCAG21/#dfn-essential">essential</a> for the function and doing so would invalidate the activity.</li>
</ul>
</div>
</div>
</li>
</ul>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fbf"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fbf" aria-hidden="true" data-number="10.3" />10.3 Understandable</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fc0"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fc0" aria-hidden="true" data-number="10.3.1" />10.3.1 Readable</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fc1"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fc1" aria-hidden="true" data-number="10.3.1.1" />10.3.1.1 Language of page</label>
<div>
<p>Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.11.</p>
<p><strong>Table 10.11: Document success criterion: Language of page</strong></p>
<p>The default <a href="http://www.w3.org/TR/WCAG21/#dfn-human-language-s">human language</a> of each document can be <a href="http://www.w3.org/TR/WCAG21/#dfn-programmatically-determinable">programmatically determined</a>.</p>
<p>NOTE: This success criterion is identical to the <a href="https://www.w3.org/TR/WCAG21/#language-of-page">WCAG 2.1 Success Criterion 3.1.1 Language of Page</a> replacing "web page" with "document".</p>
<p><strong>WCAG 2.1 Success Criterion 3.1.1 Language of Page</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/language-of-page.html">Understanding Language of Page</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#language-of-page">How to Meet Language of Page</a></p>
<p>(Level A)</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fc2"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fc2" aria-hidden="true" data-number="10.3.1.2" />10.3.1.2 Language of parts</label>
<div>
<p>Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.12.</p>
<p><strong>Table 10.12: Document success criterion: Language of parts</strong></p>
<p>The <a href="http://www.w3.org/TR/WCAG21/#dfn-human-language-s">human language</a> of each passage or phrase in the document can be <a href="http://www.w3.org/TR/WCAG21/#dfn-programmatically-determinable">programmatically determined</a> 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.</p>
<p>NOTE 1: There are some document technologies where there is no assistive technology supported method for marking the language for the different passages or phrases in the document, and it would not be possible to meet this success criterion with those technologies.</p>
<p>NOTE 2: Inheritance is one common method. For example a document provides the language that it is using and it can be assumed that all of the text or user interface elements within that document will be using the same language unless it is indicated.</p>
<p>NOTE 3: This success criterion is identical to the <a href="http://www.w3.org/TR/WCAG21/#language-of-parts">WCAG 2.1 Success Criterion 3.1.2 Language of Parts</a> replacing "content" with "document" and with the addition of notes 1 and 2 above.</p>
<p><strong>WCAG 2.1 Success Criterion 3.1.2 Language of Parts</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/language-of-parts.html">Understanding Language of Parts</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#language-of-parts">How to Meet Language of Parts</a></p>
<p>(Level AA)</p>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fc3"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fc3" aria-hidden="true" data-number="10.3.2" />10.3.2 Predictable</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fc4"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fc4" aria-hidden="true" data-number="10.3.2.1" />10.3.2.1 On focus</label>
<div>
<p>Where ICT is a non-web document, it shall satisfy the <a href="http://www.w3.org/TR/WCAG21/#on-focus">WCAG 2.1 Success Criterion 3.2.1 On Focus</a>.</p>
<p>NOTE: Some compound documents and their user agents are designed to provide significantly different viewing and editing functionality depending upon what portion of the compound document is being interacted with (e.g. a presentation that contains an embedded spreadsheet, where the menus and toolbars of the user agent change depending upon whether the user is interacting with the presentation content, or the embedded spreadsheet content). If the user uses a mechanism other than putting focus on that portion of the compound document with which they mean to interact (e.g. by a menu choice or special keyboard gesture), any resulting change of context would not be subject to this success criterion because it was not caused by a change of focus.</p>
<p><strong>WCAG 2.1 Success Criterion 3.2.1 On Focus</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/on-focus.html">Understanding On Focus</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#on-focus">How to Meet On Focus</a></p>
<p>(Level A)</p>
<p>When any <a href="http://www.w3.org/TR/WCAG21/#dfn-user-interface-components">user interface component</a> receives focus, it does not initiate a <a href="http://www.w3.org/TR/WCAG21/#dfn-change-of-context">change of contex</a>t.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fc5"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fc5" aria-hidden="true" data-number="10.3.2.2" />10.3.2.2 On input</label>
<div>
<p>Where ICT is a non-web document, it shall satisfy the <a href="http://www.w3.org/TR/WCAG21/#on-input">WCAG 2.1 Success Criterion 3.2.2 On Input</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 3.2.2 On Input</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/on-input.html">Understanding On Input</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#on-input">How to Meet On Input</a></p>
<p>(Level A)</p>
<p>Changing the setting of any <a href="http://www.w3.org/TR/WCAG21/#dfn-user-interface-components">user interface component</a> does not automatically cause a <a href="http://www.w3.org/TR/WCAG21/#dfn-change-of-context">change of context</a> unless the user has been advised of the behavior before using the component.</p>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fc6"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fc6" aria-hidden="true" data-number="10.3.3" />10.3.3 Input assistance</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fc7"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fc7" aria-hidden="true" data-number="10.3.3.1" />10.3.3.1 Error identification</label>
<div>
<p>Where ICT is a non-web document, it shall satisfy the <a href="http://www.w3.org/TR/WCAG21/#error-identification">WCAG 2.1 Success Criterion 3.3.1 Error Identification</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 3.3.1 Error Identification</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/error-identification.html">Understanding Error Identification</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#error-identification">How to Meet Error Identification</a></p>
<p>(Level A)</p>
<p>If an <a href="http://www.w3.org/TR/WCAG21/#dfn-input-error">input error</a> is automatically detected, the item that is in error is identified and the error is described to the user in text.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fc8"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fc8" aria-hidden="true" data-number="10.3.3.2" />10.3.3.2 Labels or instructions</label>
<div>
<p>Where ICT is a non-web document, it shall satisfy the <a href="http://www.w3.org/TR/WCAG21/#labels-or-instructions">WCAG 2.1 Success Criterion 3.3.2 Labels or Instructions</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 3.3.2 Labels or Instructions</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/labels-or-instructions.html">Understanding Labels or Instructions</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#labels-or-instructions">How to Meet Labels or Instructions</a></p>
<p>(Level A)</p>
<p><a href="http://www.w3.org/TR/WCAG21/#dfn-labels">Labels</a> or instructions are provided when content requires user input.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fc9"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fc9" aria-hidden="true" data-number="10.3.3.3" />10.3.3.3 Error suggestion</label>
<div>
<p>Where ICT is a non-web document, it shall satisfy the <a href="http://www.w3.org/TR/WCAG21/#error-suggestion">WCAG 2.1 Success Criterion 3.3.3 Error Suggestion</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 3.3.3 Error Suggestion</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/error-suggestion.html">Understanding Error Suggestion</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#error-suggestion">How to Meet Error Suggestion</a></p>
<p>(Level AA)</p>
<p>If an <a href="http://www.w3.org/TR/WCAG21/#dfn-input-error">input error</a> 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.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fca"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fca" aria-hidden="true" data-number="10.3.3.4" />10.3.3.4 Error prevention (legal, financial, data)</label>
<div>
<p>Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.13.</p>
<p><strong>Table 10.13: Document success criterion: Error prevention (legal, financial, data)</strong></p>
<p>For documents that cause <a href="http://www.w3.org/TR/WCAG21/#dfn-legal-commitments">legal commitments</a> or financial transactions for the user to occur, that modify or delete <a href="http://www.w3.org/TR/WCAG21/#dfn-user-controllable">user-controllable</a> data in data storage systems, or that submit user test responses, at least one of the following is true:</p>
<ol>
<li>Reversible: Submissions are reversible.</li>
<li>Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them.</li>
<li>Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.</li>
</ol>
<p>NOTE: This success criterion is identical to the <a href="http://www.w3.org/TR/WCAG21/#error-prevention-legal-financial-data">WCAG 2.1 Success Criterion 3.3.4 Error Prevention (Legal, Financial, Data)</a> replacing "web pages" with "documents".</p>
<p><strong>WCAG 2.1 Success Criterion 3.3.4 Error Prevention (Legal, Financial, Data)</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/error-prevention-legal-financial-data.html">Understanding Error Prevention (Legal, Financial, Data)</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#error-prevention-legal-financial-data">How to Meet Error Prevention (Legal, Financial, Data)</a></p>
<p>(Level AA)</p>
</div>
</div>
</li>
</ul>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fcb"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fcb" aria-hidden="true" data-number="10.4" />10.4 Robust</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fcc"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fcc" aria-hidden="true" data-number="10.4.1" />10.4.1 Compatible</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fcd"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fcd" aria-hidden="true" data-number="10.4.1.1" />10.4.1.1 Parsing</label>
<div>
<p>Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.14.</p>
<p><strong>Table 10.14: Document success criterion: Parsing</strong></p>
<p>For documents that use markup languages, in such a way that the markup is separately exposed and available to assistive technologies and accessibility features of software or to a user-selectable user agent, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features.</p>
<p>NOTE 1: Start and end tags that are missing a critical character in their formation, such as a closing angle bracket or a mismatched attribute value quotation mark are not complete.</p>
<p>NOTE 2: Markup is not always available to assistive technology or to user selectable user agents such as browsers. In such cases, conformance to this provision would have no impact on accessibility as it can for web content where it is exposed.</p>
<p>NOTE 3: Examples of markup that is separately exposed and available to assistive technologies and to user agents include but are not limited to: documents encoded in HTML, ODF, and OOXML. In these examples, the markup can be parsed entirely in two ways: (a) by assistive technologies which may directly open the document, (b) by assistive technologies using DOM APIs of user agents for these document formats.</p>
<p>NOTE 4: This success criterion is identical to <a href="http://www.w3.org/TR/WCAG21/#parsing">the WCAG 2.1 Success Criterion 4.1.1 Parsing</a> replacing "In content implemented using markup languages" with "For documents that use markup languages, in such a way that the markup is separately exposed and available to assistive technologies and accessibility features of software or to a user-selectable user agent" with the addition of notes 2 and 3 above.</p>
<p><strong>WCAG 2.1 Success Criterion 4.1.1 Parsing</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/parsing.html">Understanding Parsing</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#parsing">How to Meet Parsing</a></p>
<p>(Level A)</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fce"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fce" aria-hidden="true" data-number="10.4.1.2" />10.4.1.2 Name, role, value</label>
<div>
<p>Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.15.</p>
<p><strong>Table 10.15: Document success criterion: Name, role, value</strong></p>
<p>For all <a href="http://www.w3.org/TR/WCAG21/#dfn-user-interface-components">user interface components</a> (including but not limited to: form elements, links and components generated by scripts), the <a href="http://www.w3.org/TR/WCAG21/#dfn-name">name</a> and <a href="http://www.w3.org/TR/WCAG21/#dfn-role">role</a> can be <a href="http://www.w3.org/TR/WCAG21/#dfn-programmatically-determinable">programmatically determined</a>; states, properties, and values that can be set by the user can be <a href="http://www.w3.org/TR/WCAG21/#dfn-programmatically-set">programmatically set;</a> and notification of changes to these items is available to <a href="http://www.w3.org/TR/WCAG21/#dfn-user-agents">user agents</a>, including <a href="http://www.w3.org/TR/WCAG21/#dfn-assistive-technologies">assistive technologies</a>.</p>
<p>NOTE 1: This success criterion is primarily for software developers who develop or use custom user interface components. Standard user interface components on most accessibility-supported platforms already meet this success criterion when used according to specification.</p>
<p>NOTE 2: For document formats that support interoperability with assistive technology, standard user interface components often meet this success criterion when used according to the general design and accessibility guidance for the document format.</p>
<p>NOTE 3: This success criterion is identical to the <a href="http://www.w3.org/TR/WCAG21/#name-role-value">WCAG 2.1 Success Criterion 4.1.2 Name, Role, Value</a> replacing the original WCAG 2.1 note with note 1 and with the addition of note 2 above.</p>
<p><strong>WCAG 2.1 Success Criterion 4.1.2 Name, Role, Value</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/name-role-value.html">Understanding Name, Role, Value</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#name-role-value">How to Meet Name, Role, Value</a></p>
<p>(Level A)</p>
</div>
</div>
</li>
</ul>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fcf"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fcf" aria-hidden="true" data-number="10.5" />10.5 Caption positioning</label>
<div>
<p>Where ICT is a non-web document that contains synchronized media with captions, the captions should not obscure relevant information in the synchronized media.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fd0"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fd0" aria-hidden="true" data-number="10.6" />10.6 Audio description timing</label>
<div>
<p>Where ICT is a non-web document that contains synchronized media with audio description, the audio description should not interfere with relevant audio information in the synchronized media.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fd1"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fd1" aria-hidden="true" data-number="11" />11 Software</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fd2"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fd2" aria-hidden="true" data-number="11.0" />11.0 General (informative)</label>
<div>
<p>This clause provides requirements for:</p>
<ul>
<li>platform software;</li>
<li>software that provides a user interface including content that is in the software;</li>
<li>authoring tools;</li>
<li>software that operates as assistive technology.</li>
</ul>
<p>NOTE 1: User agents are examples of software that provide a user interface.</p>
<p>NOTE 2: The requirements for Web content, including software that is Web content, can be found in clause 9.</p>
<p>NOTE 3: The requirements for documents, that may be presented by user agents, can be found in clause 10.</p>
<p>NOTE 4: Although the accessibility of command line interfaces is not dealt with in the present document, accessibility may be achieved by context specific requirements, some of which may be found in clauses 5 or 11.</p>
<p>Requirements in clauses 11.1 to 11.5 apply to software:</p>
<ul>
<li>that is not a web page;</li>
<li>not embedded in web pages nor used in the rendering or functioning of the page.</li>
</ul>
<p>Clause 9 provides requirements for software that is in web pages or that is embedded in web pages and that is used in the rendering or that is intended to be rendered together with the web page in which it is embedded.</p>
<p>Some requirements in clauses 11.1 to 11.5 have different versions for open or closed functionality. In those cases, the corresponding clause will be divided into two subclauses.</p>
<p>The success criteria set out in clauses 11.1 to 11.5 are intended to harmonize with the W3C Working Group Note [i.26] produced by the W3C's <a href="http://www.w3.org/WAI/GL/WCAG2ICT-TF/">WCAG2ICT Task Force</a>.</p>
<p>NOTE 5: Software that provides a user interface includes its own content. Some examples of content in software include: the controls and text displayed in a menu bar of a graphical user interface application, images that appear in a toolbar, prompts spoken in an auditory user interface, other user interaction controls, and other text, graphics or material that is not loaded from outside the software.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fd3"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fd3" aria-hidden="true" data-number="11.1" />11.1 Perceivable</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fd4"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fd4" aria-hidden="true" data-number="11.1.1" />11.1.1 Text alternatives</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fd5"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fd5" aria-hidden="true" data-number="11.1.1.1" />11.1.1.1 Non-text content</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fd6"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fd6" aria-hidden="true" data-number="11.1.1.1.1" />11.1.1.1.1 Non-text content (open functionality)</label>
<div>
<p>Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#non-text-content">WCAG 2.1 Success Criterion 1.1.1 Non-text Content</a>.</p>
<p>NOTE: CAPTCHAs do not currently appear outside of the Web. However, if they do appear, this guidance is accurate.</p>
<p><strong>WCAG 2.1 Success Criterion 1.1.1 Non-text Content</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/non-text-content.html">Understanding Non-text Content</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#non-text-content">How to Meet Non-text Content</a></p>
<p>(Level A)</p>
<p>All <a href="http://www.w3.org/TR/WCAG21/#dfn-non-text-content">non-text content</a> that is presented to the user has a <a href="http://www.w3.org/TR/WCAG21/#dfn-text-alternative">text alternative</a> that serves the equivalent purpose, except for the situations listed below.</p>
<ul>
<li>Controls, Input: If non-text content is a control or accepts user input, then it has a <a href="http://www.w3.org/TR/WCAG21/#dfn-name">name</a> that describes its purpose. (Refer to <a href="http://www.w3.org/TR/WCAG21/#name-role-value">Success Criterion 4.1.2</a> for additional requirements for controls and content that accepts user input.)</li>
<li>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 <a href="http://www.w3.org/TR/WCAG21/#time-based-media">Guideline 1.2</a> for additional requirements for media.)</li>
<li>Test: If non-text content is a test or exercise that would be invalid if presented in <a href="http://www.w3.org/TR/WCAG21/#dfn-text">text</a>, then text alternatives at least provide descriptive identification of the non-text content.</li>
<li>Sensory: If non-text content is primarily intended to create a <a href="http://www.w3.org/TR/WCAG21/#dfn-specific-sensory-experience">specific sensory experience,</a> then text alternatives at least provide descriptive identification of the non-text content.</li>
<li><a href="http://www.w3.org/TR/WCAG21/#dfn-captcha">CAPTCHA</a>: 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.</li>
<li>Decoration, Formatting, Invisible: If non-text content is <a href="http://www.w3.org/TR/WCAG21/#dfn-pure-decoration">pure decoration,</a> 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 <a href="http://www.w3.org/TR/WCAG21/#dfn-assistive-technologies">assistive technology</a>.</li>
</ul>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fd7"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fd7" aria-hidden="true" data-number="11.1.1.1.2" />11.1.1.1.2 Non-text content (closed functionality)</label>
<div>
<p>Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading, it shall meet requirement 5.1.3.6 (Speech output for non-text content).</p>
</div>
</div>
</li>
</ul>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fd8"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fd8" aria-hidden="true" data-number="11.1.2" />11.1.2 Time-based media</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fd9"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fd9" aria-hidden="true" data-number="11.1.2.1" />11.1.2.1 Audio-only and video-only (prerecorded)</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fda"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fda" aria-hidden="true" data-number="11.1.2.1.1" />11.1.2.1.1 Audio-only and video-only (prerecorded - open functionality)</label>
<div>
<p>Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading and where pre-recorded auditory information is not needed to enable the use of closed functions of ICT, it shall satisfy the <a href="http://www.w3.org/TR/WCAG21/#audio-only-and-video-only-prerecorded">WCAG 2.1 Success Criterion 1.2.1 Audio-only and Video-only (Prerecorded)</a>.</p>
<p>NOTE: The alternative can be provided directly in the software - or provided in an alternate version that meets the success criterion.</p>
<p><strong>Success Criterion 1.2.1 Audio-only and Video-only (Prerecorded)</strong></p>
<p>Understanding Audio-only and Video-only (Prerecorded)</p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#audio-only-and-video-only-prerecorded">How to Meet Audio-only and Video-only (Prerecorded)</a></p>
<p>(Level A)</p>
<p>For <a href="http://www.w3.org/TR/WCAG21/#dfn-prerecorded">prerecorded</a><a href="http://www.w3.org/TR/WCAG21/#dfn-audio-only">audio-only</a> and prerecorded <a href="http://www.w3.org/TR/WCAG21/#dfn-video-only">video-only</a> media, the following are true, except when the audio or video is a <a href="http://www.w3.org/TR/WCAG21/#dfn-media-alternative-for-text">media alternative for text</a> and is clearly labeled as such:</p>
<ul>
<li>Prerecorded Audio-only: An <a href="http://www.w3.org/TR/WCAG21/#dfn-alternative-for-time-based-media">alternative for time-based media</a> is provided that presents equivalent information for prerecorded audio-only content.</li>
<li>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</li>
</ul>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fdb"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fdb" aria-hidden="true" data-number="11.1.2.1.2" />11.1.2.1.2 Audio-only and video-only (prerecorded - closed functionality)</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fdc"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fdc" aria-hidden="true" data-number="11.1.2.1.2.1" />11.1.2.1.2.1 Prerecorded audio-only (closed functionality)</label>
<div>
<p>Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading and where pre-recorded auditory information is needed to enable the use of closed functions of ICT, the functionality of software that provides a user interface shall meet requirement 5.1.5 (Visual output for auditory information).</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fdd"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fdd" aria-hidden="true" data-number="11.1.2.1.2.2" />11.1.2.1.2.2 Prerecorded video-only (closed functionality)</label>
<div>
<p>Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading, it shall meet requirement 5.1.3.7 (Speech output for video information).</p>
</div>
</div>
</li>
</ul>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fde"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fde" aria-hidden="true" data-number="11.1.2.2" />11.1.2.2 Captions (prerecorded)</label>
<div>
<p>Where ICT is non-web software that provides a user interface, it shall satisfy the <a href="http://www.w3.org/TR/WCAG21/#captions-prerecorded">WCAG 2.1 Success Criterion 1.2.2 Captions (Prerecorded)</a>.</p>
<p>NOTE: The WCAG 2.1 definition of "captions" notes that "in some countries, captions are called subtitles". They are also sometimes referred to as "subtitles for the hearing impaired". Per the definition in WCAG 2.1, to meet this success criterion, whether called captions or subtitles, they would have to provide "synchronized visual and / or text alternative for both speech and non-speech audio information needed to understand the media content" where non-speech information includes "sound effects, music, laughter, speaker identification and location".</p>
<p><strong>WCAG 2.1 Success Criterion 1.2.2 Captions (Prerecorded)</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/captions-prerecorded.html">Understanding Captions (Prerecorded)</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#captions-prerecorded">How to Meet Captions (Prerecorded)</a></p>
<p>(Level A)</p>
<p><a href="http://www.w3.org/TR/WCAG21/#dfn-captions">Captions</a> are provided for all <a href="http://www.w3.org/TR/WCAG21/#dfn-prerecorded">prerecorded</a><a href="http://www.w3.org/TR/WCAG21/#dfn-audio">audio</a> content in <a href="http://www.w3.org/TR/WCAG21/#dfn-synchronized-media">synchronized media</a>, except when the media is a <a href="http://www.w3.org/TR/WCAG21/#dfn-media-alternative-for-text">media alternative for text</a> and is clearly labeled as such.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fdf"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fdf" aria-hidden="true" data-number="11.1.2.3" />11.1.2.3 Audio description or media alternative (prerecorded)</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fe0"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fe0" aria-hidden="true" data-number="11.1.2.3.1" />11.1.2.3.1 Audio description or media alternative (prerecorded - open functionality)</label>
<div>
<p>Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the <a href="http://www.w3.org/TR/WCAG21/#audio-description-or-media-alternative-prerecorded">WCAG 2.1 Success Criterion 1.2.3 Audio Description or Media Alternative (Prerecorded)</a>.</p>
<p>NOTE 1: The WCAG 2.1 definition of "audio description" says that "audio description" is "also called 'video description' and 'descriptive narration'".</p>
<p>NOTE 2: Secondary or alternate audio tracks are commonly used for this purpose.</p>
<p><strong>WCAG 2.1 Success Criterion 1.2.3 Audio Description or Media Alternative (Prerecorded)</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/audio-description-or-media-alternative-prerecorded.html">Understanding Audio Description or Media Alternative (Prerecorded)</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#audio-description-or-media-alternative-prerecorded">How to Meet Audio Description or Media Alternative (Prerecorded)</a></p>
<p>(Level A)</p>
<p>An <a href="http://www.w3.org/TR/WCAG21/#dfn-alternative-for-time-based-media">alternative for time-based media</a> or audio description of the <a href="http://www.w3.org/TR/WCAG21/#dfn-prerecorded">prerecorded</a><a href="http://www.w3.org/TR/WCAG21/#dfn-video">video</a> content is provided for <a href="http://www.w3.org/TR/WCAG21/#dfn-synchronized-media">synchronized media</a>, except when the media is a <a href="http://www.w3.org/TR/WCAG21/#dfn-media-alternative-for-text">media alternative for text</a> and is clearly labeled as such.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fe1"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fe1" aria-hidden="true" data-number="11.1.2.3.2" />11.1.2.3.2 Audio description or media alternative (prerecorded - closed functionality)</label>
<div>
<p>Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading, it shall meet requirement 5.1.3.7 (Speech output for video information).</p>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fe2"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fe2" aria-hidden="true" data-number="11.1.2.4" />11.1.2.4 Captions (live)</label>
<div>
<p>Where ICT is non-web software that provides a user interface, it shall satisfy the <a href="http://www.w3.org/TR/WCAG21/#captions-live">WCAG 2.1 Success Criterion 1.2.4 Captions (Live)</a>.</p>
<p>NOTE: The WCAG 2.1 definition of "captions" notes that "in some countries, captions are called subtitles". They are also sometimes referred to as "subtitles for the hearing impaired". Per the definition in WCAG 2.1, to meet this success criterion, whether called captions or subtitles, they would have to provide "synchronized visual and / or text alternative for both speech and non-speech audio information needed to understand the media content" where non-speech information includes "sound effects, music, laughter, speaker identification and location".</p>
<p><strong>WCAG 2.1 Success Criterion 1.2.4 Captions (Live)</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/captions-live.html">Understanding Captions (Live)</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#captions-live">How to Meet Captions (Live)</a></p>
<p>(Level AA)</p>
<p><a href="http://www.w3.org/TR/WCAG21/#dfn-captions">Captions</a> are provided for all <a href="http://www.w3.org/TR/WCAG21/#dfn-live">live</a><a href="http://www.w3.org/TR/WCAG21/#dfn-audio">audio</a> content in <a href="http://www.w3.org/TR/WCAG21/#dfn-synchronized-media">synchronized media</a>.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fe3"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fe3" aria-hidden="true" data-number="11.1.2.5" />11.1.2.5 Audio description (prerecorded)</label>
<div>
<p>Where ICT is non-web software that provides a user interface, it shall satisfy the <a href="http://www.w3.org/TR/WCAG21/#audio-description-prerecorded">WCAG 2.1 Success Criterion 1.2.5 Audio Description (Prerecorded)</a>.</p>
<p>NOTE 1: The WCAG 2.1 definition of "audio description" says that audio description is "Also called 'video description' and 'descriptive narration'".</p>
<p>NOTE 2: Secondary or alternate audio tracks are commonly used for this purpose.</p>
<p><strong>WCAG 2.1 Success Criterion 1.2.5 Audio Description (Prerecorded).</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/audio-description-prerecorded.html">Understanding Audio Description (Prerecorded)</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#audio-description-prerecorded">How to Meet Audio Description (Prerecorded)</a></p>
<p>(Level AA)</p>
<p><a href="http://www.w3.org/TR/WCAG21/#dfn-audio-descriptions">Audio description</a> is provided for all <a href="http://www.w3.org/TR/WCAG21/#dfn-prerecorded">prerecorded</a><a href="http://www.w3.org/TR/WCAG21/#dfn-video">video</a> content in <a href="http://www.w3.org/TR/WCAG21/#dfn-synchronized-media">synchronized media</a>.</p>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fe4"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fe4" aria-hidden="true" data-number="11.1.3" />11.1.3 Adaptable</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fe5"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fe5" aria-hidden="true" data-number="11.1.3.1" />11.1.3.1 Info and relationships</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fe6"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fe6" aria-hidden="true" data-number="11.1.3.1.1" />11.1.3.1.1 Info and relationships (open functionality)</label>
<div>
<p>Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the <a href="http://www.w3.org/TR/WCAG21/#info-and-relationships">WCAG 2.1 Success Criterion 1.3.1 Info and Relationships</a>.</p>
<p>NOTE: In software, programmatic determinability is best achieved through the use of accessibility services provided by platform software to enable interoperability between software and assistive technologies and accessibility features of software. (see clause 11.5 Interoperability with assistive technology).</p>
<p><strong>WCAG 2.1 Success Criterion 1.3.1 Info and Relationships</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/info-and-relationships.html">Understanding Info and Relationships</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#info-and-relationships">How to Meet Info and Relationships</a></p>
<p>(Level A)</p>
<p>Information, <a href="http://www.w3.org/TR/WCAG21/#dfn-structure">structure</a>, and <a href="http://www.w3.org/TR/WCAG21/#dfn-relationships">relationships</a> conveyed through <a href="http://www.w3.org/TR/WCAG21/#dfn-presentation">presentation</a> can be <a href="http://www.w3.org/TR/WCAG21/#dfn-programmatically-determinable">programmatically determined</a> or are available in text.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fe7"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fe7" aria-hidden="true" data-number="11.1.3.1.2" />11.1.3.1.2 Info and relationships (closed functionality)</label>
<div>
<p>Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading and where information is displayed on the screen, the ICT should provide auditory information that allows the user to correlate the audio with the information displayed on the screen.</p>
<p>NOTE 1: Many people who are legally blind still have visual ability, and use aspects of the visual display even if it cannot be fully comprehended. An audio alternative that is both complete and complementary includes all visual information such as focus or highlighting, so that the audio can be correlated with information that is visible on the screen at any point in time.</p>
<p>NOTE 2: Examples of auditory information that allows the user to correlate the audio with the information displayed on the screen include structure and relationships conveyed through presentation.</p>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fe8"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fe8" aria-hidden="true" data-number="11.1.3.2" />11.1.3.2 Meaningful sequence</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fe9"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fe9" aria-hidden="true" data-number="11.1.3.2.1" />11.1.3.2.1 Meaningful sequence (open functionality)</label>
<div>
<p>Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the <a href="http://www.w3.org/TR/WCAG21/#meaningful-sequence">WCAG 2.1 Success Criterion 1.3.2 Meaningful Sequence</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 1.3.2 Meaningful Sequence</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/meaningful-sequence.html">Understanding Meaningful Sequence</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#meaningful-sequence">How to Meet Meaningful Sequence</a></p>
<p>(Level A)</p>
<p>When the sequence in which content is presented affects its meaning, a <a href="http://www.w3.org/TR/WCAG21/#dfn-correct-reading-sequence">correct reading sequence</a> can be <a href="http://www.w3.org/TR/WCAG21/#dfn-programmatically-determinable">programmatically determined</a>.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fea"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fea" aria-hidden="true" data-number="11.1.3.2.2" />11.1.3.2.2 Meaningful sequence (closed functionality)</label>
<div>
<p>Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading and where information is displayed on the screen, the ICT should provide auditory information that allows the user to correlate the audio with the information displayed on the screen.</p>
<p>NOTE 1: Many people who are legally blind still have visual ability, and use aspects of the visual display even if it cannot be fully comprehended. An audio alternative that is both complete and complementary includes all visual information such as focus or highlighting, so that the audio can be correlated with information that is visible on the screen at any point in time.</p>
<p>NOTE 2: Examples of auditory information that allows the user to correlate the audio with the information displayed on the screen include structure and relationships conveyed through presentation.</p>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645feb"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645feb" aria-hidden="true" data-number="11.1.3.3" />11.1.3.3 Sensory characteristics</label>
<div>
<p>Where ICT is non-web software that provides a user interface, it shall satisfy the <a href="http://www.w3.org/TR/WCAG21/#sensory-characteristics">WCAG 2.1 Success Criterion 1.3.3 Sensory Characteristics</a>.</p>
<p><strong>Success Criterion 1.3.3 Sensory Characteristics</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/sensory-characteristics.html">Understanding Sensory Characteristics</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#sensory-characteristics">How to Meet Sensory Characteristics</a></p>
<p>(Level A)</p>
<p>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.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fec"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fec" aria-hidden="true" data-number="11.1.3.4" />11.1.3.4 Orientation</label>
<div>
<p>Where ICT is non-web software that provides a user interface, it shall satisfy the <a href="http://www.w3.org/TR/WCAG21/#orientation">WCAG 2.1 Success Criterion 1.3.4 Orientation</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 1.3.4 Orientation</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/orientation.html">Understanding Orientation</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#orientation">How to Meet Orientation</a></p>
<p>(Level AA)</p>
<p>Content does not restrict its view and operation to a single display orientation, such as portrait or landscape, unless a specific display orientation is <a href="http://www.w3.org/TR/WCAG21/#dfn-essential">essential</a>.</p>
<p>Note: Examples where a particular display orientation may be essential are a bank check, a piano application, slides for a projector or television, or virtual reality content where binary display orientation is not applicable.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fed"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fed" aria-hidden="true" data-number="11.1.3.5" />11.1.3.5 Identify input purpose</label>
<div>
<p>Where ICT is non-web software that provides a user interface, it shall satisfy the <a href="http://www.w3.org/TR/WCAG21/#identify-input-purpose">WCAG 2.1 Success Criterion 1.3.5 Identify Input Purpose</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 1.3.5 Identify Input Purpose</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/identify-input-purpose.html">Understanding Identify Input Purpose</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#identify-input-purpose">How to Meet Identify Input Purpose</a></p>
<p>(Level AA)</p>
<p>The purpose of each input field collecting information about the user can be <a href="http://www.w3.org/TR/WCAG21/#dfn-programmatically-determinable">programmatically determined</a> when:</p>
<ul>
<li>The input field serves a purpose identified in the <a href="http://www.w3.org/TR/WCAG21/#input-purposes">Input Purposes for User Interface Components</a> section; and</li>
<li>The content is implemented using technologies with support for identifying the expected meaning for form input data.</li>
</ul>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fee"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fee" aria-hidden="true" data-number="11.1.4" />11.1.4 Distinguishable</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fef"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fef" aria-hidden="true" data-number="11.1.4.1" />11.1.4.1 Use of colour</label>
<div>
<p>Where ICT is non-web software that provides a user interface, it shall satisfy the <a href="http://www.w3.org/TR/WCAG21/#use-of-color">WCAG 2.1 Success Criterion 1.4.1 Use of Color</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 1.4.1 Use of Color</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/use-of-color.html">Understanding Use of Color</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#use-of-color">How to Meet Use of Color</a></p>
<p>(Level A)</p>
<p>Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.</p>
<p>Note: This success criterion addresses color perception specifically. Other forms of perception are covered in <a href="http://www.w3.org/TR/WCAG21/#adaptable">Guideline 1.3</a> including programmatic access to color and other visual presentation coding.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645ff0"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645ff0" aria-hidden="true" data-number="11.1.4.2" />11.1.4.2 Audio control</label>
<div>
<p>Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion in Table 11.1.</p>
<p><strong>Table 11.1: Software success criterion: Audio control</strong></p>
<p>If any audio in a software plays automatically for more than 3 seconds, either a <a href="http://www.w3.org/TR/WCAG21/#dfn-mechanism">mechanism</a> is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level.</p>
<p>NOTE 1: Since any part of a software that does not meet this success criterion can interfere with a user's ability to use the whole software, all content in the software (whether or not it is used to meet other success criteria) shall meet this success criterion.</p>
<p>NOTE 2: This success criterion is identical to the <a href="http://www.w3.org/TR/WCAG21/#audio-control">WCAG 2.1 Success Criterion 1.4.2 Audio Control</a> replacing "on a Web page" with "in a software", "any content" with "any part of a software", "whole page" with "whole software", "on the Web page" with "in the software", removing "See Conformance Requirement 5: Non-Interference" and adding note 1.</p>
<p><strong>WCAG 2.1 Success Criterion 1.4.2 Audio Control</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/audio-control.html">Understanding Audio Control</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#audio-control">How to Meet Audio Control</a></p>
<p>(Level A)</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645ff1"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645ff1" aria-hidden="true" data-number="11.1.4.3" />11.1.4.3 Contrast (minimum)</label>
<div>
<p>Where ICT is non-web software that provides a user interface, it shall satisfy the <a href="http://www.w3.org/TR/WCAG21/#contrast-minimum">WCAG 2.1 Success Criterion 1.4.3 Contrast (Minimum)</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 1.4.3 Contrast (Minimum)</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/contrast-minimum.html">Understanding Contrast (Minimum)</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#contrast-minimum">How to Meet Contrast (Minimum)</a></p>
<p>(Level AA)</p>
<p>The visual presentation of <a href="http://www.w3.org/TR/WCAG21/#dfn-text">text</a> and <a href="http://www.w3.org/TR/WCAG21/#dfn-images-of-text">images of text</a> has a <a href="http://www.w3.org/TR/WCAG21/#dfn-contrast-ratio">contrast ratio</a> of at least 4.5:1, except for the following:</p>
<ul>
<li>Large Text: <a href="http://www.w3.org/TR/WCAG21/#dfn-large-scale">Large-scale text</a> and images of large-scale text have a contrast ratio of at least 3:1;</li>
<li>Incidental: Text or images of text that are part of an inactive <a href="http://www.w3.org/TR/WCAG21/#dfn-user-interface-components">user interface component</a>, that are <a href="http://www.w3.org/TR/WCAG21/#dfn-pure-decoration">pure decoration</a>, that are not visible to anyone, or that are part of a picture that contains significant other visual content, have no contrast requirement.</li>
<li>Logotypes: Text that is part of a logo or brand name has no contrast requirement.</li>
</ul>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645ff2"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645ff2" aria-hidden="true" data-number="11.1.4.4" />11.1.4.4 Resize text</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645ff3"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645ff3" aria-hidden="true" data-number="11.1.4.4.1" />11.1.4.4.1 Resize text (open functionality)</label>
<div>
<p>Where ICT is non-web software that provides a user interface and that supports access to enlargement features of platform or assistive technology, it shall satisfy the <a href="http://www.w3.org/TR/WCAG21/#resize-text">WCAG 2.1 Success Criterion 1.4.4 Resize Text</a>.</p>
<p>NOTE 1: Content for which there are software players, viewers or editors with a 200 percent zoom feature would automatically meet this success criterion when used with such players, unless the content will not work with zoom.</p>
<p>NOTE 2: This success criterion is about the ability to allow users to enlarge the text on screen at least up to 200 % without needing to use assistive technologies. This means that the application provides some means for enlarging the text 200 % (zoom or otherwise) without loss of content or functionality or that the application works with the platform features that meet this requirement.</p>
<p><strong>WCAG 2.1 Success Criterion 1.4.4 Resize text</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/resize-text.html">Understanding Resize text</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#resize-text">How to Meet Resize text</a></p>
<p>(Level AA)</p>
<p>Except for <a href="http://www.w3.org/TR/WCAG21/#dfn-captions">captions</a> and <a href="http://www.w3.org/TR/WCAG21/#dfn-images-of-text">images of text</a>, <a href="http://www.w3.org/TR/WCAG21/#dfn-text">text</a> can be resized without <a href="http://www.w3.org/TR/WCAG21/#dfn-assistive-technologies">assistive technology</a> up to 200 percent without loss of content or functionality.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645ff4"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645ff4" aria-hidden="true" data-number="11.1.4.4.2" />11.1.4.4.2 Resize text (closed functionality)</label>
<div>
<p>Where ICT is non-web software that provides a user interface which is not able to access the enlargement features of platform or assistive technology, it shall meet requirement 5.1.4 (Functionality closed to text enlargement).</p>
<p>NOTE: Because the text rendering support in a closed environment may be more limited than the support found in user agents for the Web, meeting 11.1.4.4.2 in a closed environment may place a much heavier burden on the content author.</p>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645ff5"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645ff5" aria-hidden="true" data-number="11.1.4.5" />11.1.4.5 Images of text</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645ff6"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645ff6" aria-hidden="true" data-number="11.1.4.5.1" />11.1.4.5.1 Images of text (open functionality)</label>
<div>
<p>Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the <a href="http://www.w3.org/TR/WCAG21/#images-of-text">WCAG 2.1 Success Criterion 1.4.5 Images of Text</a>.</p>
<p><strong>Criterion 1.4.5 Images of Text.</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/images-of-text.html">Understanding Images of Text</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#images-of-text">How to Meet Images of Text</a></p>
<p>(Level AA)</p>
<p>If the technologies being used can achieve the visual presentation, <a href="http://www.w3.org/TR/WCAG21/#dfn-text">text</a> is used to convey information rather than <a href="http://www.w3.org/TR/WCAG21/#dfn-images-of-text">images of text</a> except for the following:</p>
<ul>
<li>Customizable: The image of text can be <a href="http://www.w3.org/TR/WCAG21/#dfn-visually-customized">visually customized</a> to the user's requirements;</li>
<li>Essential: A particular presentation of text is <a href="http://www.w3.org/TR/WCAG21/#dfn-essential">essential</a> to the information being conveyed.</li>
</ul>
<p>Note: Logotypes (text that is part of a logo or brand name) are considered essential.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645ff7"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645ff7" aria-hidden="true" data-number="11.1.4.5.2" />11.1.4.5.2 Images of text (closed functionality)</label>
<div>
<p>Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading, it does not need to meet the <a href="http://www.w3.org/TR/WCAG21/#images-of-text">WCAG 2.1 Success Criterion 1.4.5 Images of Text</a> because there is no need to impose a requirement on all closed functionality that text displayed on the screen actually be represented internally as text (as defined by WCAG 2.1), given that there is no interoperability with assistive technology.</p>
<p><strong>Criterion 1.4.5 Images of Text.</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/images-of-text.html">Understanding Images of Text</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#images-of-text">How to Meet Images of Text</a></p>
<p>(Level AA)</p>
<p>If the technologies being used can achieve the visual presentation, <a href="http://www.w3.org/TR/WCAG21/#dfn-text">text</a> is used to convey information rather than <a href="http://www.w3.org/TR/WCAG21/#dfn-images-of-text">images of text</a> except for the following:</p>
<ul>
<li>Customizable: The image of text can be <a href="http://www.w3.org/TR/WCAG21/#dfn-visually-customized">visually customized</a> to the user's requirements;</li>
<li>Essential: A particular presentation of text is <a href="http://www.w3.org/TR/WCAG21/#dfn-essential">essential</a> to the information being conveyed.</li>
</ul>
<p>Note: Logotypes (text that is part of a logo or brand name) are considered essential.</p>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645ff8"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645ff8" aria-hidden="true" data-number="11.1.4.10" />11.1.4.10 Reflow</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645ff9"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645ff9" aria-hidden="true" data-number="11.1.4.10.1" />11.1.4.10.1 Reflow (open functionality)</label>
<div>
<p>Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the success criterion in Table 11.2.</p>
<p><strong>Table 11.2: Document success criterion: Reflow (open functionality)</strong></p>
<p>Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions for:</p>
<ul>
<li>Vertical scrolling content at a width equivalent to 320 <a href="http://www.w3.org/TR/WCAG21/#dfn-css-pixels">CSS pixels</a>;</li>
<li>Horizontal scrolling content at a height equivalent to 256 <a href="http://www.w3.org/TR/WCAG21/#dfn-css-pixels">CSS pixels</a>;</li>
</ul>
<p>Except for parts of the content which require two-dimensional layout for usage or meaning.</p>
<p>NOTE 1: 320 CSS pixels is equivalent to a starting viewport width of 1280 CSS pixels wide at 400% zoom. For non-web software which are designed to scroll horizontally (e.g. with vertical text), the 256 CSS pixels is equivalent to a starting viewport height of 1024 px at 400% zoom.</p>
<p>NOTE 2: Examples of content which require two-dimensional layout are images, maps, diagrams, video, games, presentations, data tables, and interfaces where it is necessary to keep toolbars in view while manipulating content.</p>
<p>NOTE 3: This success criterion is identical to the <a href="http://www.w3.org/TR/WCAG21/#reflow">WCAG 2.1 Success Criterion 1.4.10 Reflow</a> replacing the original WCAG 2.1 notes with notes 1 and 2, above.</p>
<p><strong>WCAG 2.1 Success Criterion 1.4.10 Reflow</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/reflow.html">Understanding Reflow</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#reflow">How to Meet Reflow</a></p>
<p>(Level AA)</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645ffa"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645ffa" aria-hidden="true" data-number="11.1.4.10.2" />11.1.4.10.2 Reflow (closed functionality)</label>
<div>
<p>Where ICT is non-web software that provides a user interface which is not able to access the enlargement features of platform or assistive technology, it shall meet requirement 5.1.4 (Functionality closed to text enlargement).</p>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645ffb"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645ffb" aria-hidden="true" data-number="11.1.4.11" />11.1.4.11 Non-text contrast</label>
<div>
<p>Where ICT is non-web software that provides a user interface, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#non-text-contrast">WCAG 2.1 Success Criterion 1.4.11 Non-text Contrast</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 1.4.11 Non-text Contrast</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/non-text-contrast.html">Understanding Non-text Contrast</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#non-text-contrast">How to Meet Non-text Contrast</a></p>
<p>(Level AA)</p>
<p>The visual <a href="http://www.w3.org/TR/WCAG21/#dfn-presentation">presentation</a> of the following have a <a href="http://www.w3.org/TR/WCAG21/#dfn-contrast-ratio">contrast ratio</a> of at least 3:1 against adjacent color(s):</p>
<ul>
<li>User Interface Components: Visual information required to identify <a href="http://www.w3.org/TR/WCAG21/#dfn-user-interface-components">user interface components</a> and <a href="http://www.w3.org/TR/WCAG21/#dfn-states">states</a>, except for inactive components or where the appearance of the component is determined by the user agent and not modified by the author;</li>
<li>Graphical Objects: Parts of graphics required to understand the content, except when a particular presentation of graphics is essential to the information being conveyed.</li>
</ul>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645ffc"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645ffc" aria-hidden="true" data-number="11.1.4.12" />11.1.4.12 Text spacing</label>
<div>
<p>Where ICT is non-web software that provides a user interface and that does not have a fixed size content layout area that is essential to the information being conveyed, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#text-spacing">WCAG 2.1 Success Criterion 1.4.12 Text spacing</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 1.4.12 Text spacing</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/text-spacing.html">Understanding Text Spacing</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#text-spacing">How to Meet Text Spacing</a></p>
<p>(Level AA)</p>
<p>In content implemented using markup languages that support the following <a href="http://www.w3.org/TR/WCAG21/#dfn-text">text</a><a href="http://www.w3.org/TR/WCAG21/#dfn-style-properties">style properties</a>, no loss of content or functionality occurs by setting all of the following and by changing no other style property:</p>
<ul>
<li>Line height (line spacing) to at least 1.5 times the font size;</li>
<li>Spacing following paragraphs to at least 2 times the font size;</li>
<li>Letter spacing (tracking) to at least 0.12 times the font size;</li>
<li>Word spacing to at least 0.16 times the font size.</li>
</ul>
<p>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.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645ffd"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645ffd" aria-hidden="true" data-number="11.1.4.13" />11.1.4.13 Content on hover or focus</label>
<div>
<p>Where ICT is a non-web software that provides a user interface, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#content-on-hover-or-focus">WCAG 2.1 Success Criterion 1.4.13 Content on hover or focus</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 1.4.13 Content on Hover or Focus</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/content-on-hover-or-focus.html">Understanding Content on Hover or Focus</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#content-on-hover-or-focus">How to Meet Content on Hover or Focus</a></p>
<p>(Level AA)</p>
<p>Where receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden, the following are true:</p>
<ul>
<li>Dismissable: A <a href="http://www.w3.org/TR/WCAG21/#dfn-mechanism">mechanism</a> is available to dismiss the additional content without moving pointer hover or keyboard focus, unless the additional content communicates an <a href="http://www.w3.org/TR/WCAG21/#dfn-input-error">input error</a> or does not obscure or replace other content;</li>
<li>Hoverable: If pointer hover can trigger the additional content, then the pointer can be moved over the additional content without the additional content disappearing;</li>
<li>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.</li>
</ul>
<p>Exception: The visual presentation of the additional content is controlled by the user agent and is not modified by the author.</p>
<p>Note: Examples of additional content controlled by the user agent include browser tooltips created through use of the HTML <a href="http://www.w3.org/TR/html/dom.html#the-title-attribute">title attribute</a>.</p>
<p>Note: Custom tooltips, sub-menus, and other nonmodal popups that display on hover and focus are examples of additional content covered by this criterion.</p>
</div>
</div>
</li>
</ul>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645ffe"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645ffe" aria-hidden="true" data-number="11.2" />11.2 Operable</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4645fff"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4645fff" aria-hidden="true" data-number="11.2.1" />11.2.1 Keyboard accessible</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646000"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646000" aria-hidden="true" data-number="11.2.1.1" />11.2.1.1 Keyboard</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646001"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646001" aria-hidden="true" data-number="11.2.1.1.1" />11.2.1.1.1 Keyboard (open functionality)</label>
<div>
<p>Where ICT is non-web software that provides a user interface and that supports access to keyboards or a keyboard interface, it shall satisfy the <a href="http://www.w3.org/TR/WCAG21/#keyboard">WCAG 2.1 Success Criterion 2.1.1 Keyboard</a>.</p>
<p>NOTE: This does not imply that software is required to directly support a keyboard or "keyboard interface". Nor does it imply that software is required to provide a soft keyboard. Underlying platform software may provide device independent input services to applications that enable operation via a keyboard. Software that supports operation via such platform device independent services would be operable by a keyboard and would comply.</p>
<p><strong>WCAG 2.1 Success Criterion 2.1.1 Keyboard</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/keyboard.html">Understanding Keyboard</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#keyboard">How to Meet Keyboard</a></p>
<p>(Level A)</p>
<p>All <a href="http://www.w3.org/TR/WCAG21/#dfn-functionality">functionality</a> of the content is operable through a <a href="http://www.w3.org/TR/WCAG21/#dfn-keyboard-interface">keyboard interface</a> 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.</p>
<p>Note: 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.</p>
<p>Note: This does not forbid and should not discourage providing mouse input or other input methods in addition to keyboard operation.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646002"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646002" aria-hidden="true" data-number="11.2.1.1.2" />11.2.1.1.2 Keyboard (closed functionality)</label>
<div>
<p>Where ICT is non-web software that provides a user interface which is closed to keyboards or keyboard interface, it shall meet requirement 5.1.6.1 (Operation without keyboard interface: Closed functionality).</p>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646003"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646003" aria-hidden="true" data-number="11.2.1.2" />11.2.1.2 No keyboard trap</label>
<div>
<p>Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion in Table 11.3.</p>
<p><strong>Table 11.3: Software success criterion: No keyboard trap</strong></p>
<p>If keyboard focus can be moved to a component of the software using a <a href="http://www.w3.org/TR/WCAG21/#dfn-keyboard-interface">keyboard interface</a>, 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.</p>
<p>NOTE 1: Since any part of a software that does not meet this success criterion can interfere with a user's ability to use the whole software, it is necessary for all content in the software (whether or not it is used to meet other success criteria) to meet this success criterion.</p>
<p>NOTE 2: Standard exit methods may vary by platform. For example, on many desktop platforms, the Escape key is a standard method for exiting.</p>
<p>NOTE 3: This success criterion is identical to the <a href="http://www.w3.org/TR/WCAG21/#no-keyboard-trap">WCAG 2.1 Success Criterion 2.1.2 No Keyboard Trap</a> replacing "content", "page" and "Web page" with "software", removing "See Conformance Requirement 5: Non-Interference" and with the addition of note 2 above " and with note 1 above re-drafted to avoid the use of the word "shall".</p>
<p><strong>WCAG 2.1 Success Criterion 2.1.2 No Keyboard Trap</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/no-keyboard-trap.html">Understanding No Keyboard Trap</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#no-keyboard-trap">How to Meet No Keyboard Trap</a></p>
<p>(Level A)</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646004"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646004" aria-hidden="true" data-number="11.2.1.4" />11.2.1.4 Character key shortcuts</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646005"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646005" aria-hidden="true" data-number="11.2.1.4.1" />11.2.1.4.1 Character key shortcuts (open functionality)</label>
<div>
<p>Where ICT is non-web software that provides a user interface, it shall satisfy <a href="https://w3c.github.io/wcag21/guidelines/#character-key-shortcuts">WCAG 2.1 Success Criterion 2.1.4 Character Key Shortcuts</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 2.1.4 Character Key Shortcuts</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/character-key-shortcuts.html">Understanding Character Key Shortcuts</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#character-key-shortcuts">How to Meet Character Key Shortcuts</a></p>
<p>(Level A)</p>
<p>If a <a href="http://www.w3.org/TR/WCAG21/#dfn-keyboard-shortcuts">keyboard shortcut</a> 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:</p>
<ul>
<li>Turn off: A <a href="http://www.w3.org/TR/WCAG21/#dfn-mechanism">mechanism</a> is available to turn the shortcut off;</li>
<li>Remap: A mechanism is available to remap the shortcut to use one or more non-printable keyboard characters (e.g. Ctrl, Alt, etc.);</li>
<li>Active only on focus: The keyboard shortcut for a <a href="http://www.w3.org/TR/WCAG21/#dfn-user-interface-components">user interface component</a> is only active when that component has focus.</li>
</ul>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646006"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646006" aria-hidden="true" data-number="11.2.1.4.2" />11.2.1.4.2 Character key shortcuts (closed functionality)</label>
<div>
<p>Where ICT is non-web software that provides a user interface which is closed to keyboards or keyboard interface, it shall meet requirement 5.1.6.1 (Operation without keyboard interface: Closed functionality).</p>
</div>
</div>
</li>
</ul>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646007"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646007" aria-hidden="true" data-number="11.2.2" />11.2.2 Enough time</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646008"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646008" aria-hidden="true" data-number="11.2.2.1" />11.2.2.1 Timing adjustable</label>
<div>
<p>Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion in Table 11.4.</p>
<p><strong>Table 11.4: Software success criterion: Timing adjustable</strong></p>
<p>For each time limit that is set by the software, at least one of the following is true:</p>
<ul>
<li>Turn off: The user is allowed to turn off the time limit before encountering it; or</li>
<li>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</li>
<li>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</li>
<li>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</li>
<li>Essential Exception: The time limit is <a href="http://www.w3.org/TR/WCAG21/#dfn-essential">essential</a> and extending it would invalidate the activity; or</li>
<li>20 Hour Exception: The time limit is longer than 20 hours.</li>
</ul>
<p>NOTE 1: 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 <a href="http://www.w3.org/TR/WCAG21/#on-focus">WCAG 2.1 Success Criterion 3.2.1</a>, which puts limits on changes of content or context as a result of user action.</p>
<p>NOTE 2: This success criterion is identical to the <a href="http://www.w3.org/TR/WCAG21/#timing-adjustable">WCAG 2.1 Success Criterion 2.2.1 Timing Adjustable</a> replacing "the content" with "software" and with the words "WCAG 2.1" added before the word "Success Criterion" in note 1 above.</p>
<p><strong>WCAG 2.1 Success Criterion 2.2.1 Timing Adjustable</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/timing-adjustable.html">Understanding Timing Adjustable</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#timing-adjustable">How to Meet Timing Adjustable</a></p>
<p>(Level A)</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646009"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646009" aria-hidden="true" data-number="11.2.2.2" />11.2.2.2 Pause, stop, hide</label>
<div>
<p>Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion in Table 11.5.</p>
<p><strong>Table 11.5: Software success criterion: Pause, stop, hide</strong></p>
<p>For moving, <a href="http://www.w3.org/TR/WCAG21/#dfn-blinking">blinking</a>, scrolling, or auto-updating information, all of the following are true:</p>
<ul>
<li>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</li>
<li>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 <a href="http://www.w3.org/TR/WCAG21/#dfn-pause">pause</a>, stop, or hide it or to control the frequency of the update unless the auto-updating is part of an activity where it is <a href="http://www.w3.org/TR/WCAG21/#dfn-essential">essential</a>.</li>
</ul>
<p>NOTE 1: For requirements related to flickering or flashing content, refer to <a href="https://w3c.github.io/wcag21/guidelines/#seizures-and-physical-reactions">WCAG 2.1 Guideline 2.3</a>.</p>
<p>NOTE 2: This success criteria is applicable to all content in the software (whether or not there is an alternate accessible mode of operation of the software) since any part of a software that does not meet this success criterion can interfere with a user's ability to use the whole software (including a user interface element that enables the user to activate the alternate accessible mode of operation).</p>
<p>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.</p>
<p>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.</p>
<p>NOTE 5: This is to be applied to all content. Any content, whether informative or decorative, that is updated automatically, blinks, or moves may create an accessibility barrier.</p>
<p>NOTE 6: This success criterion is identical to the <a href="http://www.w3.org/TR/WCAG21/#pause-stop-hide">WCAG 2.1 Success Criterion 2.2.2 Pause, Stop, Hide</a> replacing "page" and "Web page" with "software", removing "See Conformance Requirement 5: Non-Interference" in note 2 of the success criterion, with the words "WCAG 2.1" added before the word "Guideline" in note 1 above, with note 2 above re-drafted to avoid the use of the word "must" and with the addition of note 5 above.</p>
<p><strong>WCAG 2.1 Success Criterion 2.2.2 Pause, Stop, Hide</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/pause-stop-hide.html">Understanding Pause, Stop, Hide</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#pause-stop-hide">How to Meet Pause, Stop, Hide</a></p>
<p>(Level A)</p>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa464600a"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa464600a" aria-hidden="true" data-number="11.2.3" />11.2.3 Seizures and physical reactions</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa464600b"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa464600b" aria-hidden="true" data-number="11.2.3.1" />11.2.3.1 Three flashes or below threshold</label>
<div>
<p>Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion in Table 11.6.</p>
<p><strong>Table 11.6: Software success criterion: Three flashes or below threshold</strong></p>
<p>Software does not contain anything that flashes more than three times in any one second period, or the <a href="http://www.w3.org/TR/WCAG21/#dfn-flashes">flash</a> is below the <a href="http://www.w3.org/TR/WCAG21/#dfn-general-flash-and-red-flash-thresholds">general flash and red flash thresholds</a>.</p>
<p>NOTE 1: This success criteria is applicable to all content in the software (whether or not there is an alternate accessible mode of operation of the software) since any part of a software that does not meet this success criterion can interfere with a user's ability to use the whole software (including a user interface element that enables the user to activate the alternate accessible mode of operation).</p>
<p>NOTE 2: This success criterion is identical to the <a href="http://www.w3.org/TR/WCAG21/#three-flashes-or-below-threshold">WCAG 2.1 Success Criterion 2.3.1 Three Flashes or Below Threshold</a> replacing "Web pages" with "software", "the whole page" with "the whole software", "the Web page" with "the software" and removing "See Conformance Requirement 5: Non-Interference" and with note 1 above re-drafted to avoid the use of the word "must".</p>
<p><strong>WCAG 2.1 Success Criterion 2.3.1 Three Flashes or Below Threshold</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/three-flashes-or-below-threshold.html">Understanding Three Flashes or Below Threshold</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#three-flashes-or-below-threshold">How to Meet Three Flashes or Below Threshold</a></p>
<p>(Level A)</p>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa464600c"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa464600c" aria-hidden="true" data-number="11.2.4" />11.2.4 Navigable</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa464600d"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa464600d" aria-hidden="true" data-number="11.2.4.3" />11.2.4.3 Focus order</label>
<div>
<p>Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion in Table 11.7.</p>
<p><strong>Table 11.7: Software success criterion: Focus order</strong></p>
<p>If software can be <a href="http://www.w3.org/TR/WCAG21/#dfn-navigated-sequentially">navigated sequentially</a> and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability.</p>
<p>NOTE: This success criterion is identical to the <a href="http://www.w3.org/TR/WCAG21/#focus-order">WCAG 2.1 Success Criterion 2.4.3 Focus order</a> replacing "Web page" with "software".</p>
<p><strong>WCAG 2.1 Success Criterion 2.4.3 Focus Order</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/focus-order.html">Understanding Focus Order</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#focus-order">How to Meet Focus Order</a></p>
<p>(Level A)</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa464600e"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa464600e" aria-hidden="true" data-number="11.2.4.4" />11.2.4.4 Link purpose (in context)</label>
<div>
<p>Where ICT is non-web software that provides a user interface, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#link-purpose-in-context">WCAG 2.1 Success Criterion 2.4.4 Link Purpose (In Context)</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 2.4.4 Link Purpose (In Context)</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/link-purpose-in-context.html">Understanding Link Purpose (In Context)</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#link-purpose-in-context">How to Meet Link Purpose (In Context)</a></p>
<p>(Level A)</p>
<p>The <a href="http://www.w3.org/TR/WCAG21/#dfn-purpose-of-each-link">purpose of each link</a> can be determined from the link text alone or from the link text together with its <a href="http://www.w3.org/TR/WCAG21/#dfn-programmatically-determined-link-context">programmatically determined link context</a>, except where the purpose of the link would be <a href="http://www.w3.org/TR/WCAG21/#dfn-ambiguous-to-users-in-general">ambiguous to users in general</a>.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa464600f"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa464600f" aria-hidden="true" data-number="11.2.4.6" />11.2.4.6 Headings and labels</label>
<div>
<p>Where ICT is non-web software that provides a user interface, it shall satisfy the <a href="http://www.w3.org/TR/WCAG21/#headings-and-labels">WCAG 2.1 Success Criterion 2.4.6 Headings and Labels</a>.</p>
<p>NOTE: In software, headings and labels are used to describe sections of content and controls respectively. In some cases it may be unclear whether a piece of static text is a heading or a label. But whether treated as a label or a heading, the requirement is the same: that if they are present they describe the topic or purpose of the item(s) they are associated with.</p>
<p><strong>WCAG 2.1 Success Criterion 2.4.6 Headings and Labels</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/headings-and-labels.html">Understanding Headings and Labels</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#headings-and-labels">How to Meet Headings and Labels</a></p>
<p>(Level AA)</p>
<p>Headings and <a href="http://www.w3.org/TR/WCAG21/#dfn-labels">labels</a> describe topic or purpose.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646010"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646010" aria-hidden="true" data-number="11.2.4.7" />11.2.4.7 Focus visible</label>
<div>
<p>Where ICT is non-web software that provides a user interface, it shall satisfy the <a href="https://www.w3.org/TR/WCAG21/#focus-visible">WCAG 2.1 Success Criterion 2.4.7 Focus Visible</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 2.4.7 Focus Visible</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/focus-visible.html">Understanding Focus Visible</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#focus-visible">How to Meet Focus Visible</a></p>
<p>(Level AA)</p>
<p>Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible.</p>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646011"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646011" aria-hidden="true" data-number="11.2.5" />11.2.5 Input modalities</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646012"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646012" aria-hidden="true" data-number="11.2.5.1" />11.2.5.1 Pointer gestures</label>
<div>
<p>Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion in Table 11.8.</p>
<p><strong>Table 11.8: Software success criterion: Pointer gestures</strong></p>
<p>All <a href="http://www.w3.org/TR/WCAG21/#dfn-functionality">functionality</a> that uses multipoint or path-based gestures for operation can be operated with a <a href="http://www.w3.org/TR/WCAG21/#dfn-single-pointer">single pointer</a> without a path-based gesture, unless a multipoint or path-based gesture is <a href="http://www.w3.org/TR/WCAG21/#dfn-essential">essential</a>.</p>
<p>NOTE 1: This requirement applies to non-web software that interprets pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive technology).</p>
<p>NOTE 2: This success criterion is identical to the <a href="http://www.w3.org/TR/WCAG21/#pointer-gestures">WCAG 2.1 Success Criterion 2.5.1 Pointer Gestures</a> replacing the original WCAG 2.1 note with note 1 above.</p>
<p><strong>WCAG 2.1 Success Criterion 2.5.1 Pointer Gestures</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/pointer-gestures.html">Understanding Pointer Gestures</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#pointer-gestures">How to Meet Pointer Gestures</a></p>
<p>(Level A)</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646013"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646013" aria-hidden="true" data-number="11.2.5.2" />11.2.5.2 Pointer cancellation</label>
<div>
<p>Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion in Table 11.9.</p>
<p><strong>Table 11.9: Software success criterion: Pointer cancellation</strong></p>
<p>For <a href="http://www.w3.org/TR/WCAG21/#dfn-functionality">functionality</a> that can be operated using a <a href="http://www.w3.org/TR/WCAG21/#dfn-single-pointer">single pointer</a>, at least one of the following is true:</p>
<ul>
<li>No Down-Event: The <a href="http://www.w3.org/TR/WCAG21/#dfn-down-event">down-event</a> of the pointer is not used to execute any part of the function;</li>
<li>Abort or Undo: Completion of the function is on the <a href="http://www.w3.org/TR/WCAG21/#dfn-up-event">up-event,</a> and a <a href="http://www.w3.org/TR/WCAG21/#dfn-mechanism">mechanism</a> is available to abort the function before completion or to undo the function after completion;</li>
<li>Up Reversal: The up-event reverses any outcome of the preceding down-event;</li>
<li>Essential: Completing the function on the down-event is <a href="http://www.w3.org/TR/WCAG21/#dfn-essential">essential</a>.</li>
</ul>
<p>NOTE 1: Functions that emulate a keyboard or numeric keypad key press are considered essential.</p>
<p>NOTE 2: This requirement applies to non-web software that interprets pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive technology).</p>
<p>NOTE 3: This success criterion is identical to the <a href="http://www.w3.org/TR/WCAG21/#pointer-cancellation">WCAG 2.1 Success Criterion 2.5.2 Pointer Cancellation</a> replacing the original WCAG 2.1 note with notes 1 and 2 above.</p>
<p><strong>WCAG 2.1 Success Criterion 2.5.2 Pointer Cancellation</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/pointer-cancellation.html">Understanding Pointer Cancellation</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#pointer-cancellation">How to Meet Pointer Cancellation</a></p>
<p>(Level A)</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646014"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646014" aria-hidden="true" data-number="11.2.5.3" />11.2.5.3 Label in name</label>
<div>
<p>Where ICT is non-web software that provides a user interface, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#label-in-name">WCAG 2.1 Success Criterion 2.5.3 Label in Name</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 2.5.3 Label in Name</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/label-in-name.html">Understanding Label in Name</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#label-in-name">How to Meet Label in Name</a></p>
<p>(Level A)</p>
<p>For user <a href="http://www.w3.org/TR/WCAG21/#dfn-user-interface-components">interface components</a> with <a href="http://www.w3.org/TR/WCAG21/#dfn-labels">labels</a> that include <a href="http://www.w3.org/TR/WCAG21/#dfn-text">text</a> or <a href="http://www.w3.org/TR/WCAG21/#dfn-images-of-text">images of text</a>, the <a href="http://www.w3.org/TR/WCAG21/#dfn-name">name</a> contains the text that is presented visually.</p>
<p>Note: A best practice is to have the text of the label at the start of the name.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646015"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646015" aria-hidden="true" data-number="11.2.5.4" />11.2.5.4 Motion actuation</label>
<div>
<p>Where ICT is non-web software that provides a user interface, it shall satisfy <a href="http://www.w3.org/TR/WCAG21/#motion-actuation">WCAG 2.1 Success Criterion 2.5.4 Motion Actuation</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 2.5.4 Motion Actuation</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/motion-actuation.html">Understanding Motion Actuation</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#motion-actuation">How to Meet Motion Actuation</a></p>
<p>(Level A)</p>
<p><a href="http://www.w3.org/TR/WCAG21/#dfn-functionality">Functionality</a> that can be operated by device motion or user motion can also be operated by <a href="http://www.w3.org/TR/WCAG21/#dfn-user-interface-components">user interface components</a> and responding to the motion can be disabled to prevent accidental actuation, except when:</p>
<ul>
<li>Supported Interface: The motion is used to operate functionality through an <a href="http://www.w3.org/TR/WCAG21/#dfn-accessibility-supported">accessibility supported</a> interface;</li>
<li>Essential: The motion is <a href="http://www.w3.org/TR/WCAG21/#dfn-essential">essential</a> for the function and doing so would invalidate the activity.</li>
</ul>
</div>
</div>
</li>
</ul>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646016"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646016" aria-hidden="true" data-number="11.3" />11.3 Understandable</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646017"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646017" aria-hidden="true" data-number="11.3.1" />11.3.1 Readable</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646018"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646018" aria-hidden="true" data-number="11.3.1.1" />11.3.1.1 Language of software</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646019"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646019" aria-hidden="true" data-number="11.3.1.1.1" />11.3.1.1.1 Language of software (open functionality)</label>
<div>
<p>Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the success criterion in Table 11.10.</p>
<p><strong>Table 11.10: Software success criterion: Language of software</strong></p>
<p>The default <a href="http://www.w3.org/TR/WCAG21/#dfn-human-language-s">human language</a> of software can be <a href="http://www.w3.org/TR/WCAG21/#dfn-programmatically-determinable">programmatically determined</a>.</p>
<p>NOTE 1: Where software platforms provide a "locale / language" setting, applications that use that setting and render their interface in that "locale / language" would comply with this success criterion. Applications that do not use the platform "locale / language" setting but instead use an accessibility-supported method for exposing the human language of the software would also comply with this success criterion. Applications implemented in technologies where assistive technologies cannot determine the human language and that do not support the platform "locale / language" setting may not be able to meet this success criterion in that locale / language.</p>
<p>NOTE 2: This success criterion is identical to the <a href="http://www.w3.org/TR/WCAG21/#language-of-page">WCAG 2.1 Success Criterion 3.1.1 Language of page</a>, replacing "each web page" with "software" and with the addition of note 1 above.</p>
<p><strong>WCAG 2.1 Success Criterion 3.1.1 Language of Page</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/language-of-page.html">Understanding Language of Page</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#language-of-page">How to Meet Language of Page</a></p>
<p>(Level A)</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa464601a"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa464601a" aria-hidden="true" data-number="11.3.1.1.2" />11.3.1.1.2 Language of software (closed functionality)</label>
<div>
<p>Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading, it shall meet requirement 5.1.3.14 (Spoken languages).</p>
</div>
</div>
</li>
</ul>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa464601b"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa464601b" aria-hidden="true" data-number="11.3.2" />11.3.2 Predictable</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa464601c"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa464601c" aria-hidden="true" data-number="11.3.2.1" />11.3.2.1 On focus</label>
<div>
<p>Where ICT is non-web software that provides a user interface, it shall satisfy the <a href="http://www.w3.org/TR/WCAG21/#on-focus">WCAG 2.1 Success Criterion 3.2.1 On Focus</a>.</p>
<p>NOTE: Some compound documents and their user agents are designed to provide significantly different viewing and editing functionality depending upon what portion of the compound document is being interacted with (e.g. a presentation that contains an embedded spreadsheet, where the menus and toolbars of the user agent change depending upon whether the user is interacting with the presentation content, or the embedded spreadsheet content). If the user uses a mechanism other than putting focus on that portion of the compound document with which they mean to interact (e.g. by a menu choice or special keyboard gesture), any resulting change of context would not be subject to this success criterion because it was not caused by a change of focus.</p>
<p><strong>WCAG 2.1 Success Criterion 3.2.1 On Focus</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/on-focus.html">Understanding On Focus</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#on-focus">How to Meet On Focus</a></p>
<p>(Level A)</p>
<p>When any <a href="http://www.w3.org/TR/WCAG21/#dfn-user-interface-components">user interface component</a> receives focus, it does not initiate a <a href="http://www.w3.org/TR/WCAG21/#dfn-change-of-context">change of context</a>.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa464601d"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa464601d" aria-hidden="true" data-number="11.3.2.2" />11.3.2.2 On input</label>
<div>
<p>Where ICT is non-web software that provides a user interface, it shall satisfy the <a href="http://www.w3.org/TR/WCAG21/#on-input">WCAG 2.1 Success Criterion 3.2.2 On Input</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 3.2.2 On Input</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/on-input.html">Understanding On Input</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#on-input">How to Meet On Input</a></p>
<p>(Level A)</p>
<p>Changing the setting of any <a href="http://www.w3.org/TR/WCAG21/#dfn-user-interface-components">user interface component</a> does not automatically cause a <a href="http://www.w3.org/TR/WCAG21/#dfn-change-of-context">change of context</a> unless the user has been advised of the behavior before using the component.</p>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa464601e"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa464601e" aria-hidden="true" data-number="11.3.3" />11.3.3 Input assistance</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa464601f"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa464601f" aria-hidden="true" data-number="11.3.3.1" />11.3.3.1 Error identification</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646020"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646020" aria-hidden="true" data-number="11.3.3.1.1" />11.3.3.1.1 Error identification (open functionality)</label>
<div>
<p>Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the <a href="http://www.w3.org/TR/WCAG21/#error-identification">WCAG 2.1 Success Criterion 3.3.1 Error Identification</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 3.3.1 Error Identification</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/error-identification.html">Understanding Error Identification</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#error-identification">How to Meet Error Identification</a></p>
<p>(Level A)</p>
<p>If an <a href="http://www.w3.org/TR/WCAG21/#dfn-input-error">input error</a> is automatically detected, the item that is in error is identified and the error is described to the user in text.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646021"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646021" aria-hidden="true" data-number="11.3.3.1.2" />11.3.3.1.2 Error Identification (closed functionality)</label>
<div>
<p>Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading, it shall meet requirement 5.1.3.15 (Non-visual error identification).</p>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646022"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646022" aria-hidden="true" data-number="11.3.3.2" />11.3.3.2 Labels or instructions</label>
<div>
<p>Where ICT is non-web software that provides a user interface, it shall satisfy the <a href="http://www.w3.org/TR/WCAG21/#labels-or-instructions">WCAG 2.1 Success Criterion 3.3.2 Labels or Instructions</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 3.3.2 Labels or Instructions</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/labels-or-instructions.html">Understanding Labels or Instructions</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#labels-or-instructions">How to Meet Labels or Instructions</a></p>
<p>(Level A)</p>
<p><a href="http://www.w3.org/TR/WCAG21/#dfn-labels">Labels</a> or instructions are provided when content requires user input.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646023"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646023" aria-hidden="true" data-number="11.3.3.3" />11.3.3.3 Error suggestion</label>
<div>
<p>Where ICT is non-web software that provides a user interface, it shall satisfy the <a href="http://www.w3.org/TR/WCAG21/#error-suggestion">WCAG 2.1 Success Criterion 3.3.3 Error Suggestion</a>.</p>
<p><strong>WCAG 2.1 Success Criterion 3.3.3 Error Suggestion</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/error-suggestion.html">Understanding Error Suggestion</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#error-suggestion">How to Meet Error Suggestion</a></p>
<p>(Level AA)</p>
<p>If an <a href="http://www.w3.org/TR/WCAG21/#dfn-input-error">input error</a> 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.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646024"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646024" aria-hidden="true" data-number="11.3.3.4" />11.3.3.4 Error prevention (legal, financial, data)</label>
<div>
<p>Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion in Table 11.11.</p>
<p><strong>Table 11.11: Software success criterion: Error prevention (legal, financial, data)</strong></p>
<p>For software that cause <a href="http://www.w3.org/TR/WCAG21/#dfn-legal-commitments">legal commitments</a> or financial transactions for the user to occur, that modify or delete <a href="http://www.w3.org/TR/WCAG21/#dfn-user-controllable">user-controllable</a> data in data storage systems, or that submit user test responses, at least one of the following is true:</p>
<ol>
<li>Reversible: Submissions are reversible.</li>
<li>Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them.</li>
<li>Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.</li>
</ol>
<p>NOTE: This success criterion is identical to the <a href="http://www.w3.org/TR/WCAG21/#error-prevention-legal-financial-data">WCAG 2.1 Success Criterion 3.3.4 Error Prevention (Legal, Financial, Data</a>) replacing "web pages" with "software".</p>
<p><strong>WCAG 2.1 Success Criterion 3.3.4 Error Prevention (Legal, Financial, Data)</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/error-prevention-legal-financial-data.html">Understanding Error Prevention (Legal, Financial, Data)</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#error-prevention-legal-financial-data">How to Meet Error Prevention (Legal, Financial, Data)</a></p>
<p>(Level AA)</p>
</div>
</div>
</li>
</ul>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646025"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646025" aria-hidden="true" data-number="11.4" />11.4 Robust</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646026"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646026" aria-hidden="true" data-number="11.4.1" />11.4.1 Compatible</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646027"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646027" aria-hidden="true" data-number="11.4.1.1" />11.4.1.1 Parsing</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646028"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646028" aria-hidden="true" data-number="11.4.1.1.1" />11.4.1.1.1 Parsing (open functionality)</label>
<div>
<p>Where ICT is non-web software that provides a user interface and that supports access to any assistive technologies, it shall satisfy the success criterion in Table 11.12.</p>
<p><strong>Table 11.12: Software success criterion: Parsing</strong></p>
<p>For software that uses markup languages, in such a way that the markup is separately exposed and available to assistive technologies and accessibility features of software or to a user-selectable user agent, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features.</p>
<p>NOTE 1: Start and end tags that are missing a critical character in their formation, such as a closing angle bracket or a mismatched attribute value quotation mark are not complete.</p>
<p>NOTE 2: Markup is not always available to assistive technology or to user selectable user agents such as browsers. In such cases, conformance to this provision would have no impact on accessibility as it can for web content where it is exposed.</p>
<p>NOTE 3: Examples of markup that is separately exposed and available to assistive technologies and to user agents include but are not limited to: documents encoded in HTML, ODF, and OOXML. In these examples, the markup can be parsed entirely in two ways: (a) by assistive technologies which may directly open the document, (b) by assistive technologies using DOM APIs of user agents for these document formats.</p>
<p>NOTE 4: Examples of markup used internally for persistence of the software user interface that are never exposed to assistive technology include but are not limited to: XUL, GladeXML, and FXML. In these examples assistive technology only interacts with the user interface of generated software.</p>
<p>NOTE 5: This success criterion is identical to the <a href="http://www.w3.org/TR/WCAG21/#parsing">WCAG 2.1 Success Criterion 4.1.1 Parsing</a> replacing "In content implemented using markup languages" with "For software that uses markup languages, in such a way that the markup is separately exposed and available to assistive technologies and accessibility features of software or to a user-selectable user agent" with the addition of notes 2, 3 and 4 above.</p>
<p><strong>WCAG 2.1 Success Criterion 4.1.1 Parsing</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/parsing.html">Understanding Parsing</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#parsing">How to Meet Parsing</a></p>
<p>(Level A)</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646029"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646029" aria-hidden="true" data-number="11.4.1.1.2" />11.4.1.1.2 Parsing (closed functionality)</label>
<div>
<p>Where ICT is non-web software that provides a user interface which is closed to all assistive technology it shall not have to meet the "Parsing" success criterion in Table 11.10 because the intent of this success criterion is to provide consistency so that different user agents or assistive technologies will yield the same result.</p>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa464602a"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa464602a" aria-hidden="true" data-number="11.4.1.2" />11.4.1.2 Name, role, value</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa464602b"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa464602b" aria-hidden="true" data-number="11.4.1.2.1" />11.4.1.2.1 Name, role, value (open functionality)</label>
<div>
<p>Where ICT is non-web software that provides a user interface and that supports access to any assistive technologies, it shall satisfy the success criterion in Table 11.13.</p>
<p><strong>Table 11.13: Software success criterion: Name, role, value</strong></p>
<p>For all <a href="http://www.w3.org/TR/WCAG21/#dfn-user-interface-components">user interface components</a> (including but not limited to: form elements, links and components generated by scripts), the <a href="http://www.w3.org/TR/WCAG21/#dfn-name">name</a> and <a href="http://www.w3.org/TR/WCAG21/#dfn-role">role</a> can be <a href="http://www.w3.org/TR/WCAG21/#dfn-programmatically-determinable">programmatically determined</a>; states, properties, and values that can be set by the user can be <a href="http://www.w3.org/TR/WCAG21/#dfn-programmatically-set">programmatically set</a>; and notification of changes to these items is available to <a href="http://www.w3.org/TR/WCAG21/#dfn-user-agents">user agents</a>, including <a href="http://www.w3.org/TR/WCAG21/#dfn-assistive-technologies">assistive technologies</a>.</p>
<p>NOTE 1: This success criterion is primarily for software developers who develop or use custom user interface components. Standard user interface components on most accessibility-supported platforms already meet this success criterion when used according to specification.</p>
<p>NOTE 2: For conforming to this success criterion, it is usually best practice for software user interfaces to use the accessibility services provided by platform software. These accessibility services enable interoperability between software user interfaces and both assistive technologies and accessibility features of software in standardised ways. Most platform accessibility services go beyond programmatic exposure of name and role, and programmatic setting of states, properties and values (and notification of same), and specify additional information that could or should be exposed and / or set (for instance, a list of the available actions for a given user interface component, and a means to programmatically execute one of the listed actions).</p>
<p>NOTE 3: This success criterion is identical to the <a href="http://www.w3.org/TR/WCAG21/#name-role-value">WCAG 2.1 Success Criterion 4.1.2 Name, Role, Value</a> replacing the original WCAG 2.1 note with: "This success criterion is primarily for software developers who develop or use custom user interface components. Standard user interface components on most accessibility-supported platforms already meet this success criterion when used according to specification." and the addition of note 2 above.</p>
<p><strong>WCAG 2.1 Success Criterion 4.1.2 Name, Role, Value</strong></p>
<p><a href="http://www.w3.org/WAI/WCAG21/Understanding/name-role-value.html">Understanding Name, Role, Value</a></p>
<p><a href="http://www.w3.org/WAI/WCAG21/quickref/#name-role-value">How to Meet Name, Role, Value</a></p>
<p>(Level A)</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa464602c"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa464602c" aria-hidden="true" data-number="11.4.1.2.2" />11.4.1.2.2 Name, role, value (closed functionality)</label>
<div>
<p>Where ICT is non-web software that provides a user interface which is closed to all assistive technology it shall not have to meet the "Name, role, value" success criterion in Table 11.11 because this success criterion requires information in a programmatically determinable form.</p>
</div>
</div>
</li>
</ul>
</li>
</ul>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa464602d"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa464602d" aria-hidden="true" data-number="11.5" />11.5 Interoperability with assistive technology</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa464602e"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa464602e" aria-hidden="true" data-number="11.5.1" />11.5.1 Closed functionality</label>
<div>
<p>Where the closed functionality of software conforms to clause 5.1 (Closed functionality) it shall not be required to conform with clause 11.5.2 to clause 11.5.2.17.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa464602f"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa464602f" aria-hidden="true" data-number="11.5.2" />11.5.2 Accessibility services</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646030"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646030" aria-hidden="true" data-number="11.5.2.1" />11.5.2.1 Platform accessibility service support for software that provides a user interface</label>
<div>
<p>Platform software shall provide a set of documented platform services that enable software that provides a user interface running on the platform software to interoperate with assistive technology.</p>
<p>Platform software should support requirements 11.5.2.5 to 11.5.2.17 except that, where a user interface concept that corresponds to one of the clauses 11.5.2.5 to 11.5.2.17 is not supported within the software environment, these requirements are not applicable. For example, selection attributes from 11.5.2.14 (Modification of focus and selection attributes) may not exist in environments that do not allow selection, which is most commonly associated with copy and paste.</p>
<p>NOTE 1: These define the minimum functionality of software providing user interfaces when using platform services.</p>
<p>NOTE 2: In some platforms these services may be called accessibility services, but in some other platforms these services may be provided as part of the user interface services.</p>
<p>NOTE 3: User interface services that provide accessibility support by default are considered to be part of the services provided to conform to this clause (e.g. the service for creating a new user interface element provides role, state, boundary, name and description).</p>
<p>NOTE 4: To comply with this requirement the platform software can provide its own set of services or expose the services provided by its underlying platform layers, if those services conform to this requirement.</p>
<p>NOTE 5: Within specific programming environments, the technical attributes associated with the user interface properties described in clauses 11.5.2.5 to 11.5.2.17 might have different names than those used within the clauses.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646031"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646031" aria-hidden="true" data-number="11.5.2.2" />11.5.2.2 Platform accessibility service support for assistive technologies</label>
<div>
<p>Platform software shall provide a set of documented platform accessibility services that enable assistive technology to interoperate with software that provides a user interface running on the platform software.</p>
<p>Platform software should support the requirements of clauses 11.5.2.5 to 11.5.2.17 except that, where a user interface concept that corresponds to one of the clauses 11.5.2.5 to 11.5.2.17 is not supported within the software environment, these requirement are not applicable. For example, selection attributes from 11.5.2.14 (Modification of focus and selection attributes) may not exist in environments that do not allow selection, which is most commonly associated with copy and paste.</p>
<p>NOTE 1: These define the minimum functionality available to assistive technologies when using platform services.</p>
<p>NOTE 2: The definition of platform in clause 3.1 applies to software that provides services to other software, including but not limited to, operating systems, web browsers, virtual machines.</p>
<p>NOTE 3: In some platforms these services may be called accessibility services, but in some other platforms these services may be provided as part of the user interface services.</p>
<p>NOTE 4: Typically these services belong to the same set of services that are described in clause 11.5.2.1.</p>
<p>NOTE 5: To comply with this requirement the platform software can provide its own set of services or expose the services provided by its underlying platform layers, if those services conform to this requirement.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646032"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646032" aria-hidden="true" data-number="11.5.2.3" />11.5.2.3 Use of accessibility services</label>
<div>
<p>Where the software provides a user interface it shall use the applicable documented platform accessibility services. If the documented platform accessibility services do not allow the software to meet the applicable requirements of clauses 11.5.2.5 to 11.5.2.17, then software that provides a user interface shall use other documented services to interoperate with assistive technology.</p>
<p>NOTE: The term "documented platform accessibility services" refers to the set of services provided by the platform according to clauses 11.5.2.1 and 11.5.2.2.</p>
<p>It is best practice to develop software using toolkits that automatically implement the underlying platform accessibility services.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646033"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646033" aria-hidden="true" data-number="11.5.2.4" />11.5.2.4 Assistive technology</label>
<div>
<p>Where the ICT is assistive technology it shall use the documented platform accessibility services.</p>
<p>NOTE 1: The term "documented platform accessibility services" refers to the set of services provided by the platform according to clauses 11.5.2.1 and 11.5.2.2.</p>
<p>NOTE 2: Assistive technology can also use other documented accessibility services.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646034"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646034" aria-hidden="true" data-number="11.5.2.5" />11.5.2.5 Object information</label>
<div>
<p>Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make the user interface elements' role, state(s), boundary, name, and description programmatically determinable by assistive technologies.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646035"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646035" aria-hidden="true" data-number="11.5.2.6" />11.5.2.6 Row, column, and headers</label>
<div>
<p>Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make the row and column of each cell in a data table, including headers of the row and column if present, programmatically determinable by assistive technologies.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646036"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646036" aria-hidden="true" data-number="11.5.2.7" />11.5.2.7 Values</label>
<div>
<p>Where the software provides a user interface, it shall, by using the services as described in clause 11.5.2.3, make the current value of a user interface element and any minimum or maximum values of the range, if the user interface element conveys information about a range of values, programmatically determinable by assistive technologies.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646037"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646037" aria-hidden="true" data-number="11.5.2.8" />11.5.2.8 Label relationships</label>
<div>
<p>Where the software provides a user interface it shall expose the relationship that a user interface element has as a label for another element, or of being labelled by another element, using the services as described in clause 11.5.2.3, so that this information is programmatically determinable by assistive technologies.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646038"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646038" aria-hidden="true" data-number="11.5.2.9" />11.5.2.9 Parent-child relationships</label>
<div>
<p>Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make the relationship between a user interface element and any parent or children elements programmatically determinable by assistive technologies.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646039"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646039" aria-hidden="true" data-number="11.5.2.10" />11.5.2.10 Text</label>
<div>
<p>Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make the text contents, text attributes, and the boundary of text rendered to the screen programmatically determinable by assistive technologies.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa464603a"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa464603a" aria-hidden="true" data-number="11.5.2.11" />11.5.2.11 List of available actions</label>
<div>
<p>Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make a list of available actions that can be executed on a user interface element, programmatically determinable by assistive technologies.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa464603b"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa464603b" aria-hidden="true" data-number="11.5.2.12" />11.5.2.12 Execution of available actions</label>
<div>
<p>Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow the programmatic execution of the actions exposed according to clause 11.5.2.11 by assistive technologies.</p>
<p>NOTE 1: In some cases the security requirements imposed on a software product may forbid external software from interfering with the ICT product. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.</p>
<p>NOTE 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa464603c"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa464603c" aria-hidden="true" data-number="11.5.2.13" />11.5.2.13 Tracking of focus and selection attributes</label>
<div>
<p>Where software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make information and mechanisms necessary to track focus, text insertion point, and selection attributes of user interface elements programmatically determinable by assistive technologies.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa464603d"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa464603d" aria-hidden="true" data-number="11.5.2.14" />11.5.2.14 Modification of focus and selection attributes</label>
<div>
<p>Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow assistive technologies to programmatically modify focus, text insertion point, and selection attributes of user interface elements where the user can modify these items.</p>
<p>NOTE 1: In some cases the security requirements imposed on a software product may forbid external software from interfering with the ICT product and so this requirement would not apply. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.</p>
<p>NOTE 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa464603e"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa464603e" aria-hidden="true" data-number="11.5.2.15" />11.5.2.15 Change notification</label>
<div>
<p>Where software provides a user interface it shall, by using the services as described in clause 11.5.2.3, notify assistive technologies about changes in those programmatically determinable attributes of user interface elements that are referenced in requirements 11.5.2.5 to 11.5.2.11 and 11.5.2.13.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa464603f"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa464603f" aria-hidden="true" data-number="11.5.2.16" />11.5.2.16 Modifications of states and properties</label>
<div>
<p>Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow assistive technologies to programmatically modify states and properties of user interface elements, where the user can modify these items.</p>
<p>NOTE 1: In some cases the security requirements imposed on a software product may forbid external software from interfering with the ICT product and so this requirement would not apply. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.</p>
<p>NOTE 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646040"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646040" aria-hidden="true" data-number="11.5.2.17" />11.5.2.17 Modifications of values and text</label>
<div>
<p>Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow assistive technologies to modify values and text of user interface elements using the input methods of the platform, where a user can modify these items without the use of assistive technology.</p>
<p>NOTE 1: In some cases the security requirements imposed on a software product may forbid external software from interfering with the ICT product and so this requirement would not apply. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.</p>
<p>NOTE 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.</p>
</div>
</div>
</li>
</ul>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646041"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646041" aria-hidden="true" data-number="11.6" />11.6 Documented accessibility usage</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646042"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646042" aria-hidden="true" data-number="11.6.1" />11.6.1 User control of accessibility features</label>
<div>
<p>Where software is a platform it shall provide sufficient modes of operation for user control over those platform accessibility features documented as intended for users.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646043"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646043" aria-hidden="true" data-number="11.6.2" />11.6.2 No disruption of accessibility features</label>
<div>
<p>Where software provides a user interface it shall not disrupt those documented accessibility features that are defined in platform documentation except when requested to do so by the user during the operation of the software.</p>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646044"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646044" aria-hidden="true" data-number="11.7" />11.7 User preferences</label>
<div>
<p>Where software provides a user interface it shall provide sufficient modes of operation that use user preferences for platform settings for colour, contrast, font type, font size, and focus cursor except for software that is designed to be isolated from its underlying platforms.</p>
<p>NOTE: Software that is isolated from its underlying platform has no access to user settings in the platform and thus cannot adhere to them.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646045"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646045" aria-hidden="true" data-number="11.8" />11.8 Authoring tools</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646046"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646046" aria-hidden="true" data-number="11.8.1" />11.8.1 Content technology</label>
<div>
<p>Authoring tools shall conform to clauses 11.8.2 to 11.8.5 to the extent that information required for accessibility is supported by the format used for the output of the authoring tool.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646047"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646047" aria-hidden="true" data-number="11.8.2" />11.8.2 Accessible content creation</label>
<div>
<p>Authoring tools shall enable and guide the production of content that conforms to clauses 9 (Web content) or 10 (Non-Web content) as applicable.</p>
<p>NOTE: Authoring tools may rely on additional tools where conformance with specific requirements is not achievable by a single tool. For example, a video editing tool may enable the creation of video files for distribution via broadcast television and the web, but authoring of caption files for multiple formats may be provided by a different tool.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646048"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646048" aria-hidden="true" data-number="11.8.3" />11.8.3 Preservation of accessibility information in transformations</label>
<div>
<p>If the authoring tool provides restructuring transformations or re-coding transformations, then accessibility information shall be preserved in the output if equivalent mechanisms exist in the content technology of the output.</p>
<p>NOTE 1: Restructuring transformations are transformations in which the content technology stays the same, but the structural features of the content are changed (e.g. linearizing tables, splitting a document into pages).</p>
<p>NOTE 2: Re-coding transformations are transformations in which the technology used to encode the content is changed.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646049"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646049" aria-hidden="true" data-number="11.8.4" />11.8.4 Repair assistance</label>
<div>
<p>If the accessibility checking functionality of an authoring tool can detect that content does not meet a requirement of clauses 9 (Web) or 10 (Non-web documents) as applicable, then the authoring tool shall provide repair suggestion(s).</p>
<p>NOTE: This does not preclude automated and semi-automated repair which is possible (and encouraged) for many types of content accessibility problems.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa464604a"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa464604a" aria-hidden="true" data-number="11.8.5" />11.8.5 Templates</label>
<div>
<p>When an authoring tool provides templates, at least one template that supports the creation of content that conforms to the requirements of clauses 9 (Web) or 10 (Non-web documents) as applicable shall be available and identified as such.</p>
</div>
</div>
</li>
</ul>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa464604b"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa464604b" aria-hidden="true" data-number="12" />12 Documentation and support services</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa464604c"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa464604c" aria-hidden="true" data-number="12.1" />12.1 Product documentation</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa464604d"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa464604d" aria-hidden="true" data-number="12.1.1" />12.1.1 Accessibility and compatibility features</label>
<div>
<p>Product documentation provided with the ICT whether provided separately or integrated within the ICT shall list and explain how to use the accessibility and compatibility features of the ICT.</p>
<p>NOTE: Accessibility and compatibility features include accessibility features that are built-in and accessibility features that provide compatibility with assistive technology.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa464604e"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa464604e" aria-hidden="true" data-number="12.1.2" />12.1.2 Accessible documentation</label>
<div>
<p>Product documentation provided with the ICT shall be made available in at least one of the following electronic formats:</p>
<ol>
<li>a Web format that conforms to the requirements of clause 9, or</li>
<li>a non-web format that conforms to the requirements of clause 10.</li>
</ol>
<p>NOTE 1: This does not preclude the possibility of also providing the product documentation in other formats (electronic or printed) that are not accessible.</p>
<p>NOTE 2: It also does not preclude the possibility of providing alternate formats that meet the needs of some specific type of users (e.g. Braille documents for blind people or easy-to-read information for persons with cognitive impairments).</p>
<p>NOTE 3: Where the documentation is integral to the ICT it will be provided through the user interface which is accessible.</p>
<p>NOTE 4: A user agent that supports automatic media conversion would be beneficial to enhancing accessibility.</p>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa464604f"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa464604f" aria-hidden="true" data-number="12.2" />12.2 Support services</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646050"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646050" aria-hidden="true" data-number="12.2.1" />12.2.1 General (informative)</label>
<div>
<p>ICT support services include, but are not limited to: help desks, call centres, technical support, relay services and training services.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646051"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646051" aria-hidden="true" data-number="12.2.2" />12.2.2 Information on accessibility and compatibility features</label>
<div>
<p>ICT support services shall provide information on the accessibility and compatibility features that are included in the product documentation.</p>
<p>NOTE: Accessibility and compatibility features include accessibility features that are built-in and accessibility features that provide compatibility with assistive technology.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646052"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646052" aria-hidden="true" data-number="12.2.3" />12.2.3 Effective communication</label>
<div>
<p>ICT support services shall accommodate the communication needs of individuals with disabilities either directly or through a referral point.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646053"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646053" aria-hidden="true" data-number="12.2.4" />12.2.4 Accessible documentation</label>
<div>
<p>Documentation provided by support services shall be made available in at least one of the following electronic formats:</p>
<ol>
<li>a Web format that conforms to clause 9; or</li>
<li>a non-web format that conforms to clause 10.</li>
</ol>
<p>NOTE 1: This does not preclude the possibility of also providing the documentation in other formats (electronic or printed) that are not accessible.</p>
<p>NOTE 2: It also does not preclude the possibility of providing alternate formats that meet the needs of some specific type of users (e.g. Braille documents for blind people or easy-to-read information for persons with cognitive impairments).</p>
<p>NOTE 3: A user agent that supports automatic media conversion would be beneficial to enhancing accessibility.</p>
</div>
</div>
</li>
</ul>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646054"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646054" aria-hidden="true" data-number="13" />13 ICT providing relay or emergency service access</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646055"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646055" aria-hidden="true" data-number="13.1" />13.1 Relay services requirements</label></div>
<ul role="group">
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646056"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646056" aria-hidden="true" data-number="13.1.1" />13.1.1 General (informative)</label>
<div>
<p>Relay services enable users of different modes of communication e.g. text, sign, speech, to interact remotely through ICT with two-way communication by providing conversion between the modes of communication, normally by a human operator.</p>
<p>It is best practice to meet the applicable relay service requirements of ETSI ES 202 975 [i.5].</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646057"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646057" aria-hidden="true" data-number="13.1.2" />13.1.2 Text relay services</label>
<div>
<p>Where ICT is intended to provide a text relay service, the text relay service shall enable text users and speech users to interact by providing conversion between the two modes of communication.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646058"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646058" aria-hidden="true" data-number="13.1.3" />13.1.3 Sign relay services</label>
<div>
<p>Where ICT is intended to provide a sign relay service, the sign relay service shall enable sign language users and speech users to interact by providing conversion between the two modes of communication.</p>
<p>NOTE: Sign relay services are also sometimes referred to as sign language relay services or video relay services.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa4646059"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa4646059" aria-hidden="true" data-number="13.1.4" />13.1.4 Lip-reading relay services</label>
<div>
<p>Where ICT is intended to provide a lip-reading relay service, the lip-reading service shall enable lip-readers and voice telephone users to interact by providing conversion between the two modes of communication.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa464605a"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa464605a" aria-hidden="true" data-number="13.1.5" />13.1.5 Captioned telephony services</label>
<div>
<p>Where ICT is intended to provide a captioned telephony service, the captioned telephony service shall assist a deaf or hard of hearing user in a spoken dialogue by providing text captions translating the incoming part of the conversation.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa464605b"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa464605b" aria-hidden="true" data-number="13.1.6" />13.1.6 Speech to speech relay services</label>
<div>
<p>Where ICT is intended to provide a speech to speech relay service, the speech to speech relay service shall enable speech or cognitively impaired telephone users and any other user to communicate by providing assistance between them.</p>
</div>
</div>
</li>
</ul>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa464605c"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa464605c" aria-hidden="true" data-number="13.2" />13.2 Access to relay services</label>
<div>
<p>Where ICT systems support two-way communication and a set of relay services for such communication is specified, access to those relay services shall not be prevented for outgoing and incoming calls.</p>
<p>NOTE 1: Two-way communication may include voice, real-time text, or video, singly or in combinations supported by both the relay service and the ICT system.</p>
<p>NOTE 2: The purpose of this requirement is to achieve functionally equivalent communication access by persons with disabilities.</p>
</div>
</div>
</li>
<li role="treeitem" aria-expanded="false">
<div><label for="5d94c4763a40e40aa464605d"><input tabindex="-1" name="clauses" type="checkbox" value="5d94c4763a40e40aa464605d" aria-hidden="true" data-number="13.3" />13.3 Access to emergency services</label>
<div>
<p>Where ICT systems support two-way communication and a set of emergency services for such communication is specified, access to those emergency services shall not be prevented for outgoing and incoming calls.</p>
<p>NOTE 1: Two-way communication may include voice, real-time text, or video, singly or in combinations supported by both the emergency service and the ICT system.</p>
<p>NOTE 2: The purpose of this requirement is to achieve functionally equivalent communication access to the emergency service by persons with disabilities.</p>
</div>
</div>
</li>
</ul>
</li>
</ul>

</fieldset></section>



<div>
    <h1>
        <a name="_Information_additionelle"></a>
        <a name="_Renseignement_supplémentaire"></a>
        <a name="_Outil_et_ressources"></a>
        <a name="_Outils_et_ressources"></a>
        Outils et ressources
    </h1>
</div>
<h2>
    Normes et politiques de l’accessibilité
</h2>
<ul>
    <li>
        Secrétariat du Conseil du Trésor (SCT)
    </li>
</ul>
<p>
    o
    <a href="https://www.tbs-sct.gc.ca/pol/doc-fra.aspx?id=23601">
        Norme sur l'accessibilité des sites Web
    </a>
</p>
<p>
    o
    <a href="https://www.tbs-sct.gc.ca/pol/doc-fra.aspx?id=25875">
        Norme sur l’interopérabilité du Web
    </a>
</p>
<p>
    o
    <a href="https://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=27088">
        Norme sur l’optimisation des sites Web et des applications pour
        appareils mobiles
    </a>
</p>
<ul>
    <li>
        <a
            href="http://mandate376.standards.eu/standard/technical-requirements/"
        >
            EU Standard EN 301 549 – Accessible ICT Procurement Toolkit
        </a>
        [en anglais seulement]
    </li>
    <li>
        <a href="https://www.w3.org/TR/ATAG20/">
            Authoring Tool Accessibility Guidelines (ATAG) 2.0
        </a>
        [en anglais seulement]
    </li>
    <li>
        <a href="https://www.w3.org/TR/WCAG21/">
            W3C - Web Content Accessibility Guidelines 2.1
        </a>
        [en anglais seulement]
    </li>
    <li>
        <a
            href="https://www.gcpedia.gc.ca/wiki/Solution_de_gabarits_à_déploiement_centralisé_(SGDC)?setlang=fr&amp;uselang=fr"
        >
            Solution de gabarits à déploiement centralisé (SGDC)
        </a>
        [en anglais seulement]?
    </li>
    <li>
        <a
            href="https://www.canada.ca/fr/gouvernement/a-propos/systeme-conception.html"
        >
            Système de conception de Canada.ca
        </a>
    </li>
</ul>
<h2>
    <a name="_Ref19622421"></a>
    <a name="_Ref19866516">
        Échantillon de listes de vérification d'autoévaluation
    </a>
</h2>
<p>
    Ces outils aideront votre équipe de projet à satisfaire aux exigences
    d'accessibilité afin que l'accessibilité ne soit pas un obstacle pour votre
    projet.
</p>
<ul>
    <li>
        <a href="https://www.w3.org/WAI/fundamentals/accessibility-intro/">
            Introduction to Web Accessibility
        </a>
        [en anglais seulement]
    </li>
    <li>
        <a href="http://www.w3.org/WAI/WCAG21/quickref/">
            How to Meet WCAG (Quick Reference)
        </a>
        [en anglais seulement]
    </li>
    <li>
        <a href="https://www.w3.org/WAI/test-evaluate/preliminary/">
            A First Review of Web Accessibility
        </a>
        <a name="_Ref19867948"> [en anglais seulement]</a>
    </li>
    <li>
        <a href="http://www.w3.org/WAI/eval/report-tool/#/">
            Website Accessibility Evaluation Report Generator
        </a>
        [en anglais seulement]
    </li>
</ul>
<h2>
    Possibilités de formation
</h2>
<p>
    Veuillez visiter le site
    <a
        href="http://iservice.prv/fra/giti/A11E/outils_et_ressources/curriculum-accessibilite.shtml"
    >
        Programme de formation sur l'accessibilité pour la Direction générale
        de l'innovation, de l'information et de la technologie
    </a>
    pour obtenir une liste de cours sur l’accessibilité.
</p>