CINXE.COM

<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html lang="en" xmlns="http://www.w3.org/1999/xhtml" xml:lang="en"> <head> <meta http-equiv="content-type" content="text/html; charset=UTF-8" /> <title>User Agent Accessibility Guidelines (UAAG) 2.0</title> <style type="text/css"> .mobile-ex { background-color:#FCF; } .editor-notes {BORDER: red 1px solid;} h2.principle { background-color:#FFFFFF; border:thin solid #666666; color:#000000; font-weight:bold; padding:0.5em; } div.guideline { background-color:#CFE8EF !important; border: none; /* border:thin solid #000066; */ color:#000000; font-weight:bold; margin-bottom:0; padding:0.5em; } div.sc-level ul { margin-top: 0; margin-bottom: 0; margin-left:0.5em} div.sc-level { border-bottom:thin solid #666666; display:block; margin-left:1em; padding-bottom:0.25em; } h2.pr-title:after { content:": " } h2.pr-title, p.pr-text { display: inline; color: #000000;} h3.gl-title:after { content:": " } h3.gl-title, p.gl-text { display: inline; color: #000000;} /* h4.sc-title:after { content:": " } */ h4.sc-title, p.sc-text { display: inline;} h4.sc-title { margin-top: .5em; margin-bottom: .5em; font-size:.9em; } h4.sc span.sc-bullet { display:block; padding-left:1em; } p.sc-txt {margin-top: .25em; margin-bottom: 0} h5.implementing-heading { font-size:smaller; font-weight:bold; font-style:normal; margin-top: 0em; margin-bottom: 0.5em; } .diff-new { BACKGROUND-COLOR:#FFFF66 !important; } .proposed-text { BACKGROUND-COLOR:#FFCCFF !important; } .diff-old { color: white; BACKGROUND-COLOR:#663333; text-decoration:line-through; } .diff-chg { background-color:#98fb98 !important;} .diff-renumber{ font-weight:normal; color:#666666; font-size:x-small; } dfn { font-weight:bold; font-style:italic; } .glossary-note { font-weight:bold; } .glossary-adapted { font-weight:normal; color:#666666; font-size:x-small; } .glossary-adapted a{ font-weight:normal; color:#666666; font-size:x-small; } .figure { font-size:x-small; } DL { MARGIN-BOTTOM: 1em; } strong.handle { font-size: .9em; } em.note-handle { font-size: .9em; } .summary { margin: .5em; padding: 1em; font-weight:200; color:#000000; background-color:#FFFFFF; border:thin solid #666666; } ul.toc a { border-bottom:1px dotted #585858; color:#000000 !important; text-decoration:none; } div.toc ul.toc li a { margin-top:.3em; font-size:1.1em; font-weight:400; } div.toc ul.toc li ul.toc li a { margin-top:.3em; font-size:1.1em; font-weight:400; } div.toc ul.toc li ul.toc li ul.toc li a { margin-top:0; font-size:1em; font-weight:200; } ul.techs-only{ BORDER: black 1px solid; padding: 0.5em; MARGIN: 0.4em; list-style:none; } .dfn-instance { border-bottom:1px dotted #585858; color:#000000 !important; text-decoration:none; } h5.implementing-heading { font-size:0.9em; font-weight:bold; font-style:normal; margin-top: 0em; margin-bottom: 0.5em; } div.implementing-section { border: #DDDDDD 1px solid; margin-left: 0.5em; margin-top: 0.5em; padding:0.5em; } div.implementing-section p { margin-top: 0.5em; margin-bottom: 0.5em; } span.level { background-color:#FFFFBB; font-size: 0.9em; } div.implementing-link { font-size: 0.9em; margin-top: 0.5em; margin-left: 0.5em; } div.implementing-link a { background-color: #F4F4FF; border-color:#BBBBBB; border-style: solid; border-width: 1px; padding: 0.25em; } ul.sc-bullets { display:block; padding-left:2em; margin-top: 0em; margin-bottom: 0em; list-style-type:disc; } ol.sc-bullets { display:block; padding-left:2em; margin-top: 0em; margin-bottom: 0em; } ul.sc-notes { display:block; padding-left:1em; margin-top: 0em; list-style-type: none; } </style> <link rel="stylesheet" type="text/css" href="https://www.w3.org/StyleSheets/TR/W3C-WG-NOTE" /> </head> <body> <div class="gl-only"> <p align="center">[<a href="#toc">Table of Contents</a>] | [<a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/">UAAG 2.0 Reference</a>]</p> <div class="head"> <a href="https://www.w3.org/"><img height="48" src="https://www.w3.org/Icons/w3c_home" width="72" alt="W3C" /></a> <h1><a name="title" id="title"></a>User Agent Accessibility Guidelines (UAAG) 2.0</h1> <h2><a name="w3c-doctype" id="w3c-doctype"></a>W3C Working Group Note 15 December 2015</h2> <dl> <dt>This version:</dt> <dd><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-20151215/">http://www.w3.org/TR/2015/NOTE-UAAG20-20151215/</a></dd> <dt>Latest version:</dt> <dd><a href="https://www.w3.org/TR/UAAG20/">http://www.w3.org/TR/UAAG20/</a></dd> <dt>Previous version:</dt> <dd><a href="https://www.w3.org/TR/2015/WD-UAAG20-20150915/">http://www.w3.org/TR/2015/WD-UAAG20-20150915/</a></dd> <dt>Latest Editor's Draft:</dt> <dd><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-20151215/">http://www.w3.org/TR/2015/NOTE-UAAG20-20151215/</a></dd> <dt>Editors:</dt> <dd>James Allan, Texas School for the Blind and Visually Impaired</dd> <dd>Greg Lowney, Lowney Access Research</dd> <dd>Kim Patch, Redstart Systems</dd> <dd>Jeanne Spellman, W3C/Web Accessibility Initiative </dd> </dl> <p class="copyright"><a href="https://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2015 <a href="https://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.eu/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>, <a href="http://ev.buaa.edu.cn/">Beihang</a>). W3C <a href="https://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="https://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="https://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p> <hr /> </div> </div> <div class="gl-only"> <h2 class="nonb"><a name="abstract" id="abstract">Abstract</a></h2> <p>UAAG 2.0 guides developers in designing <a class="dfn-instance" href="#def-user-agent" rel="glossary" title="definition: User agent">user agents</a> that make the web more accessible to people with disabilities. User agents include browsers, browser extensions, media players, readers and other applications that render <a class="dfn-instance" href="#def-content" rel="glossary" title="definition: Content">web content</a>. A user agent that follows UAAG 2.0 will improve accessibility through its own user interface and its ability to communicate with other technologies, including <a class="dfn-instance" href="#def-assistive-technology" rel="glossary" title="definition: Assistive technology">assistive technologies</a>. UAAG and supporting resources are also intended to meet the needs of different audiences, including developers, policy makers, and managers. All users, not just users with disabilities, will benefit from user agents that follow UAAG 2.0. </p> <p>In addition to helping developers of browsers and media players, UAAG 2.0 benefits developers of assistive technologies because it explains what types of information and control an assistive technology can expect from a user agent that follows UAAG 2.0. Assistive technologies not addressed directly by UAAG 2.0 (e.g. braille rendering) are still essential to ensuring web access for some users with disabilities.</p> <p>The "User Agent Accessibility Guidelines 2.0" (<acronym title="User Agent Accessibility Guidelines">UAAG</acronym> 2.0) is part of a series of accessibility guidelines published by the <acronym title="World Wide Web Consortium">W3C</acronym> <a href="https://www.w3.org/WAI/" title="Link to W3C-WAI">Web Accessibility Initiative</a> (<acronym title="Web Access Initiative">WAI</acronym>). UAAG is introduced in the <a rel="nofollow" href="https://www.w3.org/WAI/intro/uaag">User Agent Accessibility Guidelines (UAAG) Overview</a>.</p> <h2 class="nonb"><a name="status" id="status">Status of this Document</a></h2> <h3><a name="status-superseded" id="status-superseded"></a>May be Superseded</h3> <p><em>This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current <acronym title="the World Wide Web Consortium">W3C</acronym> publications and the latest revision of this technical report can be found in the <a href="https://www.w3.org/TR/"><acronym title="the World Wide Web Consortium">W3C</acronym> technical reports index</a> at http://www.w3.org/TR/.</em></p> <h3 id="W3C-WD">W3C Working Group Note of UAAG 2.0</h3> <p>This is a W3C Working Group Note of 15 December 2015 from the <a href="https://www.w3.org/WAI/UA/">User Agent Accessibility Guidelines Working Group</a> (UAWG). This Note was Recommendation track work that closed before entering the Candidate Recommendation (CR) phase. Contributing factors included insufficient resources for formal CR testing. A partial test suite is available, and at least two candidate implementations have been identified for 90% of the features, but not formally tested. </p> <ul> <li>UAAG 2.0 completed <a href="https://www.w3.org/TR/2013/WD-UAAG20-20131107/">Last Call</a> in 2013 and UAWG has published 2 subsequent working drafts in response to comments. </li> <li>UAAG 2.0 has received <a href="https://www.w3.org/WAI/UA/2015/UAAGwideReview.html">wide review</a> with 246 issues raised from 37 organizations or individuals representing browsers, media players, W3C working groups, and accessibility experts.</li> <li>All comments and issues have been resolved and there are no outstanding objections to UAAG 2.0.</li> <li>There are 3 features at risk where no implementations have been identified <ul> <li>1.4.5 Default to Platform Text Settings (examples of high contrast, but not text settings)</li> <li>2.2.4 Options for Wrapping in Navigation</li> <li>3.1.6 Form Submission Confirm</li> </ul> </li> </ul> <p>UAAG 2.0 addresses barriers for people with disabilities that could be improved or solved with greater user agent accessibility. UAWG hopes that publication of this Note will provide user agent developers, people with disabilities, accessibility experts, and other involved parties a useful reference for improving the accessibility of user agents.</p> <p><a name="status-changes" id="status-changes"></a>Important changes to this document since the previous version are highlighted below. A <a href="http://services.w3.org/htmldiff?doc1=http%3A//www.w3.org/TR/2015/WD-UAAG20-20150915/&doc2=http%3A//www.w3.org/TR/2015/NOTE-UAAG20-20151215/">diff document of all changes</a> is available.</p> <ul> <li> <p>Changed term "Content Specifications" in 5.1.2 Implement Accessibility Features of Content Specifications to "Web Content Technology Specifications"</p> </li> </ul> <p>Comments on the Note should be sent to <a href="mailto:public-uaag2-comments@w3.org">public-uaag2-comments@w3.org</a> (<a href="http://lists.w3.org/Archives/Public/public-uaag2-comments/">Public Archive</a>). Although the UAWG is closing and will not respond to comments, comments can provide useful input for future work in this area. </p> <h3><a name="status-wai" id="status-wai"></a>Web Accessibility Initiative</h3> <p>This document has been produced as part of the <acronym title="World Wide Web Consortium">W3C</acronym> <a href="https://www.w3.org/WAI/">Web Accessibility Initiative</a> (WAI). The goals of the User Agent Working Group (UAWG) are discussed in the <a href="https://www.w3.org/WAI/UA/2010/uawg_charter.html">Working Group charter</a>. </p> <h3><a name="status-no-endorsement" id="status-no-endorsement"></a>No Endorsement</h3> <p>Publication as a Working Group Note does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.</p> <h3><a name="status-patents" id="status-patents"></a>Patents</h3> <p> This document was produced by a group operating under the <a href="https://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 W3C Patent Policy</a>. W3C maintains a <a rel="disclosure" href="https://www.w3.org/2004/01/pp-impl/36791/status">public list of any patent disclosures</a> made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains <a href="https://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a> must disclose the information in accordance with <a href="https://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section 6 of the W3C Patent Policy</a>.</p> <p>This document is governed by the <a id="w3c_process_revision" href="https://www.w3.org/2015/Process-20150901/">1 September 2015 W3C Process Document</a>. </p> <hr /> </div>  <div class="toc"> <h2><a name="toc" id="toc">Table of Contents</a></h2> <ul class="toc"> <li><a href="#abstract">Abstract</a></li> <li><a href="#status">Status of this Document</a></li> <li><a href="#introduction">Introduction</a> <ul class="toc"> <li class="gl-only"><a href="#conceptual_overview">Overview</a></li> <li class="gl-only"><a href="#layers_guide">UAAG 2.0 Layers of Guidance</a></li> <li class="gl-only"><a href="#supporting_docs">UAAG 2.0 Supporting Documents</a></li> <li class="gl-only"><a href="#intro-components">Components of Web Accessibility</a></li> <li><a href="#intro-conf-levels">Levels of Conformance</a></li> <li class="gl-only"><a href="#intro-wcag">Relationship with Web Content Accessibility Guidelines(WCAG) 2.0 </a></li> <li class="gl-only"><a href="#intro-atag">Relationship with Authoring Tool Accessibility Guidelines (ATAG) 2.0 </a></li> </ul> </li> <li><a href="#Guidelines">UAAG 2.0 Guidelines</a> <ul class="toc"> <li><a href="#applicability-notes">UAAG 2.0 Conformance Applicability Notes</a></li> <li><a href="#principle-perceivable">PRINCIPLE 1: Perceivable</a> <ul class="toc"> <li><a href="#gl-access-alternative-content">Guideline 1.1: Alternative content</a></li> <li><a href="#gl-missing-alt">Guideline 1.2: Missing content</a> </li> <li><a href="#gl-interaction-highlight">Guideline 1.3: Highlighting</a></li> <li><a href="#gl-text-config">Guideline 1.4: Text configuration</a></li> <li><a href="#gl-volume-config">Guideline 1.5: Volume configuration</a></li> <li><a href="#gl-speech-config">Guideline 1.6: Synthesized speech configuration</a></li> <li><a href="#gl-style-sheets-config">Guideline 1.7: User style sheet configuration</a></li> <li><a href="#gl-viewport-orient">Guideline 1.8: Orientation in viewports</a></li> <li><a href="#gl-alternative-views">Guideline 1.9: Alternative views</a></li> <li><a href="#gl-info-link">Guideline 1.10: Element Information</a></li> </ul> </li> <li><a href="#principle-operable">PRINCIPLE 2: Operable</a> <ul class="toc"> <li><a href="#gl-keyboard-access">Guideline 2.1: Keyboard access</a></li> <li><a href="#gl-sequential-navigation">Guideline 2.2: Sequential navigation</a></li> <li><a href="#gl-direct-navigation-and-activation">Guideline 2.3: Direct navigation and activation</a></li> <li><a href="#gl-search-text">Guideline 2.4: Text Search</a></li> <li><a href="#gl-nav-structure">Guideline 2.5: Structural navigation</a></li> <li><a href="#gl-store-prefs">Guideline 2.6: Preference settings</a></li> <li><a href="#gl-configure-controls">Guideline 2.7: Graphical controls</a></li> <li><a href="#gl-time-independent">Guideline 2.8: Time-independent interaction</a></li> <li><a href="#gl-prevent-flash">Guideline 2.9: Flashing</a></li> <li><a href="#gl-control-inaccessible-content">Guideline 2.10: Time-based media</a></li> <li><a href="#gl-other-devices">Guideline 2.11: Other Input Devices</a></li> </ul> </li> <li><a href="#principle-understandable">PRINCIPLE 3: Understandable</a> <ul class="toc"> <li><a href="#gl-avoid-mistakes">Guideline 3.1: Mistakes</a> </li> <li><a href="#gl-doc-access-features">Guideline 3.2: Documentation</a></li> <li><a href="#gl-predictable-operation">Guideline 3.3: Predictable</a></li> </ul> </li> <li><a href="#principle-AT-access">PRINCIPLE 4: Programmatic access</a> <ul class="toc"> <li><a href="#gl-AT-access">Guideline 4.1: Assistive technology</a> </li> </ul> </li> <li><a href="#principle-follow-specs">PRINCIPLE 5: Specifications and conventions</a> <ul class="toc"> <li><a href="#gl-obs-env-conventions">Guideline 5.1: Follow specifications</a></li> </ul> </li> </ul> </li> <li><a href="#conformance">Conformance</a></li> <li>Appendix A: <a href="#glossary">Glossary</a></li> <li>Appendix B: <a href="#ref-this-doc">How to refer to UAAG 2.0 from other documents</a></li> <li>Appendix C: <a href="#references">References</a></li> <li>Appendix D: <a href="#acknowledgments">Acknowledgements</a></li> </ul> </div> <hr /> <h2><a name="introduction" id="introduction">Introduction</a></h2> <div class="gl-only"> <p>This document is divided into two types of sections. The <a class="dfn-instance" href="#def-normative" title="definition: Normative">normative</a> sections are: principles, guidelines, success criteria, notes, conformance, and glossary. These are required to claim conformance to UAAG 2.0. The other sections of this document, including this introduction, Appendix B, C and D, are <a class="dfn-instance" title="definition: informative" href="#def-informative">informative</a>. They explain and amplify the normative sections.</p> <p>A user agent is any software that retrieves, renders and facilitates end-user interaction with web content. User agents include web browsers, media players, <a href="#def-extension" class="dfn-instance">add-ons</a> (plug-ins & extensions), and web applications that help in retrieving, rendering and interacting with web content. UAAG 2.0 specifies requirements for <a class="dfn-instance" href="#def-user-agent" rel="glossary" title="definition: User agent">user agent</a> developers that will lower barriers to accessibility.</p> <p>For an introduction to UAAG, see the <a href="https://www.w3.org/WAI/intro/uaag.php">User Agent Accessibility Guidelines (UAAG) Overview</a>.</p> <h3 id="conceptual_overview">Overview</h3> <p>Improving accessibility means considering a wide range of disabilities. These include visual, auditory, physical, speech, cognitive, language, learning, neurological disabilities, and disabilities related to aging. The goal of UAAG 2.0 is to ensure that all users, including users with disabilities, have equal control over the environment they use to access the web.</p> <p>Some users have more than one disability, and the needs of different disabilities can conflict. Many UAAG 2.0 requirements use configuration preferences to ensure that a feature designed to improve accessibility for one user does not interfere with the needs of another user. To avoid overwhelming users with an abundance of configuration options, UAAG 2.0 includes requirements that promote clear documentation and ease of configuration. </p> <p>The UAWG expects that software that satisfies the requirements of UAAG 2.0 will be more flexible, manageable, extensible, and beneficial for a broad range of users. </p> <h3 id="layers_guide">UAAG 2.0 Layers of Guidance</h3> <p>In order to meet the needs of different audiences, UAAG provides three layers of guidance: overall <strong>principles</strong>, general <strong>guidelines</strong>, and testable <strong>success criteria</strong>. There is more detail for each success criterion in a separate document, <a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/">UAAG 2.0 Reference</a>, including explanatory intent, examples of how the criterion can apply in different user situations, and links to resources. </p> <ol> <li><strong>Principles</strong> – Five principles provide a foundation for accessible user agents. Principles 1, 2, and 3 are parallel to <a href="https://www.w3.org/WAI/intro/wcag">Web Content Accessibility Guidelines (WCAG) 2.0</a>. Principles 4 and 5 are specific to user agents. <ul> <li>Principle 1 ensures that the user agent is perceivable, so users can access user agent output</li> <li>Principle 2 ensures that the user agent is operable, so users can communicate with the user agent</li> <li>Principle 3 ensures that the user agent is understandable, so users know what to do to use the user agent</li> <li>Principle 4 ensures that assistive technologies can access user agent controls</li> <li>Principle 5 ensures that user agents comply with other accessibility specifications (e.g WCAG) and platform conventions (e.g. Windows, iOS, Linux, Blackberry). </li></ul></li> <li><strong>Guidelines</strong> – Under each principle is a set of guidelines for making user agents more accessible to users with disabilities. These guidelines provide a framework to help authors understand the objectives for success criteria so they can better implement them. </li> <li><strong>Success Criteria</strong> – Under each guideline is a set of testable success criteria that can be used wherever conformance testing is necessary, including design specification, purchasing, regulation, and contractual agreements. <br /> <br /> Each success criterion is assigned a level. The levels are designed to meet the needs of different groups and different situations: A (minimum conformance), AA (recommended conformance), and AAA ( advanced conformance). Additional information on UAAG levels can be found in the <a href="https://www.w3.org/TR/2015/NOTE-UAAG20-20151215/#intro-conf-levels">Levels of Conformance</a> section.</li> </ol> <h3 id="supporting_docs">UAAG 2.0 Supporting Documents</h3> <p><strong>A separate document, entitled <em>UAAG 2.0 Reference: Explanations, Examples, and Resources for User Agent Accessibility Guidelines 2.0</em></strong> (hereafter referred to as the "Reference document") provides explanations and examples of how each success criteria might be satisfied. It also includes references to other accessibility resources (such as platform-specific software accessibility guidelines) that provide additional information on how a user agent can satisfy each success criteria. The examples in <em>UAAG 2.0 Reference</em> are <a class="dfn-instance" href="#def-informative" rel="glossary" title="definition: informative">informative</a> only. Other strategies can be used or required to satisfy the success criteria. The <acronym>UAWG</acronym> expects to update<em> UAAG 2.0 Reference</em> more frequently than the <em>User Agent Accessibility Guidelines 2.0</em>. Developers, W3C Working Groups, users, and others are encouraged to contribute examples and resources to <em>UAAG 2.0 Reference</em>. </p> <h3><a name="intro-components" id="intro-components"></a>Components of Web Accessibility</h3> <p>Web accessibility depends on both accessible user agents and accessible content. The level of accessibility of content is largely influenced by the authoring tool used to create it. For an overview of how these components of web development and interaction work together, see</p> <ul> <li><strong><a href="https://www.w3.org/WAI/intro/components">Essential Components of Web Accessibility</a></strong></li> <li><strong><a href="https://www.w3.org/WAI/intro/wcag.php">Web Content Accessibility Guidelines (WCAG) Overview</a></strong></li> <li><strong><a href="https://www.w3.org/WAI/intro/atag.php">Authoring Tool Accessibility Guidelines (ATAG) Overview</a></strong></li> </ul> <p>Additional information about the relationship between UAAG 2.0 and ATAG 2.0, and the relationship between UAAG 2.0 and WCAG 2.0, is in the sections on <a href="https://www.w3.org/TR/2015/NOTE-UAAG20-20151215/#intro-atag">Relationship with ATAG</a> and <a href="https://www.w3.org/TR/2015/NOTE-UAAG20-20151215/#intro-wcag">Relationship with WCAG</a>. </p> </div> <div> <h3><a name="intro-conf-levels" id="intro-conf-levels"></a>Levels of Conformance</h3> <p>User agents can conform to UAAG 2.0 at one of three conformance levels: levels A (minimum), AA (recommended), and AAA (advanced). The three levels of UAAG 2.0 conformance are based on the corresponding level designations (A, AA, or AAA) of the individual success criteria (i.e., specific requirements). The user agent can conform to a level by meeting the success criteria of that level and the levels below it. </p> <ul> <li>Level A conformance: The user agent complies with all applicable level A success criteria. </li> <li>Level AA conformance: The user agent complies with all applicable level A and AA success criteria </li> <li>Level AAA conformance: The user agent complies with all applicable level A, AA, and AAA success criteria. </li> </ul> <p>UAAG 2.0 has many options that can be managed through preference settings. </p> <div class="gl-only"> <p>For details about what each level represents, how the levels were determined, and how user agent developers and managers can use the levels for prioritizing accessibility improvements and designing user interfaces, see <a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#intro-conf-levels">UAAG 2.0 Reference Levels of Conformance</a> .</p></div> </div>   <div class="gl-only"> <h3><a name="intro-wcag" id="intro-wcag"></a>Relationship to the Web Content Accessibility Guidelines (WCAG) 2.0</h3> <p>The W3C recommendation, <a href="https://www.w3.org/WAI/intro/wcag.php">Web Content Accessibility Guidelines (WCAG</a>), applies to all web content; UAAG provides additional advice on the application user interface. </p> <p>Some user agents are used to package web content into native applications, especially on mobile platforms. If the finished application is used to retrieve, render, and facilitate end-user interaction with web content of the end-users choosing, then the application should be considered a stand-alone user agent. If the finished application only renders a constrained set of content specified by the developer, then the application might not be considered a user agent. In both cases, the WCAG 2.0 Guidelines apply to the web content. If the application is not a user agent, application developers are not responsible for UAAG 2.0 requirements that extend beyond WCAG 2.0 requirements. For more detail, see the definition of <a class="dfn-instance" href="#def-user-agent" rel="glossary" title="definition: user agent">user agent</a>. </p> </div> <div class="gl-only"> <h3><a name="intro-atag" id="intro-atag"></a>Relationship to the Authoring Tool Accessibility Guidelines (ATAG) 2.0</h3> <p>While it is common to think of user agents retrieving and rendering web content for one group of people (end-users) that was previously authored by another group (authors), user agents are also frequently involved with the process of authoring content.</p> <p> For these cases, it is important for user agent developers to consider the application of another W3C-WAI Recommendation, the <a href="https://www.w3.org/WAI/intro/atag.php">Authoring Tool Accessibility Guidelines (ATAG)</a>. ATAG (currently 2.0 is in draft) provides guidance to the developers of tools regarding the accessibility of authoring interfaces to authors (ATAG 2.0 Part A) and ways in which all authors can be supported in producing accessible web content (ATAG 2.0 Part B). </p> <p>For more information on the role of user agents in web authoring see <a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#intro-atag-role">UAAG 2.0 Reference</a></p> </div> <h2><a name="Guidelines" id="Guidelines"></a>UAAG 2.0 Guidelines</h2> <div class="gl-only"> <p>The guidelines, success criteria, their notes, and the conformance applicability notes are <a class="dfn-instance" title="definition: Normative" href="#def-normative">normative</a>. Guideline summaries are <a class="dfn-instance" title="definition: Informative" href="#def-informative">informative</a>. </p> </div> <h3><a name="applicability-notes" id="applicability-notes"></a>UAAG 2.0 Conformance Applicability Notes:</h3> <p>The Conformance Applicability Notes are a list of normative conditions that apply broadly to many of the success criteria in these guidelines. Generally, the notes clarify how the success criteria would apply under certain circumstances. </p> <ol> <li><strong class="handle">Retrieved Content Only</strong>: UAAG 2.0 success criteria only apply to web content that has been retrieved by the user agent (e.g. if a user agent saves bandwidth by retrieving video element content only on demand, then captions associated with that video content do not need to be searchable as per 2.4.5 until the video is retrieved).</li> <li><strong class="handle">Current Content Only</strong>: At any point in time, UAAG 2.0 success criteria only apply to web content that has not been hidden or removed (e.g., a bookmark created as per <a href="#sc_1816">1.8.16</a> will no longer be operable if the content it refers to is hidden or removed).</li> <li><strong class="handle">Recognized Content Only: </strong>UAAG 2.0 success criteria only apply to web content and its behaviors that can be <a class="dfn-instance" href="#def-recognize" rel="glossary" title="definition: recognize">recognized</a> by user agents.</li> <li><strong class="handle">Optional Settings:</strong> Throughout UAAG 2.0, all required behaviors can be provided as optional preference settings unless a success criterion explicitly says otherwise. For example, if a success criterion requires high contrast between foreground text and its background, the user agent can also provide choices with low contrast. While it is preferred to have a required behavior as a default option, it does not need to be, unless the success criterion explicitly says otherwise.</li> <li><strong class="handle">RFC 2119 language not used: </strong>UAAG 2.0 does not use <a class="dfn-instance" href="#def-rfc2119" rel="glossary" title="definition: RFC 2119">RFC 2119</a> language (must, may, should) as it is not an interoperable specifications. Note, even if these terms appear from time to time they do not have any RFC 2119 implication.</li> <li><strong class="handle">Simultaneous satisfaction of success criteria: </strong>Users can access all behaviors required by UAAG 2.0 at the same time (e.g. when the user resizes the viewport per 1.8.8, content is reflowed per 1.8.6), except where those behaviors are mutually exclusive.</li> <li><strong class="handle">Vertical layout languages</strong>: When user agents render vertical layout languages (e.g. Mongolian, Han), success criteria normally relating to horizontal rendering should be applied to vertical rendering instead. </li> <li><strong class="handle"><a name="applicability-note-addons"></a>Add-ons (Extensions and Plug-ins):</strong> Success criteria can be met by a user agent alone or in conjunction with <a href="#def-extension" class="dfn-instance">add-on</a>s, as long as those are: <ol type="a"> <li>discoverable by the user</li> <li>no extra cost to the user</li> <li>easily installed (i.e. not requiring expert knowledge or editing of configuration files, databases, or registry entries)</li></ol> See <a href="#conformance-req-components">Components of UAAG 2.0 Conformance Claims</a>.</li> <li><strong class="handle"><a name="applicability-note-platform" id="applicability-note-platform"></a>Relationship with operating system or platform</strong>: The user agent does not need to implement every behavior itself. A required behavior can be provided by the platform, user agent, user agent <a href="#def-extension" class="dfn-instance">add-on</a>s, or potentially other layers. All are acceptable, as long as they are enumerated in the conformance claim. </li> <li><strong class="handle"><a name="applicabilitynote-platform_limitations" id="applicabilitynote-platform_limitations"></a>Platform limitations:</strong> If the platform (hardware or operating system) does not support a capability necessary for a given UAAG 2.0 success criterion, see <a href="#conformance-req-components">Components of UAAG 2.0 Conformance Claims</a> #8. </li> <li><strong class="handle">Override author settings for text configuration</strong>: All of the success criteria under guideline 1.4 allow users to override the text characteristics specified by authors, and override user agent defaults. </li> </ol> <div class="principle" id="p-1"> <h2 class="principle"><a name="principle-perceivable" id="principle-perceivable"></a>PRINCIPLE 1 - Ensure that the user interface and rendered content are perceivable</h2> <div class="guideline-box" id="g-1-1"> <h3 class="guideline"> <a name="gl-access-alternative-content" id="gl-access-alternative-content"></a> Guideline 1.1 - Provide access to alternative content <span class="gl-only">[<a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#gl-access-alternative-content">Reference for 1.1</a>] </span> </h3> <p class="summary" id="summary11"><strong>Summary</strong>: The user can choose to render any type of alternative content available (1.1.1) with an indicator that the alternative content is present (1.1.2) or a placeholder replacing the non-text content (1.1.3) . It's recommended that users can also choose at least one alternative, such as alt text, to be displayed by default (1.1.5). It's recommended that caption text or sign language alternative cannot obscure the video or the controls (1.1.4) and that the user can configure the text (1.1.6), size and position of media alternatives (1.1.7).</p> <div class="sc-level"> <h4 class="sc-title"><a id="sc_111" name="sc_111"></a>1.1.1 Render Alternative Content: </h4> <p class="sc-text"> The user can choose to render any type of <a class="dfn-instance" href="#def-recognize" rel="glossary" title="definition: recognize">recognized</a> <a class="dfn-instance" href="#def-conditional-content" title="definition: Conditional content">alternative content</a> that is present for a content <a class="dfn-instance" href="#def-element" rel="glossary" title="definition: element">element</a>. <span class="level">(Level A)</span> </p> <ul class="sc-notes"> <li class="sc-note"><em class="note-handle">Note</em>: It is recommended that the <span class="sc-bullet"><a class="dfn-instance" href="#def-user-agent" rel="glossary" title="definition: User agent"> user agent</a></span> allow the user to choose whether the alternative content replaces or supplements the original content element.</li></ul> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_111">Reference for 1.1.1</a></div> </div> <h4 class="sc-title"><a id="sc_112" name="sc_112"></a>1.1.2 Indicate Unrendered Alternative Content: </h4> <p class="sc-text"> The user can specify that indicators be displayed along with rendered content when <a class="dfn-instance" href="#def-recognize" rel="glossary" title="definition: recognize">recognized</a> unrendered <a class="dfn-instance" href="#def-conditional-content" title="definition: Conditional content">alternative content</a> is present. <span class="level">(Level A)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_112">Reference for 1.1.2</a></div> </div> <h4 class="sc-title"><a id="sc_113" name="sc_113"></a>1.1.3 Replace Non-Text Content: </h4> <p class="sc-text"> The user can request a placeholder that incorporates <a class="dfn-instance" href="#def-recognize" rel="glossary" title="definition: recognize">recognized</a> text alternative content instead of recognized non-text content, until explicit user request to render the non-text content. <span class="level">(Level A)</span> </p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_113">Reference for 1.1.3</a></div> </div> <h4 class="sc-title"> <a id="sc_114" name="sc_114"></a>1.1.4 Facilitate Clear Display of Alternative Content for Time-based Media: </h4> <p class="sc-text">For <a class="dfn-instance" href="#def-recognize" rel="glossary" title="definition:recognized">recognized</a> on-screen alternative content for time-based media (e.g. captions, sign language video), the following are all true: <span class="level">(Level A)</span></p> <ul class="sc-bullets"> <li class="sc-bullet"> <strong class="handle">Don't obscure controls:</strong> Displaying time-based media alternatives doesn't <a class="dfn-obscure" href="#def-obscure" rel="glossary" title="definition: obscure">obscure</a> recognized controls for the primary time-based media.</li> <li class="sc-bullet"><strong class="handle">Don't obscure primary media:</strong> The user can specify that displaying time-based media alternatives doesn't obscure the primary time-based media. </li> </ul> <ul class="sc-notes"> <li class="sc-note"><em class="note-handle">Note</em>: Depending on the screen area available, the display of the primary time-based media can need to be reduced in size to meet this requirement. </li></ul> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_114">Reference for 1.1.4</a></div> </div> </div> <div class="sc-level"> <h4 class="sc-title"><a id="sc_115" name="sc_115"></a>1.1.5 Provide Configurable Alternative Content Defaults: </h4> <p class="sc-text">The user can specify which type(s) of <a class="dfn-instance" href="#def-conditional-content" title="definition: Conditional content">alternative content</a> to render by default for each type of non-text content, including time based media. <span class="level">(Level AA)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_115">Reference for 1.1.5</a></div> </div> <h4 class="sc-title"> <a id="sc_116" name="sc_116"></a>1.1.6 Use Configurable Text for Time-based Media Captions: </h4> <p class="sc-text">For <a class="dfn-instance" href="#def-recognize" rel="glossary" title="definition:recognized">recognized</a> on-screen alternative content for time-based media (e.g. captions, sign language video), t<span class="sc-bullet">he user can configure recognized text within time-based media alternatives (e.g. captions) in conformance with <a href="#sc_141">1.4.1</a>.</span> <span class="level">(Level AA)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_116">Reference for 1.1.6</a></div> </div> </div> <div class="sc-level"> <h4 class="sc-title"><a id="sc_117" name="sc_117"></a>1.1.7 Allow Resize and Reposition of Time-based Media Alternatives: </h4> <p class="sc-text">The user can configure <a class="dfn-instance" href="#def-recognize" rel="glossary" title="definition:recognized">recognized</a> alternative content for time-based media (e.g. captions, sign language video) as follows: <span class="level">(Level AAA)</span></p> <ul class="sc-bullets"> <li class="sc-bullet"><strong class="handle">Resize:</strong> The user can resize alternative content for time-based media to at least 50% of the size of the <a href="#def-viewport-toplevel" class="dfn-instance" title="definition: top-level viewport">top-level viewports</a>.</li> <li class="sc-bullet"><strong class="handle">Reposition:</strong> The user can reposition alternative content for time-based media to two or more of the following: above, below, to the right, to the left, and overlapping the primary time-based media.</li> </ul> <ul class="sc-notes"> <li class="sc-note"><em class="note-handle">Note 1:</em> Depending on the screen area available, the display of the primary time-based media can need to be reduced in size or hidden to meet this requirement. </li> <li class="sc-note"><em class="note-handle">Note 2:</em> Implementation can involve displaying alternative content for time-based media in a separate viewport, but this is not required. </li></ul> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_117">Reference for 1.1.7</a></div> </div> </div> </div> <div class="guideline-box" id="g-1-2"> <h3 class="guideline"> <a name="gl-missing-alt" id="gl-missing-alt"></a> Guideline 1.2 - Repair missing content <span class="gl-only">[<a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#gl-missing-alt">Reference for 1.2</a>] </span> </h3> <p class="summary" id="summary12"><strong>Summary</strong>: The user can request useful alternative content when the author fails to provide it. For example, showing metadata in place of missing or empty (1.2.1) alt text. The user can ask the browser to predict missing structural information, such as field labels, table headings or section headings (1.2.2).</p> <div class="sc-level"> <h4 class="sc-title"><a id="sc_121" name="sc_121"></a>1.2.1 Support Repair by Assistive Technologies: </h4> <p class="sc-text">If text alternatives for non-text content are missing or empty, the user agent doesn't attempt to repair the text alternatives by substituting text values that are also available to assistive technologies (e.g. image file name). <span class="level">(Level AA)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_121">Reference for 1.2.1</a></div> </div> </div> </div> <div class="guideline-box" id="g-1-3"> <h3 class="guideline"> <a name="gl-interaction-highlight" id="gl-interaction-highlight"></a> Guideline 1.3 - Provide highlighting for selection, keyboard focus, enabled elements, visited links <span class="gl-only">[<a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#gl-interaction-highlight">Reference for 1.3</a>] </span> </h3> <p class="summary" id="summary13"><strong>Summary</strong>: The user can visually distinguish between selected, focused, and enabled items; and recently visited links (1.3.1); with a choice of highlighting options that at least include foreground and background colors, and border color and thickness (1.3.2).</p> <div class="sc-level"> <h4 class="sc-title"><a id="sc_131" name="sc_131"></a>1.3.1 Distinguishable Highlighting: <span class="diff-old"></span></h4> <p class="sc-text">The user can have the following types of content uniquely highlighted, overriding any values specified by the author: <span class="level">(Level A)</span></p> <ul class="sc-bullets"> <li class="sc-bullet"><strong class="handle"></strong> Selection</li> <li class="sc-bullet">In-page search results</li> <li class="sc-bullet"><strong class="handle"></strong> <a href="#def-active-input-focus" class="dfn-instance" rel="glossary" title="definition:active input focus">Active keyboard focus</a> (indicated by focus cursors and/or text cursors)</li> <li class="sc-bullet"><strong class="handle"></strong> Unvisited links</li> <li class="sc-bullet"><strong class="handle"></strong>Visited links </li> </ul> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_131">Reference for 1.3.1</a></div> </div> </div> <div class="sc-level"> <h4 class="sc-title"><a id="sc_132" name="sc_132"></a>1.3.2 Highlighting Options: </h4> <p class="sc-text"> The user can set all of the following characteristics of selection highlighting, overriding any values specified by the author: <span class="level">(Level AA)</span> </p> <ul class="sc-bullets"> <li class="sc-bullet">Foreground color</li> <li class="sc-bullet">Background color</li> </ul> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_132">Reference for 1.3.2</a></div> </div> <h4 class="sc-title"><a id="sc_133" name="sc_133"></a>1.3.3 Highlighting Active Keyboard Focus: </h4> <p class="sc-text"> The user can set all of the following characteristics of active keyboard focus highlighting, overriding any values specified by the author: <span class="level">(Level AA)</span> </p> <ul class="sc-bullets"> <li class="sc-bullet">Foreground color</li> <li class="sc-bullet">Background color</li> <li class="sc-bullet">Border (color, style, and thickness)</li> <li class="sc-bullet">Text cursor blink rate</li> </ul> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_133">Reference for 1.3.3</a></div> </div> <h4 class="sc-title"><a id="sc_134" name="sc_134"></a>1.3.4 Distinguishing Enabled Elements: </h4> <p class="sc-text"> The user can set all of the following characteristics of enabled element highlighting, overriding any values specified by the author: <span class="level">(Level AA)</span> </p> <ul class="sc-bullets"> <li class="sc-bullet">Foreground color</li> <li class="sc-bullet">Background color</li> <li class="sc-bullet">Border (color, style, and thickness)</li> </ul> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_134">Reference for 1.3.4</a></div> </div> <h4 class="sc-title"><a id="sc_135" name="sc_135"></a>1.3.5 Distinguishing Enabled Elements: </h4> <p class="sc-text"> The user can set all of the following characteristics for visited links and separately for unvisited links, overriding any values specified by the author: <span class="level">(Level AA)</span> </p> <ul class="sc-bullets"> <li class="sc-bullet">Foreground color</li> <li class="sc-bullet">Underline</li> </ul> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_135">Reference for 1.3.5</a></div> </div> </div> </div> <div class="guideline-box" id="g-1-4"> <h3 class="guideline"> <a name="gl-text-config" id="gl-text-config"></a> Guideline 1.4 - Provide text configuration <span class="gl-only">[<a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#gl-text-config">Reference for 1.4</a>] </span> </h3> <p class="summary" id="summary14"><strong>Summary:</strong> The user can set text scale, color, style, line spacing, and font family globally (1.4.1, Level A). It is recommended that the user agent implement the user-selected text configuration settings of the platform (1.4.5 Level AA), users set text size, color, line spacing, text style and font family for element types (1.4.2, Level AA); set character spacing, justification and margin sizes globally (1.4.3, Level AA); set capitalization, hyphenation, and borders globally (1.4.6, Level AAA); and print configured and reflowed text (1.4.4 Level AA). </p> <p><em class="note-handle">Note 1</em>: The success criteria in guideline 1.4 can be met through user stylesheets. For platforms without user stylesheets, text configuration needs to be provided to users through the user agent's main user interface or via an add-on. </p> <p><em class="note-handle">Note 2:</em> Users have varying needs for text size and spacing. Therefore, it’s recommended that user agents provide a wider range of values, and a greater number of increments, to allow the user to adjust the view for their current task. </p> <div class="sc-level"> <h4 class="sc-title"><a id="sc_141" name="sc_141"></a>1.4.1 Basic text formatting (Globally): </h4> <p class="sc-text"> The user can <a class="dfn-instance" href="#def-global-configuration" rel="glossary" title="definition: globally">globally</a> set all of the following characteristics of visually <a class="dfn-instance" href="#def-rendered-text" title="definition: rendered text">rendered text</a> content: <span class="level">(Level A) </span> </p> <ul class="sc-bullets"> <li class="sc-bullet">Text scale with preserved size distinctions (e.g. keeping headings proportional to main font) </li> <li class="sc-bullet"> Text color and background color, choosing from all platform color options</li> <li class="sc-bullet">Font family, choosing from all installed fonts</li> <li class="sc-bullet">Line spacing, choosing from a range with at least three values up to at least 2 times the default</li> <li class="sc-bullet">Text style, choosing to turn on/off underline, italic, bold</li> </ul> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_141">Reference for 1.4.1</a></div> </div> </div> <div class="sc-level"> <h4 class="sc-title"><a id="sc_142" name="sc_142"></a>1.4.2 Basic text formatting (by Element): </h4> <p class="sc-text">The user can set all of the following characteristics of visually rendered text content for text element types including at least headings, input fields, and links: <span class="level">(Level AA) </span> </p> <ul class="sc-bullets"> <li>Text size (e.g. 18 point) or scale (e.g. 150%)</li> <li>Text color and background color, choosing from all platform color options</li> <li>Font family, choosing from at least all installed fonts </li> <li><span class="sc-bullet">Line spacing, choosing from a range with at least three values up to at least 2 times the default</span></li> <li><span class="sc-bullet">Text style, choosing to turn on/off underline, italic, bold</span></li> <li>Margins around blocks of text</li> <li>Borders</li> </ul> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_142">Reference for 1.4.2</a></div> </div> <h4 class="sc-title"><a id="sc_143" name="sc_143"></a>1.4.3 Blocks of text (Globally): </h4> <p class="sc-text">The user can <a class="dfn-instance" href="#def-global-configuration" rel="glossary" title="definition: globally">globally</a> set all of the following characteristics of visually rendered <a class="dfn-instance" href="#def-blocks-of-text" rel="glossary" title="definition: blocks of text">blocks of text</a>: <span class="level">(Level AA) </span> </p> <ul class="sc-bullets"> <li>Character spacing, choosing from a range with at least 5 values </li> <li>Justification (left or right, including turning off full justification)</li> <li>Margins around blocks of text</li> <li>Borders</li> </ul> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_143">Reference for 1.4.3</a></div> </div> <h4 class="sc-title"><a id="sc_144" name="sc_144"></a>1.4.4 Configured and Reflowed Text Printing: </h4> <p class="sc-text">The user can print the <a class="dfn-instance" href="#def-rendered-content" title="definition: Rendered content">rendered content</a>, and the following are all true: <span class="level">(Level AA)</span></p> <ul class="sc-bullets"> <li>any visual, non-time-based, rendered content can be printed </li> <li>the user can choose between <a class="dfn-instance" href="#def-printing-devices" rel="glossary" title="definition: available printing devices">available printing devices</a></li> <li>the user can have content printed as it is rendered on screen, reflecting any user scaling, highlighting, and other modifications</li> <li>the user can have printed content reflow as if the <a href="#def-viewport-toplevel" class="dfn-instance" title="definition: top-level viewport">top-level viewports</a> had been resized to match the horizontal dimension of the printing device's printable area</li> </ul> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_144">Reference for 1.4.4</a></div> </div> <h4 class="sc-title"><a id="sc_145" name="sc_145"></a>1.4.5 Default to platform text settings:</h4> <p class="sc-text"> The user can specify that platform text settings be used as the default values for text configuration. <span class="level">(Level AA)</span> </p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_145">Reference for 1.4.5</a></div> </div> </div> <div class="sc-level"> <h4 class="sc-title"><a id="sc_146" name="sc_146"></a>1.4.6 Advanced text formatting: </h4> <p class="sc-text">The user can <a class="dfn-instance" href="#def-global-configuration" rel="glossary" title="definition: globally">globally</a> set all of the following characteristics of visually rendered <a class="dfn-instance" href="#def-blocks-of-text" rel="glossary" title="definition: blocks of text">blocks of text</a>: <span class="level">(Level AAA) </span></p> <ul class="sc-bullets"> <li>Capitalization (overriding upper case and small caps style)</li> <li>Word-breaking properties (e.g. auto-hyphenation)</li> <li>Word spacing (choosing from a range of at least 5 values)</li> </ul> <p class="sc-notes"><em class="note-handle">Note:</em> This success criterion does not apply to text entered as all caps. Content authors are encouraged to use styles instead of typing text as all caps.</p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_146">Reference for 1.4.6</a></div> </div> </div> </div> <div class="guideline-box" id="g-1-5"> <h3 class="guideline"> <a name="gl-volume-config" id="gl-volume-config"></a> Guideline 1.5 - Provide volume configuration <span class="gl-only">[<a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#gl-volume-config">Reference for 1.5</a>]</span> </h3> <p class="summary" id="summary15"><strong>Summary</strong>: The user can adjust the volume of each audio track relative to the global volume level (1.5.1).</p> <div class="sc-level"> <h4 class="sc-title"><a id="sc_151" name="sc_151"></a>1.5.1 Global Volume: </h4> <p class="sc-text"> The user can adjust the volume of each <a class="dfn-instance" href="#def-audio-track" title="definition: Audio track">audio track</a> independently of other tracks, relative to the global volume level set through <a class="dfn-instance" href="#def-operating-environment" title="definition: Operating environment">operating environment</a> mechanisms. <span class="level">(Level A)</span> </p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_151">Reference for 1.5.1</a></div> </div> </div> </div> <div class="guideline-box" id="g-1-6"> <h3 class="guideline"> <a name="gl-speech-config" id="gl-speech-config"></a> Guideline 1.6 - Provide synthesized speech configuration <span class="gl-only">[<a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#gl-speech-config">Reference for 1.6</a>] </span> </h3> <p class="summary" id="summary16"><strong>Summary</strong>: If synthesized speech is produced, the user can specify speech rate, volume, and voice (1.6.1, Level A), pitch and pitch range (1.6.2, Level AA), advanced synthesizer speech characteristics such as emphasis (1.6.3, Level AAA) and features such as spelling (1.6.3, Level AAA).</p> <p class="sc-notes"><em class="note-handle">Note</em>: If browsers provide speech output for mainstream users, they should make the speech configurable enough to be usable by a wide range of individuals. When an add-on adds speech output to the user agent, it becomes part of the user agent, and therefore should meet the requirements of 1.6. </p> <div class="sc-level"> <h4 class="sc-title"><a id="sc_161" name="sc_161"></a>1.6.1 Speech Rate, Volume, and Voice: </h4> <p class="sc-text">If synthesized speech is produced, the user can specify the following: <span class="level">(Level A) </span> </p> <ul class="sc-bullets"> <li class="sc-bullet">Speech rate</li> <li class="sc-bullet">Speech volume (independently of other sources of <a class="dfn-instance" href="#def-audio" title="definition: Audio">audio</a>) </li> <li class="sc-bullet">Voice, when more than one voice is available</li> </ul> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_162">Reference for 1.6.1</a></div> </div> </div> <div class="sc-level"> <h4 class="sc-title"><a id="sc_162" name="sc_162"></a>1.6.2 Speech Pitch and Range: </h4> <p class="sc-text">If synthesized speech is produced, the user can specify the following if offered by the speech synthesizer: <span class="level">(Level AA)</span></p> <ul class="sc-bullets"> <li class="sc-bullet">Pitch (average frequency of the speaking voice)</li> <li class="sc-bullet"> Pitch range (variation in average frequency)</li> </ul> <ul class="sc-notes"> <li class="sc-note"><em class="note-handle">Note:</em> Because the technical implementations of text to speech engines vary (e.g. formant-based synthesis, concatenative synthesis), a specific engine may not support varying pitch or pitch range. A user agent should expose the availability of pitch and pitch range control if the currently selected or installed text to speech engine offers this capability.</li></ul> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_162">Reference for 1.6.2</a></div> </div> </div> <div class="sc-level"> <h4 class="sc-title"><a id="sc_163" name="sc_163"></a>1.6.3 Synthesized Speech Features: </h4> <p class="sc-text"> If synthesized speech is produced, the following features are provided: <span class="level">(Level AA)</span> </p> <ul class="sc-bullets"> <li class="sc-bullet"><strong class="handle">User-defined add-ons</strong> to the synthesized speech dictionary.</li> <li class="sc-bullet"><strong class="handle">"Spell-out":</strong> text is spelled one character at a time, or according to language-dependent pronunciation rules.</li> <li class="sc-bullet"><strong class="handle">At least two ways of speaking numerals: </strong> spoken as individual digits and punctuation (e.g. "one two zero three point five" for 1203.5 or "one comma two zero three point five" for 1,203.5), and spoken as full numbers are spoken (e.g. "one thousand, two hundred and three point five" for 1203.5).</li> <li class="sc-bullet"><strong class="handle">At least two ways of speaking punctuation:</strong> spoken literally, and with punctuation understood from speech characteristics like pauses.</li> </ul> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_163">Reference for 1.6.3</a></div> </div> <h4 class="sc-title"><a id="sc_164" name="sc_164"></a>1.6.4 Synthesized Speech Language: </h4> <p class="sc-text"> If synthesized speech is produced and more than one language is available, the user can change the language. <span class="level">(Level AA)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_164">Reference for 1.6.4</a></div> </div> </div> <div class="sc-level"> <h4 class="sc-title"><a id="sc_165" name="sc_165"></a>1.6.5 Advanced Speech Characteristics: </h4> <p class="sc-text"> If synthesized speech is produced, the user can adjust all of the speech characteristics provided by the speech synthesizer. <span class="level">(Level AAA)</span> </p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_165">Reference for 1.6.5</a></div> </div> </div> </div> <div class="guideline-box" id="g-1-7"> <h3 class="guideline"> <a name="gl-style-sheets-config" id="gl-style-sheets-config"></a> Guideline 1.7 - Enable configuration of user stylesheets <span class="gl-only">[<a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#gl-style-sheets-config">Reference for 1.7</a>] </span> </h3> <p class="summary" id="summary17"><strong>Summary</strong>: The user agent can disable author stylesheets (1.7.1, Level A) , supports user stylesheets or style mechanism (1.7.2, Level A), the user can choose which if any user-supplied (1.7.3, Level A) stylesheets to use, and the user can save stylesheets (1.7.4, Level AA).</p> <div class="sc-level"> <h4 class="sc-title"><a id="sc_171" name="sc_171"></a>1.7.1 Disable Author Stylesheets: </h4> <p class="sc-text">If the user agent supports a mechanism for <a class="dfn-instance" href="#def-author-styles" title="definition: author styles">author styles</a>, the user can disable the use of author styles on the current page. <span class="level">(Level A)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_171">Reference for 1.7.1</a></div> </div> <h4 class="sc-title"><a id="sc_172" name="sc_172"></a>1.7.2 Support User Stylesheet or User Style Modification Mechanism:</h4> If the user agent supports a mechanism for <a class="dfn-instance" href="#def-author-styles" title="definition: author styles">author styles</a>, the user agent also provides a mechanism for a user styling to override author styling. <span class="level">(Level A)</span> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_172">Reference for 1.7.2</a></div> </div> <h4 class="sc-title"><a id="sc_173" name="sc_173"></a>1.7.3 Apply User Stylesheets: </h4> <p class="sc-text"> If <a class="dfn-instance" href="#def-user-styles" title="definition: User Styles">user styles</a> are supported, then the user can enable or disable user styles for: <span class="level">(Level A)</span> </p> <ul class="sc-bullets"> <li class="sc-bullet">All pages on specified websites, or</li> <li class="sc-bullet">All pages</li> </ul> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_173">Reference for 1.7.3</a></div> </div> <h4 class="sc-title"><a id="sc_174" name="sc_174"></a>1.7.4 Save Copies of Stylesheets: </h4> <p class="sc-text">The user can save copies of the stylesheets referenced by the current page. This allows the user to edit and load the copies as user <a href="#def-stylesheet" title="definition: Stylesheet" class="dfn-instance">stylesheets</a>. <span class="level">(Level AA)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_174">Reference for 1.7.4</a></div> </div> </div> </div> <div class="guideline-box" id="g-1-8"> <h3 class="guideline"> <a name="gl-viewport-orient" id="gl-viewport-orient"></a> Guideline 1.8 - Help users to orient within, and control, windows and viewports <span class="gl-only">[<a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#gl-viewport-orient">Reference for 1.8</a>] </span> </h3> <p class="summary" id="summary18"><strong>Summary</strong>: The user agent provides programmatic and visual cues to keep the user oriented. These include highlighting the viewport (1.8.1, Level A) and customizing the highlighting attributes (1.8.7, Level AA), keeping the focus within the viewport (1.8.2 & 1.8.6, Level A), resizing the viewport (1.8.8, Level A), providing scrollbars that identify when content is outside the visible region (1.8.3, Level A) and which portion is visible (1.8.4, Level A), changing the size of graphical content with zoom (1.8.5, Level A & 1.8.7, Level A), and restoring the focus and point of regard when the user returns to a previously viewed page (1.8.9, Level AA). The user can specify that all viewports have the same user interface elements (1.8.12, Level AA), if and how new viewports open (1.8.10, Level AA), and whether the new viewport automatically gets focus (1.8.11, Level AA). The user can specify that multi-column text blocks be reflowed into a single column (1.8.13, Level AA), that the user can override absolute layout dimensions (1.8.14, Level AA), and linearize the content (1.8.15, Level AA). The user can mark items in a web page and use shortcuts to navigate back to marked items. (1.8.16, Level AAA). </p> <div class="sc-level"> <h4 class="sc-title"><a id="sc_181" name="sc_181"></a>1.8.1 Highlight Viewport: </h4> <p class="sc-text">The user can have the <a class="dfn-instance" href="#def-viewport" rel="glossary" title="definition: viewport">viewport</a> with the input focus be highlighted. <span class="level">(Level A) </span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_181">Reference for 1.8.1</a></div> </div> <h4 class="sc-title"><a id="sc_182" name="sc_182"></a>1.8.2 Move Viewport to Selection and Focus: </h4> <p class="sc-text"> When a viewport's <a class="dfn-instance" href="#def-selection" title="definition: Selection">selection</a> or <a class="dfn-instance" href="#def-input-focus" title="definition: input focus">input focus</a> changes, the <a class="dfn-instance" href="#def-viewport" title="definition: viewport">viewport</a>'s content moves as necessary to ensure that the new selection or input focus location is at least partially in the visible portion of the viewport. <span class="level">(Level A)</span> </p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_182">Reference for 1.8.2</a></div> </div> <h4 class="sc-title"><a id="sc_183" name="sc_183"></a>1.8.3 Provide Viewport Scrollbars: </h4> When the <a class="dfn-instance" href="#def-rendered-content" title="definition: Rendered content">rendered content</a> extends beyond the <a class="dfn-instance" href="#def-viewport" rel="glossary" title="definition: viewport">viewport</a> dimensions, users can have graphical viewports include scrollbars, <a class="dfn-instance" href="#def-override" title="definition: Override">overriding</a> any values specified by the author. <span class="level">(Level A)</span> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_183">Reference for 1.8.3</a></div> </div> <h4 class="sc-title"><a id="sc_184" name="sc_184"></a>1.8.4 Indicate Viewport Position: </h4> <p class="sc-text"> The user can determine the <a class="dfn-instance" href="#def-viewport" rel="glossary" title="definition: viewport">viewport</a>'s position relative to the full extent of the <a class="dfn-instance" href="#def-rendered-content" title="definition: Rendered content">rendered content</a>. <span class="level">(Level A)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_184">Reference for 1.8.4</a></div> </div> <h4 class="sc-title"><a id="sc_185" name="sc_185"></a>1.8.5 Allow Zoom: </h4> <p class="sc-text"> The user can rescale content within top-level graphical <a class="dfn-instance" href="#def-viewport" rel="glossary" title="definition: viewport">viewports</a> as follows: <span class="level">(Level A)</span></p> <ul class="sc-bullets"> <li class="sc-bullet"><strong class="handle">Zoom in:</strong> to 500% or more of the default size</li> <li class="sc-bullet"><strong class="handle">Zoom out:</strong> to 10% or less of the default size, so the content fits within the height or width of the viewport</li> </ul> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_185">Reference for 1.8.5</a></div> </div> <h4 class="sc-title"><a id="sc_186" name="sc_186"></a>1.8.6 Maintain Point of Regard: </h4> <p class="sc-text"> The <a class="dfn-instance" href="#def-point-of-regard" rel="glossary" title="definition: point of regard">point of regard</a> remains visible within the <a class="dfn-instance" href="#def-viewport" rel="glossary" title="definition: viewport">viewport</a> when the viewport is resized, when content is zoomed or scaled, or when content formatting is changed. <span class="level">(Level A)</span> </p> <ul class="sc-notes"><li><em class="note-handle">Note</em>: When the point of regard is larger than the viewport, the user agent keeps visible the beginning of the point of regard according to the current language's reading order (e.g. top-left in English)</li></ul> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_186">Reference for 1.8.6</a></div> </div> </div> <div class="sc-level"> <h4 class="sc-title"><a id="sc_187" name="sc_187"></a>1.8.7 Customize Viewport Highlighting: </h4> <p class="sc-text">When highlighting <a class="dfn-instance" href="#def-viewport" rel="glossary" title="definition: viewport">viewports</a> as specified by <a href="#sc_181">1.8.1 Highlight Viewport</a>, the user can customize attributes of the viewport highlighting mechanism (e.g. color and width of borders). <span class="level">(Level AA)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_187">Reference for 1.8.7</a></div> </div> <h4 class="sc-title"><a id="sc_188" name="sc_188"></a>1.8.8 Allow Viewport Resize: </h4> <p class="sc-text">The user can resize <a class="dfn-instance" href="#def-viewport" rel="glossary" title="definition: viewport"> viewports</a> within restrictions imposed by the platform, <a class="dfn-instance" href="#def-override" title="definition: Override">overriding</a> any values specified by the <a class="def-instance" title="definition: author" href="#def-author">author</a>. <span class="level">(Level AA)</span> </p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_188">Reference for 1.8.8</a></div> </div> <h4 class="sc-title"><a id="sc_189" name="sc_189"></a>1.8.9 Provide Viewport History: </h4> <p class="sc-text"> For <a class="dfn-instance" href="#def-user-agent" rel="glossary" title="definition: User agent">user agents </a> that implement a history mechanism for <a href="#def-viewport-toplevel" class="dfn-instance" title="definition: top-level viewport">top-level viewports</a> (e.g. "back" button), the user can return to any state in the viewport history that is allowed by the content, including: <span class="level">(Level AA)</span> </p> <ol type="a" class="sc-bullets"> <li>restored <a class="dfn-instance" href="#def-point-of-regard" rel="glossary" title="definition: point of regard">point of regard</a></li> <li>input focus, and</li> <li>user's form field entries</li> </ol> <ul class="sc-notes"> <li><em class="note-handle">Note</em>: It is recommended that selection also be restored.</li> </ul> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_189">Reference for 1.8.9</a></div> </div> <h4 class="sc-title"><a id="sc_1810" name="sc_1810"></a>1.8.10 Allow Top-Level Viewport Open on Request: </h4> <p class="sc-text">The user can specify whether author content can open new <a href="#def-viewport-toplevel" class="dfn-instance" title="definition: top-level viewport">top-level viewports</a> (e.g. windows or tabs). <span class="level">(Level AA)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_1810">Reference for 1.8.10</a></div> </div> <h4 class="sc-title"><a id="sc_1811" name="sc_1811"></a>1.8.11 Allow Top-Level Viewport Focus Control: </h4> <p class="sc-text"> If new <a href="#def-viewport-toplevel" class="dfn-instance" title="definition: top-level viewport">top-level viewports</a> (e.g. windows or tabs) are configured to open without explicit user request, the user can specify whether or not top-level viewports take the active <a class="dfn-instance" href="#def-keyboard-focus" title="definition: keyboard focus">keyboard focus</a> when they open. <span class="level">(Level AA)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_1811">Reference for 1.8.11</a></div> </div> <h4 class="sc-title"><a id="sc_1812" name="sc_1812"></a>1.8.12 Allow Same User Interface: </h4> <p class="sc-text"> The user can specify that all <a href="#def-viewport-toplevel" class="dfn-instance" title="definition: viewport">top-level viewports</a> (e.g. windows or tabs) follow the defined user interface configuration. <span class="level">(Level AA)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_1812">Reference for 1.8.12</a></div> </div> <h4 class="sc-title"><a id="sc_1813" name="sc_1813"></a>1.8.13 Multi-Column Text Reflow: </h4> <p class="sc-text">The user can specify that recognized multi-column text blocks each be reflowed into a single column. <span class="level">(Level AA)</span> </p> <ul class="sc-notes"><li class="sc-note"><em class="note-handle">Note:</em> Some layouts may become unusable if author-specified layout is overridden. In this case, the user can turn linearization off and try another strategy. It is recommended that user agents provide a convenient way for the user to turn this behavior on and off.</li></ul> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_1813">Reference for 1.8.13</a></div> </div> <h4 class="sc-title"><a id="sc_1814" name="sc_1814"></a>1.8.14 Ignore Fixed Unit Dimensions: </h4> <p class="sc-text">The user can have the user agent override author-specified unit dimensions. <span class="level">(Level AA)</span> </p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_1814">Reference for 1.8.14</a></div> </div> <h4 class="sc-title"><a id="sc_1815" name="sc_1815"></a>1.8.15 Linearize Content: </h4> <p class="sc-text">The user can have recognized content rendered as a single column, overriding author-specified formatting of columns, tables, and positioning. <span class="level">(Level AA)</span> </p> <p>Note: Some layouts may become unusable if author-specified layout is overridden. In this case, the user can turn linearization off and try another strategy. It is recommended that user agents provide a convenient way for the user to turn this behavior on and off.</p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_1815">Reference for 1.8.15</a></div> </div> </div> <div class="sc-level"> <h4 class="sc-title"><a id="sc_1816" name="sc_1816"></a>1.8.16 Provide Web Page Bookmarks: </h4> <p class="sc-text">The user can mark items in a web page, then use shortcuts to navigate back to marked items. The user can specify whether a navigation mark disappears after a session, or is persistent across sessions. <span class="level">(Level AAA)</span> </p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_1816">Reference for 1.8.16</a></div> </div> </div> </div> <div class="guideline-box" id="g-1-9"> <h3 class="guideline"> <a name="gl-alternative-views" id="gl-alternative-views"></a> Guideline 1.9 - Provide alternative views <span class="gl-only">[<a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#gl-alternative-views">Reference for 1.9</a>] </span> </h3> <p class="summary" id="summary110"><strong>Summary</strong>: The user can view the source of content (1.9.2, Level AAA), and an outline view of content. (1.9.1, Level AA).</p> <div class="sc-level"> <h4 class="sc-title"><a id="sc_191" name="sc_191"></a>1.9.1 Outline View: </h4> <p class="sc-text"> Users can view a navigable outline of the headings in <a class="dfn-instance" href="#def-rendered-content" title="definition: Rendered content">rendered content</a> that allows focus to be moved to the corresponding element in the main <a class="dfn-instance" href="#def-viewport" rel="glossary" title="definition: viewport">viewport</a>. <span class="diff-old"> </span><span class="level">(Level AA)</span> </p> <ul class="sc-notes"> <li class="sc-note"><em class="note-handle">Note:</em> Note: An outline view might also include other named elements such as document landmarks.</li></ul> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_191">Reference for 1.9.1</a></div> </div> <h4 class="sc-title"><a id="sc_192" name="sc_192"></a>1.9.2 Source View: </h4> <p class="sc-text"> The user can view all <a class="dfn-instance" href="#def-text-source" title="definition: text source">source text</a> that is available to the <a class="dfn-instance" href="#def-user-agent" rel="glossary" title="definition: User agent">user agent</a>. <span class="level">(Level AAA)</span> </p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_192">Reference for 1.9.2</a></div> </div> </div> </div> <div class="guideline-box" id="g-1-10"> <h3 class="guideline"> <a name="gl-info-link" id="gl-info-link"></a> Guideline 1.10 - Provide element information <span class="gl-only">[<a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#gl-info-link">Reference for 1.10</a>] </span> </h3> <p class="summary" id="summary111"><strong>Summary</strong>: The user can access information about relationships between elements (e.g. form labels, table headers) (1.10.1, Level AA), and extended link information (e.g. title, internal vs. external) (1.10.2, Level AAA)</p> <div class="sc-level"> <h4 class="sc-title"><a id="sc_1101" name="sc_1101"></a>1.10.1 Show Related Elements: </h4> <p class="sc-text"> The user can access the information from explicitly-defined relationships in the content, including at least the following: <span class="level">(Level AA)</span></p> <ol type="a"> <li>calculated accessible name for images</li> <li>calculated accessible name for controls (e.g. form fields, buttons)</li> <li>caption for a table</li> <li>row and column labels for a table cell</li> </ol> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_1101">Reference for 1.10.1</a></div> </div> <h4 class="sc-title"><a id="sc_1102" name="sc_1102"></a>1.10.2 Show Element Hierarchy: </h4> <p class="sc-text">The user can determine the path of element nodes going from the root element of the element hierarchy to the currently focused or selected element. <span class="level">(Level AAA)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_1102">Reference for 1.10.2</a></div> </div> </div> </div> </div> <div class="principle" id="p-2"> <h2 class="principle"><a name="principle-operable" id="principle-operable"></a>PRINCIPLE 2. Ensure that the user interface is operable</h2> <a name="intro-modality-independence" id="intro-modality-independence"></a> <ul class="sc-notes"> <li class="sc-notes"><em class="note-handle">Note</em>: <strong class="handle">Modality Independence</strong>: Users interacting with a web browser may do so using one or more input methods including keyboard, mouse, speech, touch, and gesture. It's critical that each user be free to use whatever input method, or combination of methods, works best for a given situation. If every potential user task is made accessible — so multiple modalities are supported — a user can choose what works best. For instance, if a user can't use or doesn't have access to a mouse, but can use and access a keyboard, the keyboard can call a modality independent control to activate an OnMouseOver event. Another example is a user on a mobile device that lacks keyboard who uses uses taps, wirelessly connected devices, and voice commands to simulate discrete or keyboard input. See <a href="https://www.w3.org/TR/indie-ui-events/">Independent User Interface: Events</a> for additional information on APIs and techniques for modality independent controls.</li> </ul> <div class="guideline-box" id="g-2-1"> <h3 class="guideline"> <a name="gl-keyboard-access" id="gl-keyboard-access"></a> Guideline 2.1 - Ensure full keyboard access <span class="gl-only">[<a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#gl-keyboard-access">Reference for 2.1</a>]</span> </h3> <p class="summary" id="summary21"><strong>Summary</strong>: Every viewport has a keyboard focus (2.1.2, Level A). Users can operate all functions using just the keyboard (2.1.1, Level A), activate important or common features with shortcut keys, (2.1.6, Level A), escape keyboard traps (2.1.3, Level A), specify that selecting an item in a dropdown list or menu not activate that item (2.1.4, Level A) and use standard keys for its platform (2.1.5, Level A).</p> <div class="sc-level"> <h4 class="sc-title"><a id="sc_211" name="sc_211"></a>2.1.1 Provide Full Keyboard Functionality: </h4> <p class="sc-text">All functionality can be operated via the <a class="dfn-instance" href="#def-keyboard" rel="glossary" title="definition: keyboard">keyboard</a> using sequential or direct keyboard commands that do not require 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 (e.g. free hand drawing). This does not forbid and should not discourage providing other input methods in addition to keyboard operation including mouse, touch, gesture and speech. <span class="level">(Level A)</span> </p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_211">Reference for 2.1.1</a></div> </div> <h4 class="sc-title"><a id="sc_212" name="sc_212"></a>2.1.2 Has Keyboard Focus: </h4> <p class="sc-text">Every <a class="dfn-instance" href="#def-viewport" title="definition: viewport">viewport</a> has an active or inactive <a class="dfn-instance" href="#def-keyboard-focus" title="definition: keyboard focus">keyboard focus</a> at all times. <span class="level">(Level A)</span> </p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_212">Reference for 2.1.2</a></div> </div> <h4 class="sc-title"><a id="sc_213" name="sc_213"></a>2.1.3 Avoid Keyboard Traps: </h4> <p class="sc-text"> If <a class="dfn-instance" href="#def-keyboard-focus" title="definition: keyboard focus">keyboard focus</a> can be moved to a component using a keyboard interface (including nested user agents), then focus can be moved away from that component using only a keyboard interface. If this requires more than unmodified arrow or Tab keys (or standard exit methods like Escape), users are advised of the method for moving focus away. <span class="level">(Level A)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_213">Reference for 2.1.3</a></div> </div> <h4 class="sc-title"><a id="sc_214" name="sc_214"></a>2.1.4 Separate Selection from Activation: </h4> <p class="sc-text">The user can specify that focus and selection can be moved without the user agent or author-supplied content further changing focus, selection, or the state of controls. <span class="level">(Level A)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_214">Reference for 2.1.4</a></div> </div> <h4 class="sc-title"><a id="sc_215" name="sc_215"></a>2.1.5 Follow Text Keyboard Conventions: </h4> <p class="sc-text">The user agent follows keyboard conventions for the <a class="dfn-instance" href="#def-operating-environment" title="definition: operating environment">operating environment</a>. <span class="level">(Level A)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_215">Reference for 2.1.5</a></div> </div> <h4 class="sc-title"><a id="sc_216" name="sc_216"></a>2.1.6 Make Keyboard Access Efficient: </h4> <p class="sc-text">The <a class="dfn-instance" href="#def-user-agent" rel="glossary" title="definition: User agent">user agent</a> user interface includes mechanisms to make keyboard access more efficient than sequential keyboard access. <span class="level">(Level A)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_216">Reference for 2.1.6</a></div> </div> </div> </div> <div class="guideline-box" id="g-2-2"> <h3 class="guideline"> <a name="gl-sequential-navigation" id="gl-sequential-navigation"></a> Guideline 2.2 - Provide sequential navigation <span class="gl-only">[<a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#gl-sequential-navigation">Reference for 2.2</a>] </span> </h3> <p class="summary" id="summary22"><strong>Summary</strong>:<strong> </strong>Users can use the keyboard to navigate sequentially to all the operable elements in the viewport (2.2.1, Level A) as well as between viewports (2.2.2, Level A), and the default navigation order is the document order (2.2.3, Level A). Users can optionally disable wrapping or request a signal when wrapping occurs (2.2.4, Level AA).</p> <div class="sc-level"> <h4 class="sc-title"><a id="sc_221" name="sc_221"></a>2.2.1 Sequential Navigation Between Elements: </h4> <p class="sc-text">The user can move the <a class="dfn-instance" href="#def-keyboard" rel="glossary" title="definition: keyboard">keyboard</a> focus backwards and forwards through all <a class="dfn-instance" href="#def-recognize" rel="glossary" title="definition:recognized">recognized</a> enabled elements in the <a class="dfn-instance" href="#def-rendered-content" title="definition: Rendered content">rendered content</a> of the current <a href="#def-viewport-toplevel" class="dfn-instance" title="definition: top-level viewport">top-level viewports</a>. <span class="level">(Level A)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_221">Reference for 2.2.1</a></div> </div> <h4 class="sc-title"><a id="sc_222" name="sc_222"></a>2.2.2 Sequential Navigation Between Landmarks: </h4>The user can move the keyboard focus backwards and forwards between regions identified by document landmarks. <span class="sc-text"><span class="level">(Level A)</span></span> <ul class="sc-notes"> <li><em class="note-handle">Note</em>: The user agent might also include other regions, such as viewports, in the sequential navigation.</li> </ul> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_222">Reference for 2.2.2</a></div> </div> <h4 class="sc-title"><a id="sc_223" name="sc_223"></a>2.2.3 Default Navigation Order: </h4> <p class="sc-text">If the author has not specified a navigation order, the user can have the default sequential navigation order be the source order. <span class="level">(Level AA)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_223">Reference for 2.2.3</a></div> </div> </div> <div class="sc-level"> <h4 class="sc-title"><a id="sc_224" name="sc_224"></a>2.2.4 Options for Wrapping in Navigation: </h4> <p class="sc-text"> The user can request notification when <a class="dfn-instance" href="#def-sequential-navigation" title="definition: sequential navigation">sequential navigation</a> wraps at the beginning or end of a document, and can prevent such wrapping. <span class="level">(Level AA)</span> </p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_224">Reference for 2.2.4</a></div> </div> </div> </div> <div class="guideline-box" id="g-2-3"> <h3 class="guideline"> <a name="gl-direct-navigation-and-activation" id="gl-direct-navigation-and-activation"></a> Guideline 2.3 - Provide direct navigation and activation <span class="gl-only">[<a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#gl-direct-navigation-and-activation">Reference for 2.3</a>]</span> </h3> <p class="summary" id="summary23"><strong>Summary</strong>: Users can navigate directly (e.g. using keyboard shortcuts) to elements (2.3.1, Level AA) with the option to immediately activate operable elements (2.3.2, Level AA). Display commands with the elements to make it easier for users to discover the commands (2.3.3 & 2.3.4, Level AA). The user can remap and save direct commands (2.3.5, Level AA).</p> <div class="sc-level"> <h4 class="sc-title"><a id="sc_231" name="sc_231"></a>2.3.1 Allow Direct Navigation to Enabled Elements: </h4> <p class="sc-text"> The user can move keyboard focus <a class="dfn-instance" href="#def-directly" rel="glossary" title="definition: directly">directly</a> to any <a class="dfn-instance" href="#def-enabled-element" rel="glossary" title="definition: enabled element">enabled element</a> in the <a class="dfn-instance" href="#def-rendered-content" title="definition: Rendered content">rendered content</a>. <span class="level">(Level AA)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_231">Reference for 2.3.1</a></div> </div> <h4 class="sc-title"><a id="sc_232" name="sc_232"></a>2.3.2 Allow Direct Activation of Enabled Elements: </h4> <p class="sc-text"> The user can, in a single action, move keyboard focus <a class="dfn-instance" href="#def-directly" rel="glossary" title="definition: directly">directly</a> to any <a class="dfn-instance" href="#def-enabled-element" rel="glossary" title="definition: enabled element">enabled element</a> in the <a class="dfn-instance" href="#def-rendered-content" title="definition: Rendered content">rendered content</a> and perform an activation action on that element. <span class="level">(Level AA)</span> </p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_232">Reference for 2.3.2</a></div> </div> <h4 class="sc-title"><a id="sc_233" name="sc_233"></a>2.3.3 Present Direct Commands from Rendered Content: </h4> <p class="sc-text"> The user can have any <a class="dfn-instance" href="#def-recognize" rel="glossary" title="definition:recognized">recognized</a> <a class="dfn-instance" href="#def-direct-command" rel="glossary" title="definition: direct command">direct commands</a> in <a class="dfn-instance" href="#def-rendered-content" title="definition: Rendered content">rendered content</a> (e.g. accesskey, landmark) be presented with their associated elements (e.g. Alt+R to reply to a web email). <span class="level">(Level AA)</span> </p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_233">Reference for 2.3.3</a></div> </div> <h4 class="sc-title"><a id="sc_234" name="sc_234"></a>2.3.4 Present Direct Commands in User Interface: </h4> <p class="sc-text"> The user can have any direct commands in the <a class="dfn-instance" href="#def-ua-ui" rel="glossary" title="definition: user agent user interface">UA user interface</a> (e.g. keyboard shortcuts) be presented with their associated user interface controls (e.g. "Ctrl+S" displayed on the "Save" menu item and toolbar button). <span class="level">(Level AA)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_234">Reference for 2.3.4</a></div> </div> <h4 class="sc-title"><a id="sc_235" name="sc_235"></a>2.3.5 Allow Customized Keyboard Commands: </h4> <p class="sc-text">The user can remap any <a class="dfn-instance" href="#def-keyboard-shortcut" rel="glossary" title="definition: keyboard shortcut">keyboard shortcut</a> including recognized author supplied shortcuts (e.g. accesskeys) and <a class="dfn-instance" href="#def-ua-ui" rel="glossary" title="definition: user agent user interface">UA user interface</a> controls, except for conventional bindings for the <a class="dfn-instance" href="#def-operating-environment" rel="glossary" title="definition: operating environment">operating environment</a> (e.g. arrow keys for navigating within menus). <span class="level">(Level AA)</span> </p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_235">Reference for 2.3.5</a></div> </div> </div> </div> <div class="guideline-box" id="g-2-4"> <h3 class="guideline"> <a name="gl-search-text" id="gl-search-text"></a> Guideline 2.4 - Provide text search <span class="gl-only">[<a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#gl-search-text">Reference for 2.4</a>] </span> </h3> <p class="summary" id="summary24"><strong>Summary</strong>: Users can search rendered content (2.4.1, Level A) forward or backward (2.4.2, Level A) and can have the matched content highlighted in the viewport (2.4.3, Level A). The user is notified in an accessible manner if there is no match (2.4.4, Level A). Users can also search by case and for text within alternative content (2.4.5, Level AA). </p> <div class="sc-level"> <h4 class="sc-title"><a id="sc_241" name="sc_241"></a>2.4.1 Text Search: </h4> <p class="sc-text">The user can perform a search within <a class="dfn-instance" href="#def-rendered-content" rel="glossary" title="definition: rendered content">rendered content</a>, including rendered text alternatives and rendered generated content, for any sequence of printing characters from the <a class="dfn-instance" href="#def-doc-char-set" title="definition: Document character set">document character set</a>. <span class="level">(Level A)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_241">Reference for 2.4.1</a></div> </div> <h4 class="sc-title"><a id="sc_242" name="sc_242"></a>2.4.2 Search Direction: </h4><p class="sc-text"> The user can search forward or backward in <a class="dfn-instance" href="#def-rendered-content" title="definition: Rendered content">rendered content</a>. <span class="level">(Level A)</span> </p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_242">Reference for 2.4.2</a></div> </div> <h4 class="sc-title"><a id="sc_243" name="sc_243"></a>2.4.3 Match Found: </h4> <p class="sc-text"> When a search operation produces a match, the matched content is <a class="dfn-instance" href="#def-highlight" rel="glossary" title="definition:highlight">highlighted</a>, the <a class="dfn-instance" href="#def-viewport" rel="glossary" title="definition: viewport">viewport</a> is scrolled if necessary so that the matched content is within its visible area, and the user can search from the location of the match. <span class="level">(Level A)</span> </p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_243">Reference for 2.4.3</a></div> </div> <h4 class="sc-title"><a id="sc_244" name="sc_244"></a>2.4.4 Alert on Wrap or No Match: </h4> <p class="sc-text">The user can choose to receive <a class="dfn-instance" href="#def-alert" title="definition: notify">notification</a> when there is no match to a search operation. The user can choose to receive notification when the search continues from the beginning or end of content. <span class="level">(Level A)</span> </p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_244">Reference for 2.4.4</a></div> </div> <h4 class="sc-title"><a id="sc_245" name="sc_245"></a>2.4.5 Alternative Content Search: </h4> <p class="sc-text">The user can perform text searches within alternative content that is text (e.g. <a class="dfn-instance" href="#def-conditional-content" title="definition: alternative content">text alternatives for non-text content</a>, captions) even when the alternative content is not rendered onscreen. <span class="level">(Level AA)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_245">Reference for 2.4.5</a></div> </div> </div> </div> <div class="guideline-box" id="g-2-5"> <h3 class="guideline"> <a name="gl-nav-structure" id="gl-nav-structure"></a> Guideline 2.5 - Provide structural navigation <span class="gl-only">[<a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#gl-nav-structure">Reference for 2.5</a>] </span> </h3> <p class="summary" id="summary25"><strong>Summary</strong>: Users can navigate (2.5.1, Level A) content hierarchy. </p> <div class="sc-level"> <h4 class="sc-title"><a id="sc_251" name="sc_251"></a>2.5.1 Provide Structural Navigation by Heading and within Tables: </h4> <p class="sc-text">The user agent provides at least the following types of <a class="dfn-instance" href="#def-structural-navigation" rel="glossary" title="definition: structural navigation">structural navigation</a>, where the structure types are recognized: <span class="level">(Level AA)</span></p> <ul class="sc-bullets"> <li class="sc-bullet">By heading</li> <li class="sc-bullet">By content sections</li> <li class="sc-bullet">Within tables</li> </ul> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_251">Reference for 2.5.1</a></div> </div> </div> </div> <div class="guideline-box" id="g-2-7"> <h3 class="guideline"> <a name="gl-store-prefs" id="gl-store-prefs"></a> Guideline 2.6 - Configure and store preference settings <span class="gl-only">[<a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#gl-store-prefs">Reference for 2.6</a>] </span> </h3> <p class="summary" id="summary27"><strong>Summary</strong>: Users can restore preference settings to default (2.6.2, Level A), and accessibility settings persist between sessions (2.6.1, Level A). Users can manage multiple sets of preference settings (2.6.3, Level AA), and adjust preference settings outside the user interface so the current user interface does not prevent access (2.6.4, Level AA), and transport settings to compatible systems (2.6.5, Level AA).</p> <div class="sc-level"> <h4 class="sc-title"><a id="sc_261" name="sc_261"></a>2.6.1 Allow Persistent Accessibility Settings: </h4> <p class="sc-text">User agent accessibility preference settings persist between sessions. <span class="level">(Level A)</span> </p> <ul class="sc-notes"> <li class="sc-note"><em class="note-handle">Note:</em> User agents may have a public access setting that turns this off. </li></ul> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_261">Reference for 2.6.1</a></div> </div> <h4 class="sc-title"><a id="sc_262" name="sc_262"></a>2.6.2 Allow Restore All to Default: </h4> <p class="sc-text">The user can restore all preference settings to default values. <span class="level">(Level A)</span> </p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_262">Reference for 2.6.2</a></div> </div> <h4 class="sc-title"><a id="sc_263" name="sc_263"></a>2.6.3 Allow Multiple Sets of Preference Settings: </h4> <p class="sc-text">The user can save and retrieve multiple sets of user agent preference settings. <span class="level">(Level AA)</span> </p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_263">Reference for 2.6.3</a></div> </div> <h4 class="sc-title"><a id="sc_264" name="sc_264"></a>2.6.4 Allow Preference Changes from outside the User Interface: </h4> <p class="sc-text">The user can adjust any preference settings required to meet the User Agent Accessibility Guidelines (UAAG) 2.0 from outside the <a class="dfn-instance" href="#def-ua-ui" rel="glossary" title="definition: user agent user interface">UA user interface</a>. <span class="level">(Level AAA)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_264">Reference for 2.6.4</a></div> </div> <h4 class="sc-title"><a id="sc_265" name="sc_265"></a>2.6.5 Make Preference Settings Transferable: </h4> <p class="sc-text">The user can transfer all compatible user agent preference settings between devices. <span class="level">(Level AAA)</span> </p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_265">Reference for 2.6.5</a></div> </div> </div> </div> <div class="guideline-box" id="g-2-8"> <h3 class="guideline"> <a name="gl-configure-controls" id="gl-configure-controls"></a> Guideline 2.7 - Customize display of graphical controls <span class="gl-only">[<a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#gl-configure-controls">Reference for 2.7</a>] </span> </h3> <p class="summary" id="summary28"><strong>Summary</strong>: It's recommended that users can add, remove, reposition, and assign shortcuts to user agent controls, and restore them to their default settings (2.7.1, Level AA).</p> <div class="sc-level"> <h4 class="sc-title"><a id="sc_271" name="sc_271"></a>2.7.1 Customize Display of Controls for User Interface Commands, Functions, and Add-ons: </h4> <p class="sc-text">The user can customize which user agent commands, functions, and add-ons are displayed within the user agent user interface as follows: <span class="level">(Level AA)</span> </p> <ul class="sc-bullets"> <li class="sc-bullet"><strong class="handle">Show:</strong> The user can choose to display any controls available within the user agent user interface, including user-installed add-ons. It is acceptable to limit the total number of controls that are displayed onscreen. </li> <li class="sc-bullet"><strong class="handle">Simplify:</strong> The user can simplify the default user interface by choosing to display only commands essential for basic operation (e.g. by hiding some controls). </li> <li class="sc-bullet"><strong class="handle">Reposition:</strong> The user can choose to reposition individual controls within containers (e.g. toolbars or tool palettes), as well as reposition the containers themselves to facilitate physical access (e.g. to minimize hand travel on touch screens, or to facilitate preferred hand access on handheld mobile devices). </li> <li class="sc-bullet"><strong class="handle">Assign Activation Keystrokes or Gestures:</strong> The user can choose to view, assign or change default keystrokes or gestures used to activate controls. </li> <li class="sc-bullet"><strong class="handle">Reset:</strong> The user has the option to reset the containers and controls to their default configuration. </li> </ul> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_271">Reference for 2.7.1</a></div> </div> </div> </div> <div class="guideline-box" id="g-2-9"> <h3 class="guideline"> <a name="gl-time-independent" id="gl-time-independent"></a> Guideline 2.8 - Allow time-independent interaction <span class="gl-only">[<a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#gl-time-independent">Reference for 2.8</a>] </span> </h3> <p class="summary" id="summary29"><strong>Summary</strong>: Users can extend the time limits for user input when such limits are controllable by the user agent (2.8.1, Level A). </p> <div class="sc-level"> <h4 class="sc-title"><a id="sc_281" name="sc_281"></a>2.8.1 Adjustable Time Limits: </h4> <p class="sc-text"> The <a class="dfn-instance" href="#def-ua-ui" rel="glossary" title="definition: user agent user interface">UA user interface</a> does not include time limits or at least one of the following is true: <span class="level">(Level A)</span> </p> <ol type="a"> <li><strong class="sc-bullet">Turn Off: </strong>Users are allowed to turn off the time limit before encountering it; or </li> <li><strong class="sc-bullet">Adjust:</strong> Users are 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><strong class="sc-bullet">Extend:</strong> Users are warned before time expires and given at least 20 seconds to extend the time limit with a simple action (e.g. "press the space bar"), and users are allowed to extend the time limit at least ten times; or</li> <li><strong class="sc-bullet">Real-time Exception:</strong> The time limit is a required part of a real-time event and no alternative to the time limit is possible; or</li> <li><strong class="sc-bullet">Essential Exception:</strong> The time limit is essential and extending it would invalidate the activity; or </li> <li><strong class="sc-bullet">20 Hour Exception:</strong> The time limit is longer than 20 hours. </li> </ol> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_281">Reference for 2.8.1</a></div> </div> </div> </div> <div class="guideline-box" id="g-2-10"> <h3 class="guideline"><a name="gl-prevent-flash" id="gl-prevent-flash"></a>Guideline 2.9 - Help users avoid flashing that could cause seizures <span class="gl-only">[<a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#gl-prevent-flash">Reference for 2.9</a>]</span> </h3> <p class="summary" id="summary210"><strong>Summary</strong>: To help users avoid seizures, the default configuration prevents the browser user interface from flashing more than three times a second above luminescence or color thresholds (2.9.1, Level A), or even below the thresholds (2.9.2, Level AAA). </p> <div class="sc-level"> <h4 class="sc-title"><a id="sc_291" name="sc_291"></a>2.9.1 Three Flashes or Below Threshold: </h4> <p class="sc-text">In its default configuration, the user agent does not display any UA user interface components that flashes more than three times in any one-second period, unless the flash is below general flash and red flash thresholds. <span class="level">(Level A)</span> </p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_291">Reference for 2.9.1</a></div> </div> </div> <div class="sc-level"> <h4 class="sc-title"><a id="sc_292" name="sc_292"></a>2.9.2 Three Flashes: </h4> <p class="sc-text">In its default configuration, the user agent does not display any UA user interface components that flashes more than three times in any one-second period (regardless of whether not the flash is below the general flash and red flash thresholds). <span class="level">(Level AAA)</span> </p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_292">Reference for 2.9.2</a></div> </div> </div> </div> <div class="guideline-box" id="g-2-11"> <h3 class="guideline"><a name="gl-control-inaccessible-content" id="gl-control-inaccessible-content">Guideline 2.10 - </a> Provide control of time-based media <span class="gl-only">[<a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#gl-control-inaccessible-content">Reference for 2.10</a>] </span> </h3> <p class="summary" id="summary211"><strong>Summary</strong>: The user can present placeholders for time-based media (2.10.1, Level A) and executable regions (2.10.2, Level A), or block all executable content (2.10.3, Level A), adjust playback (2.10.4, Level A), stop/pause/resume (2.10.5, Level A), navigate by time (2.10.6, Level A) or semantic structures such as chapter (2.10.7, Level AA). It is recommended that the user can adjust contrast and brightness of visual time-based media (2.10.8, Level AAA). Enable or disable tracks is included in <a href="#sc_111">1.1.1 Render Alternative Content</a>.</p> <div class="sc-level"> <h4 class="sc-title"><a id="sc_2101" name="sc_2101"></a>2.10.1 Time-Based Media Load-Only: </h4> <p class="sc-text">The user can override the play on load of <a class="dfn-instance" href="#def-recognize" rel="glossary" title="definition:recognized">recognized</a> time-based media content such that the content is not played until <a class="dfn-instance" href="#def-user-request" title="definition: Explicit user request">explicit user request</a>. <span class="level">(Level A)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_2101">Reference for 2.10.1</a></div> </div> <h4 class="sc-title"><a id="sc_2102" name="sc_2102"></a>2.10.2 Execution Placeholder: </h4> <p class="sc-text"> The user can request a <a href="#def-placeholder">placeholder</a> instead of executable content that would normally be contained within an on-screen area (e.g. Applet, Flash), until <a class="dfn-instance" href="#def-user-request" title="definition: Explicit user request">explicit user request</a> to execute. <span class="level">(Level A)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_2102">Reference for 2.10.2</a></div> </div> <h4 class="sc-title"><a id="sc_2103" name="sc_2103"></a>2.10.3 Execution Toggle: </h4> <p class="sc-text"> The user can turn on/off the execution of dynamic or executable content (e.g. Javascript, canvas, media). <span class="level">(Level A)</span> </p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_2103">Reference for 2.10.3</a></div> </div> <h4 class="sc-title"><a id="sc_2104" name="sc_2104"></a>2.10.4 Adjustable Playback Rate for Prerecorded Content: </h4> <p class="sc-text"> The user can adjust the playback rate of prerecorded time-based media content, such that all of the following are true: <span class="level">(Level AA)</span> </p> <ul class="sc-bullets"> <li class="sc-bullet"><strong class="handle">Playback Rate:</strong> The user can adjust the playback rate of the time-based media tracks to between 50% and 250% of real time. </li> <li class="sc-bullet"><strong class="handle">Pitch:</strong> Speech whose playback rate has been adjusted by the user maintains pitch in order to limit degradation of the speech quality.</li> <li class="sc-bullet"><strong class="handle">Synchronization:</strong> Audio and video tracks remain <a href="#def-synchronize" title="defintion: synchronize" class="dfn-instance">synchronized</a> across this required range of playback rates.</li> <li class="sc-bullet"><strong class="handle">Reset:</strong> The user agent provides a function that resets the playback rate to normal (100%).</li> </ul> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_2104">Reference for 2.10.4</a></div> </div> <h4 class="sc-title"><a id="sc_2105" name="sc_2105"></a>2.10.5 Stop/Pause/Resume Time-Based Media: </h4> <p class="sc-text"> The user can stop, pause, and resume rendered audio and <a class="dfn-instance" href="#def-animation" title="definition: Animation">animation</a> content (e.g video, animation, changing text) that lasts three or more seconds at the default playback rate. <span class="level">(Level A)</span> </p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_2105">Reference for 2.10.5</a></div> </div> <h4 class="sc-title"><a id="sc_2106" name="sc_2106"></a>2.10.6 Navigation of Time-Based Media by Time: </h4> <p class="sc-text"> If time-based media lasts three or more seconds at the default playback rate, the user can navigate it using a continuous scale and by <a class="dfn-instance" href="#def-relative-time-units" rel="glossary" title="definition: relative time units">relative time units</a>. <span class="level">(Level A)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_2106">Reference for 2.10.6</a></div> </div> </div> <div class="sc-level"> <h4 class="sc-title"><a id="sc_2107" name="sc_2107"></a>2.10.7 Navigation of Time-Based Media by Semantics: </h4> <p class="sc-text"> The user can navigate by semantic structure within the time-based media, such as by chapters or scenes present in the media. <span class="level">(Level AA)</span> </p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_2107">Reference for 2.10.7</a></div> </div> </div> <div class="sc-level"> <h4 class="sc-title"><a id="sc_2108" name="sc_2108"></a>2.10.8 Video Contrast and Brightness: </h4> <p class="sc-text"> Users can adjust the contrast and brightness of visual time-based media. <span class="level">(Level AAA)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_2108">Reference for 2.10.8</a></div> </div> </div> </div> <div class="guideline-box" id="g-2-12"> <h3 class="guideline"><a name="gl-other-devices" id="gl-other-devices">Guideline 2.11 - </a> Support other input devices <span class="gl-only">[<a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#gl-other-devices">Reference for 2.11</a>] </span> </h3> <p class="summary" id="summary212"><strong>Summary</strong>: User agents support platform text input devices including text input (2.11.1, Level AA). </p> <div class="sc-level"> <h4 class="sc-title"><a id="sc_2111" name="sc_2111"></a>2.11.1 Text Input With Any Device: </h4> <p class="sc-text"> If an input device is supported by the <a class="dfn-instance" href="#def-platform" rel="glossary" title="definition: platform">platform</a>, all user agent functionality including text input can be operated using that device. <span class="level">(Level AA)</span> </p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_2111">Reference for 2.11.1</a></div> </div> </div> </div> </div> <div class="principle" id="p-3"> <h2 class="principle"><a name="principle-understandable" id="principle-understandable"></a>PRINCIPLE 3: Ensure that the user interface is understandable</h2> <div class="guideline-box" id="g-3-2"> <h3 class="guideline"><a name="gl-avoid-mistakes" id="gl-avoid-mistakes">Guideline 3.1 - </a> Help users avoid and correct mistakes <span class="gl-only">[<a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#gl-avoid-mistakes">Reference for 3.1</a>] </span> </h3> <p class="summary" id="summary31"><strong>Summary</strong>: Users can undo text entry (3.1.1, Level A), avoid or undo settings changes (3.1.2, Level A), and receive indications of progress activity (3.1.3, Level A). It is recommended that users can have their text checked for spelling errors (3.1.4, Level AA), go back after navigating (3.1.5, Level AA), have form submissions require confirmation (3.1.6, Level AA), have auto-form fill of basic information (3.1.7, Level AA), and save form entry data with a local save (3.1.8, Level AA). </p> <div class="sc-level"> <h4 class="sc-title"><a id="sc_311" name="sc_311"></a>3.1.1 Text Entry Undo: </h4> <p class="sc-text"> The user can reverse <a class="dfn-instance" href="#def-recognize" rel="glossary" title="definition:recognized">recognized</a> text entry actions prior to submission. <span class="level">(Level A)</span> </p> <ul class="sc-notes"> <li class="sc-note"><em class="note-handle">Note:</em> Submission can be triggered in many different ways, such as clicking a submit button, typing a key in a control with an onkeypress event, or by a script responding to a timer. </li></ul> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_311">Reference for 3.1.1</a></div> </div> <h4 class="sc-title"><a id="sc_312" name="sc_312"></a>3.1.2 Settings Changes can be Reversed or Confirmed: </h4> <p class="sc-text"> If the user agent provides mechanisms for changing its user interface settings, it either allows the user to reverse the setting changes, or the user agent can require user confirmation to proceed. <span class="level">(Level A)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_312">Reference for 3.1.2</a></div> </div> <h4 class="sc-title"><a id="sc_313" name="sc_313"></a>3.1.3 Retrieval Progress: </h4> <p class="sc-text">By default, the user agent shows the state of content retrieval activity. <span class="level">(Level A)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_313">Reference for 3.1.3</a></div> </div> </div> <div class="sc-level"> <h4 class="sc-title"><a id="sc_314" name="sc_314"></a>3.1.4 Spell Check: </h4> <p class="sc-text">The user can have spelling assistance for editable text in rendered content. <span class="level">(Level AA)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_314">Reference for 3.1.4</a></div> </div> <h4 class="sc-title"><a id="sc_315" name="sc_315"></a>3.1.5 Back Button: </h4> <p class="sc-text">The user can reverse <a class="dfn-instance" href="#def-recognize" rel="glossary" title="definition:recognized">recognized</a> navigation between web addresses (e.g. standard "back button" functionality). <span class="level">(Level AA)</span> </p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_315">Reference for 3.1.5</a></div> </div> <h4 class="sc-title"><a id="sc_316" name="sc_316"></a>3.1.6 Form Submission Confirm: </h4> <p class="sc-text">The user can specify whether or not <a class="dfn-instance" href="#def-recognize" rel="glossary" title="definition:recognized">recognized</a> form submissions must be confirmed. <span class="level">(Level AA)</span> </p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_316">Reference for 3.1.6</a></div> </div> </div> <div class="sc-level"> <h4 class="sc-title"><a id="sc_317" name="sc_317"></a>3.1.7 Form Auto-Fill: </h4> <p class="sc-text">The user can have the following information stored and used to auto-fill form fields by request: <span class="level">(Level AA)</span> </p> <ol type="a"> <li>user's name</li> <li>user's email address</li> <li>user's phone number</li> </ol> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_317">Reference for 3.1.7</a></div> </div> <h4 class="sc-title"><a id="sc_318" name="sc_318"></a>3.1.8 Save Form Entries: </h4> <p class="sc-text">If the user agent provides a feature to save local versions of web content, then any form fields the user has filled retain any entries in the saved version. <span class="level">(Level AA)</span> </p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_318">Reference for 3.1.8</a></div> </div> </div> </div> <div class="guideline-box" id="g-3-3"> <h3 class="guideline"><a name="gl-doc-access-features" id="gl-doc-access-features">Guideline 3.2 - </a> Document the user agent user interface including accessibility features <span class="gl-only">[<a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#gl-doc-access-features">Reference for 3.2</a>] </span> </h3> <p class="summary" id="summary32"><strong>Summary</strong>: User documentation is available in an accessible format (3.2.1, Level A), it includes accessibility features (3.2.2, Level A), it documents all the user features (3.2.3, Level AA), it delineates differences between versions (3.2.4, Level AA), and provides a centralized view of conformance UAAG2.0 (3.2.5, Level AAA). </p> <div class="sc-level"> <h4 class="sc-title"><a id="sc_321" name="sc_321"></a>3.2.1 Accessible Documentation: </h4> <p class="sc-text"> Product <a class="dfn-instance" href="#def-documentation" title="definition: documentation">documentation</a> is available in a format that meets success criteria of WCAG 2.0 level "A" or greater. <span class="level">(Level A)</span> </p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_321">Reference for 3.2.1</a></div> </div> <h4 class="sc-title"><a id="sc_322" name="sc_322"></a>3.2.2 Describe Accessibility Features: </h4> <p class="sc-text"> For each user agent feature that is used to meet UAAG 2.0, at least one of the following is true: <span class="level">(Level A)</span></p> <ol type="a" class="sc-bullets"> <li class="sc-bullet"><strong class="handle">Described in the Documentation</strong>: Use of the feature is explained in the user agent's documentation; or</li> <li class="sc-bullet"><strong class="handle">Described in the Interface</strong>: Use of the feature is explained in the <a class="dfn-instance" href="#def-ua-ui" rel="glossary" title="definition: user agent user interface">UA user interface</a>; or</li> <li class="sc-bullet"><strong class="handle">Platform Service</strong>: The feature is a service provided by an underlying platform; or</li> <li class="sc-bullet"><strong class="handle">Not Used by Users</strong>: The feature is not used directly by users (e.g., passing information to a platform accessibility service). </li> </ol> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_322">Reference for 3.2.2</a></div> </div> </div> <div class="sc-level"> <h4 class="sc-title"><a id="sc_323" name="sc_323"></a>3.2.3 Document All Features: </h4> <p class="sc-text">For each user agent feature, at least one of the following is true: <span class="level">(Level AA)</span> </p> <ol type="a" class="sc-bullets"> <li class="sc-bullet"><strong class="handle">Described in the Documentation</strong>: Use of the feature is explained in the user agent's documentation; or</li> <li class="sc-bullet"><strong class="handle">Described in the Interface</strong>: Use of the feature is explained in the <a class="dfn-instance" href="#def-ua-ui" rel="glossary" title="definition: user agent user interface">UA user interface</a>; or</li> <li class="sc-bullet"><strong class="handle">Platform Service</strong>: The feature is a service provided by an underlying platform; or</li> <li class="sc-bullet"><strong class="handle">Not Used by Users</strong>: The feature is not used directly by users (e.g., passing information to a platform accessibility service). </li> </ol> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_323">Reference for 3.2.3</a></div> </div> <h4 class="sc-title"><a id="sc_324" name="sc_324"></a>3.2.4 Changes Between Versions: </h4> <p class="sc-text"> Changes to features that meet UAAG 2.0 success criteria since the previous user agent release are documented. <span class="level">(Level AA)</span> </p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_324">Reference for 3.2.4</a></div> </div> </div> <div class="sc-level"> <h4 class="sc-title"><a id="sc_325" name="sc_325"></a>3.2.5 Centralized View: </h4> <p class="sc-text">There is a dedicated section of the documentation that presents a view of all features of the user agent necessary to meet the requirements of User Agent Accessibility Guidelines 2.0. <span class="level">(Level AAA)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_325">Reference for 3.2.5</a></div> </div> </div> </div> <div class="guideline-box" id="g-3-4"> <h3 class="guideline"><a name="gl-predictable-operation" id="gl-predictable-operation"></a>Guideline 3.3 - Make the user agent behave in predictable ways <span class="gl-only">[<a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#gl-predictable-operation">Reference for 3.3</a>] </span> </h3> <p class="summary" id="summary33"><strong>Summary</strong>: Users can prevent non-requested focus changes (3.3.1, Level A). </p> <div class="sc-level"> <h4 class="sc-title"><a id="sc_331" name="sc_331"></a>3.3.1 Avoid Unpredictable Focus: </h4> <p class="sc-text"> The user can prevent focus changes that are not a result of explicit user request. <span class="level">(Level A)</span> </p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_331">Reference for 3.3.1</a></div> </div> </div> </div> </div> <div class="principle" id="p-4"> <h2 class="principle"><a name="principle-AT-access" id="principle-AT-access"></a>PRINCIPLE 4: Facilitate programmatic access</h2> <div class="guideline-box" id="g-4-1"> <h3 class="guideline"><a name="gl-AT-access" id="gl-AT-access"></a>Guideline 4.1 - <span class="principle">Facilitate programmatic access to assistive technology </span> <span class="gl-only">[<a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#gl-AT-access">Reference for 4.1</a>] </span> </h3> <p class="summary" id="summary41"><strong>Summary</strong>: The user agent supports platform accessibility services (4.1.1, Level A), including providing information about all controls and operation (4.1.2, Level A), access to DOMs when platform accessibility services are not available (4.1.4, Level A). Controls can be adjusted programmatically (4.1.5, Level A). Where something can't be made accessible, provide an accessible alternative version, such as a standard window in place of a customized window (4.1.3, Level A).</p> <div class="sc-level"> <p class="sc-title" ><strong>Note</strong>: UAAG 2.0 assumes that a platform accessibility service will be built on top of underlying security architectures that will allow user agents to comply with both the success criteria and security needs. </p> <h4 class="sc-title"><a id="sc_411" name="sc_411"></a>4.1.1 Support Platform Accessibility Services: </h4> <p class="sc-text">The user agent supports relevant <a href="#def-access-platform-arch" class="dfn-instance" title="definition: Platform Accessibility Service">platform accessibility services</a>. <span class="level">(Level A)</span> </p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_411">Reference for 4.1.1</a></div> </div> <h4 class="sc-title"><a id="sc_412" name="sc_412"></a>4.1.2 Expose Accessible Properties: </h4> <p class="sc-text">For all user interface components (including <a class="dfn-instance" href="#def-ua-ui" rel="glossary" title="definition: user agent user interface">UA user interface</a>, <a class="dfn-instance" href="#def-rendered-content" rel="glossary" title="definition: rendered content">rendered content</a>, and generated content) the user agent makes <a href="#def-programmatically-avail" class="dfn-instance" rel="glossary" title="definition: available"> available</a> the following properties and any change notifications via<a href="#def-access-platform-arch" class="dfn-instance" title="definition: Platform Accessibility Service"> a platform accessibility service</a>: <span class="level">(Level A)</span> </p> <ul class="sc-bullets"> <li> Name, Role, State</li> <li>Value</li> <li>Selection</li> <li>Focus </li> <li>Bounding dimensions and coordinates</li> <li>Font family of text</li> <li>Foreground and background color for text</li> <li>Highlighting</li> <li><a href="#def-keyboard-command" class="dfn-instance">Keyboard commands</a></li> <li>Caret position</li> <li>Explicitly defined relationships (e.g. ARIA relationships <a href="#ref-ARIA10">[ARIA 1.0]</a>)</li> </ul> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_412">Reference for 4.1.2</a></div> </div> <h4 class="sc-title"><a id="sc_413" name="sc_413"></a>4.1.3 Provide Equivalent Accessible Alternatives: </h4> <p class="sc-text"> If <a class="dfn-instance" href="#def-ua-ui" rel="glossary" title="definition: user agent user interface">UA user interface</a> functionality cannot be exposed through <a href="#def-access-platform-arch" class="dfn-instance" title="definition: Platform Accessibility Service">platform accessibility services</a>, then the user agent provides equivalent functionality that can be exposed through the platform accessibility service. <span class="level">(Level A)</span> </p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_413">Reference for 4.1.3</a></div> </div> <h4 class="sc-title"><a id="sc_414" name="sc_414"></a>4.1.4 DOMs Programmatically Available as fallback: </h4> <p class="sc-text">If the user agent accessibility API does not provide sufficient information to one or more platform accessibility services, then Document Object Models (DOM), must be made programmatically available to assistive technologies. <span class="level">(Level A)</span> </p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_414">Reference for 4.1.4</a></div> </div> <h4 class="sc-title"><a id="sc_415" name="sc_415"></a>4.1.5 Make Content Interaction Programmatically Available: </h4> <p class="sc-text">If the user can interact with content (e.g. by checking a box or editing a text area), the same degree of interaction is programmatically available. <span class="level">(Level A)</span> </p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_415">Reference for 4.1.5</a></div> </div> </div> </div> </div> <div class="principle" id="p-5"> <h2 class="principle"><a name="principle-follow-specs" id="principle-follow-specs"></a>PRINCIPLE 5: Comply with applicable specifications and conventions</h2> <div class="guideline-box" id="g-5-1"> <h3 class="guideline"><a name="gl-obs-env-conventions" id="gl-obs-env-conventions"></a>Guideline 5.1 - Comply with applicable specifications and conventions <span class="gl-only">[<a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#gl-obs-env-conventions">Reference for 5.1</a>] </span> </h3> <p class="summary" id="summary52"><strong>Summary</strong>: When the browser's controls are authored in HTML or similar standards, they need to meet W3C's Web Content Accessibility Guidelines (5.1.1, Levels A, AA, AAA). The user agent supports the accessibility features of content formats (5.1.2, Level A) and of the platform (5.1.3, Level A), allows handling of unrendered technologies (5.1.4, Level A), allows alternative viewers (5.1.4, Level AA), and allows users to report accessibility issues (5.1.5, Level AAA). </p> <div class="sc-level"> <h4 class="sc-title"><a id="sc_511" name="sc_511"></a>5.1.1 Comply with WCAG: </h4> <p class="sc-text">Web-based <a class="dfn-instance" href="#def-ua-ui" rel="glossary" title="definition: user agent user interface">UA user interfaces</a> meet the WCAG 2.0 success criteria. <span class="level">(Level A to meet WCAG 2.0 Level A success criteria; Level AA to meet WCAG 2.0 Level A and AA success criteria; and Level AAA to meet WCAG 2.0 Level A, AA, and AAA success criteria)</span></p> <ul class="sc-notes"> <li class="sc-note"><em class="note-handle">Note:</em> This success criterion does not apply to native UA user interfaces, but does include any parts of native user agents that are web-based (e.g. help systems). However, it is recommended that developers of native user agent user interfaces follow the Guidance on Applying WCAG 2.0 to Non-Web Information and Communications Technologies (WCAG2ICT) <a href="#ref-wcag2ict">[WCAG2ICT]</a>.</li></ul> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_511">Reference for 5.1.1</a></div> </div> <h4 class="sc-title"><a id="sc_512" name="sc_512"></a>5.1.2 Implement Accessibility Features of Web Content Technology Specifications: </h4> <p class="sc-text">Implement the accessibility features of web content technology specifications. Accessibility features are those that are either <span class="level">(Level A)</span>:</p> <ul class="sc-bullets"> <li class="sc-bullet">Identified as such in the content specifications or</li> <li class="sc-bullet">Allow authors to satisfy a requirement of WCAG 2.0</li> </ul> <ul class="sc-notes"> <li class="sc-note"><em class="note-handle">Note 1</em>: If a conformance claim is filed, cite the implemented specifications in the conformance claim. See <a href="#conformance-req-components">Components of a UAAG 2.0 Conformance Claim</a> - #9 Web Content Technologies. </li> <li class="sc-note"><em class="note-handle">Note 2</em>: When a rendering requirement of another specification contradicts a requirement of UAAG 2.0, the user agent can disregard the rendering requirement of the other specification and still satisfy this guideline.</li></ul> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_512">Reference for 5.1.2</a></div> </div> <h4 class="sc-title"><a id="sc_513" name="sc_513"></a>5.1.3 Implement Accessibility Features of the Platform: </h4> <p class="sc-text"> If the user agent contains native user interfaces, then those native user interfaces follow user interface accessibility guidelines for the platform. <span class="level">(Level A)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_513">Reference for 5.1.3</a></div> </div> <h4 class="sc-title"><a id="sc_514" name="sc_514"></a>5.1.4 Allow Content Elements to be Rendered in Alternative Viewers: </h4> <p class="sc-text">The user can select content elements and have them rendered in alternative viewers. <span class="level">(Level AA)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_514">Reference for 5.1.4</a></div> </div> <h4 class="sc-title"> <a id="sc_515" name="sc_515"></a>5.1.5 Enable Reporting of User Agent Accessibility Faults: </h4> <p class="sc-text">The user agent provides a mechanism for users to report user agent accessibility issues. <span class="level">(Level AAA)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-UAAG20-Reference-20151215/#sc_515">Reference for 5.1.5</a></div> </div> </div> </div> </div> <h2><a name="conformance" id="conformance"></a>Conformance</h2> <p>This section is normative.</p> <p>Conformance means that the user agent satisfies the success criteria defined in the guidelines section. This section lists requirements for conformance and conformance claims.</p> <h3><a name="conformance-require" id="conformance-require"></a>Conformance Requirements </h3> <p> In order for a web page to conform to UAAG 2.0, one of the following levels of conformance is met in full.</p> <ul> <li>Level A: For level A conformance (the minimum level of conformance), the user agent satisfies all the Level A success criteria.</li> <li>Level AA: For level AA conformance (recommended), the user agent satisfies all level A and level AA Success Criteria.</li> <li>Level AAA: For level AAA conformance (advanced), the user agent satisfies all level A, level AA and level AAA Success Criteria.</li> </ul> <p>The <a href="#applicability-notes">Conformance Applicability Notes</a> provide additional guidance on the applicability of the success criteria under certain circumstances.</p> <p> Although conformance can only be achieved at the stated levels, developers are encouraged to report (in their claim) any progress toward meeting success criteria from all levels beyond the achieved level of conformance. </p> <h3><a name="conformance-claims" id="conformance-claims"></a>Conformance Claims</h3> <h4><a name="conformance-conditions" id="conformance-conditions"></a>Conditions on Conformance Claims</h4> <p>If a conformance claim is made, the conformance claim must meet the following conditions:</p> <ul> <li>At least one version of the conformance claim must be published on the web as a document meeting level "A" of WCAG 2.0. A suggested metadata description for this document is "UAAG 2.0 Conformance Claim".</li> <li>Whenever the claimed conformance level is published (e.g. product information website), the URI for the on-line published version of the conformance claim must be included. </li> <li>The existence of a conformance claim does not imply that the W3C has reviewed the claim or assured its validity. </li> <li>There are no restrictions on who can make a claim. </li> <li>Claimants are solely responsible for the accuracy of their claims. </li> <li>Claimants are encouraged to claim conformance to the most recent version of the User Agent Accessibility Guidelines Recommendation. </li> </ul> <h4><a name="conformance-req-components" id="conformance-req-components"></a>Components of UAAG 2.0 Conformance Claims</h4> <ol> <li>Claimant name and affiliation</li> <li>Claimant contact information</li> <li>Date of the claim</li> <li>Type of compliance: [ ] User Agent (full) [ ] <a href="#def-extension">Add-on</a> only (limited) </li> <li>Conformance level satisfied</li> <li><strong>User agent information</strong>: <ol type="a"> <li>Name and manufacturer</li> <li>Version number or version range</li> <li>Required patches or updates, language of the user interface and documentation (e.g. English, French, Chinese)</li> <li>Plug-ins or add-ons (including version numbers) needed to meet the success criteria (e.g. mouseless browsing)</li> <li>Configuration changes to the user agent, plug-ins and add-ons that are needed to meet the success criteria (e.g. ignore author foreground/background color, turn on Carat Browsing)</li> </ol> </li> <li><strong>Platform:</strong> Provide relevant information about the software and/or hardware platform(s) that the user agent relies on for conformance. This information can include: <ol type="a"> <li>Name and manufacturer</li> <li>Version of key software components (e.g. operating system, other software environment)</li> <li>Hardware requirements (e.g. audio output enabled, minimum screen size: 2", bluetooth keyboard attached)</li> <li>Operating system(s) (e.g. Windows, Android, iOS, GNOME)</li> <li>Other software environment (Java, Eclipse) </li> <li>Host web browser when the conforming user agent is web-based (e.g. JW Player on Firefox)</li> <li>Configuration changes to the platform that are needed to meet the success criteria (e.g. turn on Sticky Keys, use High Contrast Mode)</li> </ol> </li> <li><strong>Platform Limitations:</strong> If the platform (hardware or operating system) does not support a capability necessary for a given UAAG 2.0 success criterion, list the success criterion and the feature (e.g. a mobile operating system does not support platform accessibility services, therefore the user agent cannot meet success criterion 4.1.2). For these listed features, the user agent can claim that the success criteria do not apply (see 10.b.1 following). </li> <li><strong>Web Content Technologies:</strong> List the web content technologies rendered by the user agent that are included in the claim. If there are any web content technologies rendered by the user agent that are excluded from the conformance claim, list these separately. Examples of web content technologies include web markup languages such HTML, XML, CSS, SVG, and MathML, image formats such as PNG, JPG and GIF, scripting languages such as JavaScript/EcmaScript, specific video codecs, and proprietary document formats. </li> <li><strong>Declarations:</strong> For each success criterion, provide a declaration of either <ol type="a"> <li>whether or not the success criterion has been satisfied; or </li> <li>declaration that the success criterion is not applicable and a rationale for why not, from the following choices: <ol> <li><strong>Platform</strong>: not applicable due constraints of the platform, per Paragraph 7 above (e.g. color handling on a monochrome device, video handling in a purely audio browser, or interprocess communication on an operating system that does not support multitasking). Describe the specific platform limitation. </li> <li><strong>Input</strong>: not applicable due to a constrained input set (e.g. a help system that only displays the HTML files included with the product)</li> <li><strong>Output</strong>: not applicable due to intentionally limited output modalities (e.g. video handling in a browser that only does audio output, even though the platform can support video)</li> </ol></li> </ol> </li> </ol> <h4><a name="conformance-limited" id="conformance-limited"></a>Limited Conformance for Add-ons</h4> <p> This option can be used for a user agent add-on or plug-in with limited functionality that wishes to claim UAAG 2.0 conformance. An add-on or plug-in can claim conformance for a specific success criterion or a narrow range of success criteria as stated in the claim. All other success criteria can be denoted as Not Applicable. </p> <p>UAAG recognizes that some add-ons can be so specialized to the needs of a particular disability that the add-on is mutually exclusive with other success criteria of UAAG, but the goal would be for add-ons to work with the user agent so that any features of the user agent needed for UAAG conformance are not broken by one add-on. If the add-on limits other accessibility features of the user agent, then include a statement to that effect, such as: "This add-on breaks success criterion x.x.x because it is intended to meet [foo] need of [this] class of user." An example would be a (hypothetical) add-on that breaks 1.8.2 and 1.8.3 (viewport navigation) to provide a simplified page for people with high distraction levels. </p> <h4><a name="conformance-opt-components" id="conformance-opt-conponents"></a>Optional Components of an UAAG 2.0 Conformance Claim</h4> <p>A description of how the UAAG 2.0 success criteria were met where this is not obvious. </p> <h3><a name="conformance-disclaimer" id="conformance-disclaimer"></a>Disclaimer</h3> <p>Neither W3C, WAI, nor UAWG take any responsibility for any aspect or result of any UAAG 2.0 conformance claim that has not been published under the authority of the W3C, WAI, or UAWG. </p> <h2><a name="glossary" id="glossary">Appendix A: Glossary</a></h2> <p>This glossary is <a class="dfn-instance" href="#def-normative" title="definition: Normative">normative</a>.</p> <div class="noprint"> <map name="navbar-glossary" class="navbar" id="navbar-glossary"> <p><a href="#a">a</a> · b · <a href="#c">c</a> · <a href="#d">d</a> · <a href="#e">e</a> · <a href="#f">f</a> · <a href="#g">g</a> · <a href="#h">h</a> · <a href="#i">i</a> · j · <a href="#k">k</a> · l · m · <a href="#n">n</a> · <a href="#o">o</a> · <a href="#p">p</a> · q · <a href="#r">r</a> · <a href="#s">s</a> · <a href="#t">t</a> · <a href="#u">u</a> · <a href="#v">v</a> · <a href="#w">w</a> · x · y · z</p> </map> </div> <dl id="term-list"> <dt class="glossary"><a name="a" id="a"></a><a name="def-activate" id="def-activate"><dfn>activate</dfn></a></dt> <dd class="glossary">To carry out the behaviors associated with an <a class="dfn-instance" href="#def-enabled-element" title="definition: Enabled element">enabled element</a> in the <a href="#def-rendered-content">rendered content</a> or a component of the <a class="dfn-instance" href="#def-ua-ui" title="definition: user agent user interface">UA user interface</a>.</dd> <dt><span class="glossary"><a name="def-conditional-content" id="def-conditional-content"></a></span><span class="glossary"><a name="def-equivalent" id="def-equivalent"></a></span><a id="def-Alternative-Content" name="def-Alternative-Content"></a><dfn>alternative content</dfn></dt> <dd><a href="#def-content">Web content</a> that user agents can programmatically determine is usable in place of other content that some people are not able to access. Alternative content fulfills essentially the same function or purpose as the original content. There are several general types of alternative content: <ul> <li><dfn><a id="def-Text-Alternatives" name="def-Text-Alternatives"></a>text alternative for non-text content</dfn>: Text that is programmatically associated with <a href="#def-non-text-content">non-text content</a> or referred to from text that is programmatically associated with non-text content. For example, an image of a chart might have two text alternatives: a short text alternative and a described-by relationship to a nearby paragraph that more fully describes the content of the chart.</li> <li><dfn><a id="def-Time-Based-Alternatives" name="def-Time-Based-Alternatives"></a>alternative for time-based media</dfn>: <a href="#def-content">Web content</a> that serves the same function or purpose as one or more tracks in a time-based media presentation. This includes alternatives for audio such as <a href="#def-captions">captions</a> and sign language interpretation, and alternatives for video such as <a href="#def-audio-description">audio descriptions</a> and <a href="#def-Auditory-Description-Extended"> extended audio descriptions</a>. Another form of time-based media alternative is a correctly sequenced text description of time-based visual and auditory information that also is capable of achieving the outcomes of any interactivity in the time-based presentation.</li> <li><dfn><a id="def-text-alternatives-for-text" name="def-text-alternatives-for-text"></a>text alternatives for text content</dfn>: Text that is programmatically associated with certain types of text content to provide expanded information. For example, an abbreviation (or acronym) can provide an expansion of the shortened word or initialized words (<abbr title="User Agent Accessibility Guidelines">UAAG</abbr>). </li> <li><dfn><a id="def-Media-Alternatives" name="def-Media-Alternatives"></a>media alternative for text</dfn>: Media that presents no more information than is already presented in text (directly or via text alternatives). A media alternative for text is provided for people who benefit from alternate representations of text. Media alternatives for text can be audio-only, video-only (including sign-language video), or audio-video.<br /> </li> </ul> <span class="glossary-note">Note</span>: According to WCAG 2.0, alternative content may or may not be programmatically determinable (e.g., a short description for an image might appear in the image's description attribute or within text near the image). However, UAAG 2.0 adds the <a href="#def-programmatically-avail">programmatically available</a> condition because this is the only type of alternative content that user agents can recognize. </dd> <dt class="glossary"><a name="def-animation" id="def-animation"><dfn>animation</dfn></a></dt> <dd class="glossary">Graphical <a href="#def-content" title="definition: Content">content</a> rendered to automatically change over time, giving the user a visual perception of movement. Examples include <a href="#def-video">video</a>, animated images, scrolling text, programmatic animation (e.g. moving or replacing rendered objects). </dd> <dt class="glossary"><a name="def-api" id="def-api"><dfn>application programming interface (API)</dfn></a></dt> <dd class="glossary">A mechanism that defines how communication can take place between applications.</dd> <dt class="glossary"><a name="def-assistive-technology" id="def-assistive-technology"><dfn>assistive technology</dfn></a></dt> <dd class="glossary">For the purpose of UAAG 2.0 conformance, assistive technology meets the following criteria: <ol> <li>Relies on services (such as retrieving <a class="dfn-instance" href="#def-web-resource" title="definition: Web resource">web resources</a> and parsing markup) provided by one or more host user agents. </li> <li>Communicates data and messages with host user agents by monitoring and using <a class="dfn-instance" href="#def-api" title="definition: Application Programming Interface (API)">APIs</a>.</li> <li>Provides services beyond those offered by the host user agents to meet the requirements of users with disabilities. Additional services include alternative renderings (e.g. as synthesized speech or magnified content), alternative input methods (e.g. voice), additional navigation or orientation mechanisms, and content transformations (e.g. to make tables more accessible).</li> </ol> Examples of assistive technologies that are important in the context of UAAG 2.0 include the following: <ul> <li>Screen magnifiers, which are used by people with visual disabilities to enlarge and change colors on the screen to improve the visual readability of rendered text and images.</li> <li>Screen readers, which are used by people who are blind or have reading disabilities to read textual information through synthesized speech or braille displays.</li> <li>Voice recognition software, which is used by some people who have physical disabilities to simulate the keyboard and mouse.</li> <li>Alternative keyboards, which are used by some people with physical disabilities to simulate the keyboard and mouse.</li> <li>Alternative pointing devices, which are used by some people with physical disabilities to simulate mouse pointing and button activations.</li> </ul> </dd> <dt class="glossary"><a name="def-audio" id="def-audio"><dfn>audio</dfn></a></dt> <dd class="glossary">The technology of sound transmission. Audio can be created synthetically (including speech synthesis), streamed from a live source (e.g. a radio broadcast), or recorded from real world sounds. There can be multiple <a href="#def-audio-track">audio tracks</a> in a presentation.</dd> <dt class="glossary"><a name="def-audio-description" id="def-audio-description"></a><dfn>audio description</dfn></dt> <dd>A type of <a href="#def-conditional-content">alternative content</a> that takes the form of narration added to the <a href="#def-audio">audio</a> to describe important visual details that cannot be understood from the main soundtrack alone. Audio description of <a href="#def-video">video</a> provides information about actions, characters, scene changes, on-screen text, and other visual content. In standard audio description, narration is added during existing pauses in dialogue. <ul> <li><a id="def-Auditory-Description-Extended" name="def-Auditory-Description-Extended"></a><dfn>extended audio description</dfn>: An <a href="#def-audio-description">audio description</a> in which the <a href="#def-video">video</a> is sometimes paused so that there is time to add additional description.</li> </ul> </dd> <dt class="glossary"><a name="def-audio-track" id="def-audio-track"><dfn>audio track</dfn></a></dt> <dd class="glossary">All or part of the <a href="#def-audio">audio</a> portion of a presentation (e.g. each instrument can have a track, or each stereo channel can have a track).</dd> <dt><dfn><a id="def-author" name="def-author"></a>author</dfn></dt> <dd>A person who works alone or collaboratively to create <a href="#def-content" title="definition: Content">content</a> (e.g. content author, designer, programmer, publisher, tester).</dd> <dt class="glossary"><a name="def-printing-devices" id="def-printing-devices"><dfn>available printing devices</dfn></a></dt> <dd class="glossary">Printing devices that are identified as available to applications via the <a class="dfn-instance" href="#def-platform" rel="glossary" title="definition: platform">platform</a>.</dd> <dt class="glossary"><a name="c" id="c"></a><a name="def-captions" id="def-captions"><dfn>captions</dfn></a></dt> <dd>A type of <a href="#def-conditional-content">alternative content</a> that takes the form of text presented and synchronized with time-based media to provide not only the speech, but also non-speech information conveyed through sound, including meaningful sound effects and identification of speakers. In some countries, the term "subtitle" is used to refer to dialogue only and "captions" is used as the term for dialogue plus sounds and speaker identification. In other countries, "subtitle" (or its translation) is used to refer to both. <ul> <li><dfn><a name="def-open-captions" id="def-open-captions"></a>open captions</dfn>: Captions that are always rendered with a visual track; they cannot be turned off.</li> <li><dfn><a name="def-closed-captions" id="def-closed-captions"></a>closed captions</dfn>: Captions that can be turned on and off. The captions requirements of UAAG 2.0 assume that the user agent can <a class="dfn-instance" href="#def-recognize" title="definition: Recognize">recognize</a> the captions as such.</li> </ul> <em>Note:</em> Other terms that include the word "caption" can have different meanings. For instance, a "table caption" is a title for a table, often positioned graphically above or below the table.</dd> <dt class="glossary"><a name="def-command" id="def-command"></a><dfn>command</dfn>s</dt> <dd>Actions made by users to control the <span class="glossary"><a href="#def-user-agent">user agent</a></span>. These include: <ul> <li><dfn><span class="glossary"><a name="def-direct-command" id="def-direct-command"></a></span>direct commands</dfn>: Commands that apply to a specified item (e.g. button) or action (e.g. save function), regardless of the current focus location. Also see <a href="#def-keyboard-command"><dfn>keyboard command</dfn></a> <ul> <li><dfn class="glossary"><a name="def-direct-navigation" id="def-direct-navigation"></a>direct navigation commands</dfn>: Commands that move focus to a specified item.</li> <li><dfn class="glossary"><a name="def-direct-activation" id="def-direct-activation"></a>direct activation commands</dfn>: Commands that activate the specified item (and can also move focus to it) or action.</li> </ul> </li> <li><dfn><span class="glossary"><a name="def-linear-navigation" id="def-linear-navigation"></a></span><span class="glossary"><a name="def-sequential-navigation" id="def-sequential-navigation"></a></span>sequential navigation commands</dfn> (sometimes called "logical navigation commands" or "linear navigation commands"): Commands that move focus forwards and backwards through a list of items. The element list being navigated can be the list of all elements or just a subset (e.g. the list of headers, the list of links).</li> <li><dfn><span class="glossary"><a name="def-spacial-command" id="def-spacial-command"></a></span>spatial commands</dfn> (sometimes called "directional commands"): Commands that require the user to be aware of the spatial arrangement of items on the screen: <ul> <li><a name="def-spatial-navigation" id="def-spatial-navigation"></a><dfn>spatial navigation commands</dfn>: Commands that move from one item to another based on direction on the screen.</li> <li><a name="def-spatial-manipulation" id="def-spatial-manipulation"></a><dfn>spatial manipulation commands</dfn>: Commands that resize or reposition an item on the screen.</li> </ul> </li> <li><dfn><span class="glossary"><a name="def-structural-navigation" id="def-structural-navigation"></a></span>structural navigation commands</dfn>: Commands that move forwards, backwards, up and down a hierarchy. </li> </ul> </dd> <dt class="glossary"><a name="def-content" id="def-content"><dfn>content (web content)</dfn></a></dt> <dd class="glossary">Information and sensory experience to be communicated to the user by means of a <a href="#def-user-agent">user agent</a>, including code or markup that defines the content's structure, presentation, and interactions.</dd> <dt class="glossary"><a name="def-continuous-scale" id="def-continuous-scale"></a><dfn>continuous scale</dfn></dt> <dd class="glossary"> When interacting with a time-based media presentation, a continuous scale allows user (or programmatic) action to set the active playback position to any time point on the presentation time line. The granularity of the positioning is determined by the smallest resolvable time unit in the media timebase.</dd> <dt><a name="d" id="d"></a><dfn>default</dfn><span class="glossary"></span></dt> <dd>see <a href="#def-Properties-and-Values"><dfn>properties</dfn></a></dd> <dt class="glossary"><a name="def-directly" id="def-directly"></a><dfn>directly</dfn></dt> <dd>using a <a href="#def-direct-command"><dfn>direct command</dfn></a></dd> <dt class="glossary"><dfn>disabled element</dfn></dt> <dd>see <a href="#def-element"><strong>element</strong></a><strong></strong></dd> <dt class="glossary"> <a name="def-doc-char-set" id="def-doc-char-set"><dfn>document character set</dfn></a></dt> <dd class="glossary">The internal representation of data in the <a href="#def-text-source">source</a> content by a <a href="#def-user-agent">user agent</a>.</dd> <dt class="glossary"> <a name="def-document-object" id="def-document-object"><dfn>document object</dfn></a>, <a name="def-dom" id="def-dom"><dfn>Document Object Model (DOM)</dfn></a></dt> <dd class="glossary">A platform- and language-neutral interface that allows programs and scripts to dynamically access and update the content, structure and style of documents. The document can be further processed and the results of that processing can be incorporated back into the presented page. Overview of DOM-related materials: <a href="https://www.w3.org/DOM/#what">http://www.w3.org/DOM/#what</a>.</dd> <dt class="glossary"><a name="def-documentation" id="def-documentation"><dfn>documentation</dfn></a></dt> <dd class="glossary">Any information that supports the use of a <a href="#def-user-agent">user agent</a>. This information can be provided electronically or otherwise and includes help, manuals, installation instructions, tutorials, etc. Documentation can be accessed in various ways (e.g. as files included in the installation, available on the web). <br /> Note: The level of technical detail in documentation for users should match the technical level of the feature. For example, user documentation for a browser's zoom function should not refer users to the source code repository for that browser.</dd> <dt class="glossary"><a name="e" id="e"></a><a name="def-element" id="def-element"><dfn>element</dfn></a></dt> <dd class="glossary">Primarily, a syntactic construct of a document type definition (DTD) for its application. This is the sense employed by the XML 1.0 specification (<cite><a href="#ref-XML" title="Link to reference XML">[XML]</a></cite>, section 3). UAAG 2.0 also uses the term "element" more generally to refer to any discrete unit within the content (e.g. a specific image, video, sound, heading, list, or list item). <ul> <li><a name="def-enabled-element" id="def-enabled-element"></a><dfn>enabled element</dfn>: An <a href="#def-element">element</a> with associated behaviors that can be activated through the user interface or through an <a class="dfn-instance" href="#def-api" title="definition: Application Programming Interface (API)">API</a>. The set of elements that a user agent enables is generally derived from, but is not limited to, the set of <a class="dfn-instance" href="#def-element" title="definition: Interactive element">elements</a> defined by implemented markup languages. </li> <li><a name="def-disabled-element" id="def-disabled-element"></a><dfn>disabled element</dfn>: A potentially enabled element that is not currently available for activation (e.g. a "grayed out" menu item).</li> <li><a name="def-element-type" id="def-element-type"><dfn>element type</dfn></a>: A category of elements (such as images, videos, sounds, first level headings, lists, or list items).</li> </ul> </dd> <dt class="glossary"><a name="def-event" id="def-event"><dfn>events and scripting, event handler, event type</dfn></a></dt> <dd class="glossary">User agents often perform a task when an event having a particular "event type" occurs, including a user interface event, a change to content, loading of content, or a request from the <a class="dfn-instance" href="#def-operating-environment" title="definition: Operating environment">operating environment</a>. Some markup languages allow authors to specify that a script, called an <a name="def-event-handler" id="def-event-handler"><dfn>event handler</dfn></a>, be executed when an event of a given type occurs. An event handler is <a name="def-explicit-handler" id="def-explicit-handler"><dfn>explicitly associated with an element</dfn></a> through scripting, markup or the <a href="#def-dom" ><acronym title="Document Object Model">DOM</acronym></a>.</dd> <dt class="glossary"><dfn>enabled element</dfn></dt> <dd>see <a href="#def-element"><strong>element</strong></a><strong></strong></dd> <dt><a name="def-user-request" id="def-user-request"><dfn>explicit user request</dfn></a><span class="glossary"></span></dt> <dd class="glossary">An interaction by the user through the <a class="dfn-instance" href="#def-ua-ui" title="definition: user agent user interface">UA user interface</a>, the <a class="dfn-instance" href="#def-focus" title="definition: Focus">focus</a>, or the <a class="dfn-instance" href="#def-selection" title="definition: Selection">selection</a>. User requests are made, for example, through <a class="dfn-instance" href="#def-ui-control" title="definition: user interface control">user agent user interface controls</a> and <a href="#def-keyboard-command" title="definition: keyboard command">keyboard commands</a>. Some examples of explicit user requests include when the user selects "New viewport," responds "yes" to a <a href="#def-prompt">prompt</a> in the user agent's user interface, configures the user agent to behave in a certain way, or changes the selection or focus with the keyboard or pointing device. <em>Note: </em>Users can make errors when interacting with the user agent. For example, a user can inadvertently respond "yes" to a prompt instead of "no." This type of error is still considered an explicit user request. </dd> <dt class="glossary"><dfn>extended audio description</dfn></dt> <dd>see <a href="#def-audio-description"><strong>audio description</strong></a></dd> <dt><a name="f" id="f"></a><a name="def-current-focus" id="def-current-focus"></a><a name="def-input-focus" id="def-input-focus"></a><a name="def-focus" id="def-focus"><dfn>focus, input focus</dfn></a></dt> <dd>The location where input will occur if a <a href="#def-viewport">viewport</a> is active. Examples include: <ul> <li><a name="def-keyboard-focus" id="def-keyboard-focus"></a><dfn>keyboard focus</dfn>: The screen location where <a href="#def-keyboard">keyboard</a> input will occur if a viewport is active.</li> <li><a name="def-pointing-device-focus" id="def-pointing-device-focus"></a><dfn>pointing device focus</dfn>: The screen location where <a href="#def-pointer">pointer</a> input will occur if a viewport is active. There can be multiple pointing device foci for example when using a screen sharing utility there is typically one for the user's physical mouse and one for the remote mouse.</li> </ul> The <a name="def-active-input-focus" id="def-active-input-focus"></a><dfn>active input focus</dfn> is in the active viewport. The <a name="def-inactive-input-focus" id="def-inactive-input-focus"></a><dfn>inactive input focus</dfn> is in the inactive viewport. Focus is typically indicated by a <a href="#def-cursor">focus cursor</a>.</dd> <dt class="glossary"><a name="def-cursor" id="def-cursor"></a><dfn>focus cursor</dfn></dt> <dd>Visual indicator that <a href="#def-highlight">highlights</a> a user interface element to show that it has <a href="#def-input-focus">input focus</a> (e.g. the dotted line around a button, outline around a pane, or brightened title bar on a window). <ul> <li><a name="def-focus-cursor" id="def-focus-cursor"></a><dfn>keyboard focus cursor</dfn>: Indicator showing the enabled element with current input focus where focus has been moved by the keyboard (e.g. the dotted line around a button). </li> <li><dfn><a name="def-text-cursor" id="def-text-cursor"></a>text cursor</dfn>: Indicator showing where keyboard input will occur in text (e.g. the flashing vertical bar in a text field, also called a caret).</li> <li><a name="def-pointer" id="def-pointer"></a><dfn>pointer</dfn>: Indicator showing where pointing device input will occur. The indicator can be moved with a pointing device or emulator such as a mouse, pen tablet, keyboard-based mouse emulator, speech-based mouse commands, or 3-D wand. A pointing device click typically moves the <a href="#def-input-focus">input focus</a> to the pointer location. The indicator can change to reflect different states. When touchscreens are used, the "pointing device" is a combination of the touchscreen and the user's finger or stylus. On most touchscreen systems there is no pointer (on-screen visual indication).</li> </ul> Cursors are active when in the active viewport, and inactive when in an inactive viewport. </dd> <dt class="glossary"><a name="def-focusable-element" id="def-focusable-element"></a><dfn>focusable element</dfn></dt> <dd>Any <a href="#def-element">element</a> capable of having <a href="#def-input-focus">input focus</a> (e.g. a link, text box, or menu item). In order to be accessible and fully usable, every focusable element should take <a href="#def-keyboard-focus">keyboard focus</a>, and ideally would also take <a href="#def-pointing-device-focus">pointer focus</a>.</dd> <dt class="glossary"><a name="g" id="g"></a><a name="def-global-configuration" id="def-global-configuration"></a><dfn>globally, global configuration</dfn></dt> <dd class="glossary">A setting is one that applies to the entire <a href="#def-user-agent">user agent</a> or all content being rendered by it, rather than to a specific feature within the user agent or a specific document being viewed.</dd> <dt class="glossary"><a name="def-graphical" id="def-graphical"><dfn>graphical</dfn></a></dt> <dd class="glossary">Information (e.g. text, colors, graphics, images, or <a href="#def-animation">animations</a>) rendered for visual consumption.</dd> <dt class="glossary"><a name="h" id="h"></a><a name="def-highlight-focus" id="def-highlight-focus"></a><a name="def-highlight" id="def-highlight"></a><dfn>highlight, highlighted, highlighting</dfn></dt> <dd>Emphasis indicated through the user interface. For example, <a href="#def-user-agent">user agents</a> highlight content that is selected, focused, or matched by a search operation. Graphical highlight mechanisms include dotted boxes, changed colors or fonts, underlining, adjacent icons, magnification, and reverse video. Synthesized speech highlight mechanisms include alterations of voice pitch and volume ( i.e. speech prosody). User interface items can also be highlighted, for example a specific set of foreground and background colors for the title bar of the active window. Content that is highlighted may or may not be a <a href="#def-selection">selection</a>.</dd> <dt class="glossary"><a name="i" id="i"></a><a name="def-image" id="def-image"><dfn>image</dfn></a></dt> <dd class="glossary">Pictorial content that is static (i.e. not moving or changing). Also see <a class="dfn-instance" href="#def-animation" title="definition: Animation">animation</a>.</dd> <dt><dfn>informative (non-normative)</dfn></dt> <dd>see <a class="dfn-instance" href="#def-informative">normative</a></dd> <dt class="glossary"><a name="k" id="k"></a><a name="def-keyboard" id="def-keyboard"></a><dfn>keyboard</dfn></dt> <dd>The letter, symbol and command keys or key indicators that allow a user to control a computing device. Assistive technologies have traditionally relied on the keyboard interface as a universal, or modality independent interface. In this document references to keyboard include keyboard emulators and <a class="dfn-instance" href="#def-keyboard-interface">keyboard interfaces</a> that make use of the keyboard's role as a modality independent interface (see <a class="dfn-instance" href="https://www.w3.org/TR/2015/NOTE-UAAG20-20151215/#intro-modality-independence">Modality Independence</a>). Keyboard emulators and interfaces can be used on devices which do not have a physical keyboard, such as mobile devices based on touchscreen input.</dd> <dt><a name="def-keyboard-interface" id="def-keyboard-interface"><dfn>keyboard interface</dfn></a></dt> <dd>Keyboard interfaces are programmatic services provided by many platforms that allow operation in a device independent manner. A keyboard interface can allow keystroke input even if particular devices do not contain a hardware keyboard (e.g. a touchscreen-controlled device can have a keyboard interface built into its <a class="dfn-instance" href="#def-operating-system" rel="glossary" title="definition: operating system">operating system</a> to support onscreen keyboards as well as external keyboards that can be connected). <br /> <em>Note:</em> Keyboard-operated mouse emulators, such as MouseKeys, do not qualify as operation through a keyboard interface because these emulators use pointing device interfaces, not keyboard interfaces.</dd> <dt class="glossary"><a name="def-keyboard-command" id="def-keyboard-command"><dfn>keyboard command</dfn></a> (<a name="def-keyboard-binding" id="def-keyboard-binding2"><dfn>keyboard binding</dfn></a>, <a name="def-keyboard-shortcut" id="def-keyboard-shortcut"><dfn>keyboard shortcuts</dfn></a>, <dfn>accesskey, access key, </dfn><a name="def-accelerator-key" id="def-accelerator-key"><dfn>accelerator keys</dfn></a>, <dfn>direct keyboard command</dfn>)</dt> <dd>A key or set of keys that are tied to a particular UI control or application function, allowing the user to navigate to or activate the control or function without traversing any intervening controls (e.g. CTRL+"S" to save a document). It is sometimes useful to distinguish keyboard commands that are associated with controls that are rendered in the current context (e.g. ALT+"D" to move focus to the address bar) from those that can be able to activate program functionality that is not associated with any currently rendered controls (e.g. "F1" to open the Help system). Keyboard commands can be triggered using a physical keyboard or keyboard emulator (e.g. on-screen keyboard or speech recognition). (See <a class="dfn-instance" href="#intro-modality-independence">Modality Independent Controls</a>). <a name="def-seq-keyboard-command" id="def-seq-keyboard-command"><dfn>Sequential keyboard commands</dfn></a> require multiple keystrokes to carry out an action (e.g. a series of Tab or arrow presses followed by Enter, or a sequence like ALT-F, V to drop down a File menu and choose Print Preview). </dd> <dt><dfn><a name="n" id="n"></a>non-text content (non-text element, non-text equivalent)</dfn><span class="glossary"></span></dt> <dd>see <a href="#def-text"><dfn>text</dfn></a></dd> <dt class="glossary"><a name="def-normative" id="def-normative"><dfn>normative</dfn></a>, <a name="def-informative" id="def-informative"></a><dfn>informative (non-normative)</dfn></dt> <dd class="glossary">Required (or not required) for conformance. Abilities identified as "normative" are required for <a class="dfn-instance" href="#conformance">conformance</a> (noting that one can conform in a variety of well-defined ways to UAAG 2.0). Abilities identified as "informative" (or, "non-normative") are never required for conformance.</dd> <dt class="glossary"><a name="def-alert" id="def-alert"><dfn>notify</dfn></a></dt> <dd class="glossary">To make the user aware of events or status changes. Notifications can occur within the <a class="dfn-instance" href="#def-ua-ui" rel="glossary" title="definition: user agent user interface">UA user interface</a> (e.g. a status bar) or within the content display. Notifications can be passive and not require user acknowledgment, or they can be presented in the form of a <a href="#def-prompt">prompt</a> requesting a user response (e.g. a confirmation dialog).</dd> <dt class="glossary"><a name="o" id="o"></a><a name="def-obscure" id="def-obscure"><dfn>obscure</dfn></a></dt> <dd class="glossary">To render a visual element in the same screen space as a second visual element in a way that prevents the second visual element from being visually perceived. <br /> Note: The use of transparent backgrounds for the overlaying visual element (e.g., video captions) is an acceptable technique for reducing obscuration, if space is available.</dd> <dt class="glossary"><a name="def-operating-environment" id="def-operating-environment"><dfn>operating environment</dfn></a></dt> <dd class="glossary">The software environment that governs the user agent's operation, whether it is an <a class="dfn-instance" href="#def-operating-system" rel="glossary" title="definition: operating system">operating system</a> or a programming language environment such as Java.</dd> <dt class="glossary"><a name="def-operating-system" id="def-operating-system"><dfn>operating system (OS)</dfn></a></dt> <dd>Software that supports a device's basic functions, such as scheduling tasks, executing applications, and managing hardware and peripherals. <br /> <em>Note: </em>Many operating systems mediate communication between executing applications and <a href="#def-assistive-technology">assistive technology</a> via a <a href="#def-access-platform-arch">platform accessibility service</a>.</dd> <dt class="glossary"><a name="def-override" id="def-override"><dfn>override</dfn></a></dt> <dd class="glossary">When one configuration or behavior preference prevails over another. Generally, the requirements of UAAG 2.0 involve user preferences prevailing over author preferences and user agent default settings and behaviors. Preferences can be multi-valued in general (e.g. the user prefers blue over red or yellow), and include the special case of two values (e.g. turn on or off blinking text content).</dd> <dt class="glossary"><a name="p" id="p"></a><a name="def-placeholder" id="def-placeholder"><dfn>placeholder</dfn></a></dt> <dd class="glossary">Content generated by the user agent to replace author-supplied content. A placeholder can be generated as the result of a user preference (e.g. to not render images) or as <a class="dfn-instance" href="#def-repair-content" title="definition: Repair content">repair content</a> (e.g. when an image cannot be found). A placeholder can be any type of content, including text, images, and audio cues. A placeholder should identify the technology of the replaced object.</dd> <dt class="glossary"><a name="def-platform" id="def-platform"></a><dfn>platform</dfn></dt> <dd class="glossary"> The software and hardware environment(s) within which the <a href="#def-user-agent">user agent</a> operates. Platforms provide a consistent operational environment. There can be layers of software in an hardware architecture and each layer can be considered a platform. Native platforms include desktop <a class="dfn-instance" href="#def-operating-system" rel="glossary" title="definition: operating system">operating system</a> (e.g. Linux, Mac OS, Windows, etc.), mobile operating systems (e.g. Android, Blackberry, iOS, Windows Phone, etc.), and cross-OS environments (e.g. Java). Web-based platforms are other user agents. User agents can employ server-based processing, such as web content transformations, text-to-speech production, etc.<br /> <em>Note 1</em>: A user agent can include functionality hosted on multiple platforms (e.g. a browser running on the desktop can include server-based pre-processing and web-based documentation).<br /> <em>Note 2</em>: Accessibility guidelines for developers exist for many platforms.</dd> <dt class="glossary"><a name="def-access-platform-arch" id="def-access-platform-arch"><dfn>platform accessibility service</dfn></a></dt> <dd>A programmatic interface that is engineered to enhance communication between mainstream software applications and assistive technologies (e.g. MSAA, UI Automation, and IAccessible2 for Windows applications, AXAPI for Mac OSX applications, Gnome Accessibility Toolkit API for GNOME applications, Java Access for Java applications). On some platforms it can be conventional to enhance communication further by implementing a <a class="dfn-instance" href="#def-dom" title="definition: Document Object Model">DOM</a>.</dd> <dt class="glossary"><dfn>plug-in</dfn></dt> <dd class="glossary">see <a href="#def-user-agent"><strong>user agent</strong></a><strong></strong></dd> <dt class="glossary"><a name="def-point-of-regard" id="def-point-of-regard"><dfn>point of regard</dfn></a></dt> <dd class="glossary">The position in <a class="dfn-instance" href="#def-rendered-content" title="definition: Rendered content">rendered content</a> that the user is presumed to be viewing. The dimensions of the point of regard can vary. For example,it can be a two-dimensional area (e.g. content rendered through a two-dimensional graphical viewport), or a point (e.g. a moment during an audio rendering or a cursor position in a graphical rendering), or a range of text (e.g. focused text), or a two-dimensional area (e.g. content rendered through a two-dimensional graphical viewport). The point of regard is almost always within the viewport, but it can exceed the spatial or temporal <a href="#viewport-dimension">dimensions</a> of the viewport (see the definition of <a class="dfn-instance" href="#def-rendered-content" title="definition: Rendered content">rendered content</a> for more information about viewport dimensions). The point of regard can also refer to a particular moment in time for content that changes over time (e.g. an audio-only presentation). User agents can determine the point of regard in a number of ways, including based on viewport position in content, <a class="dfn-instance" href="#def-keyboard-focus" title="definition: content focus">keyboard focus</a>, and <a class="dfn-instance" href="#def-selection" title="definition: Selection">selection</a>.</dd> <dt class="glossary"><dfn>pointer</dfn></dt> <dd>see <a href="#def-pointer"><strong>focus cursor</strong></a></dd> <dt><a name="def-profile" id="def-profile"><dfn>profile</dfn></a><span class="glossary"></span></dt> <dd class="glossary">A named and persistent representation of user preferences that can be used to configure a <a href="#def-user-agent">user agent</a>. Preferences include input configurations, style preferences, and natural language preferences. In <a class="dfn-instance" href="#def-operating-environment" title="definition: Operating environment">operating environments</a> with distinct user accounts, profiles enable users to reconfigure software quickly when they log on. Users can share their profiles with one another. Platform-independent profiles are useful for those who use the same user agent on different devices.</dd> <dt><a name="def-programmatically-avail" id="def-programmatically-avail"><dfn>programmatically available</dfn></a><span class="glossary"></span></dt> <dd>Information that is encoded in a way that allows different software, including <a href="#def-assistive-technology" title="definition: assistive technology">assistive technologies</a>, to extract and use the information relying on published, supported mechanisms, such as, platform accessibility services, APIs, or the document object models (DOM). For web-based user interfaces, this means ensuring that the <a href="#def-user-agent" title="definition: user agent">user agent</a> can pass on the information (e.g. through the use of WAI-ARIA). Something is programmatically available if the entity presenting the information does so in a way that is explicit and unambiguous, in a way that can be understood without reverse-engineering or complex (and thus potentially fallible) heuristics, and only relying on methods that are published, and officially supported by the developers of the software being evaluated. </dd> <dt class="glossary"><a name="def-prompt" id="def-prompt"><dfn>prompt</dfn></a></dt> <dd>Any <a href="#def-user-agent" title="definition: user agent">user agent</a>-initiated request for a decision or piece of information from a user.</dd> <dt class="glossary"><a name="def-Properties-and-Values" id="def-Properties-and-Values"><dfn>properties, values, and defaults</dfn></a></dt> <dd class="glossary">A user agent renders a document by applying formatting algorithms and style information to the document's elements. Formatting depends on a number of factors, including where the document is rendered (e.g. on screen, on paper, through loudspeakers, on a braille display, on a mobile device). Style information (e.g. fonts, colors, synthesized speech prosody) can come from the elements themselves (e.g. certain font and phrase elements in HTML), from stylesheets, or from user agent settings. For the purposes of these guidelines, each formatting or style option is governed by a property and each property can take one value from a set of legal values. Generally in UAAG 2.0, the term "<a href="https://www.w3.org/TR/1998/REC-CSS2-19980512/conform.html">property</a>" has the meaning defined in <a href="https://www.w3.org/TR/CSS2/conform.html#property">CSS 2.1 Conformance</a> (<cite><a href="#ref-CSS2" title="Link to reference CSS2">[CSS21]</a></cite>, ). A reference to "styles" in UAAG 2.0 means a set of style-related properties. <ul> <li><a name="default-value" id="default-value"><dfn>default value</dfn></a>: The value given to a property by a user agent at installation.</li> </ul> </dd> <dt class="glossary"><a name="r" id="r"></a><a name="def-recognize" id="def-recognize"><dfn>recognize</dfn></a></dt> <dd class="glossary">Information or events that can be identified unambiguously by user agents. <br /> <a name="def-recognized-content" id="def-recognized-content"><dfn>recognized content</dfn></a>: Information that is encoded within content in a way that can be unambiguously recognized by user agents. <a href="#def-author">Authors</a> encode information in many ways, including in markup languages, style sheet languages, scripting languages, and protocols. When the information is encoded in a manner that allows the user agent to process it with certainty, the user agent can "recognize" the information. For instance, HTML allows authors to specify a heading with the <code>H1</code> element, so a user agent that implements HTML can recognize that content as a heading. If the author creates a heading using a visual effect alone (e.g. just by increasing the font size), then the author has encoded the heading in a manner that does not allow the user agent to recognize it as a heading. Some requirements of UAAG 2.0 depend on content roles, content relationships, timing relationships, and other information supplied by the author. These requirements only apply when the author has encoded that information in a manner that the user agent can recognize. See the section on <a href="#conformance">conformance</a> for more information about applicability. User agents will rely heavily on information that the author has encoded in a markup language or style sheet language. Behaviors, style, meaning encoded in a <a class="dfn-instance" href="#def-script" title="definition: Script">script</a>, and markup in an unfamiliar XML namespace can not be recognized by the user agent as easily or at all. <br /> <a name="def-recognized-actions" id="def-recognized-actions"><dfn>recognized actions</dfn></a>: Actions or events that can be unambiguously identified by a user agent. This can include actions or events initiated by users, scripts, add-ons, or other sources. For example, if the keyboard focus is on a web page when the user presses a key, the user agent can recognize the keystroke and can act upon it. If the keyboard focus is on an embedded media player when the user presses a key, the host user agent may or may not be able to detect the keystroke, depending on the embedding architecture. Similarly, when the user activates an INPUT element with type="submit", the user agent will recognize this as a form submission action and carry out the proper interchange with the server. However, if a page includes a custom control that looks like a button labeled "Submit**" but whose actions are entirely handled by an author-provided script, the user agent would not be able to recognize the user action as equivalent to a form submission. Actions such as opening of new browser window would always be implemented by the user agent, so the action would be recognized regardless of whether it was initiated by the user clicking a button or by a script calling a browser function. </dd> <dt><a name="def-reflow-content" id="def-reflow-content"><dfn>reflowable content<span class="glossary"></span></dfn></a></dt> <dd><a href="#def-content">Web content</a> that can be arbitrarily wrapped over multiple lines. The primary exceptions to reflowable content are graphics and <a href="#def-video">video</a>.</dd> <dt><a name="def-relative-time-units" id="def-relative-time-units"><dfn>relative time units</dfn></a><span class="glossary"></span></dt> <dd class="glossary">Time intervals for navigating media relative to the current point (e.g. move forward 30 seconds). When interacting with a time-based media presentation, a user can find it beneficial to move forward or backward via a time interval relative to their current position. For example, a user can find a concept unclear in a video lecture and elect to skip back 30 seconds from the current position to review what had been described. Relative time units can be preset by the user agent, configurable by the user, and/or automatically calculated based upon media duration (e.g. jump 5 seconds in a 30-second clip, or 5 minutes in a 60-minute clip). Relative time units are distinct from absolute time values such as the 2 minute mark, the half-way point, or the end.</dd> <dt class="glossary"><a name="def-rendered-content" id="def-rendered-content"><dfn>rendered content</dfn></a></dt> <dd class="glossary">The presentation generated by the user agent based on the author supplied code. This includes: <ul><li>content specified by the author</li><li>dynamic content created or altered by scripts</li><li>content inserted by the user agent (e.g. repair text and security warnings on links)</li> <li>content inserted by style sheets or markup (e.g. number or letter preceding an ordered list item, the CSS content property)</li> </ul> <dfn><a name="def-rendered-text" id="def-rendered-text"></a>rendered text</dfn>: <a class="dfn-instance" href="#def-text" title="definition: Text">Text</a> content that is rendered in a way that communicates information about the characters themselves, whether visually or as synthesized speech. </dd> <dt class="glossary"><a name="def-repair-content" id="def-repair-content"></a><dfn>repair content</dfn>, <a name="def-repair-text" id="def-repair-text"></a><dfn>repair text</dfn></dt> <dd class="glossary">Content generated by the user agent to correct an error condition. "Repair text" refers to the <a class="dfn-instance" href="#def-text" title="definition: Text">text</a> portion of repair content. Error conditions that can lead to the generation of repair content include: <ul> <li>Erroneous or incomplete content (e.g. ill-formed markup, invalid markup, or missing <a class="dfn-instance" href="#def-conditional-content" title="definition: Conditional content">alternative content</a> that is required by format specification);</li> <li>Missing resources for handling or rendering content (e.g. the user agent lacks a font family to display some characters, or the user agent does not implement a particular scripting language).</li> </ul> <em>Note:</em> UAAG 2.0 does not require user agents to include repair content in the <a class="dfn-instance" href="#def-document-object" title="definition: Document object">document object</a>. Repair content inserted in the document object should conform to the Web Content Accessibility Guidelines 2.0 <cite><a href="#ref-WCAG20" title="Link to reference WCAG20">[WCAG20]</a></cite>. For more information about repair techniques for web content and software, refer to "Implementing ATAG 2.0" <cite><a href="#ref-ATAG10-TECHS" title="Link to reference ATAG20-IMPLEMENTING">[ATAG20-IMPLEMENTING]</a></cite>.</dd> <dt class="glossary"><a name="def-rfc2119" id="def-rfc2119"><dfn>RFC 2119</dfn></a></dt> <dd class="glossary">A publication of the Internet Engineering Task Force (IETF) on Key words for use in Request for Comments (RFC) to Indicate Requirement Levels. The key words are "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" . This information is provided for explanation. UAAG 2.0 does not use these terms as defined in RFC 2119.</dd> <dt class="glossary"><a name="s" id="s"></a><a name="def-script" id="def-script"><dfn>script</dfn></a></dt> <dd class="glossary">Instructions to create dynamic web content that are written in a programming (scripting) language. In guidelines referring to the written (natural) language of content, as referenced in Unicode <cite><a href="#ref-UNICODE" title="Link to reference UNICODE">[UNICODE]</a></cite>), script can also refer to "a collection of symbols used to represent textual information in one or more writing systems". Information encoded in (programming) scripts can be difficult for a user agent to <a class="dfn-instance" href="#def-recognize" title="definition: Recognize">recognize</a>. For instance, a user agent is not expected to recognize that, when executed, a script will calculate a factorial. The user agent will be able to recognize some information in a script by virtue of implementing the scripting language or a known program library (e.g. the user agent is expected to recognize when a script will open a viewport or retrieve a resource from the web).</dd> <dt><a name="def-selection" id="def-selection"></a><dfn>selection</dfn><span class="glossary"></span></dt> <dd>A <span class="glossary"><a class="dfn-instance" href="#def-user-agent">user agent</a></span> mechanism for identifying a (possibly empty) range of content that will be the implicit source or target for subsequent operations. The selection can be used for a variety of purposes, including for cut-and-paste operations, to designate a specific element in a document for the purposes of a query, and as an indication of <a class="dfn-instance" href="#def-point-of-regard" rel="glossary" title="definition: point of regard">point of regard</a> (e.g. the matched results of a search can be automatically selected). The selection should be <a class="dfn-instance" href="#def-highlight">highlighted</a> in a distinctive manner. On the screen, the selection can be highlighted in a variety of ways, including through colors, fonts, graphics, and magnification. When rendered using synthesized speech, the selection can be highlighted through changes in pitch, speed, or prosody. </dd> <dt class="glossary"><a name="def-text-source" id="def-text-source"><dfn>source text</dfn></a></dt> <dd class="glossary">Text that the <a href="#def-user-agent">user agent</a> renders upon user request to view the source of specific <a href="#def-viewport">viewport</a> content (e.g. selected content, frame, page).</dd> <dt class="glossary"><a name="def-style-properties" id="def-style-properties"></a><dfn>style properties</dfn></dt> <dd>Properties whose values determine the presentation (e.g. font, color, size, location, padding, volume, synthesized speech prosody) of content elements as they are rendered (e.g. onscreen, via loudspeaker, via braille display) by <a href="#def-user-agent">user agents</a>. Style properties can have several origins: <ul> <li><dfn><span class="glossary"><a name="def-user-agent-default-styles" id="def-user-agent-default-styles"></a></span>user agent default styles</dfn>: The default style property values applied in the absence of any author or user styles. Some <a href="#def-Web-Content-Technology">web content technologies</a> specify a default rendering; others do not.</li> <li><dfn><a name="def-author-styles" id="def-author-styles"></a>author styles</dfn>: Style property values that are set by the author as part of the content (e.g. in-line styles,<a href="#def-author-stylesheet"> author style sheets</a>).</li> <li><dfn><span class="glossary"><a name="def-user-styles" id="def-user-styles"></a></span>user styles</dfn>: Style property values that are set by the user (e.g. via user agent interface settings, <a href="#def-user-stylesheet">user style sheets</a>).</li> </ul> </dd> <dt class="glossary"><a name="def-style-profile" id="def-style-profile"></a><a name="def-stylesheet" id="def-stylesheet"></a><dfn>style sheet</dfn></dt> <dd class="glossary">A mechanism for communicating <a href="#def-style-properties">style property</a> settings for web content, in which the style property settings are separable from other content resources. This separation allows author style sheets to be toggled or substituted, and user style sheets defined to apply to more than one resource. Style sheet <a href="#def-Web-Content-Technology">web content technologies</a> include Cascading Style Sheets (CSS) and Extensible Stylesheet Language (XSL). <ul > <li><dfn><a name="def-user-stylesheet" id="def-user-stylesheet"></a>user style sheet</dfn>: Style sheets that are not provided by the web content author. The user interface for configuring user style sheets can be targeted at advanced users.</li> <li><dfn><a name="def-author-stylesheet" id="def-author-stylesheet"></a>author style sheet</dfn>: Style sheets specified by the author, resulting in <a href="#def-author-styles">author styles</a>. </li> </ul> </dd> <dt class="glossary"><a id="def-synchronize" name="def-synchronize"></a><dfn>synchronize</dfn></dt> <dd class="glossary">The act of time-coordinating two or more presentation components (e.g. a <a href="#def-visual-track">visual track</a> with captions, several tracks in a multimedia presentation). For authors, the requirement to synchronize means to provide the data that will permit sensible time-coordinated rendering by a user agent. For example, web content developers can ensure that the segments of caption text are neither too long nor too short, and that they map to segments of the visual track that are appropriate in length. For user agent developers, the requirement to synchronize means to present the content in a sensible time-coordinated fashion under a wide range of circumstances including technology constraints (e.g. small text-only displays), user limitations (e.g. slow reading speeds, large font sizes, high need for review or repeat functions), and content that is sub-optimal in terms of accessibility.</dd> <dt><a name="t" id="t"></a><a id="def-Web-Content-Technology" name="def-Web-Content-Technology"></a><dfn>technology (web content technology)</dfn></dt> <dd>A mechanism for encoding instructions to be rendered, played or executed by <a href="#def-user-agent">user agents</a>. Web content technologies can include markup languages, data formats, or programming languages that <a href="#def-author">authors</a> can use alone or in combination to create end-user experiences that range from static web pages to multimedia presentations to dynamic web applications. Some common examples of web content technologies include HTML, CSS, SVG, PNG, PDF, Flash, and JavaScript.</dd> <dt><a name="def-text" id="def-text">text</a><span class="glossary"></span></dt> <dd>A sequence of characters that are <a title="definition: programmatically available" href="#def-programmatically-avail">programmatically available</a>, where the sequence is expressing something in human language. <ul> <li><a name="def-non-text-content" id="def-non-text-content"><dfn>non-text content</dfn></a>: Any content that is not a sequence of characters that can be programmatically determined or where the sequence is not expressing something in human language Note: This includes ASCII Art (which is a pattern of characters), emoticons, leetspeak (which uses character substitution), and images representing text.</li> <li><a name="def-blocks-of-text" id="def-blocks-of-text"><dfn>blocks of text</dfn></a>: More than one sentence of text [ based on <a href="https://www.w3.org/TR/WCAG20/#blockstextdef">WCAG definition: blocks of text</a>]</li> </ul> </dd> <dt class="glossary"><a name="def-text-transcript" id="def-text-transcript"><dfn>text transcript</dfn></a></dt> <dd class="glossary">A type of alternative content that takes the form of text equivalents of audio information (e.g. an audio-only presentation or the <a class="dfn-instance" href="#def-audio-track" title="definition: Audio track">audio track</a> of a movie or other animation). A text transcript provides text for both spoken words and non-spoken sounds such as sound effects. Text transcripts make audio information accessible to people who have hearing disabilities and to people who cannot play the audio. Text transcripts are usually created by hand but can be generated on the fly (e.g. by voice-to-text converters).</dd> <dt><dfn>top-level viewport</dfn><span class="glossary"></span></dt> <dd>see <a href="#def-viewport"><strong>viewport</strong></a><strong></strong></dd> <dt class="glossary"><a name="u" id="u"></a><a name="def-user-agent" id="def-user-agent"></a><dfn>user agent</dfn></dt> <dd class="glossary">Any software that retrieves, renders and facilitates end user interaction with web content. UAAG 2.0 identifies the following user agent architectures: <ul> <li><a name="def-stand-alone" id="def-stand-alone"></a><dfn>platform-based user agent, native user agent</dfn>: User agents that run on non-web platforms (operating systems and cross-OS platforms, such as Java) and perform content retrieval, rendering and end-user interaction facilitation themselves (e.g. Firefox, Internet Explorer, Chrome, Opera, Windows Media Player, QuickTime Pro, RealPlayer). </li> <li><a name="def-plug-in" id="def-plug-in"></a><a name="def-embedded" id="def-embedded"><dfn>embedded user agent, plug-in</dfn></a>: User agents that "plug-in" to other user agents or applications (e.g. media player plug-in for a web browser, web view component). Embedded user agents can establish direct connections with the platform (e.g. communication via platform accessibility services). See <a href="#def-extension" class="dfn-instance">user agent add-on</a>. </li> <li><a name="def-web-based" id="def-web-based2"><dfn>web-based user agent</dfn></a>: User agents that have user interfaces that are implemented using web content technologies and are accessed by users via a user agent. Web-based user agents transform content into web content technologies that the host user agent can render (e.g.web-based ePub reader, web-based video player).</li> </ul> <em>Note 1: </em>Success criteria may also be met by other software. See the applicability notes on <a href="#applicability-note-addons">Add-ons (Extensions and Plug-ins)</a> and <a href="#applicability-note-platform">Relationship with operating system or platform</a>. <br /> <em>Note 2:</em> Many web applications retrieve, render and facilitate interaction with very limited data sets (e.g. online ticket booking). In such cases, WCAG 2.0, without UAAG 2.0, can be appropriate for assessing the application's accessibility. <br/> Examples of software that are generally considered user agents under UAAG 2.0: <ul> <li>Desktop web browsers (e.g. Internet Explorer, Firefox, Chrome, Safari, Opera)</li> <li>Mobile web browsers (e.g. Firefox, Chrome, Safari, Android Browser, Opera Mini, Atomic Web, Puffin)</li> <li>Browser plug-ins (e.g. QuickTime Plug-in for Firefox, Acrobat Reader Plug-in for Internet Explorer, Shockwave Plug-in for Chrome)</li> <li>Web view components (e.g. Webkit Webview component, Web Tools Platform Plug-in for Eclipse, UIWebView for iOS)</li> <li>Authoring tools that render the web content being edited (e.g. Word, Dreamweaver, HTML-Kit)</li> </ul> Examples of software that are not considered user agents under UAAG 2.0 (in all cases, WCAG 2.0 still applies if the software is web-based): <ul> <li>Operating environments or software bundles that include platform-based user agents (e.g. Windows, OS X, KDE, iOS), though the included user agents themselves are covered by UAAG 2.0.</li> <li>General-purpose platforms or toolkits that don't use web technologies, even though they can be used by user agents for other purposes (e.g. GNOME, KDE, .NET Framework/CLR).</li> <li>Narrow-purpose platform-based or web applications (e.g. online ticket booking applications).</li> <li>Authoring tools that only display a source view of the web content being edited (e.g. Notepad, Vim).</li> </ul> </dd> <dt class="glossary"><a name="def-extension" id="def-extension"></a><dfn>user agent add-on (add-in, extension, plug-in)</dfn></dt> <dd>Software installed into a <a class="dfn-instance" href="#def-user-agent">user agent</a> that adds one or more additional features that modify the behavior of the user agent. Extensions and plug-ins are types of add-ons. See <a href="#def-plug-in" class="dfn-instance">embedded user agent</a> and applicability note on <a href="#applicability-note-addons">Add-ons (Extensions and Plug-ins)</a> for additional information. Two common capabilities for user agent add-ons are the ability to <ul> <li>modify the <a class="dfn-instance" href="#def-content">content</a> before the user agent renders it (e.g. to add highlights if certain types of alternative content are present), and</li> <li>modify the user agent's own <a href="#def-ua-ui" class="dfn-instance"> user interface</a> (e.g. add a headings view).</li> </ul> </dd> <dt class="glossary"><a name="def-user-interface" id="def-user-interface"></a><dfn>user interface</dfn></dt> <dd class="glossary">For the purposes of UAAG 2.0, the user interface includes both: <ul> <li><a name="def-ua-ui" id="def-ua-ui"></a><dfn>user agent user interface (UA user interface)</dfn>: The <a href="#def-ui-control">controls</a> (e.g. menus, buttons, <a href="#def-prompt">prompts</a>, native audio/video player controls, and other components for input and output) and mechanisms (e.g. selection and focus) provided by the <a href="#def-user-agent">user agent</a> that are not created on the basis of the author-supplied <a class="dfn-instance" href="#def-content" title="definition: Content">content</a>. The UA user interface can include <a href="#def-extension">extensions</a> that become part of the UA user interface (e.g. toolbars, additional menus).</li> <li><a name="def-content-ui" id="def-content-ui"></a><dfn>content user interface</dfn>: The user interface that emerges from the user agent rendering of the author-supplied content. It includes all <a href="#def-rendered-content">rendered content</a> (e.g. <a href="#def-text">text</a>, headings, <a class="dfn-instance" href="#def-enabled-element" title="definition: Enabled element">enabled elements</a>, disabled elements, author-supplied audio/video controls). <br /> <em> Note:</em> There can be a mix of <a href="#def-recognize">recognized</a> and unrecognized user interface controls depending on the author-supplied content.</li> </ul> This document distinguishes UA user interface and content user interface only where required for clarity.</dd> <dt><a name="def-ui-control" id="def-ui-control"></a><dfn>user interface control</dfn></dt> <dd>A component of the <a href="#def-ua-ui">user agent user interface</a> or the <a href="#def-content-ui">content user interface</a>, distinguished where necessary. </dd> <dt><a name="v" id="v"></a><a name="def-video" id="def-video"></a><dfn>video</dfn></dt> <dd>The technology of moving pictures or images. Video can be made up of animated or photographic images, or both.</dd> <dt><a name="def-view" id="def-view"></a><dfn>view</dfn><span class="glossary"></span></dt> <dd class="glossary"> A user interface function that lets users interact with web content. UAAG 2.0 recognizes a variety of approaches to presenting the content in a view, including: <ul> <li><a name="def-rendered-view" id="def-rendered-view"><dfn>rendered view</dfn></a>: A view where content is presented such that it is rendered, played or executed. There are two sub-types: <ul> <li>In conventionally rendered views the content is rendered, played or executed according to the web content technology specification. This is the default view of most user agents.</li> <li>In unconventionally rendered views the content is rendered quite differently than specified in the technology specification (e.g. rendering an audio file as a graphical wavefront).</li> </ul> </li> <li><a name="def-source-view" id="def-source-view"><dfn>source view</dfn></a>: A view where the web content is presented without being rendered, played or executed. The source view can be plain text (i.e. "View Source") or it can include some other organization (e.g. presenting the markup in a tree).</li> <li><a name="def-outline-view" id="def-outline-view"><dfn>outline view</dfn></a>: A view where only a subset of the rendered content is presented, usually composed of labels or placeholders for important structural elements. The important structural elements will depend on the web content technology, but can include headings, table captions, and content sections.</li> </ul> <em>Note: </em>A view can be visual, audio, or tactile.</dd> <dt class="glossary"><a name="def-viewport" id="def-viewport"></a><dfn>viewport</dfn></dt> <dd>A mechanism for presenting only part of a visual or tactile <a href="#def-view">view</a> to the user via a screen or tactile display. There can be multiple viewports on to the same underlying view (e.g. when a split-screen is used to present the top and bottom of a document simultaneously) and viewports can be nested (e.g. a scrolling frame located within a larger document). When the viewport is smaller than the view it is presenting, some of the view will not be presented. Mechanisms are typically provided to move the view or the viewport such that all of the view can be brought into the viewport (e.g. scrollbars). </dd> <dd><span class="glossary-note">Note</span>: In UAAG 1.0 viewports were defined as having a temporal dimension. In UAAG 2.0, this is not the case. Since audio content is inherently time-based, audio viewports are excluded.</dd><dd> <ul> <li><a name="def-viewport-toplevel" id="def-viewport-toplevel"></a><dfn>top-level viewport</dfn>: A viewport that is not contained within another viewport of a platform-based user agent. Web-based user agents are always displayed inside another viewport, and therefore are never top-level viewports. A popular browser implementation is to provide a window that includes some <a class="dfn-instance" href="#def-ua-ui" rel="glossary" title="definition: user agent user interface">UA user interface</a> elements (e.g., menus) and a series of tabbed panels, each of which contains additional UA user interface elements (e.g., address bar, bookmarks, back/forward buttons) and a top-level viewport for rendering a view of the addressed web resource.</li> </ul> </dd> <dt class="glossary"><a name="viewport-dimension" id="viewport-dimension"></a><dfn>viewport dimensions</dfn></dt> <dd>The onscreen size of a <a href="#def-viewport">viewport</a>, or the temporal duration of a viewport displaying time-based media. When the dimensions (spatial or temporal) of rendered content exceed the dimensions of the viewport, the user agent provides mechanisms such as scroll bars and advance and rewind controls so that the user can access the rendered content "outside" the viewport (e.g. when the user can only view a portion of a large document through a small graphical viewport, or when audio content has already been played).</dd> <dt class="glossary"><a name="def-visual-only-presentation" id="def-visual-only-presentation"></a><dfn>visual-only</dfn></dt> <dd class="glossary">Content consisting exclusively of one or more <a class="dfn-instance" href="#def-visual-track" title="definition: Visual track">visual tracks</a> presented concurrently or in series (e.g. a silent movie is an example of a visual-only presentation).</dd> <dt class="glossary"><a name="def-visual-track" id="def-visual-track"></a><dfn>visual track</dfn></dt> <dd class="glossary">Content rendered through a graphical <a class="dfn-instance" href="#def-viewport" title="definition: viewport">viewport</a>. Visual objects include graphics, text, and visual portions of movies and other animations. A visual track is a visual object that is intended as a whole or partial presentation. A visual track does not necessarily correspond to a single physical object or software object.</dd> <dt class="glossary"><a name="def-voice-browser" id="def-voice-browser"></a><dfn>voice browser</dfn></dt> <dd class="glossary">A device (hardware and software) that interprets voice markup languages to generate voice output, interpret voice input, and possibly accept and produce other modalities of input and output. Definition from "Introduction and Overview of W3C Speech Interface Framework" <cite><a href="#ref-VOICEBROWSER" title="Link to reference VOICEBROWSER">[VOICEBROWSER]</a></cite>.</dd> <dt class="glossary"><a name="w" id="w"></a><a name="def-web-resource" id="def-web-resource"></a><dfn>web resource</dfn></dt> <dd>Anything that can be identified by a Uniform Resource Identifier (<acronym>URI</acronym>).</dd> </dl> <hr /> <div id="sect-this-doc-ref"> <h2><a name="ref-this-doc" id="ref-this-doc"></a>Appendix B: How to refer to UAAG 2.0 from other documents</h2> <p>This section is <a href="#def-informative" title="definition: informative" class="dfn-instance">informative</a>. </p> <p>For the most up-to-date information, see "Referencing and Linking to WAI Guidelines and Technical Documents" at <<a href="https://www.w3.org/WAI/intro/linking.html">http://www.w3.org/WAI/intro/linking.html</a>>. </p> <p>There are two recommended ways to refer to the "User Agent Accessibility Guidelines 2.0" (and to W3C documents in general):</p> <ol> <li>References to a specific version of "User Agent Accessibility Guidelines 2.0." For example, use the "this version" <acronym>URI</acronym> to refer to the current document:<br /> <a href="https://www.w3.org/TR/2015/NOTE-UAAG20-20151215/">http://www.w3.org/TR/2015/NOTE-UAAG20-20151215/</a></li> <li>References to the latest version of "User Agent Accessibility Guidelines 2.0." Use the "latest version" URI to refer to the most recently published document in the series: <br /> <a href="https://www.w3.org/TR/UAAG20/">http://www.w3.org/TR/UAAG20/</a>.</li> </ol> <p>The top of UAAG 2.0 includes the relevant catalog metadata for specific references (including title, publication date, "this version" <acronym>URI</acronym>, editors' names, and copyright information).</p> <div id="example"> <p>An XHTML 1.0 paragraph including a reference to this specific document might be written: </p> <blockquote> <p><code><p><br /> <cite><a href="http://www.w3.org/TR/2010/WD-UAAG20-20100617/"><br /> "User Agent Accessibility Guidelines 2.0,"</a></cite><br /> J. Allan, K. Ford, J. Spellman, eds.,<br /> W3C Recommendation, http://www.w3.org/TR/ATAG20/.<br /> The <a href="http://www.w3.org/TR/ATAG20/">latest version</a> of this document is available at http://www.w3.org/TR/ATAG20/.</p> </code></p> </blockquote> </div>  <p>For very general references to this document (where stability of content and anchors is not required), it can be appropriate to refer to the latest version of this document. Other sections of this document explain how to build a <a href="#conformance">conformance claim</a>.</p> <hr /> </div>  <h2><a name="references" id="references"></a>Appendix C: References</h2> <p>This section is <a href="#def-informative">informative</a>.</p> <p>For the <strong>latest version</strong> of any <acronym title="the World Wide Web Consortium">W3C</acronym> specification please consult the list of <a href="https://www.w3.org/TR/"><acronym title="the World Wide Web Consortium">W3C</acronym> Technical Reports</a> at http://www.w3.org/TR/. Some documents listed below may have been superseded since the publication of UAAG 2.0.</p> <p><strong>Note:</strong> In UAAG 2.0, bracketed labels such as "[WCAG20]" link to the corresponding entries in this section. These labels are also identified as references through markup.</p> <dl> <dt><a name="ref-ARIA10" id="ref-ARIA10">[ARIA10]</a></dt> <dd>"Accessible Rich Internet Applications (WAI-ARIA) 1.0" J. Craig, M. Cooper, eds., 20 March 2014. This W3C Recommendation is <a href="https://www.w3.org/TR/2014/REC-wai-aria-20140320/">http://www.w3.org/TR/2014/REC-wai-aria-20140320/</a></dd> <dt><a name="ref-ATAG10" id="ref-ATAG10">[ATAG20]</a></dt> <dd><a href="https://www.w3.org/TR/2015/REC-ATAG20-20150924/">"Authoring Tool Accessibility Guidelines (ATAG) 2.0,"</a> J. Richards, J. Spellman, J. Treviranus, eds., 24 September 2015. This W3C Recommendation is http://www.w3.org/TR/2015/REC-ATAG20-20150924/</dd> <dt><a name="ref-ATAG10-TECHS" id="ref-ATAG10-TECHS">[ATAG20-IMPLEMENTING]</a></dt> <dd><cite><a href="https://www.w3.org/TR/2002/NOTE-ATAG10-TECHS-20021029/">"Implementing ATAG 2.0"</a></cite> J. Richards, J. Spellman, J. Treviranus, eds., 24 September 2015. This W3C Note is http://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/. </dd> <dt><a name="ref-CHARMOD" id="ref-CHARMOD">[CHARMOD]</a></dt> <dd><cite><a href="https://www.w3.org/TR/2002/WD-charmod-20020430/">"Character Model for the World Wide Web,"</a></cite> M. Dürst and F. Yergeau, eds., 30 April 2002. This W3C Working Draft is http://www.w3.org/TR/2002/WD-charmod-20020430/. The <a href="https://www.w3.org/TR/charmod/">latest version</a> is available at http://www.w3.org/TR/charmod/.</dd> <dt><a name="ref-CSS2" id="ref-CSS2">[CSS21]</a></dt> <dd><cite><a href="https://www.w3.org/TR/2011/REC-CSS2-20110607/">"Cascading Style Sheets Level 2 Revision 1 (CSS 2.1) Specification,"</a></cite> B. Bos, T. Celik, I. Hickson, H. Lie, eds., 07 June 2011. This W3C Recommendation is http://www.w3.org/TR/2011/REC-CSS2-20110607/.</dd> <dt><a name="ref-DOM2HTML" id="ref-DOM2HTML">[DOM2HTML]</a></dt> <dd><cite><a href="https://www.w3.org/TR/2002/PR-DOM-Level-2-HTML-20021108/">"Document Object Model (DOM) Level 2 HTML Specification,"</a></cite> J. Stenback, P. Le Hégaret, A. Le Hors, eds., 8 November 2002. This W3C Proposed Recommendation is http://www.w3.org/TR/2002/PR-DOM-Level-2-HTML-20021108/. The <a href="https://www.w3.org/TR/DOM-Level-2-HTML/">latest version</a> is available at http://www.w3.org/TR/DOM-Level-2-HTML/.</dd> <dt><a name="ref-HTML4" id="ref-HTML4">[HTML4]</a></dt> <dd><cite><a href="https://www.w3.org/TR/1999/REC-html401-19991224/">"HTML 4.01 Recommendation,"</a></cite> D. Raggett, A. Le Hors, and I. Jacobs, eds., 24 December 1999. This W3C Recommendation is http://www.w3.org/TR/1999/REC-html401-19991224/.</dd> <dt><a name="ref-RFC2616" id="ref-RFC2616">[RFC2616]</a></dt> <dd><cite><a href="http://www.ietf.org/rfc/rfc2616.txt">"Hypertext Transfer Protocol — HTTP/1.1,"</a></cite> J. Gettys, J. Mogul, H. Frystyk, L. Masinter, P. Leach, T. Berners-Lee, June 1999.</dd> <dt><a name="ref-RFC3023" id="ref-RFC3023">[RFC3023]</a></dt> <dd><cite><a href="http://www.ietf.org/rfc/rfc3023.txt">"XML Media Types,"</a></cite> M. Murata, S. St. Laurent, D. Kohn, January 2001.</dd> <dt><a name="ref-SMIL" id="ref-SMIL">[SMIL]</a></dt> <dd><cite><a href="https://www.w3.org/TR/1998/REC-smil-19980615/">"Synchronized Multimedia Integration Language (SMIL) 1.0 Specification,"</a></cite> P. Hoschka, ed., 15 June 1998. This W3C Recommendation is http://www.w3.org/TR/1998/REC-smil-19980615/.</dd> <dt><a name="ref-SMIL20" id="ref-SMIL20">[SMIL20]</a></dt> <dd><cite><a href="https://www.w3.org/TR/2001/REC-smil20-20010807/">"Synchronized Multimedia Integration Language (SMIL 2.0) Specification,"</a></cite> J. Ayars, et al., eds., 7 August 2001. This W3C Recommendation is http://www.w3.org/TR/2001/REC-smil20-20010807/.</dd> <dt><a name="ref-SVG" id="ref-SVG">[SVG]</a></dt> <dd><cite><a href="https://www.w3.org/TR/2001/REC-SVG-20010904/">"Scalable Vector Graphics (SVG) 1.0 Specification,"</a></cite> J. Ferraiolo, ed., 4 September 2001. This W3C Recommendation is http://www.w3.org/TR/2001/REC-SVG-20010904/.</dd> <dt><a name="ref-UAAG10" id="ref-UAAG10"><strong>[UAAG10]</strong></a></dt> <dd>"<a href="https://www.w3.org/TR/2002/REC-UAAG10-20021217/">User Agent Accessibility Guidelines 1.0</a>," I. Jacobs, J. Gunderson, E. Hansen, eds.17 December 2002. This W3C Recommendation is available at http://www.w3.org/TR/2002/REC-UAAG10-20021217/. </dd> <dt><a name="ref-UAAG10-CHECKLIST" id="ref-UAAG10-CHECKLIST">[UAAG10-CHECKLIST]</a></dt> <dd>An appendix to UAAG 2.0 lists all of the checkpoints, sorted by priority. The checklist is available in either <a rel="Appendix" title="Tabular form of AUGL Checklist" href="https://www.w3.org/TR/2002/REC-UAAG10-20021217/uaag10-chktable">tabular form</a> or <a rel="Appendix" title="List form of AUGL Checklist" href="https://www.w3.org/TR/2002/REC-UAAG10-20021217/uaag10-chklist">list form</a>.</dd> <dt><a name="ref-UAAG10-ICONS" id="ref-UAAG10-ICONS">[UAAG10-ICONS]</a></dt> <dd>Information about <a href="https://www.w3.org/WAI/UAAG10-Conformance">UAAG 1.0 conformance icons</a> and their usage is available at http://www.w3.org/WAI/UAAG10-Conformance.</dd> <dt><a name="ref-UAAG10-SUMMARY" id="ref-UAAG10-SUMMARY">[UAAG10-SUMMARY]</a></dt> <dd>An appendix to UAAG 1.0 provides a <a href="https://www.w3.org/TR/2002/REC-UAAG10-20021217/uaag10-summary" rel="Appendix">summary</a> of the goals and structure of User Agent Accessibility Guidelines 1.0.</dd> <dt><a name="ref-UAAG10-TECHS" id="ref-UAAG10-TECHS">[UAAG10-TECHS]</a></dt> <dd><cite><a href="https://www.w3.org/TR/UAAG10-TECHS/">"Techniques for User Agent Accessibility Guidelines 1.0,"</a></cite> I. Jacobs, J. Gunderson, E. Hansen, eds. The latest draft of the techniques document is available at http://www.w3.org/TR/UAAG10-TECHS/.</dd> <dt><a name="ref-UNICODE" id="ref-UNICODE">[UNICODE]</a></dt> <dd>The Unicode Consortium. <em><a href="http://www.unicode.org/versions/Unicode8.0.0/">The Unicode Standard, Version 8.0.0</a></em>, (Mountain View, CA: The Unicode Consortium, 2015. ISBN 978-1-936213-10-8) <br /> link: http://www.unicode.org/versions/Unicode8.0.0/</dd> <dt><a name="ref-VOICEBROWSER" id="ref-VOICEBROWSER">[VOICEBROWSER]</a></dt> <dd><cite><a href="https://www.w3.org/TR/2000/WD-voice-intro-20001204/">"Introduction and Overview of W3C Speech Interface Framework,"</a></cite> J. Larson, 4 December 2000. This W3C Working Draft is http://www.w3.org/TR/2000/WD-voice-intro-20001204/. The <a href="https://www.w3.org/TR/voice-intro/">latest version</a> is available at http://www.w3.org/TR/voice-intro/. UAAG 2.0 includes references to additional W3C specifications about voice browser technology.</dd> <dt><a name="ref-W3CPROCESS" id="ref-W3CPROCESS">[W3CPROCESS]</a></dt> <dd><cite><a href="https://www.w3.org/Consortium/Process-20010719/">"World Wide Web Consortium Process Document,"</a></cite> I. Jacobs ed. The 19 July 2001 version of the Process Document is http://www.w3.org/Consortium/Process-20010719/. The <a href="https://www.w3.org/Consortium/Process/">latest version</a> is available at http://www.w3.org/Consortium/Process/.</dd> <dt><a name="ref-WCAG20" id="ref-WCAG20">[WCAG20]</a></dt> <dd><cite><a href="https://www.w3.org/TR/WCAG20/">"Web Content Accessibility Guidelines (WCAG) 2.0"</a></cite> B. Caldwell, M. Cooper, L. Guarino Reid, G. Vanderheiden, eds., 8 December 2008. This W3C Recommendation is http://www.w3.org/TR/2008/REC-WCAG20-20081211/. The <a href="https://www.w3.org/TR/WCAG20/">latest version</a> is available at http://www.w3.org/TR/WCAG20/. Additional format-specific techniques documents are available from this Recommendation.</dd> <dt><a name="ref-WCAG10-TECHS" id="ref-WCAG10-TECHS">[WCAG20-TECHS]</a></dt> <dd><cite><a href="https://www.w3.org/TR/WCAG10-TECHS/">"Techniques for Web Content Accessibility Guidelines 2.0,"</a></cite> B. Caldwell, M. Cooper, L. Guarino Reid, G. Vanderheiden, eds., 8 December 2008. This W3C Note is http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/. The <a href="https://www.w3.org/TR/WCAG20-TECHS/">latest version</a> is available at http://www.w3.org/TR/WCAG20-TECHS/. Additional format-specific techniques documents are available from this Note.</dd> <dt><a name="ref-WCAG-EM" id="ref-WCAG-EM"></a>[WCAG-EM]</dt> <dd><a href="https://www.w3.org/TR/2013/WD-WCAG-EM-20130226/">"Website Accessibility Conformance Evaluation Methodology (WCAG-EM) 1.0"</a> E. Velleman, S. Abou-Zahra, eds., 26 February 2013. This is an informative draft of a Working Group Note. The <a href="https://www.w3.org/TR/WCAG-EM/">latest version</a> is available at http://www.w3.org/TR/WCAG-EM/</dd> <dt><a name="ref-wcag2ict" id="ref-wcag2ict"></a>[WCAG2ICT]</dt> <dd><a href="https://www.w3.org/TR/wcag2ict/">Guidance on Applying WCAG 2.0 to Non-Web Information and Communications Technologies (WCAG2ICT)</a> M. Cooper, P. Korn, A. Snow-Weaver, G. Vanderheiden, eds., 5 September 2013. This document is available in an <a href="https://www.w3.org/WAI/GL/2013/WD-wcag2ict-20130905/accordion">expandable / collapsible alternate version</a> in which the “Intent” sections copied from Understanding WCAG 2.0 are hidden and individually expandable, for easier reading. </dd> <dt><a name="ref-WEBCHAR" id="ref-WEBCHAR">[WEBCHAR]</a></dt> <dd><cite><a href="https://www.w3.org/1999/05/WCA-terms/01">"Web Characterization Terminology and Definitions Sheet,"</a></cite> B. Lavoie, H. F. Nielsen, eds., 24 May 1999. This is a W3C Working Draft that defines some terms to establish a common understanding about key Web concepts. This W3C Working Draft is http://www.w3.org/1999/05/WCA-terms/01.</dd> <dt><a name="ref-XAG10" id="ref-XAG10">[XAG10]</a></dt> <dd><cite><a href="https://www.w3.org/TR/2002/WD-xag-20021003">"XML Accessibility Guidelines 1.0,"</a></cite> D. Dardailler, S. Palmer, C. McCathieNevile, eds., 3 October 2001. This W3C Working Draft is http://www.w3.org/TR/2002/WD-xag-20021003. The <a href="https://www.w3.org/TR/xag">latest version</a> is available at http://www.w3.org/TR/xag.</dd> <dt><a name="ref-XML" id="ref-XML">[XML]</a></dt> <dd><a href="https://www.w3.org/TR/1998/REC-xml-19980210">"Extensible Markup Language (XML) 1.0 (Second Edition),"</a> T. Bray, J. Paoli, C.M. Sperberg-McQueen, eds., 6 October 2000. This W3C Recommendation is http://www.w3.org/TR/2000/REC-xml-20001006.</dd> <dt><a name="ref-XHTML10" id="ref-XHTML10">[XHTML10]</a></dt> <dd><cite><a href="https://www.w3.org/TR/2000/REC-xhtml1-20000126/">"XHTML[tm] 1.0: The Extensible HyperText Markup Language,"</a></cite> S. Pemberton, et al., 26 January 2000. This W3C Recommendation is http://www.w3.org/TR/2000/REC-xhtml1-20000126/.</dd> <dt><a name="ref-XMLDSIG" id="ref-XMLDSIG">[XMLDSIG]</a></dt> <dd><cite><a href="https://www.w3.org/TR/2002/REC-xmldsig-core-20020212/">"XML-Signature Syntax and Processing,"</a></cite> D. Eastlake, J. Reagle, D. Solo, eds., 12 February 2002. This W3C Recommendation is http://www.w3.org/TR/2002/REC-xmldsig-core-20020212/.</dd> <dt><a name="ref-XMLENC" id="ref-XMLENC">[XMLENC]</a></dt> <dd><cite><a href="https://www.w3.org/TR/2002/REC-xmlenc-core-20021210/">"XML Encryption Syntax and Processing,"</a></cite> D. Eastlake, J. Reagle, eds., 10 December 2002. This W3C Recommendation is http://www.w3.org/TR/2002/REC-xmlenc-core-20021210/.</dd> </dl> <hr /> <h2><a id="acknowledgments" name="acknowledgments"></a>Appendix D: Acknowledgments</h2> <h3><a name="active-participants" id="active-participants"></a>Participants active in the UAWG prior to publication:</h3> <ul> <li>Jim Allan (Chair, Texas School for the Blind and Visually Impaired)</li> <li>Eric Hansen (Educational Testing Service)</li> <li>Greg Lowney (Invited Expert)</li> <li>Kimberly Patch (Invited Expert)</li> <li>Jan Richards ( Inclusive Design Institute, OCAD University)</li> <li>Jeanne Spellman (W3C Staff Contact)</li> </ul> <dl> <dt>Previous Editors:</dt> <dd>Kelly Ford, Microsoft</dd> <dd>Jan Richards, Inclusive Design Institute, OCAD University</dd> </dl> <h3 id="mobile_contributors">Additional Contributors of Mobile Examples </h3> <ul> <li>Kathy Walhbin</li> <li>Mark Sadecki</li> </ul> <h3><a name="previous-participants" id="previous-participants"></a>Other previously active UAWG participants and other contributors to UAAG 2.0:</h3> <ul> <li>Judy Brewer (W3C)</li> <li>Alan Cantor (Invited Expert)</li> <li>Wayne Dick (Invited Expert)</li> <li>Bim Egan (Royal National Institute of Blind People)</li> <li>Kelly Ford (Microsoft)</li> <li>Mark Hakkinen (Educational Testing Service)</li> <li>Simon Harper (University of Manchester)</li> <li>Sean Hayes (Microsoft)</li> <li>Dean Hudson (Apple)</li> <li>Patrick Lauke (Opera Software)</li> <li>Cathy Laws (IBM)</li> <li>Peter Parente (IBM)</li> <li>David Poehlman (Invited Expert)</li> <li>Simon Pieters (Opera Software)</li> <li>Henny Swan (Opera Software)</li> <li>Gregory Rosmaita (Invited Expert)</li> <li>David Tseng (Apple) </li> </ul> <p>UAAG 2.0 would not have been possible without the work of <a href="https://www.w3.org/TR/WAI-USERAGENT/acks.html#Acknowledgments">those who contributed to UAAG 1.0</a>.</p> <p>This publication has been funded in part with Federal funds from the U.S. Department of Health and Human Services, National Institute on Disability Independent Living and Rehabilitation Research (NIDILRR) under contract HHSP23301500054, and previously by the Department of Education's NIDILRR contracts ED05CO0039 and ED-OSE-10-C-006. The content of this publication does not necessarily reflect the views or official policies of the U.S. Department of Education or U.S. Department of Health and Human Services, nor does mention of trade names, commercial products, or organizations imply endorsement by the U.S. Government. </p> <hr /> <script type="application/javascript" src="https://www.w3.org/scripts/TR/fixup.js"></script></body> </html>