CINXE.COM

<!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> <title>Authoring Tool Accessibility Guidelines (ATAG) 2.0</title> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <style type="text/css"> body { color: #000000; font-weight: normal; line-height: 1.3; } h2.principle { background-color:#FFFFFF; border:thin solid #666666; color:#000000; font-weight:bold; padding:0.5em; } h3.guideline { background-color:#CFE8EF !important; border:thin solid #000066; color:#000000; margin-bottom:0; padding:0.5em; } h4.sc-title { display: inline; margin-bottom: 0.5em; margin-top: 0.5em; font: bold 0.9em sans-serif; } p.sc-title { display: inline; } ul.sc-bullets { display:block; padding-left:2em; margin-top: 0em; margin-bottom: 0em; list-style-type: none; } ul.sc-notes { display:block; padding-left:1em; margin-top: 0em; margin-bottom: 0em; list-style-type: none; } h5.implementing-heading { font-size:0.9em; font-weight:bold; font-style:normal; margin-top: 0em; 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; margin-bottom: 1em; } div.implementing-link a{ background-color: #F4F4FF; border-color:#BBBBBB; border-style: solid; border-width: 1px; padding: 0.25em; } 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; } p.rationale { margin-left: 1em; } ul.techs-only { border: gray 1px solid; padding: 0.5em; margin: 0.1em; list-style:none; } strong.handle { font-size: .9em; } em.note-handle { font-size: .9em; } dfn { font-weight:bold; font-style:normal; } .figure { font-size:x-small; } DL { margin-bottom: 1em; } .termdef { border-bottom:1px dotted #585858; color:#000000 !important; text-decoration:none; } dt {margin-top: 0.5em} div.toc ul.toc li a { margin-top:.3em; } div.toc ul.toc li ul.toc li a { margin-top:.3em; } div.toc ul.toc li ul.toc li ul.toc li a { margin-top:0; } </style> <link href="https://www.w3.org/StyleSheets/TR/W3C-REC.css" type="text/css" rel="stylesheet" /> </head> <body> <div class="head"> <div class="gl-only"> <p align="center">[<a href="#contents">Table of Contents</a>]  |  [<a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/">Implementing ATAG 2.0</a>] </p> <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>Authoring Tool Accessibility Guidelines (ATAG) 2.0</h1> <h2><a name="w3c-doctype" id="w3c-doctype"></a>W3C Recommendation 24 September 2015</h2> <dl> <dt>This version:</dt> <dd><a href="https://www.w3.org/TR/2015/REC-ATAG20-20150924/">http://www.w3.org/TR/2015/REC-ATAG20-20150924/</a></dd> <dt>Latest version:</dt> <dd><a href="https://www.w3.org/TR/ATAG20/">http://www.w3.org/TR/ATAG20/</a></dd> <dt>Previous version:</dt> <dd><a href="https://www.w3.org/TR/2015/PR-ATAG20-20150721/">http://www.w3.org/TR/2015/PR-ATAG20-20150721/</a></dd> <dt>Editors:</dt> <dd>Jan Richards, Inclusive Design Institute, OCAD University </dd> <dd>Jeanne Spellman, W3C</dd> <dd>Jutta Treviranus, Inclusive Design Institute, OCAD University</dd> </dl> <p>Please refer to the <a href="https://www.w3.org/WAI/AU/errata/"><strong>errata</strong></a> for this document for any errors or issues reported since publication. </p> <p>See also <a href="https://www.w3.org/2003/03/Translations/byTechnology?technology=ATAG20"><strong>translations</strong></a>.</p> <p> </p> <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> </div>  </div>  <hr /> <div id="sect-abstract"> <h2><a id="abstract" name="abstract">Abstract</a></h2> <div class="gl-only"> <p>The Authoring Tool Accessibility Guidelines (ATAG) 2.0 provides guidelines for designing web content authoring tools that are both more accessible to authors with disabilities (Part A) and designed to enable, support, and promote the production of more accessible web content by all authors (Part B). See <a href="https://www.w3.org/WAI/intro/atag.php">Authoring Tool Accessibility Guidelines (ATAG) Overview</a> for an introduction and links to ATAG technical and educational material.</p> </div> </div>  <div id="sect-status"> <h2><a id="status" name="status">Status of This Document</a></h2> <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 W3C publications and the latest revision of this technical report can be found in the <a href="https://www.w3.org/TR/">W3C technical reports index</a> at http://www.w3.org/TR/.</em></p> <div class="gl-only"> <h3><a name="status-status" id="status-status"></a>W3C Recommendation of ATAG 2.0</h3> <p>This is the Authoring Tool Accessibility Guidelines (ATAG) 2.0 <a href="https://www.w3.org/2004/02/Process-20040205/tr.html#RecsW3C"> W3C Recommendation</a> of 24 September 2015 from the <a href="https://www.w3.org/WAI/AU/">Authoring Tool Accessibility Guidelines Working Group</a>. The Working Group created an <a href="https://www.w3.org/WAI/AU/CR20/ImplementationReport">implementation report</a> that shows the <a href="https://www.w3.org/TR/2015/CR-ATAG20-20150604/#exit">exit criteria</a> have been met. The Director approved transition to Recommendation after reviewing this report and after Advisory Committee vote which supported publication. There are no changes to the text of ATAG 2.0. There have been minor edits to the code to fix spacing and to remove superfluous or commented HTML. </p> <p>This document has been reviewed by W3C Members, by software developers, and by other W3C groups and interested parties, and is endorsed by the Director as a W3C Recommendation. It is a stable document and may be used as reference material or cited from another document. W3C's role in making the Recommendation is to draw attention to the specification and to promote its widespread deployment. This enhances the functionality and interoperability of the Web. </p> <p>ATAG 2.0 is supported by the associated non-normative document, <a href="https://www.w3.org/TR/IMPLEMENTING-ATAG20/">Implementing ATAG 2.0</a><a href="https://www.w3.org/TR/WCAG20-TECHS/"></a>. Although this document does not have the formal status that ATAG 2.0 itself has, it provides information important to understanding and implementing ATAG 2.0. </p> <p>The Working Group requests that any comments sent to <a href="mailto:public-atag2-comments@w3.org">public-atag2-comments@w3.org</a>. The <a href="http://lists.w3.org/Archives/Public/public-atag2-comments/">archives for the public comments list</a> are publicly available. Comments received on the ATAG 2.0 Recommendation cannot result in changes to this version of the guidelines, but may be addressed in errata or future versions of ATAG. The Working Group does not plan to make formal responses to comments. Archives of the <a href="https://lists.w3.org/Archives/Public/w3c-wai-au/">ATAG WG mailing list discussions</a> are publicly available, and future work undertaken by the Working Group or subsequent group may address comments received on this document.</p> </div>  <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 AUWG are discussed in the <a href="https://www.w3.org/WAI/AU/2010/auwg_charter.html">Working Group charter</a>. </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/35520/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> </div>  <hr /> <div class="toc"> <h2><a id="contents" name="contents"></a>Table of Contents</h2> <div class="gl-only"> <ul class="toc"> <li><a href="#abstract">Abstract</a></li> <li><a href="#status">Status of This Document</a> </li> <li><a href="#intro">Introduction</a> <ul class="toc"><li><a href="#intro-organization">ATAG 2.0 Layers of Guidance</a></li> <li><a href="#intro_understand_levels_conformance">Levels of Conformance</a></li> <li><a href="#intro-integrate_acc_features">Integration of Accessibility Features</a></li> </ul> </li> <li><a href="#guidelines">ATAG 2.0 Guidelines</a> <ul class="toc"> <li><a href="#part_a">A. Make the authoring tool user interface accessible</a> <ul class="toc"> <li><a href="#principle_a1">A.1. Authoring tool user interfaces follow applicable accessibility guidelines</a> <ul> <li><a href="#gl_a11">A.1.1. (For the authoring tool user interface) Ensure that web-based functionality is accessible</a></li> <li><a href="#gl_a12">A.1.2. (For the authoring tool user interface) Ensure that non-web-based functionality is accessible</a></li> </ul> </li> <li><a href="#principle_a2">A.2. Editing-views are perceivable </a> <ul> <li><a href="#gl_a21">A.2.1. (For the authoring tool user interface) Make alternative content available to authors</a></li> <li><a href="#gl_a22">A.2.2. (For the authoring tool user interface) Ensure that editing-view presentation can be programmatically determined</a></li> </ul> </li> <li><a href="#principle_a3">A.3. Editing-views are operable</a> <ul> <li><a href="#gl_a31">A.3.1. (For the authoring tool user interface) Provide keyboard access to authoring features</a></li> <li><a href="#gl_a32">A.3.2. (For the authoring tool user interface) Provide authors with enough time</a></li> <li><a href="#gl_a33">A.3.3. (For the authoring tool user interface) Help authors avoid flashing that could cause seizures</a></li> <li><a href="#gl_a34">A.3.4. (For the authoring tool user interface) Enhance navigation and editing via content structure</a></li> <li><a href="#gl_a35">A.3.5. (For the authoring tool user interface) Provide text search of the content</a></li> <li><a href="#gl_a36">A.3.6. (For the authoring tool user interface) Manage preference settings</a></li> <li><a href="#gl_a37">A.3.7. (For the authoring tool user interface) Ensure that previews are at least as accessible as in-market user agents</a></li> </ul> </li> <li><a href="#principle_a4">A.4. Editing-views are understandable</a> <ul> <li><a href="#gl_a41">A.4.1. (For the authoring tool user interface) Help authors avoid and correct mistakes</a></li> <li><a href="#gl_a42">A.4.2. (For the authoring tool user interface) Document the user interface, including all accessibility features</a></li> </ul> </li> </ul> </li> <li><a href="#part_b">B. Support the production of accessible content</a> <ul class="toc"> <li><a href="#principle_b1">B.1. Fully automatic processes produce accessible content </a> <ul> <li><a href="#gl_b11">B.1.1. Ensure that automatically-specified content is accessible</a></li> <li><a href="#gl_b12">B.1.2. Ensure that accessibility information is preserved</a></li> </ul> </li> <li><a href="#principle_b2">B.2. Authors are supported in producing accessible content</a> <ul> <li><a href="#gl_b21">B.2.1. Ensure that accessible content production is possible</a></li> <li><a href="#gl_b22">B.2.2. Guide authors to produce accessible content</a></li> <li><a href="#gl_b23">B.2.3. Assist authors with managing alternative content for non-text content</a></li> <li><a href="#gl_b24">B.2.4. Assist authors with accessible templates</a></li> <li><a href="#gl_b25">B.2.5. Assist authors with accessible pre-authored content</a></li> </ul> </li> <li><a href="#principle_b3">B.3. Authors are supported in improving the accessibility of existing content</a> <ul> <li><a href="#gl_b31">B.3.1. Assist authors in checking for accessibility problems</a></li> <li><a href="#gl_b32">B.3.2. Assist authors in repairing accessibility problems</a></li> </ul> </li> <li><a href="#principle_b4">B.4. Authoring tools promote and integrate their accessibility features</a> <ul> <li><a href="#gl_b41">B.4.1. Ensure the availability of features that support the production of accessible content</a></li> <li><a href="#gl_b42">B.4.2. Ensure that documentation promotes the production of accessible content</a></li> </ul> </li> </ul> </li> </ul> </li> <li><a href="#Conformance">Implementing ATAG 2.0 Conformance</a> <ul class="toc"> <li><a href="#conf-req">Conformance Requirements </a> <ul> <li><a href="#conf-sc-satisfaction">Success Criteria Satisfaction</a></li> <li><a href="#conf-rel-wcag">Relationship to the Web Content Accessibility Guidelines (WCAG) 2.0</a></li> <li><a href="#conf-levels">Conformance Options and Levels</a></li> <li><a href="#conf-techs-produced">Web Content Technologies Produced</a></li> <li><a href="#conf-live-publishing">Live Publishing Authoring Tools</a></li> </ul> </li> <li><a href="#conf-claim">Conformance Claims (Optional)</a> <ul> <li><a href="#conf-sc-satisfaction">Required Components of a Conformance Claim</a></li> <li><a href="#conf-claim-optional-components">Optional Components of a Conformance Claim</a></li> </ul> </li> <li><a href="#conf-disclaimer">Disclaimer</a></li> </ul> </li> <li><a href="#glossary">Appendix A: Glossary</a></li> <li><a href="#references">Appendix B: References</a></li> <li><a href="#acknowledgments">Appendix C: Acknowledgments</a></li> </ul> </div>  </div>  <hr /> <div id="sect-intro"> <h2><a id="intro" name="intro">Introduction</a></h2> <div class="gl-only"> <p>This section is <a class="termdef" href="#def-Informative" title="definition: informative">informative</a>.</p> <p>This is W3C Recommendation (standard) of the Authoring Tool Accessibility Guidelines (ATAG) version 2.0. This document includes recommendations for assisting <a class="termdef" href="#def-Developer" title="definition: authoring tool developers">authoring tool developers</a> to make their <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tools</a> more accessible to people with disabilities, including auditory, cognitive, neurological, physical, speech, and visual disabilities. </p> <p>Authoring tool accessibility addresses the needs of two overlapping user groups with disabilities:</p> <ul> <li><a class="termdef" href="#def-Author" title="definition: authors">authors</a> of <a class="termdef" href="#def-Web-Content" title="definition: web content">web content</a>, whose needs are met by ensuring that <a class="termdef" href="#def-Authoring-Tool-Interface" title="definition: authoring tool user interface">authoring tool user interfaces</a> are more accessible (addressed by <a href="#part_a">Part A of the Guidelines</a>), and </li> <li><a class="termdef" href="#def-End-Users" title="definition: end user">end users</a> of web content, whose needs are met by ensuring that all authors are enabled, supported, and guided by the authoring tools that they use toward producing <a class="termdef" href="#def-Accessible-Web-Content" title="definition: accessible Web content">accessible web content (WCAG)</a> (addressed by <a href="#part_b">Part B of the Guidelines</a>).</li> </ul> <p>It is important to note that while the requirements for meeting these two sets of user needs are separated for clarity within the guidelines, the accelerating trend toward user-produced content means that, in reality, they are deeply inter-connected. For example, when a user participates in an online forum, the user frequently authors content that is then incorporated with content authored by other users. Accessibility problems in either the authoring user interface or the content produced by the other forum users would reduce the overall accessibility of the forum. </p> <h4><a id="intro-notes" name="intro-notes"></a>Notes:</h4> <ol> <li>The term "<a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tools</a>" has a specific definition in ATAG 2.0. The definition, which includes several <a class="termdef" href="#def-Normative" title="definition: normative">normative</a> notes, appears in the <a href="#glossary">Glossary</a>.</li> <li>The term "<a class="termdef" href="#def-Accessible-Web-Content" title="definition: accessible web content">accessible content (WCAG)</a>" and related terms, such as "<a href="#def-Accessible-Template" title="definition: accessible templates" class="termdef">accessible template (WCAG)</a>" is used by ATAG 2.0 to refer to "content that would conform to <a href="#conf-rel-wcag">WCAG 2.0</a>", at either Level A, AA, or AAA, assuming that any <a href="#def-Web-Content-Technology" title="definition: technology (Web content)" class="termdef">web content technologies</a> relied upon to satisfy the WCAG 2.0 success criteria are accessibility supported. The definition of the term reflects the WCAG 2.0 note that even content that conforms to the highest level of WCAG 2.0 (Level AAA) may not be "accessible to individuals with all types, degrees, or combinations of disability". For more information, see "<a href="#conf-rel-wcag">Relationship to the Web Content Accessibility Guidelines (WCAG) 2.0</a>".</li> <li>ATAG 2.0 does not include standard usability recommendations, except where they have a significantly greater impact on people with disabilities than on other people.</li> <li>Authoring tools are just one aspect of web accessibility. For an overview of the different components of web accessibility and how they work together see: <ul> <li> <a href="https://www.w3.org/WAI/intro/components.php">Essential Components of Web Accessibility</a></li> <li> <a href="https://www.w3.org/WAI/intro/wcag.php">Web Content Accessibility Guidelines (WCAG) Overview</a></li> <li> <a href="https://www.w3.org/WAI/intro/uaag.php">User Agent Accessibility Guidelines (UAAG) Overview</a> (This will be of special interest to developers of "<a class="termdef" href="#def-comb-ua-authoring-tool" title="definition: combined user agent/authoring tools">Combined User Agent/Authoring Tools</a>" and "<a class="termdef" href="#def-ua-with-authoring-tool-role" title="definition: user agents with authoring tool modes">User Agents with Authoring Tool Modes</a>")</li> </ul> </li> </ol> </div>  <h3><a name="intro-organization" id="intro-organization"></a>ATAG 2.0 Layers of Guidance</h3> <p>The individuals and organizations that may use ATAG 2.0 vary widely and include <a class="termdef" href="#def-Developer" title="definition: authoring tool developers">authoring tool developers</a>, <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> users (<a class="termdef" href="#def-Author" title="definition: authors">authors</a>), authoring tool purchasers, and policy makers. In order to meet the varying needs of these audiences, several layers of guidance are provided:</p> <ul> <li><strong>Parts:</strong> ATAG 2.0 is divided into two parts, each reflecting a key aspect of accessibility with respect to authoring tools. <a href="#part_a">Part A</a> relates to the accessibility of <a class="termdef" title="defintion: authoring tool user interfaces" href="#def-Authoring-Tool-Interface">authoring tool user interfaces</a> to authors with disabilities. <a href="#part_b">Part B</a> relates to support by authoring tools for the creation, by any author (not just those with disabilities), of <a class="termdef" href="#def-Web-Content" title="definition: web content">web content</a> that is more accessible to <a class="termdef" href="#def-End-Users" title="definition: end user">end users</a> with disabilities. Both parts include <a class="termdef" href="#def-Normative" title="definition: normative">normative</a> "Conformance Applicability Notes" that apply to all of the success criteria within that part: <a href="#part_a_applic_notes">Part A Conformance Applicability Notes</a> and <a href="#part_b_applic_notes">Part B Conformance Applicability Notes</a>.</li> <li><strong>Principles:</strong> Under each part are several high-level principles that organize the guidelines.</li> <li><strong>Guidelines:</strong> Under the principles are guidelines. The guidelines provide the basic goals that authoring tool developers should work toward in order to make authoring tools more accessible to both authors and end users of web content with different disabilities. The guidelines are not testable, but provide the framework and overall objectives to help authoring tool developers understand the success criteria. Each guideline includes a brief rationale for why the guideline was included.</li> <li><strong>Success Criteria:</strong> For each guideline, testable success criteria are provided to allow ATAG 2.0 to be used where requirements and conformance testing are necessary, such as in design specification, purchasing, regulation, and contractual agreements. In order to meet the needs of different groups and different situations, multiple levels of full and partial conformance are defined (see <a href="#conf-levels">Levels of Conformance</a>).</li> <li><strong>Implementing ATAG 2.0 document:</strong> The <a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/">Implementing ATAG 2.0</a> document provides additional non-normative information for each success criterion, including a description of the intent of the success criterion, examples, and links to related resources.<a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/"></a></li> </ul> <p>See <a href="https://www.w3.org/WAI/intro/atag.php">Authoring Tool Accessibility Guidelines (ATAG) Overview</a> for links to additional ATAG technical and educational material.</p> <h3><a name="intro_understand_levels_conformance" id="intro_understand_levels_conformance"></a>Levels of Conformance</h3> <p>In order to ensure that the process of using ATAG 2.0 and <a href="#conf-rel-wcag">WCAG 2.0</a> together in the development of <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tools</a> is as simple as possible, ATAG 2.0 shares <a href="#conf-rel-wcag">WCAG 2.0</a>'s three level conformance model: Level A (lowest), AA (middle), AAA (highest). <span class="gl-only">For more information, see <a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#intro_understand_levels_conformance">Understanding Levels of Conformance</a>. </span></p> <h3><a id="intro-integrate_acc_features" name="intro-integrate_acc_features"></a>Integration of Accessibility Features</h3> <p>When implementing ATAG 2.0, <a class="termdef" href="#def-Developer" title="definition: authoring tool developers">authoring tool developers</a> should carefully integrate features that support more accessible authoring into the same "look-and-feel" as other features of the <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a>. Close integration has the potential to: </p> <ul> <li>produce a more seamless product; </li> <li>leverage the existing knowledge and skills of <a class="termdef" href="#def-Author" title="definition: authors">authors</a>; </li> <li>make authors more receptive to new accessibility-related authoring requirements; and </li> <li>reduce the likelihood of author confusion.</li> </ul> </div>  <hr /> <div id="sect-guidelines" > <h2><a id="guidelines" name="guidelines"></a>Guidelines</h2> <div class="gl-only"> <p>The success criteria and the conformance applicability notes in this section are <a class="termdef" href="#def-Normative" title="definition: normative">normative</a>.</p> </div>  <div id="subsect-tool-accessible"> <h2><a name="part_a" id="part_a"></a>Part A: Make the authoring tool user interface accessible</h2> <h3 id="partA-tool-accessible-notes"><a name="part_a_applic_notes" id="part_a_applic_notes"></a>Part A Conformance Applicability Notes:</h3> <ol> <li><a name="part_a_applic_note_1" id="part_a_applic_note_1"></a><strong class="handle">Scope of "authoring tool user interface":</strong> The Part A success criteria apply to all aspects of the <a href="#def-Authoring-Tool-Interface" title="definition: authoring tool user interface" class="termdef">authoring tool user interface</a> that are concerned with producing the <a href="#conf-techs-produced">"included" web content technologies</a>. This includes <a class="termdef" href="#def-View" title="definition: view">views</a> of the <a class="termdef" href="#def-Content-Being-Edited" title="definition: web content being edited">web content being edited</a> and features that are independent of the content being edited (e.g. menus, button bars, status bars, user preferences, <a class="termdef" href="#def-Documentation" title="definition: documentation">documentation</a>). </li> <li><a name="part_a_applic_note_2" id="part_a_applic_note_2"></a><strong class="handle">Reflected content accessibility problems:</strong> The <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> is responsible for ensuring that <a href="#def-Editing-View" title="definition: editing views" class="termdef">editing-views</a> display the <a class="termdef" href="#def-Content-Being-Edited" title="definition: web content being edited">web content being edited</a> in a way that is more accessible to <a class="termdef" href="#def-Author" title="definition: authors">authors</a> with disabilities (e.g. ensuring that <span class="sc-bullet"><a class="termdef" href="#def-Text-Alternatives" title="text alternatives for non-text content">text alternatives</a></span> in the content can be <a class="termdef" href="#def-Programmatically-Determined" title="definition: programmatically determined">programmatically determined</a>). However, where an <a href="#def-Authoring-Interface-Accessibility-Problem" title="definition: authoring tool user interface accessibility problem" class="termdef">authoring tool user interface accessibility problem</a> is caused directly by the content being edited (e.g. if an image in the content lacks a text alternative), then this would not be considered a deficiency in the accessibility of the <a href="#def-Authoring-Tool-Interface" title="definition: authoring tool user interface" class="termdef">authoring tool user interface</a>.<br /> </li> <li><a name="part_a_applic_note_3" id="part_a_applic_note_3"></a><strong class="handle">Developer control:</strong> The Part A success criteria only apply to the <a href="#def-Authoring-Tool-Interface" title="definition: authoring tool user interface" class="termdef">authoring tool user interface</a> as it is provided by the <a class="termdef" href="#def-Developer" title="definition: authoring tool developers">developer</a>. They do not apply to any subsequent modifications by parties other than the authoring tool developer (e.g. user modifications of default settings, third-party plug-ins).</li> <li><a name="part_a_applic_note_4" id="part_a_applic_note_4"></a><strong class="handle">User agent features:</strong> <a href="#def-Web-Based-UI" title="definition: authoring tool user interface (Web-based)" class="termdef">Web-based authoring tools</a> may rely on <a class="termdef" href="#def-User-Agent" title="definition: user agent">user agent</a> features (e.g. keyboard navigation, find functions, display preferences, undo features) to satisfy success criteria. <a href="#conf-claim">Conformance claims</a> are optional, but any claim that is made must <a href="#conf-user-agents">record the user agent(s)</a>.</li> <li><a name="part_a_applic_note_5" id="part_a_applic_note_5"></a><strong class="handle">Accessibility of features provided to meet Part A:</strong> The Part A success criteria apply to the entire <a href="#def-Authoring-Tool-Interface" title="definition: authoring tool user interface" class="termdef">authoring tool user interface</a>, including any features added to meet the success criteria in Part A (e.g. documentation, search functions). The only exemption is for <a class="termdef" href="#def-Preview" title="definition: preview">preview</a> features, as long as they meet the relevant success criteria in <a href="#gl_a37">Guideline A.3.7</a>. Previews are treated differently than editing-views because all authors, including those with disabilities, benefit when preview features accurately reflect the functionality of user agents that are actually in use by <span class="rationale"><a class="termdef" href="#def-End-Users" title="definition: end user">end users</a></span>.</li> <li><strong class="handle"><a name="part_a_applic_note_6" id="part_a_applic_note_6"></a>Unrecognizable content:</strong> When success criteria require authoring tools to treat web content according to semantic criteria, the success criteria only apply when these semantics are encoded programmatically (e.g. text describing an image can only be considered a <a class="termdef" href="#def-Text-Alternatives" title="text alternatives for non-text content">text alternatives for non-text content</a> when this role is encoded within markup).</li> </ol> <h2 class="principle"><a name="principle_a1" id="principle_a1"> </a>Principle A.1: Authoring tool user interfaces follow applicable accessibility guidelines </h2> <h3 class="guideline"><a name="gl_a11" id="gl_a11"> </a> Guideline A.1.1: (For the authoring tool user interface) Ensure that web-based functionality is accessible. <span class="gl-only"><span class="implementing-link">[<a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#gl_a11">Implementing A.1.1</a>] </span></span> </h3> <p class="rationale">Rationale: When <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tools</a> (or parts of authoring tools) are <a class="termdef" href="#def-Web-Based-UI" title="definition: authoring tool user interface (Web-based)">web-based</a>, conforming to <a href="#conf-rel-wcag">WCAG 2.0</a> will facilitate access by all <a href="#def-Author" title="definition: authors" class="termdef">authors</a>, including those using <a class="termdef" href="#def-Assistive-Technology" title="definition: assistive technology">assistive technologies</a>.</p> <div class="sc-level"> <h4 class="sc-title"><a id="sc_a111" name="sc_a111"></a>A.1.1.1 Web-Based Accessible (WCAG): </h4> <p class="sc-title">If the <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> contains <a class="termdef" href="#def-Web-Based-UI" title="definition: authoring tool user interface (Web-based)">web-based user interfaces</a>, then those web-based user interfaces meet the <a href="#conf-rel-wcag">WCAG 2.0</a> success criteria. <span class="level">(<strong>Level A</strong> to meet WCAG 2.0 Level A success criteria; <strong>Level AA</strong> to meet WCAG 2.0 Level A and AA success criteria; <strong>Level AAA</strong> to meet all WCAG 2.0 success criteria)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_a111">Implementing A.1.1.1</a></div> </div>   </div>  <h3 class="guideline"><a name="gl_a12" id="gl_a12"> </a> Guideline A.1.2: (For the authoring tool user interface) Ensure that non-web-based functionality is accessible. <span class="gl-only">[<a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#gl_a12">Implementing A.1.2</a>]</span> </h3> <p class="rationale">Rationale: When <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tools</a> (or parts of authoring tools) are <a class="termdef" href="#def-Non-Web-Based" title="definition: authoring tool user interface (non-Web-Based)">non-web-based</a>, following existing <a href="#def-Platform" title="definition: platform" class="termdef">platform</a> accessibility guidelines and implementing communication with <a class="termdef" href="#def-Accessibility-Platform-Service" title="definition: accessibility platform architecture">platform accessibility services</a> facilitates access by all <a href="#def-Author" title="definition: authors" class="termdef">authors</a>, including those using <a class="termdef" href="#def-Assistive-Technology" title="definition: assistive technology">assistive technologies</a>.</p> <div class="sc-level"> <h4 class="sc-title"><a id="sc_a121" name="sc_a121"></a>A.1.2.1 Accessibility Guidelines: </h4> <p class="sc-title">If the <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> contains <a class="termdef" href="#def-Non-Web-Based" title="definition: authoring tool user interface (non-Web-Based)">non-web-based user interfaces</a>, then those non-web-based user interfaces follow user interface accessibility guidelines for the <a class="termdef" href="#def-Platform" title="definition: platform">platform</a>. <span class="level">(<strong>Level A</strong>)</span></p> <ul class="sc-notes"> <li class="sc-note"><em class="note-handle">Note: </em>The (optional) <a href="#conf-explanation-results">explanation of conformance claim results</a> should record the user interface accessibility guidelines that were followed.</li> </ul> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_a121">Implementing A.1.2.1</a></div> </div>  <h4 class="sc-title"><a id="sc_a122" name="sc_a122"></a>A.1.2.2 Platform Accessibility Services: </h4> <p class="sc-title">If the <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> contains <a class="termdef" href="#def-Non-Web-Based" title="definition: authoring tool user interface (non-Web-Based)">non-web-based user interfaces</a>, then those non-web-based user interfaces expose accessibility information through <a class="termdef" href="#def-Accessibility-Platform-Service" title="definition: accessibility platform architecture">platform accessibility services</a>. <span class="level">(<strong>Level A</strong>)</span></p> <ul class="sc-notes"> <li class="sc-note"><em class="note-handle">Note: </em><em class="note-handle"></em>The (optional) <a href="#conf-explanation-results">explanation of conformance claim results</a> should record the platform accessibility service(s) that were implemented.</li> </ul> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_a122">Implementing A.1.2.2</a></div> </div>  </div>  <h2 class="principle"><a name="principle_a2" id="principle_a2"></a>Principle A.2: Editing-views are perceivable </h2> <h3 class="guideline"><a name="gl_a21" id="gl_a21"> </a> Guideline A.2.1: (For the authoring tool user interface) Make alternative content available to authors. <span class="gl-only">[<a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#gl_a21">Implementing A.2.1</a>] </span> </h3> <p class="rationale">Rationale: Some <a class="termdef" href="#def-Author" title="definition: authors">authors</a> require access to <a href="#def-Alternative-Content" title="definition: alternative content" class="termdef">alternative content</a> in order to interact with the <a class="termdef" href="#def-Web-Content" title="definition: web content">web content</a> that they are editing. </p> <div class="sc-level"> <h4 class="sc-title"><a id="sc_a211" name="sc_a211"></a>A.2.1.1 Text Alternatives for Rendered Non-Text Content: </h4> <p class="sc-title"> If an <a class="termdef" href="#def-Editing-View" title="definition: editing view">editing-view</a> <a class="termdef" href="#def-Content-Renderings" title="definition: content rendering">renders</a> <a class="termdef" href="#def-Non-Text-Objects" title="definition: non-text objects">non-text content</a>, then any <a href="#def-Associated-Alternative-Content" title="definition: alternative content" class="termdef">programmatically associated</a> <a class="termdef" href="#def-Text-Alternatives" title="text alternatives for non-text content">text alternatives for the non-text content</a> can be <a class="termdef" href="#def-Programmatically-Determined" title="definition: programmatically determined">programmatically determined</a>. <span class="level">(<strong>Level A</strong>)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_a211">Implementing A.2.1.1</a></div> </div>  <h4 class="sc-title"><a id="sc_a212" name="sc_a212"></a>A.2.1.2 Alternatives for Rendered Time-Based Media: </h4><p class="sc-title"> If an <a class="termdef" href="#def-Editing-View" title="definition: editing view">editing-view</a> <a class="termdef" href="#def-Content-Renderings" title="definition: content rendering">renders</a> time-based media, then at least one of the following is true: <span class="level">(<strong>Level A</strong>)</span></p> <ul class="sc-bullets"> <li class="sc-bullet"><strong class="handle">(a) Option to Render:</strong> The <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> provides the <a href="#def-Option" title="definition: option" class="termdef">option</a> to render alternatives for the time-based media; or</li> <li class="sc-bullet"><strong class="handle">(b) User Agent Option:</strong> <a class="termdef" href="#def-Author" title="definition: authors">Authors</a> have the option to <a class="termdef" href="#def-Preview" title="definition: preview">preview</a> the time-based media in a <a class="termdef" href="#def-User-Agent" title="definition: user agent">user agent</a> that is able to render the alternatives.</li> </ul> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_a212">Implementing A.2.1.2</a></div> </div>  </div>  <h3 class="guideline"><a name="gl_a22" id="gl_a22"> </a> Guideline A.2.2: (For the authoring tool user interface) Ensure that editing-view presentation can be programmatically determined. <span class="gl-only">[<a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#gl_a22">Implementing A.2.2</a>] </span> </h3> <p class="rationale">Rationale: Some <a class="termdef" href="#def-Author" title="definition: authors">authors</a> need access to details about the <a class="termdef" href="#def-Editing-View" title="definition: editing view">editing-view</a> <a class="termdef" href="#def-Presentation" title="definition: presentation">presentation</a>, via their assistive technology, when that presentation is used to convey status messages (e.g. underlining misspelled words) or provide information about how the <a class="termdef" href="#def-End-Users" title="definition: end users">end user</a> will experience the <a class="termdef" href="#def-Content-Being-Edited" title="definition: web content being edited">web content being edited</a>.</p> <div class="sc-level"> <h4 class="sc-title"><strong class="handle"><a id="sc_a221" name="sc_a221"></a></strong>A.2.2.1 Editing-View Status Indicators: </h4> <p class="sc-title"> If an <a class="termdef" href="#def-Editing-View" title="definition: editing view">editing-view</a> adds status indicators to the <span class="rationale"><a class="termdef" href="#def-Content-Being-Edited" title="definition: web content being edited">content being edited</a></span>, then the information being conveyed by the status indicators can be <a class="termdef" href="#def-Programmatically-Determined" title="definition: programmatically determined">programmatically determined</a>. <span class="level">(<strong>Level A</strong>)</span></p> <ul class="sc-notes"> <li class="sc-note"><em class="note-handle">Note: </em>Status indicators may indicate errors (e.g. spelling errors), tracked changes, hidden elements, or other information.</li> </ul> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_a221">Implementing A.2.2.1</a></div> </div>  </div> <div class="sc-level"> <h4 class="sc-title"><a id="sc_a222" name="sc_a222"> </a>A.2.2.2 Access to Rendered Text Properties:</h4> <p class="sc-title"> If an <a class="termdef" href="#def-Editing-View" title="definition: editing view">editing-view</a> renders any text formatting <a href="#def-Web-Content-Properties" title="definition: content property" class="termdef">properties</a> that <a class="termdef" href="#def-Author" title="definition: authors">authors</a> can also edit using the editing-view, then the properties can be <a class="termdef" href="#def-Programmatically-Determined" title="definition: programmatically determined">programmatically determined</a>. <span class="level">(<strong>Level AA</strong>)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_a222">Implementing A.2.2.2</a></div> </div> </div> <h2 class="principle"><a name="principle_a3" id="principle_a3"> </a>Principle A.3: Editing-views are operable</h2> <h3 class="guideline"><a name="gl_a31" id="gl_a31"> </a> Guideline A.3.1: (For the authoring tool user interface) Provide keyboard access to authoring features. <span class="gl-only">[<a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#gl_a31">Implementing A.3.1</a>] </span></h3> <p class="rationale">Rationale: Some <a class="termdef" href="#def-Author" title="definition: authors">authors</a> with limited mobility or visual disabilities do not use a mouse and instead require keyboard interface access to all of the functionality of the <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a>.</p> <div class="sc-level"> <h4 class="sc-title"><a id="sc_a311" name="sc_a311"></a>A.3.1.1 Keyboard Access (Minimum): </h4><p class="sc-title"> All functionality of the <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> is operable through a <a class="termdef" href="#def-Keyboard-Interface" title="definition: keyboard interface">keyboard interface</a> without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints. <span class="level">(<strong>Level A</strong>)</span></p> <ul class="sc-notes"> <li class="sc-notes"><em class="note-handle">Note 1:</em> Keyboard interfaces are programmatic services provided by many <a class="termdef" href="#def-Platform" title="definition: platform">platforms</a> that allow operation in a device independent manner. This success criterion does not imply the presence of a hardware keyboard.</li> <li class="sc-note"><em class="note-handle">Note 2:</em> The path exception relates to the underlying function, not the input technique. For example, if using handwriting to enter text, the input technique (handwriting) requires path-dependent input, but the underlying function (text input) does not. The path exception encompasses other input variables that are continuously sampled from pointing devices, including pressure, speed, and angle.</li> <li class="sc-note"><em class="note-handle">Note 3:</em> This success criterion does not forbid and should not discourage other input methods (e.g. mouse, touch) in addition to keyboard operation.</li></ul> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_a311">Implementing A.3.1.1</a></div> </div> <h4 class="sc-title"><a id="sc_a312" name="sc_a312"></a>A.3.1.2 No Keyboard Traps: </h4> <p class="sc-title"> If keyboard focus can be moved to a <a class="termdef" href="#def-UI-Component" title="definition: user interface component">component</a> using a <a class="termdef" href="#def-Keyboard-Interface" title="definition: keyboard interface">keyboard interface</a>, then focus can be moved away from that component using only a keyboard interface. If it requires more than unmodified arrow or tab keys or other standard exit methods, <span class="sc-bullet"><a class="termdef" href="#def-Author" title="definition: authors">authors</a></span> are advised of the method for moving focus away. <span class="level">(<strong>Level A</strong>)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_a312">Implementing A.3.1.2</a></div> </div> </div> <div class="sc-level"> <h4 class="sc-title"><a id="sc_a313" name="sc_a313"></a>A.3.1.3 Efficient Keyboard Access: </h4> <p class="sc-title"> The <a href="#def-Authoring-Tool-Interface" title="definition: authoring tool user interface" class="termdef">authoring tool user interface</a> includes mechanisms to make keyboard access more efficient than <a href="#def-Sequential-Keyboard-Access" title="definition: sequential keyboard navigation" class="termdef">sequential keyboard access</a>. <span class="level">(<strong>Level AA</strong>)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_a313">Implementing A.3.1.3</a></div> </div> </div> <div class="sc-level"> <h4 class="sc-title"><a id="sc_a314" name="sc_a314"> </a>A.3.1.4 Keyboard Access (Enhanced): </h4><p class="sc-title"> All functionality of the <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> is operable through a <a class="termdef" href="#def-Keyboard-Interface" title="definition: keyboard interface">keyboard interface</a> without requiring specific timings for individual keystrokes. <span class="level">(<strong>Level AAA</strong>)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_a314">Implementing A.3.1.4</a></div> </div> <h4 class="sc-title"><a id="sc_a315" name="sc_a315"> </a>A.3.1.5 Customize Keyboard Access: </h4><p class="sc-title"> If the <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> includes keyboard commands, then those keyboard commands can be customized. <span class="level">(<strong>Level AAA</strong>)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_a315">Implementing A.3.1.5</a></div> </div> <h4 class="sc-title"><a id="sc_a316" name="sc_a316"> </a> A.3.1.6 Present Keyboard Commands:</h4> <p class="sc-title"> If the <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> includes keyboard commands,</p> then the authoring tool provides a way for <a class="termdef" href="#def-Author" title="definition: authors">authors</a> to determine the keyboard commands associated with <a href="#def-Authoring-Tool-Interface" title="definition: authoring tool user interface" class="termdef">authoring tool user interface</a> <a class="termdef" href="#def-UI-Component" title="definition: user interface component">components</a>. <span class="level">(<strong>Level AAA</strong>)</span> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_a316">Implementing A.3.1.6</a></div> </div> </div> <h3 class="guideline"><a name="gl_a32" id="gl_a32"> </a> Guideline A.3.2: (For the authoring tool user interface) Provide authors with enough time. <span class="gl-only">[<a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#gl_a32">Implementing A.3.2</a>] </span> </h3> <p class="rationale">Rationale: Some <a class="termdef" href="#def-Author" title="definition: authors">authors</a> who have difficulty typing, operating the mouse, or processing information can be prevented from using systems with short <a class="termdef" href="#def-Time-Limit" title="definition: time limit">time limits</a> or that require fast reaction speeds, such as clicking on a moving target.</p> <div class="sc-level"> <h4 class="sc-title"><a id="sc_a321" name="sc_a321"> </a>A.3.2.1 Auto-Save (Minimum): </h4> <p class="sc-title"> The <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> does not include <a href="#def-Authoring-Session" title="definition: authoring session" class="termdef">session</a> <a class="termdef" href="#def-Time-Limit" title="definition: time limit">time limits</a> or the authoring tool can automatically save edits made before the session time limits are reached. <span class="level">(<strong>Level A</strong>)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_a321">Implementing A.3.2.1</a></div> </div> <h4 class="sc-title"><a id="sc_a322" name="sc_a322"> </a>A.3.2.2 Timing Adjustable: </h4> <p class="sc-title"> The <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> does not include <a class="termdef" href="#def-Time-Limit" title="definition: time limit">time limits</a> or at least one of the following is true: <span class="level">(<strong>Level A</strong>)</span></p> <ul class="sc-bullets"> <li class="sc-bullet"><strong class="handle">(a) Turn Off:</strong> <a class="termdef" href="#def-Author" title="definition: authors">Authors</a> are allowed to turn off the time limit before encountering it; or</li> <li class="sc-bullet"><strong class="handle">(b) Adjust:</strong> Authors 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 class="sc-bullet"><strong class="handle">(c) Extend:</strong> Authors 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 authors are allowed to extend the time limit at least ten times; or</li> <li class="sc-bullet"><strong class="handle">(d) Real-time Exception:</strong> The time limit is a required part of a real-time event (e.g. a collaborative authoring system), and no alternative to the time limit is possible; or</li> <li class="sc-bullet"><strong class="handle">(e) Essential Exception:</strong> The time limit is essential and extending it would invalidate the activity; or</li> <li class="sc-bullet"><strong class="handle">(f) 20 Hour Exception:</strong> The time limit is longer than 20 hours.</li></ul> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_a322">Implementing A.3.2.2</a></div> </div> <h4 class="sc-title"><a id="sc_a323" name="sc_a323"> </a>A.3.2.3 Static Input Components: </h4> <p class="sc-title">The <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> does not include moving <a class="termdef" href="#def-UI-Component" title="definition: user interface component">user interface components</a> that accept input where the movement of these components cannot be paused by <a class="termdef" href="#def-Author" title="definition: authors">authors</a>. <span class="level">(<strong>Level A</strong>)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_a323">Implementing A.3.2.3</a></div> </div> </div> <div class="sc-level"> <h4 class="sc-title"><a id="sc_a324" name="sc_a324"> </a>A.3.2.4 Content Edits Saved (Extended): </h4> <p class="sc-title"> The <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> can be set to automatically save <a class="termdef" href="#def-Web-Content" title="definition: web content">web content</a> edits made using the authoring tool. <span class="level">(<strong>Level AAA</strong>)</span> </p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_a324">Implementing A.3.2.4</a></div> </div> </div>  <h3 class="guideline"><a name="gl_a33" id="gl_a33"> </a> Guideline A.3.3: (For the authoring tool user interface) Help authors avoid flashing that could cause seizures. <span class="gl-only"> [<a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#gl_a33">Implementing A.3.3</a>] </span> </h3> <p class="rationale">Rationale: Flashing can cause seizures in <a class="termdef" href="#def-Author" title="definition: authors">authors</a> with photosensitive seizure disorder.</p> <div class="sc-level"> <h4 class="sc-title"><a id="sc_a331" name="sc_a331"> </a>A.3.3.1 Static View Option: </h4> <p class="sc-title"> If an <a class="termdef" href="#def-Editing-View" title="definition: editing view">editing-view</a> can play visual time-based content, then playing is not necessarily automatic upon loading the content and playing can be paused. <span class="level">(<strong>Level A</strong>)</span> </p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_a331">Implementing A.3.3.1</a></div> </div> </div>  <h3 class="guideline"><a name="gl_a34" id="gl_a34"> </a> Guideline A.3.4: (For the authoring tool user interface) Enhance navigation and editing via content structure. <span class="gl-only">[<a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#gl_a34">Implementing A.3.4</a>] </span> </h3> <p class="rationale">Rationale: Some <a class="termdef" href="#def-Author" title="definition: authors">authors</a> who have difficulty typing or operating the mouse benefit when <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tools</a> make use of the structure present in <a class="termdef" href="#def-Web-Content" title="definition: web content">web content</a> to simplify navigating and editing the content.</p> <div class="sc-level"> <h4 class="sc-title"><a id="sc_a341" name="sc_a341"> </a>A.3.4.1 Navigate By Structure: </h4><p class="sc-title"> If <a class="termdef" href="#def-Editing-View" title="definition: editing view">editing-views</a> expose the <a href="#def-Markup" title="definition: markup" class="termdef">markup</a> <a href="#def-Element" title="definition: element" class="termdef">elements</a> in the <a class="termdef" href="#def-Content-Being-Edited" title="definition: web content being edited">web content being edited</a>, then the markup elements (e.g. source code, content renderings) are selectable and navigation mechanisms are provided to move the selection focus between elements. <span class="level">(<strong>Level AA</strong>)</span> </p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_a341">Implementing A.3.4.1</a></div> </div> </div>  <div class="sc-level"> <h4 class="sc-title"><a id="sc_a342" name="sc_a342"> </a>A.3.4.2 Navigate by Programmatic Relationships: </h4><p class="sc-title"> If <a class="termdef" href="#def-Editing-View" title="definition: editing view">editing-views</a> allow editing of programmatic <a href="#def-Relationships" title="definition: relationships" class="termdef">relationships</a> within <a class="termdef" href="#def-Web-Content" title="definition: web content">web content</a>, then mechanisms are provided that support navigation between the related content. <span class="level">(<strong>Level AAA</strong>)</span></p> <ul class="sc-notes"> <li class="sc-note"><em class="note-handle">Note:</em><span class="sc-title"> Depending on the <a href="#def-Web-Content-Technology" title="definition: technology (Web content)" class="termdef">web content technology</a> and the nature of the <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a>, relationships may include, but are not limited to, element nesting, headings, labeling, programmatic definitions, and ID relationships.</span></li> </ul> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_a342">Implementing A.3.4.2</a></div> </div> </div> <h3 class="guideline"><a name="gl_a35" id="gl_a35"> </a> Guideline A.3.5: (For the authoring tool user interface) Provide text search of the content. <span class="gl-only">[<a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#gl_a35">Implementing A.3.5</a>] </span> </h3> <p class="rationale">Rationale: Some <a class="termdef" href="#def-Author" title="definition: authors">authors</a> who have difficulty typing or operating the mouse benefit from the ability to use text search to navigate to arbitrary points within the <span class="sc-title"><a class="termdef" href="#def-Content-Being-Edited" title="definition: web content being edited">web content being edited</a></span>.</p> <div class="sc-level"> <h4 class="sc-title"><a id="sc_a351" name="sc_a351"> </a>A.3.5.1 Text Search: </h4> <p class="sc-title">If the authoring tool provides an <a class="termdef" href="#def-Editing-View" title="definition: editing view">editing-view</a> of text-based content, then the <a class="termdef" href="#def-Editing-View" title="definition: editing view">editing-view</a> enables text search, such that all of the following are true: <span class="level">(<strong>Level AA</strong>)</span></p> <ul class="sc-bullets"> <li class="sc-bullet"><strong class="handle">(a) All Editable Text:</strong> Any text content that is editable by the editing-view is searchable (including <a href="#def-Alternative-Content" title="definition: alternative content" class="termdef">alternative content</a>); and</li> <li class="sc-bullet"><strong class="handle">(b) Match:</strong> Matching results can be presented to authors and given focus; and</li> <li class="sc-bullet"><strong class="handle">(c) No Match:</strong> Authors are informed when no results are found; and </li> <li class="sc-bullet"><strong class="handle">(d) Two-way:</strong> The search can be made forwards or backwards.</li> </ul> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_a351">Implementing A.3.5.1</a></div> </div> </div> <h3 class="guideline"><a name="gl_a36" id="gl_a36"> </a> Guideline A.3.6: (For the authoring tool user interface) Manage preference settings. <span class="gl-only">[<a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#gl_a36">Implementing A.3.6</a>] </span> </h3> <p class="rationale">Rationale: Some <a class="termdef" href="#def-Author" title="definition: authors">authors</a> need to set their own <a class="termdef" href="#def-Display-Settings" title="definition: display settings">display settings</a> in a way that differs from the <a class="termdef" href="#def-Presentation" title="definition: presentation">presentation</a> that they want to define for the <a href="#def-Publishing" title="definition: publishing" class="termdef">published</a> <a class="termdef" href="#def-Web-Content" title="definition: web content">web content</a>. Providing the ability to save and reload sets of keyboard and display preference settings benefits <a class="termdef" href="#def-Author" title="definition: authors">authors</a> who have needs that differ over time (e.g. due to fatigue).</p> <div class="sc-level"> <h4 class="sc-title"><a id="sc_a361" name="sc_a361"></a>A.3.6.1 Independence of Display: </h4> <p class="sc-title"> If the <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> includes <a class="termdef" href="#def-Display-Settings" title="definition: display settings">display settings</a> for <a class="termdef" href="#def-Editing-View" title="definition: editing view">editing-views</a>, then the authoring tool allows <a class="termdef" href="#def-Author" title="definition: authors">authors</a> to adjust these settings without modifying the <a class="termdef" href="#def-Content-Being-Edited" title="definition: web content being edited">web content being edited</a>. <span class="level">(<strong>Level A</strong>)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_a361">Implementing A.3.6.1</a></div> </div> </div>  <div class="sc-level"> <h4 class="sc-title"><strong class="handle"><a id="sc_a362" name="sc_a362"> </a></strong>A.3.6.2 Save Settings: </h4> <p class="sc-title"> If the <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> includes <a href="#def-Display-Settings" title="definition: display settings" class="termdef">display</a> and/or <a href="#def-Control-Settings" title="definition: control settings" class="termdef">control settings</a>, then these settings can be saved between <a href="#def-Authoring-Session" title="definition: authoring session" class="termdef">authoring sessions</a>. <span class="level">(<strong>Level AA</strong>)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_a362">Implementing A.3.6.2</a></div> </div> <h4 class="sc-title"><strong class="handle"><a id="sc_a363" name="sc_a363"> </a></strong>A.3.6.3 Apply Platform Settings: </h4> <p class="sc-title"> The <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> respects changes in <a class="termdef" href="#def-Platform" title="definition: platform">platform</a> <a href="#def-Display-Settings" title="definition: display settings" class="termdef">display</a> and <a href="#def-Control-Settings" title="definition: control settings" class="termdef">control settings</a>, unless <a class="termdef" href="#def-Author" title="definition: authors">authors</a> select more specific display and control settings using the authoring tool. <span class="level">(<strong>Level AA</strong>)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_a363">Implementing A.3.6.3</a></div> </div> </div>  <h3 class="guideline"><a name="gl_a37" id="gl_a37"> </a> Guideline A.3.7: (For the authoring tool user interface) Ensure that previews are at least as accessible as in-market user agents. <span class="gl-only">[<a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#gl_a37">Implementing A.3.7</a>] </span> </h3> <p class="rationale">Rationale: <a class="termdef" href="#def-Preview" title="definition: preview">Preview</a> features are provided by many <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tools</a> because the <a class="termdef" href="#def-Workflow" title="definition: workflow">workflow</a> of <a href="#def-Author" title="definition: authors" class="termdef">authors</a> often includes periodically checking how <a class="termdef" href="#def-User-Agent" title="definition: user agent">user agents</a> will display the <a class="termdef" href="#def-Web-Content" title="definition: web content">web content</a> to <a class="termdef" href="#def-End-Users" title="definition: end user">end users</a>. Authors with disabilities need the same opportunity to check their work.</p> <div class="sc-level"> <h4 class="sc-title"><a id="sc_a371" name="sc_a371"> </a>A.3.7.1 Preview (Minimum): </h4><p class="sc-title">If a <a class="termdef" href="#def-Preview" title="definition: preview">preview</a> is provided, then at least one of the following is true: <span class="level">(<strong>Level A</strong>)</span></p> <ul class="sc-bullets"> <li class="sc-bullet"><strong class="handle">(a) In-Market User Agent:</strong> The preview renders content using a <a class="termdef" href="#def-User-Agent" title="definition: user agent">user agent</a> that is <a class="termdef" href="#def-Inmarket-User-Agent" title="definition: in-market user agent">in-market</a>; or </li> <li class="sc-bullet"><strong class="handle">(b) UAAG (Level A):</strong> The preview conforms to the User Agent Accessibility Guidelines 1.0 Level A <cite><a href="#ref-UAAG10">[UAAG10]</a></cite>.</li> </ul> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_a371">Implementing A.3.7.1</a></div> </div> </div>  <div class="sc-level"> <h4 class="sc-title"><a id="sc_a372" name="sc_a372"> </a>A.3.7.2 Preview (Enhanced): </h4><p class="sc-title">If a <a class="termdef" href="#def-Preview" title="definition: preview">preview</a> is provided, then <a href="#def-Author" title="definition: authors" class="termdef">authors</a> can specify which <a class="termdef" href="#def-User-Agent" title="definition: user agent">user agent</a> performs the preview. <span class="level">(<strong>Level AAA</strong>)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_a372">Implementing A.3.7.2</a></div> </div> </div>  <h2 class="principle"><a name="principle_a4" id="principle_a4"> </a>Principle A.4: Editing-views are understandable </h2> <h3 class="guideline"><a name="gl_a41" id="gl_a41"> </a> Guideline A.4.1: (For the authoring tool user interface) Help authors avoid and correct mistakes. <span class="gl-only">[<a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#gl_a41">Implementing A.4.1</a>]</span> </h3> <p class="rationale">Rationale: Some <a href="#def-Author" title="definition: authors" class="termdef">authors</a> with disabilities may be more susceptible to input errors due to factors such as difficulty making fine movements and speech recognition system errors. </p> <div class="sc-level"> <h4 class="sc-title"><a id="sc_a411" name="sc_a411"> </a>A.4.1.1 Content Changes Reversible (Minimum): </h4> <p class="sc-title">All <a href="#def-Authoring-Action" title="definition: authoring actions" class="termdef">authoring actions</a> are either <a href="#def-Reversible-Action" title="definition: reversible authoring action" class="termdef">reversible</a> or the <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> requires <a href="#def-Author" title="definition: authors" class="termdef">author</a> confirmation to proceed. (<strong><span class="level">Level A</span></strong>) </p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_a411">Implementing A.4.1.1</a></div> </div> <h4 class="sc-title"><a id="sc_a412" name="sc_a412"> </a>A.4.1.2 Settings Change Confirmation:</h4> <p class="sc-title"> If the <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> provides mechanisms for changing <a href="#def-Authoring-Tool-Interface" title="definition: authoring tool user interface" class="termdef">authoring tool user interface</a> settings, then those mechanisms can reverse the setting changes, or the authoring tool requires <a href="#def-Author" title="definition: authors" class="termdef">author</a> confirmation to proceed. (<strong><span class="level">Level A</span></strong>)</p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_a412">Implementing A.4.1.2</a></div> </div> </div>  <div class="sc-level"> <h4 class="sc-title"><a id="sc_a413" name="sc_a413"> </a>A.4.1.3 Content Changes Reversible (Enhanced): </h4><p class="sc-title"><a href="#def-Author" title="definition: authors" class="termdef">Authors</a> can sequentially reverse a series of <a href="#def-Reversible-Action" title="definition: reversible authoring action" class="termdef">reversible authoring actions</a>. <span class="level">(<strong>Level AAA</strong>)</span></p> <ul class="sc-notes"> <li class="sc-note"><em class="note-handle">Note:</em> It is acceptable to clear the authoring action history at the <a href="#def-End-Auth-Session" title="definition: end of an authoring session" class="termdef">end of authoring sessions</a>.</li> </ul> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_a413">Implementing A.4.1.3</a></div> </div>  </div> <h3 class="guideline"><a name="gl_a42" id="gl_a42"> </a> Guideline A.4.2: (For the authoring tool user interface) Document the user interface, including all accessibility features. <span class="gl-only">[<a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#gl_a42">Implementing A.4.2</a>] </span> </h3> <p class="rationale">Rationale: Some <a href="#def-Author" title="definition: authors" class="termdef">authors</a> may not be able to understand or operate the <a href="#def-Authoring-Tool-Interface" title="definition: authoring tool user interface" class="termdef">authoring tool user interface</a> without <a href="#def-Documentation" title="definition: documentation" class="termdef">documentation</a>.</p> <div class="sc-level"> <h4 class="sc-title"><a id="sc_a421" name="sc_a421"> </a>A.4.2.1 Describe Accessibility Features: </h4> <p class="sc-title"> For each <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> feature that is used to meet <a href="#part_a">Part A</a> of ATAG 2.0, at least one of the following is true: <span class="level">(<strong>Level A</strong>)</span></p> <ul class="sc-bullets"> <li class="sc-bullet"><strong class="handle">(a) Described in the Documentation:</strong> Use of the feature is explained in the authoring tool's <a class="termdef" href="#def-Documentation" title="definition: documentation">documentation</a>; or </li> <li class="sc-bullet"><strong class="handle">(b) Described in the Interface:</strong> Use of the feature is explained in the <a href="#def-Authoring-Tool-Interface" title="definition: authoring tool user interface" class="termdef">authoring tool user interface</a>; or </li> <li class="sc-bullet"><strong class="handle">(c) Platform Service:</strong> The feature is a service provided by an underlying platform; or </li> <li class="sc-bullet"><strong class="handle">(d) Not Used by Authors:</strong> The feature is not used directly by <a href="#def-Author" title="definition: authors" class="termdef">authors</a> (e.g. passing information to a <a class="termdef" href="#def-Accessibility-Platform-Service" title="definition: accessibility platform architecture">platform accessibility service</a>).</li> </ul> <ul class="sc-notes"> <li class="sc-note"><em class="note-handle">Note:</em> The accessibility of the documentation is covered by <a href="#gl_a11">Guideline A.1.1</a> and <a href="#gl_a11">Guideline A.1.2</a>.</li></ul> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_a421">Implementing A.4.2.1</a></div> </div> </div>  <div class="sc-level"> <h4 class="sc-title"><a id="sc_a422" name="sc_a422"> </a>A.4.2.2 Document All Features: </h4> <p class="sc-title"> For each <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> feature, at least one of the following is true: <span class="level">(<strong>Level AA</strong>)</span></p> <ul class="sc-bullets"> <li class="sc-bullet"><strong class="handle">(a) Described in the Documentation:</strong> Use of the feature is explained in the authoring tool's <a class="termdef" href="#def-Documentation" title="definition: documentation">documentation</a>; or </li> <li class="sc-bullet"><strong class="handle">(b) Described in the Interface:</strong> Use of the feature is explained in the <a href="#def-Authoring-Tool-Interface" title="definition: authoring tool user interface" class="termdef">authoring tool user interface</a>; or </li> <li class="sc-bullet"><strong class="handle">(c) Platform Service:</strong> The feature is a service provided by an underlying platform; or </li> <li class="sc-bullet"><strong class="handle">(d) Not Used by Authors:</strong> The feature is not used directly by <a href="#def-Author" title="definition: authors" class="termdef">authors</a> (e.g. passing information to a <a class="termdef" href="#def-Accessibility-Platform-Service" title="definition: accessibility platform architecture">platform accessibility service</a>).</li> </ul> <ul class="sc-notes"> <li class="sc-note"><em class="note-handle">Note:</em> The accessibility of the documentation is covered by <a href="#gl_a11">Guideline A.1.1</a> and <a href="#gl_a11">Guideline A.1.2</a>.</li></ul> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_a422">Implementing A.4.2.2</a></div> </div> </div>  </div>  <div id="subsect-support-production"> <h2><a id="part_b" name="part_b"> </a>Part B: Support the production of accessible content</h2> <h3 id="part_b-notes"><a name="part_b_applic_notes" id="part_b_applic_notes"></a>Part B Conformance Applicability Notes:</h3> <ol> <li><a name="part_b_applic_note_1" id="part_b_applic_note_1"></a><strong class="handle">Author availability:</strong> Any Part B success criteria that refer to <a href="#def-Author" title="definition: authors" class="termdef">authors</a> only apply during <a href="#def-Authoring-Session" title="definition: authoring session" class="termdef">authoring sessions</a>.</li> <li><strong class="handle"><a name="part_b_applic_note_2" id="part_b_applic_note_2"></a>Developer control:</strong> The Part B success criteria only apply to the <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> as it is provided by the <a class="termdef" href="#def-Developer" title="definition: authoring tool developers">developer</a>. This does not include subsequent modifications by parties other than the authoring tool developer (e.g. third-party plug-ins, user-defined <a href="#def-Template" title="definition: template" class="termdef">templates</a>, user modifications of default settings).</li> <li><strong class="handle"><a name="part_b_applic_note_3" id="part_b_applic_note_3"></a>Applicability after the end of an authoring session:</strong> <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">Authoring tools</a> are responsible for the <a href="#def-Accessible-Web-Content" class="termdef" title="definition: accessible web content">web content accessibility (WCAG)</a> of <a class="termdef" href="#def-Web-Content" title="definition: web content">web content</a> that they <span class="sc"><a href="#def-Content-Auto-Gen" title="definition: automatically-generated content" class="termdef">automatically generate</a></span> after the <a href="#def-End-Auth-Session" title="definition: end of an authoring session" class="termdef">end of an author's authoring session</a> (see <a href="#sc_b111">Success Criterion B.1.1.1</a>). For example, if the developer changes the site-wide <a href="#def-Template" title="definition: template" class="termdef">templates</a> of a content management system, these would be required to meet the accessibility requirements for automatically-generated content. Authoring tools are not responsible for changes to the accessibility of content that the author causes, whether it is <a class="termdef" href="#def-Content-Author-Gen" title="definition: author generated content">author-generated</a> or automatically-generated by another system that the author has specified (e.g. a third-party feed).<br /> </li> <li><strong class="handle"><a name="part_b_applic_note_4" id="part_b_applic_note_4"></a>Authoring systems:</strong> As per the ATAG 2.0 definition of <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a>, several software tools (identified in any <a href="#conf-claim">conformance claim</a>) can be used in conjunction to meet the requirements of Part B (e.g. an authoring tool could make use of a third-party software accessibility <a href="#def-Checking" title="definition: checking" class="termdef">checking</a> tool).</li> <li><strong class="handle"><a name="part_b_applic_note_5" id="part_b_applic_note_5"></a>Accessibility of features provided to meet Part B:</strong> The <a href="#part_a">Part A</a> success criteria apply to the entire <a href="#def-Authoring-Tool-Interface" title="definition: authoring tool user interface" class="termdef">authoring tool user interface</a>, including any features that must be present to meet the success criteria in Part B (e.g. checking tools, repair tools, tutorials, documentation). </li> <li><strong class="handle"><a name="part_b_applic_note_6" id="part_b_applic_note_6"></a>Multiple authoring roles:</strong> Some <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tools</a> include multiple <a href="#def-Author" title="definition: authors" class="termdef">author</a> roles, each with different views and content editing <a href="#def-Authoring-Permission" title="definition: author permission" class="termdef"> permissions</a> (e.g. a content management system may separate the roles of designers, content authors, and quality assurers). In these cases, the Part B success criteria apply to the authoring tool as a whole, not to the view provided to any particular authoring role. <a class="termdef" href="#def-Accessible-Content-Support-Features" title="definition: accessible content support features"> Accessible content support features</a> should be made available to any authoring role where it would be useful.</li> <li><strong class="handle"><a name="part_b_applic_note_7" id="part_a_applic_note_7"></a>Unrecognizable content:</strong> When success criteria require authoring tools to treat web content according to semantic criteria, the success criteria only apply when these semantics are encoded programmatically (e.g. text describing an image can only be considered a <a class="termdef" href="#def-Text-Alternatives" title="text alternatives for non-text content">text alternatives for non-text content</a> when this role is encoded within markup).</li> </ol> <h2 class="principle"><a id="principle_b1" name="principle_b1"></a>Principle B.1: Fully automatic processes produce accessible content</h2> <h3 class="guideline"><a name="gl_b11" id="gl_b11"> </a> Guideline B.1.1: Ensure that automatically-specified content is accessible. <span class="gl-only">[<a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#gl_b11">Implementing B.1.1</a>] </span> </h3> <p class="rationale">Rationale: If <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tools</a> <span class="sc"><a href="#def-Content-Auto-Gen" title="definition: automatically-generated content" class="termdef">automatically</a></span> produce <span class="sc"><a class="termdef" href="#def-Web-Content" title="definition: web content">web content</a></span> that includes <a href="#def-Web-Content-Accessibility-Problem" title="definition: web content accessibility problems" class="termdef">accessibility problems (WCAG)</a>, then this will impose additional <a href="#def-Repairing" title="definition: repairing" class="termdef">repair</a> tasks on <a href="#def-Author" title="definition: authors" class="termdef">authors</a>.</p> <div class="sc-level"> <h4 class="sc-title"><a id="sc_b111" name="sc_b111"> </a>B.1.1.1 Content Auto-Generation After Authoring Sessions (WCAG): </h4> <p class="sc-title">The <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> does not <a href="#def-Content-Auto-Gen" title="definition: automatically-generated content" class="termdef">automatically generate</a> <a class="termdef" href="#def-Web-Content" title="definition: web content">web content</a> after the <a href="#def-End-Auth-Session" title="definition: end of an authoring session" class="termdef">end of an authoring session,</a> or, <a href="#def-Author" title="definition: authors" class="termdef">authors</a> can specify that the content be <span class="rationale"><a class="termdef" href="#def-Accessible-Web-Content" title="definition: accessible Web content">accessible web content (WCAG)</a></span>. <span class="level">(<strong>Level A</strong> to meet WCAG 2.0 Level A success criteria; <strong>Level AA</strong> to meet WCAG 2.0 Level A and AA success criteria; <strong>Level AAA</strong> to meet all WCAG 2.0 success criteria)</span></p> <ul class="sc-notes"> <li class="sc-note"><em class="note-handle">Note:</em> This success criterion applies only to automatic processes specified by the <a class="termdef" href="#def-Developer" title="definition: authoring tool developers">authoring tool developer</a>. It does not apply when <a class="termdef" href="#def-Author-Actions-Prevent" title="definition: author actions prevent generation of accessible web content">author actions prevent generation of accessible web content (WCAG)</a>.</li></ul> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_b111">Implementing B.1.1.1</a></div> </div>  <h4 class="sc-title"><a id="sc_b112" name="sc_b112"> </a>B.1.1.2 Content Auto-Generation During Authoring Sessions (WCAG):</h4> If the <span class="sc-title"><a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a></span> provides the functionality for <span class="sc-title"><a href="#def-Content-Auto-Gen" title="definition: automatically-generated content" class="termdef">automatically generating</a></span> <span class="sc-title"><a class="termdef" href="#def-Web-Content" title="definition: web content">web content</a></span> during an <a href="#def-Authoring-Session" title="definition: authoring session" class="termdef">authoring session</a>, then at least one of the following is true: <span class="level">(<strong>Level A</strong> to meet WCAG 2.0 Level A success criteria; <strong>Level AA</strong> to meet WCAG 2.0 Level A and AA success criteria; <strong>Level AAA</strong> to meet all WCAG 2.0 success criteria)</span> <ul class="sc-bullets"> <li class="sc-bullet"><strong class="handle">(a) Accessible:</strong> The content is <span class="rationale"><a class="termdef" href="#def-Accessible-Web-Content" title="definition: accessible Web content">accessible web content (WCAG) </a></span> without author input; or </li> <li class="sc-bullet"><strong class="handle">(b) Prompting:</strong> During the automatic generation process, <span class="sc-title"><a href="#def-Author" title="definition: authors" class="termdef">authors</a></span> are <a href="#def-Prompt" title="definition: prompt" class="termdef">prompted</a> for any required <a class="termdef" href="#def-Accessibility-Information" title="definition: accessibility information">accessibility information (WCAG)</a>; or </li> <li class="sc-bullet"><strong class="handle">(c) Automatic Checking:</strong> After the automatic generation process, accessibility <a href="#def-Checking" title="definition: checking" class="termdef">checking</a> is automatically performed; or </li> <li class="sc-bullet"><strong class="handle">(d) Checking Suggested:</strong> After the automatic generation process, the authoring tool prompts authors to perform accessibility checking. </li> </ul> <ul class="sc-notes"> <li class="sc-note"><em class="note-handle">Note 1:</em> Automatic generation includes automatically selecting <a href="#def-Template" title="definition: template" class="termdef">templates</a> for authors.</li> <li class="sc-note"><em class="note-handle">Note 2:</em> This success criterion applies only to automatic processes specified by the <a class="termdef" href="#def-Developer" title="definition: authoring tool developers">authoring tool developer</a>. It does not apply when <a class="termdef" href="#def-Author-Actions-Prevent" title="definition: author actions prevent generation of accessible web content">author actions prevent generation of accessible web content (WCAG)</a>.</li> </ul> <div class="gl-only"><div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_b112">Implementing B.1.1.2</a></div></div>  </div>  <h3 class="guideline"><a id="gl_b12" name="gl_b12"> </a> Guideline B.1.2: Ensure that accessibility information is preserved. <span class="gl-only">[<a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#gl_b12">Implementing B.1.2</a>] </span> </h3> <p class="rationale">Rationale: <a class="termdef" href="#def-Accessibility-Information" title="definition: accessibility information">Accessibility information (WCAG)</a> is critical to maintaining comparable levels of <a class="termdef" href="#def-Accessible-Web-Content" title="definition: accessible Web content">web content accessibility (WCAG)</a> between the input and output of <a class="termdef" href="#def-Transformation" title="definition: transformation">web content transformations</a>.</p> <div class="sc-level"> <h4 class="sc-title"><a id="sc_b121" name="sc_b121"> </a>B.1.2.1 Restructuring and Recoding Transformations (WCAG): </h4> <p class="sc-title"> If the <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> provides <a class="termdef" href="#def-Restructuring-Transformation" title="definition: restructuring transformations">restructuring transformations</a> or <a class="termdef" href="#def-Recoding-Transformation" title="definition: recoding transformations">re-coding transformations</a>, and if equivalent mechanisms exist in the web content technology of the output, then at least one of the following is true: <span class="level">(<strong>Level A</strong> to meet WCAG 2.0 Level A success criteria; <strong>Level AA</strong> to meet WCAG 2.0 Level A and AA success criteria; <strong>Level AAA</strong> to meet all WCAG 2.0 success criteria)</span></p> <ul class="sc-bullets"> <li class="sc-bullet"><strong class="handle">(a) Preserve:</strong> <a class="termdef" href="#def-Accessibility-Information" title="definition: accessibility information">Accessibility information (WCAG)</a> is preserved in the output; or </li> <li class="sc-bullet"><strong class="handle">(b) Warning:</strong> Authors have the <span class="sc-title"><a class="termdef" href="#def-Default-Option" title="definition: default option" >default option</a></span> to be warned that accessibility information (WCAG) may be lost (e.g. when saving a vector graphic into a raster image format); or </li> <li class="sc-bullet"><strong class="handle">(c) Automatic Checking:</strong> After the transformation, accessibility <a href="#def-Checking" title="definition: checking" class="termdef">checking</a> is automatically performed; or </li> <li class="sc-bullet"><strong class="handle">(d) Checking Suggested:</strong> After the transformation, the authoring tool <a href="#def-Prompt" title="definition: prompt" class="termdef">prompts</a> authors to perform accessibility checking. </li></ul> <ul class="sc-notes"> <li class="sc-note"><em class="note-handle">Note 1:</em> For <a class="termdef" href="#def-Text-Alternatives" title="text alternatives for non-text content">text alternatives for non-text content</a>, see <a href="#sc_b124">Success Criterion B.1.2.4</a>.</li> <li class="sc-note"><em class="note-handle">Note 2:</em> This success criteria only applies when the output technology is <a href="#conf-techs-produced">"included"</a> for conformance.</li> </ul> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_b121">Implementing B.1.2.1</a></div> </div> <h4 class="sc-title"><a id="sc_b122" name="sc_b122"> </a>B.1.2.2 Copy-Paste Inside Authoring Tool (WCAG):</h4> <p class="sc-title"> If the <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> supports copy and paste of <a class="termdef" href="#def-Structured-Web-Content" title="definition: structured content">structured content</a>, then any <a class="termdef" href="#def-Accessibility-Information" title="definition: accessibility information">accessibility information (WCAG)</a> in the copied content is preserved when the authoring tool is both the source and destination of the copy-paste and the source and destination use the same <a href="#def-Web-Content-Technology" title="definition: technology (Web content)" class="termdef">web content technology</a>. <span class="level">(<strong>Level A</strong> to meet WCAG 2.0 Level A success criteria; <strong>Level AA</strong> to meet WCAG 2.0 Level A and AA success criteria; <strong>Level AAA</strong> to meet all WCAG 2.0 success criteria)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_b122">Implementing B.1.2.2</a></div> </div> </div>  <div class="sc-level"> <h4 class="sc-title"><a id="sc_b123" name="sc_b123"> </a>B.1.2.3 Optimizations Preserve Accessibility: </h4> <p class="sc-title"> If the <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> provides <a href="#def-Optimizing-Transformation" class="termdef" title="definition: authoring tool" >optimizing web content transformations</a>, then any <a class="termdef" href="#def-Accessibility-Information" title="definition: accessibility information">accessibility information (WCAG)</a> in the input is preserved in the output. <span class="level">(<strong>Level A</strong>)</span>.</p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_b123">Implementing B.1.2.3</a></div> </div> <h4 class="sc-title"><a id="sc_b124" name="sc_b124"> </a>B.1.2.4 Text Alternatives for Non-Text Content are Preserved: </h4><p class="sc-title"> If the <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> provides <a class="termdef" href="#def-Transformation" title="definition: transformation">web content transformations</a> that preserve <a class="termdef" href="#def-Non-Text-Objects" title="definition: non-text content">non-text content</a> in the output, then any <a class="termdef" href="#def-Text-Alternatives" title="text alternatives for non-text content">text alternatives for that non-text content</a> are also preserved, if equivalent mechanisms exist in the <a href="#def-Web-Content-Technology" title="definition: technology (Web content)" class="termdef">web content technology</a> of the output. <span class="level">(<strong>Level A</strong>)</span>.</p> <ul class="sc-notes"> <li class="sc-note"><em class="note-handle">Note:</em> This success criterion only applies when the output technology is <a href="#conf-techs-produced">"included"</a> for conformance.</li> </ul> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_b124">Implementing B.1.2.4</a></div> </div> </div>  <h2 class="principle"><a id="principle_b2" name="principle_b2"> </a>Principle B.2: Authors are supported in producing accessible content</h2> <h3 class="guideline"><a name="gl_b21" id="gl_b21"> </a> Guideline B.2.1: Ensure that accessible content production is possible. <span class="gl-only">[<a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#gl_b21">Implementing B.2.1</a>] </span> </h3> <p class="rationale"><strong><a name="gl_b11-rationale" id="gl_b11-rationale"> </a></strong>Rationale: To support <a class="termdef" href="#def-Accessible-Web-Content" title="definition: accessible Web content">accessible web content (WCAG)</a> production, at minimum, it is possible to produce <a class="termdef" href="#def-Web-Content" title="definition: web content">web content</a> that conforms with <a href="#conf-rel-wcag">WCAG 2.0</a> using the <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a>.</p> <div class="sc-level"> <h4 class="sc-title"><a id="sc_b211" name="sc_b211"> </a>B.2.1.1 Accessible Content Possible (WCAG): </h4> <p class="sc-title"> The <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> does not place <a href="#def-Restrictions" class="termdef" title="definition: web content authoring restrictions">restrictions</a> on the <a class="termdef" href="#def-Web-Content" title="definition: web content">web content</a> that <a href="#def-Author" title="definition: authors" class="termdef">authors</a> can specify or those restrictions do not prevent <span class="rationale"><a href="#conf-rel-wcag">WCAG 2.0</a></span> success criteria from being met. <span class="level">(<strong>Level A</strong> to meet WCAG 2.0 Level A success criteria; <strong>Level AA</strong> to meet WCAG 2.0 Level A and AA success criteria; <strong>Level AAA</strong> to meet all WCAG 2.0 success criteria)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_b211">Implementing B.2.1.1</a></div> </div> </div>  <h3 class="guideline"><a id="gl_b22" name="gl_b22"> </a> Guideline B.2.2: Guide authors to produce accessible content. <span class="gl-only">[<a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#gl_b22">Implementing B.2.2</a>] </span> </h3> <p class="rationale">Rationale: By guiding <a class="termdef" href="#def-Author" title="definition: author">authors</a> from the outset toward the creation and maintenance of <a class="termdef" href="#def-Accessible-Web-Content" title="definition: accessible Web content">accessible web content (WCAG)</a>, <a href="#def-Web-Content-Accessibility-Problem" title="definition: Web content accessibility problem" class="termdef">web content accessibility problems (WCAG)</a> are mitigated and less <a href="#def-Repairing" title="definition: repairing" class="termdef">repair</a> effort is required.</p> <div class="sc-level"> <h4 class="sc-title"> <a id="sc_b221" name="sc_b221"> </a>B.2.2.1 Accessible Option Prominence (WCAG): </h4><p class="sc-title"> If <a href="#def-Author" title="definition: authors" class="termdef">authors</a> are provided with a choice of <a class="termdef" href="#def-Authoring-Action" title="definition: authoring action">authoring actions</a> for achieving the same <a href="#def-Authoring-Outcome" title="definition: authoring outcome" class="termdef">authoring outcome</a> (e.g. styling text), then <a class="termdef" title="definition: options" href="#def-Option">options</a> that will result in <a class="termdef" href="#def-Web-Content" title="definition: web content">accessible web content (WCAG)</a> are <a class="termdef" href="#def-At-Least-As-Prominent" title="definition: At Least As Prominent">at least as prominent</a> as options that will not. <span class="level">(<strong>Level A</strong> to meet WCAG 2.0 Level A success criteria; <strong>Level AA</strong> to meet WCAG 2.0 Level A and AA success criteria; <strong>Level AAA</strong> to meet all WCAG 2.0 success criteria)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_b221">Implementing B.2.2.1</a></div> </div> <h4 class="sc-title"><a id="sc_b222" name="sc_b222"> </a>B.2.2.2 Setting Accessibility Properties (WCAG): </h4> <p class="sc-title"> If the authoring tool provides mechanisms to set <a class="termdef" href="#def-Web-Content-Properties" title="definition: web content properties">web content properties</a> (e.g. attribute values), then mechanisms are also provided to set web content properties related to <a class="termdef" href="#def-Accessibility-Information" title="definition: accessibility information">accessibility information (WCAG)</a>. <span class="level">(<strong>Level A</strong> to meet WCAG 2.0 Level A success criteria; <strong>Level AA</strong> to meet WCAG 2.0 Level A and AA success criteria; <strong>Level AAA</strong> to meet all WCAG 2.0 success criteria)</span></p> <ul class="sc-notes"> <li class="sc-note"><em class="note-handle">Note:</em> For the prominence of the mechanisms, see <a href="#sc_b414">Success Criterion B.4.1.4</a>.</li></ul> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_b222">Implementing B.2.2.2</a></div> </div> </div>  </div> <h3 class="guideline"><a id="gl_b23" name="gl_b23"> </a> Guideline B.2.3: Assist authors with managing alternative content for non-text content. <span class="gl-only">[<a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#gl_b23">Implementing B.2.3</a>]</span> </h3> <p class="rationale">Rationale: Improperly generated <a href="#def-Alternative-Content" title="definition: alternative content" class="termdef">alternative content</a> can create <a class="termdef" href="#def-Web-Content-Accessibility-Problem" title="definition: web content accessibility problem">web content accessibility problems (WCAG)</a> and interfere with accessibility <a href="#def-Checking" title="definition: checking" class="termdef">checking</a>.<br /> <em>Note:</em> This guideline only applies when <a class="termdef" href="#def-Non-Text-Objects" title="definition: non-text content">non-text content</a> is specified by <a href="#def-Author" title="definition: authors" class="termdef">authors</a> (e.g. inserting an image). When non-text content is <span class="sc"><a href="#def-Content-Auto-Gen" title="definition: automatically-generated content" class="termdef">automatically</a></span> added by the <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a>, see <a href="#gl_b11">Guideline B.1.1</a>.</p> <div class="sc-level"> <h4 class="sc-title"><a id="sc_b231" name="sc_b231"> </a>B.2.3.1 Alternative Content is Editable (WCAG): </h4> <p class="sc-title">If the <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> provides functionality for adding non-text content, then <a href="#def-Author" title="definition: authors" class="termdef">authors</a> are able to modify <a href="#def-Associated-Alternative-Content" title="definition: alternative content" class="termdef">programmatically associated</a> <a class="termdef" href="#def-Text-Alternatives" title="text alternatives for non-text content">text alternatives for non-text content</a>. <span class="level">(<strong>Level A</strong> to meet WCAG 2.0 Level A success criteria; <strong>Level AA</strong> to meet WCAG 2.0 Level A and AA success criteria; <strong>Level AAA</strong> to meet all WCAG 2.0 success criteria)</span></p> <ul class="sc-notes"> <li class="sc-note"><em class="note-handle">Note:</em> An exception can be made when the non-text content is known to be decoration, formatting, invisible or a CAPTCHA.</li> </ul> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_b231">Implementing B.2.3.1</a></div> </div> </div> <div class="sc-level"> <h4 class="sc-title"><a id="sc_b232" name="sc_b232"> </a>B.2.3.2 Automating Repair of Text Alternatives: </h4> <p class="sc-title"> The <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> does not attempt to <a href="#def-Repairing" title="definition: repairing" class="termdef">repair</a> <a class="termdef" href="#def-Text-Alternatives" title="text alternatives for non-text content">text alternatives for non-text content</a> or the following are all true: <span class="level">(<strong>Level A</strong>)</span></p> <ul class="sc-bullets"> <li class="sc-bullet"><strong class="handle">(a) No Generic or Irrelevant Strings:</strong> Generic strings (e.g. "image") and irrelevant strings (e.g. the file name, file format) are not used as text alternatives; and</li> <li class="sc-bullet"><strong class="handle">(b) In-Session Repairs:</strong> If the repair attempt occurs during an authoring session, <a href="#def-Author" title="definition: authors" class="termdef">authors</a> have the opportunity to accept, modify, or reject the repair attempt prior to insertion of the text alternative into the content; and</li> <li class="sc-bullet"><strong class="handle">(c) Out-of-Session Repairs:</strong> If the repair attempt occurs after an <span class="sc-title"><a href="#def-End-Auth-Session" title="definition: end of an authoring session" class="termdef">authoring session has ended</a></span>, the repaired text alternatives are indicated during subsequent authoring sessions (if any) and authors have the opportunity to accept, modify, or reject the repair strings prior to insertion in the content. </li> </ul> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_b232">Implementing B.2.3.2</a></div> </div> </div>  <div class="sc-level"> <h4 class="sc-title"><a id="sc_b233" name="sc_b233"> </a> B.2.3.3 Save for Reuse: </h4> <p class="sc-title">If the <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> provides the functionality for adding non-text content, when <a href="#def-Author" title="definition: authors" class="termdef">authors</a> enter <a href="#def-Associated-Alternative-Content" title="definition: alternative content" class="termdef">programmatically associated</a> <a class="termdef" href="#def-Text-Alternatives" title="text alternatives for non-text content">text alternatives for non-text content</a>, then both of the following are true: <span class="level">(<strong>Level AAA</strong>)</span></p> <ul class="sc-bullets"> <li class="sc-bullet"><strong class="handle">(a) Save and Suggest:</strong> The text alternatives are automatically saved and suggested by the <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a>, if the same non-text content is reused; and</li> <li class="sc-bullet"><strong class="handle">(b) Edit Option:</strong> The author has the <a class="termdef" title="definition: options" href="#def-Option">option</a> to edit or delete the saved text alternatives.</li></ul> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_b233">Implementing B.2.3.3</a></div> </div> </div>  <h3 class="guideline"><a id="gl_b24" name="gl_b24"> </a> Guideline B.2.4: Assist authors with accessible templates. <span class="gl-only">[<a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#gl_b24">Implementing B.2.4</a>]</span> </h3> <p class="rationale">Rationale: Providing <a href="#def-Accessible-Template" title="definition: accessible templates" class="termdef">accessible templates (WCAG)</a> can have several benefits, including: immediately improving the <a class="termdef" href="#def-Accessible-Web-Content" title="definition: accessible web content">accessibility of the web content (WCAG)</a> of <span class="sc">being edited</span>, reducing the effort required of <a class="termdef" href="#def-Author" title="definition: author">authors</a>, and demonstrating the importance of accessible web content (WCAG).</p> <div class="sc-level"> <h4 class="sc-title"><a id="sc_b241" name="sc_b241"> </a>B.2.4.1 Accessible Template Options (WCAG): </h4> <p class="sc-title"> If the <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> provides <a href="#def-Template" title="definition: template" class="termdef">templates</a>, then there are <a href="#def-Accessible-Template" title="definition: accessible templates" class="termdef">accessible template (WCAG) </a> <a class="termdef" title="definition: options" href="#def-Option">options</a> for a <a class="termdef" title="definition: range" href="#def-Range">range</a> of template uses. <span class="level">(<strong>Level A</strong> to meet WCAG 2.0 Level A success criteria; <strong>Level AA</strong> to meet WCAG 2.0 Level A and AA success criteria; <strong>Level AAA</strong> to meet all WCAG 2.0 success criteria)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_b241">Implementing B.2.4.1</a></div> </div> </div>  <div class="sc-level"> <h4 class="sc-title"><a id="sc_b242" name="sc_b242"> </a>B.2.4.2 Identify Template Accessibility: </h4> <p class="sc-title"> If the <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> includes a <a href="#def-Template-Selection-Mechanism" title="definition: template selection mechanism" class="termdef">template selection mechanism</a> and provides any non-<a href="#def-Accessible-Template" title="definition: accessible templates" class="termdef">accessible template (WCAG) </a> <a class="termdef" title="definition: options" href="#def-Option">options</a>, then the template selection mechanism can display distinctions between the accessible and non-accessible options. <span class="level">(<strong>Level AA</strong>)</span></p> <ul class="sc-notes"> <li class="sc-note"><em class="note-handle">Note:</em> The distinction can involve providing information for the accessible templates, the non-accessible templates or both.</li> </ul> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_b242">Implementing B.2.4.2</a></div> </div> <h4 class="sc-title"><a id="sc_b243" name="sc_b243"> </a>B.2.4.3 Author-Created Templates: </h4> <p class="sc-title"> If the <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> includes a <a href="#def-Template-Selection-Mechanism" title="definition: template selection mechanism" class="termdef">template selection mechanism</a> and allows <a href="#def-Author" title="definition: authors" class="termdef">authors</a> to create new non-<a href="#def-Accessible-Template" title="definition: accessible templates" class="termdef">accessible templates (WCAG)</a>, then authors can enable the template selection mechanism to display distinctions between accessible and non-accessible templates that they create. <span class="level">(<strong>Level AA</strong>)</span></p> <ul class="sc-notes"> <li class="sc-note"><em class="note-handle">Note:</em> The distinction can involve providing information for the accessible templates (WCAG), the non-accessible templates or both.</li> </ul> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_b243">Implementing B.2.4.3</a></div> </div> </div>  <div class="sc-level"> <h4 class="sc-title"><a id="sc_b244" name="sc_b244"> </a>B.2.4.4 Accessible Template Options (Enhanced): </h4> <p class="sc-title"> If the <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> provides <a href="#def-Template" title="definition: template" class="termdef">templates</a>, then all of the templates are <a href="#def-Accessible-Template" title="definition: accessible templates" class="termdef">accessible template (to WCAG Level AA)</a>. <span class="level">(<strong>Level AAA</strong>)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_b244">Implementing B.2.4.4</a></div> </div>  </div>  <h3 class="guideline"><a id="gl_b25" name="gl_b25"> </a> Guideline B.2.5: Assist authors with accessible pre-authored content. <span class="gl-only">[<a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#gl_b25">Implementing B.2.5</a>]</span> </h3> <p class="rationale">Rationale: Providing <a href="#def-Accessible-Preauthored-Content" title="definition: accessible pre-authored content" class="termdef">accessible pre-authored content (WCAG)</a> (e.g. clip art, synchronized media, widgets) can have several benefits, including: immediately improving the <span class="sc"><a class="termdef" href="#def-Content-Being-Edited" title="definition: web content being edited">accessibility of web content (WCAG)</a></span> being edited, reducing the effort required of <a class="termdef" href="#def-Author" title="definition: author">authors</a>, and demonstrating the importance of accessibility.</p> <div class="sc-level"> <h4 class="sc-title"><a id="sc_b251" name="sc_b251"> </a>B.2.5.1 Accessible Pre-Authored Content Options: </h4> <p class="sc-title"> If the <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> provides <a href="#def-Preauthored-Content" title="definition: pre-authored content" class="termdef">pre-authored content</a>, then a range of <span class="rationale"><a href="#def-Accessible-Preauthored-Content" title="definition: accessible pre-authored content" class="termdef">accessible pre-authored content (to WCAG Level AA)</a></span> <a class="termdef" title="definition: options" href="#def-Option">options</a> are provided. <span class="level">(<strong>Level AA</strong>)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_b251">Implementing B.2.5.1</a></div> </div> <h4 class="sc-title"><a id="sc_b252" name="sc_b252"> </a>B.2.5.2 Identify Pre-Authored Content Accessibility: </h4> <p class="sc-title"> If the <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> includes a <a href="#def-Preauthored-Content-Selection-Mechanism" title="definition: pre-authored content selection mechanism" class="termdef">pre-authored content selection mechanism </a> and provides any non-<a href="#def-Accessible-Preauthored-Content" title="definition: accessible pre-authored content" class="termdef">accessible pre-authored content (WCAG Level AA) </a> <a class="termdef" title="definition: options" href="#def-Option">options</a>, then the selection mechanism can display distinctions between the accessible and non-accessible options. <span class="level">(<strong>Level AA</strong>)</span></p> <ul class="sc-notes"> <li class="sc-note"><em class="note-handle">Note:</em> The distinction can involve providing information for the accessible pre-authored content, the non-accessible pre-authored content or both.</li> </ul> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_b252">Implementing B.2.5.2</a></div> </div> </div> <h2 class="principle"><a id="principle_b3" name="principle_b3"> </a>Principle B.3: Authors are supported in improving the accessibility of existing content </h2> <h3 class="guideline"><a id="gl_b31" name="gl_b31"> </a> Guideline B.3.1: Assist authors in checking for accessibility problems. <span class="gl-only">[<a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#gl_b31">Implementing B.3.1</a>]</span> </h3> <p class="rationale">Rationale: When <a href="#def-Checking" title="definition: checking" class="termdef">accessibility checking</a> is an integrated function of the <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a>, it helps make <a class="termdef" href="#def-Author" title="definition: author">authors</a> aware of <a href="#def-Web-Content-Accessibility-Problem" title="definition: Web content accessibility problem" class="termdef">web content accessibility problems (WCAG)</a> during the authoring process, so they can be immediately addressed.</p> <div class="sc-level"> <h4 class="sc-title"><a id="sc_b311" name="sc_b311"> </a>B.3.1.1 Checking Assistance (WCAG): </h4> <p class="sc-title"> If the <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> provides <a class="termdef" href="#def-Author" title="definition: authors">authors</a> with the ability to add or modify <a class="termdef" href="#def-Web-Content" title="definition: web content">web content</a> in such a way that a <a href="#conf-rel-wcag">WCAG 2.0</a> success criterion can be violated, then accessibility <a href="#def-Checking" title="definition: checking" class="termdef">checking</a> for that success criterion is provided (e.g. an HTML authoring tool that inserts images should check for alternative text; a <a href="#def-Video" title="definition: video" class="termdef">video</a> authoring tool with the ability to edit text tracks should check for captions). <span class="level">(<strong>Level A</strong> to meet WCAG 2.0 Level A success criteria; <strong>Level AA</strong> to meet WCAG 2.0 Level A and AA success criteria; <strong>Level AAA</strong> to meet all WCAG 2.0 success criteria)</span></p> <ul class="sc-notes"> <li class="sc-note"><em class="note-handle">Note:</em> <a class="termdef" href="#def-Automated-Checking" title="definition: automated checking">Automated </a> and <a class="termdef" href="#def-Semi-Automated-Checking" title="definition: semi-automated checking">semi-automated checking</a> is possible (and encouraged) for many types of <a href="#def-Web-Content-Accessibility-Problem" title="definition: Web content accessibility problem" class="termdef">web content accessibility problems (WCAG)</a>. However, <a href="#def-Manual-Checking" title="definition: manual checking" class="termdef">manual checking</a> is the minimum requirement to meet this success criterion. In manual checking, the authoring tool provides <a class="termdef" href="#def-Author" title="definition: author">authors</a> with instructions for detecting problems, which authors carry out by themselves. For more information on checking, see <a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#checking-types">Implementing ATAG 2.0 - Appendix B: Levels of Checking Automation</a>.</li></ul> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_b311">Implementing B.3.1.1</a></div> </div>  </div> <div class="sc-level"> <h4 class="sc-title"><a id="sc_b312" name="sc_b312"> </a>B.3.1.2 Help Authors Decide: </h4> <p class="sc-title"> If the <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> provides <a href="#def-Checking" title="definition: checking" class="termdef">accessibility checking</a> that relies on <a class="termdef" href="#def-Author" title="definition: authors">authors</a> to decide whether potential web content accessibility problems (WCAG) are correctly identified (i.e. <a href="#def-Manual-Checking" title="definition: manual checking" class="termdef">manual checking</a> and <a href="#def-Semi-Automated-Checking" title="definition: semi-automated checking" class="termdef">semi-automated checking</a>), then the accessibility checking process provides instructions that describe how to decide. <span class="level">(<strong>Level A</strong>)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_b312">Implementing B.3.1.2</a></div> </div> <h4 class="sc-title"><a id="sc_b313" name="sc_b313"> </a>B.3.1.3 Help Authors Locate: </h4> <p class="sc-title"> If the <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> provides <a href="#def-Checking" title="definition: checking" class="termdef">checks</a> that require <a class="termdef" href="#def-Author" title="definition: author">authors</a> to decide whether a potential <a href="#def-Web-Content-Accessibility-Problem" title="definition: Web content accessibility problem" class="termdef">web content accessibility problem (WCAG)</a> is correctly identified (i.e. <a href="#def-Manual-Checking" title="definition: manual checking" class="termdef">manual checking</a> and <a href="#def-Semi-Automated-Checking" title="definition: semi-automated checking" class="termdef">semi-automated checking</a>), then the relevant content is identified to the authors. <span class="level">(<strong>Level A</strong>)</span></p> <ul class="sc-notes"> <li class="sc-note"><em class="note-handle">Note:</em> Depending on the nature of the <a class="termdef" href="#def-Editing-View" title="definition: editing view">editing-view</a> and the scope of the potential web content accessibility problem (WCAG), identification might involve highlighting elements or renderings of elements, displaying line numbers, or providing instructions.</li></ul> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_b313">Implementing B.3.1.3</a></div> </div> </div>  <div class="sc-level"> <h4 class="sc-title"><a id="sc_b314" name="sc_b314"> </a>B.3.1.4 Status Report: </h4> <p class="sc-title">If the <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> provides <a href="#def-Checking" title="definition: checking" class="termdef">checks</a>, then <a href="#def-Author" title="definition: authors" class="termdef">authors</a> can receive an accessibility status report based on the results of the accessibility checks. <span class="level">(<strong>Level AA</strong>)</span></p> <ul class="sc-notes"> <li class="sc-note"><em class="note-handle">Note:</em> The format of the accessibility status report is not specified and they might include a listing of <a href="#def-Web-Content-Accessibility-Problem" title="definition: Web content accessibility problem" class="termdef">problems</a> detected or a <a href="#conf-rel-wcag">WCAG 2.0</a> conformance level, etc.</li></ul> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_b314">Implementing B.3.1.4</a></div> </div> <h4 class="sc-title"><a id="sc_b315" name="sc_b315"> </a>B.3.1.5 Programmatic Association of Results: </h4> <p class="sc-title">If the <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> provides <a href="#def-Checking" title="definition: checking" class="termdef">checks</a>, then the <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> can <a href="#def-Associated-Alternative-Content" title="definition: alternative content" class="termdef">programmatically associate</a> accessibility <a href="#def-Checking" title="definition: checking" class="termdef">checking</a> results with the <a class="termdef" href="#def-Web-Content" title="definition: web content">web content</a> that was checked. <span class="level">(<strong>Level AA</strong>)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_b315">Implementing B.3.1.5</a></div> </div> </div>  <h3 class="guideline"><a id="gl_b32" name="gl_b32"> </a> Guideline B.3.2: Assist authors in repairing accessibility problems. <span class="gl-only"> [<a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#gl_b32">Implementing B.2.3</a>] </span> </h3> <p class="rationale">Rationale: When <a href="#def-Repairing" title="definition: repairing" class="termdef">repair</a> is an integral part of the authoring process, it greatly enhances the utility of <a href="#def-Checking" title="definition: checking" class="termdef">checking</a> and increases the likelihood that <a href="#def-Web-Content-Accessibility-Problem" title="definition: web content accessibility problems" class="termdef">web content accessibility problems (WCAG)</a> will be properly addressed.</p> <div class="sc-level"> <h4 class="sc-title"><a id="sc_b321" name="sc_b321"> </a>B.3.2.1 Repair Assistance (WCAG): </h4> <p class="sc-title"> If <a href="#def-Checking" title="definition: checking" class="termdef">checking</a> (see <a href="#sc_b311">Success Criterion B.3.1.1</a>) can detect that a <a href="#conf-rel-wcag">WCAG 2.0</a> success criterion is not met, then <a href="#def-Repairing" title="definition: repairing" class="termdef">repair</a> suggestion(s) are provided: <span class="level">(<strong>Level A</strong> to meet WCAG 2.0 Level A success criteria; <strong>Level AA</strong> to meet WCAG 2.0 Level A and AA success criteria; <strong>Level AAA</strong> to meet all WCAG 2.0 success criteria)</span></p> <ul class="sc-notes"> <li class="sc-note"><em class="note-handle">Note:</em> <a class="termdef" href="#def-Automated-Repairing" title="definition: automated checking">Automated</a><a class="termdef" href="#def-Automated-Checking" title="definition: automated checking"> and</a> <a class="termdef" href="#def-Semi-Automated-Repairing" title="definition: semi-automated checking">semi-automated repair</a> is possible (and encouraged) for many types of <a href="#def-Web-Content-Accessibility-Problem" title="definition: web content accessibility problems" class="termdef">web content accessibility problems (WCAG)</a>. However, <a href="#def-Manual-Repairing" title="definition: manual repairing" class="termdef">manual repair</a> is the minimum requirement to meet this success criterion. In manual repair, the <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> provides <a class="termdef" href="#def-Author" title="definition: author">authors</a> with instructions for repairing problems, which authors carry out by themselves. For more information on repair, see <a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#repair-types">Implementing ATAG 2.0 - Appendix C: Levels of Repair Automation</a>.</li></ul> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_b321">Implementing B.3.2.1</a></div> </div> </div>  <h2 class="principle"><a id="principle_b4" name="principle_b4"> </a>Principle B.4: Authoring tools promote and integrate their accessibility features </h2> <h3 class="guideline"><a id="gl_b41" name="gl_b41"> </a> Guideline B.4.1: Ensure the availability of features that support the production of accessible content. <span class="gl-only"> [<a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#gl_b41">Implementing B.4.1</a>]</span> </h3> <p class="rationale">Rationale: The <a class="termdef" href="#def-Accessible-Content-Support-Features" title="definition: accessible content support features">accessible content support features</a> will be more likely to be used, if they are turned on and are afforded reasonable <a class="termdef" href="#def-Prominence" title="definition: prominence">prominence</a> within the <a href="#def-Authoring-Tool-Interface" title="definition: authoring tool user interface" class="termdef">authoring tool user interface</a>.</p> <div class="sc-level"> <h4 class="sc-title"><a id="sc_b411" name="sc_b411"> </a>B.4.1.1 Features Active by Default: </h4><p class="sc-title"> All <a title="definition: accessible content support features" class="termdef" href="#def-Accessible-Content-Support-Features">accessible content support features</a> are turned on by default. <span class="level">(<strong>Level A</strong>)</span> </p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_b411">Implementing B.4.1.1</a></div> </div> <h4 class="sc-title"><a id="sc_b412" name="sc_b412"> </a>B.4.1.2 Option to Reactivate Features: </h4> <p class="sc-title"> The <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> does not include the <span class="sc-bullet"><a href="#def-Option" title="definition: option" class="termdef">option</a></span> to turn off its <a title="definition: accessible content support features" class="termdef" href="#def-Accessible-Content-Support-Features">accessible content support features</a> or features which have been turned off can be turned back on. <span class="level">(<strong>Level A</strong>)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_b412">Implementing B.4.1.2</a></div> </div> </div>  <div class="sc-level"> <h4 class="sc-title"><a id="sc_b413" name="sc_b413"> </a>B.4.1.3 Feature Deactivation Warning: </h4> <p class="sc-title"> The <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> does not include the <span class="sc-bullet"><a href="#def-Option" title="definition: option" class="termdef">option</a></span> to turn off its <a title="definition: accessible content support features" class="termdef" href="#def-Accessible-Content-Support-Features">accessible content support features</a> or, if these features can be turned off, <a href="#def-Author" title="definition: authors" class="termdef">authors</a> are informed that this may increase the risk of <a title="definition: web content accessibility problem" class="termdef" href="#def-Web-Content-Accessibility-Problem">content accessibility problems (WCAG)</a>. <span class="level">(<strong>Level AA</strong>)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_b413">Implementing B.4.1.3</a></div> </div> <h4 class="sc-title"><a id="sc_b414" name="sc_b414"> </a>B.4.1.4 Feature Prominence: </h4> <p class="sc-title">All <a class="termdef" href="#def-Accessible-Content-Support-Features" title="definition: accessible content support features"> accessible content support features</a> are <a class="termdef" href="#def-At-Least-As-Prominent" title="definition: At Least As Prominent">at least as prominent</a> as features related to either invalid <a href="#def-Markup" title="definition: markup" class="termdef">markup</a>, syntax errors, spelling errors or grammar errors. <span class="level">(<strong>Level AA</strong>)</span> </p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_b414">Implementing B.4.1.4</a></div> </div> </div>  <h3 class="guideline"><a id="gl_b42" name="gl_b42"> </a> Guideline B.4.2: Ensure that documentation promotes the production of accessible content. <span class="gl-only">[<a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#gl_b42">Implementing B.4.2</a>]</span> </h3> <p class="rationale">Rationale: Some <a class="termdef" href="#def-Author" title="definition: author">authors</a> need support in determining how to use <a class="termdef" href="#def-Accessible-Content-Support-Features" title="definition: accessible content support features">accessible content production features</a> (e.g. how to respond to <a href="#def-Prompt" title="definition: prompt" class="termdef">prompts</a> for <span class="sc-bullet"><a class="termdef" href="#def-Text-Alternatives" title="text alternatives for non-text content">text alternatives</a></span>, how to use accessibility <a href="#def-Checking" title="definition: checking" class="termdef">checking</a> tools). Demonstrating accessible authoring as routine practice, or at least not demonstrating inaccessible practices, will help to encourage acceptance of accessibility by some authors.</p> <div class="sc-level"> <h4 class="sc-title"><a id="sc_b421" name="sc_b421"> </a>B.4.2.1 Model Practice (WCAG): </h4> <p class="sc-title"> A <a class="termdef" title="definition: range" href="#def-Range">range</a> of examples in the <a class="termdef" href="#def-Documentation" title="definition: documentation">documentation</a> (e.g. <a href="#def-Markup" title="definition: markup" class="termdef">markup</a>, screen shots of <a class="termdef" href="#def-WYSIWYG" title="definition: WYSIWYG">WYSIWYG</a> <a href="#def-Editing-View" title="definition: editing views" class="termdef">editing-views</a>) demonstrate <a class="termdef" href="#def-Acc-Auth-Practice" title="definition: accessible authoring practices">accessible authoring practices (WCAG)</a>. <span class="level">(<strong>Level A</strong> to meet WCAG 2.0 Level A success criteria; <strong>Level AA</strong> to meet WCAG 2.0 Level A and AA success criteria; <strong>Level AAA</strong> to meet all WCAG 2.0 success criteria)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_b421">Implementing B.4.2.1</a></div> </div> </div>  <div class="sc-level"> <h4 class="sc-title"><a id="sc_b422" name="sc_b422"> </a>B.4.2.2 Feature Instructions: </h4> <p class="sc-title"> Instructions for using any <a class="termdef" href="#def-Accessible-Content-Support-Features" title="definition: accessible content support features"> accessible content support features</a> appear in the <a class="termdef" href="#def-Documentation" title="definition: documentation">documentation</a>. <span class="level">(<strong>Level A</strong>)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_b422">Implementing B.4.2.2</a></div> </div> </div>  <div class="sc-level"> <h4 class="sc-title"><a id="sc_b423" name="sc_b423"> </a>B.4.2.3 Tutorial: </h4> <p class="sc-title"> The <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> provides a <a href="#def-Tutorial" title="definition: tutorial" class="termdef">tutorial</a> for an accessible authoring process that is specific to that authoring tool. <span class="level">(<strong>Level AAA</strong>)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_b423">Implementing B.4.2.3</a></div> </div> <h4 class="sc-title"><a id="sc_b424" name="sc_b424"> </a>B.4.2.4 Instruction Index: </h4> <p class="sc-title"> The <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> <a class="termdef" href="#def-Documentation" title="definition: documentation">documentation</a> contains an index to the instructions for using any <a class="termdef" href="#def-Accessible-Content-Support-Features" title="definition: accessible content support features"> accessible content support features</a>. <span class="level">(<strong>Level AAA</strong>)</span></p> <div class="gl-only"> <div class="implementing-link"><a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_b424">Implementing B.4.2.4</a></div> </div>  </div> </div>  <hr /> <div id="sect-conformance"> <h2><a id="Conformance" name="Conformance"> </a>Conformance</h2> <div class="gl-only"> <p>This section is <a class="termdef" href="#def-Normative" title="definition: normative">normative</a>.</p> </div>  <p>Conformance means that the <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> satisfies the <a href="#conf-applic">applicable</a> success criteria defined in the <a href="#guidelines">guidelines</a> section. This conformance section describes conformance and lists the conformance requirements.</p> <h3><a name="conf-req" id="conf-req"></a>Conformance Requirements</h3> <h4><a name="conf-sc-satisfaction" id="conf-sc-satisfaction"></a>Success Criteria Satisfaction</h4> <p>The first step in determining ATAG 2.0 conformance is to assess whether the Success Criteria have been satisfied. The potential answers are:</p> <ul> <li><strong><a name="conf-applic" id="conf-applic"></a>Not Applicable: </strong>The ATAG 2.0 <a href="#def-Authoring-Tool">definition of authoring tool</a> is inclusive and, as such, it covers software with a wide range of capabilities and contexts of operation. In order to take into account authoring tools with limited feature sets (e.g. a photo editor, a CSS editor, a status update field in a social networking application), many of the ATAG 2.0 success criteria are conditional, applying only to authoring tools with the given features(s). If a conformance claim is made, an explanation of why the success criterion is not applicable is <strong>required</strong>.</li> <li><strong>Yes:</strong> In the case of some success criteria, this will include a <a href="#conf-levels">Level</a> (A, AA, or AAA) with reference to WCAG 2.0. If a <a href="#conf-claim">conformance claim</a> is made, an explanation is <strong>optional</strong>, yet strongly recommended.</li> <li><strong>No:</strong> If a conformance claim is made, an explanation is <strong>optional</strong>, yet strongly recommended.</li> </ul> <h4><a id="conf-rel-wcag" name="conf-rel-wcag"> </a>Relationship to the Web Content Accessibility Guidelines (WCAG) 2.0</h4> <p>At the time of publishing, WCAG 2.0 <cite>[<a href="#ref-WCAG20">WCAG20</a>]</cite> is the current W3C Recommendation regarding web content accessibility. For this reason, ATAG 2.0 refers to WCAG 2.0 when setting requirements for (1) the accessibility of <a class="termdef" href="#def-Web-Based-UI" title="definition: authoring tool user interface (Web-based)">web-based authoring tool user interfaces</a> (in <a href="#part_a">Part A</a>) and (2) how <a href="#def-Author" title="definition: authors" class="termdef">authors</a> should be enabled, supported, and guided toward producing web content that is more accessible to <a href="#def-End-Users" title="definition: end user" class="termdef">end users</a> with disabilities (in <a href="#part_b"> Part B</a>). </p> <p>In particular, ATAG 2.0 refers to WCAG 2.0 within its definition of the term "<a class="termdef" href="#def-Accessible-Web-Content" title="definition: accessible web content">accessible content</a>" (and related terms, such as "<a href="#def-Accessible-Template" title="definition: accessible templates" class="termdef">accessible template</a>"). The definition of "accessible content" is content that would conform to WCAG 2.0, at either Level A, AA, or AAA, under the assumption that any web content technologies that are relied upon to satisfy the WCAG 2.0 success criteria are accessibility supported. The phrase "at either Level A, AA, or AAA" takes into account that the definition of "accessible content" can differ depending on the context of use (e.g. in a Level A success criterion of ATAG 2.0 versus in a Level AAA success criterion). The definition also includes two notes:</p> <ul> <li>The first is "If accessibility support for the relied upon technologies is lacking, then the content will not conform to WCAG 2.0 and one or more groups of end-users with disabilities will likely experience difficulty accessing the content."</li> <li>The second is "Conformance to WCAG 2.0, even at the highest level (i.e. Level AAA), still may not make content 'accessible to individuals with all types, degrees, or combinations of disability'." In order to highlight success criteria or defined terms in ATAG 2.0 that depend on WCAG 2.0, they are marked with the parenthetical: "(WCAG)".</li> </ul> <h5><a id="conf-note" name="conf-note"></a>Note on "accessibility-supported ways of using technologies":</h5> <p>Part of conformance to WCAG 2.0 is the requirement that "only accessibility-supported ways of using technologies are relied upon to satisfy the WCAG 2.0 success criteria. Any information or functionality that is provided in a way that is not accessibility supported is also available in a way that is <em>accessibility supported</em>." In broad terms, WCAG 2.0 considers a <a href="#def-Web-Content-Technology" title="definition: technology (Web content)" class="termdef">web content technology</a> to be "accessibility supported" when (1) the way that the web content technology is used is supported by users' <a class="termdef" href="#def-Assistive-Technology" title="definition: assistive technology">assistive technology</a> and (2) the web content technology has accessibility-supported <a class="termdef" href="#def-User-Agent" title="definition: user agent">user agents</a> that are available to end users. </p> <p>This concept is not easily extended to <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tools</a> because many authoring tools can be installed and used in a variety of environments with differing availabilities for assistive technologies and user agents (e.g. private intranets versus public websites, monolingual sites versus multilingual sites). Therefore: </p> <blockquote> <p><strong>ATAG 2.0 does not include the accessibility-supported requirement. As a result, ATAG 2.0 success criteria do not refer to WCAG 2.0 "conformance", and instead refer to "meeting WCAG 2.0 success criteria".</strong></p> </blockquote> <p>Once an authoring tool has been installed and put into use, it would be possible to assess the WCAG 2.0 conformance of the <a class="termdef" href="#def-Web-Content" title="definition: web content">web content</a> that the authoring tool produces, including whether the WCAG 2.0 accessibility-supported requirement is met. However, this WCAG 2.0 conformance assessment would be completely independent of the authoring tool's conformance with ATAG 2.0.</p> <h4><a name="conf-levels" id="conf-levels"> </a>Conformance Options and Levels</h4> <p>There are two types of conformance, each with three levels:</p> <h5><a name="conf-atag-conf" id="conf-atag-conf"> </a>ATAG 2.0 Conformance (Level A, AA, or AAA)</h5> <p>This conformance option <em>may</em> be selected when an <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> can be used to produce <a class="termdef" href="#def-Accessible-Web-Content" title="definition: accessible web content">accessible web content (WCAG)</a> without additional tools or components. The level of conformance is determined as follows:</p> <ul> <li><strong>Level A:</strong> The authoring tool satisfies all of the <a href="#conf-applic">applicable</a> Level A success criteria.</li> <li><strong>Level AA:</strong> The authoring tool satisfies all of the applicable Level A and Level AA success criteria.</li> <li><strong>Level AAA:</strong> The authoring tool satisfies all of the applicable success criteria.</li> </ul> <p><em>Note 1:</em> The <a href="#part_a_applic_notes">Part A Conformance Applicability Notes</a> and <a href="#part_b_applic_notes">Part B Conformance Applicability Notes</a> must be applied. <br /> <em>Note 2:</em> If the minimum conformance level (Level A) has not been achieved (i.e. at least one applicable Level A success criterion has not been met), it is still beneficial to publish a statement specifying which success criteria were met.</p> <h5><a name="conf-partial-component" id="conf-partial-component"></a>Partial ATAG 2.0 Conformance - Process Component (Level A, AA, or AAA)</h5> <p>This conformance option <em>may</em> be selected when an <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> would require additional tools or components<strong> </strong>in order to conform as a complete authoring system. This option may be used for components with very limited functionality (e.g. a plug-in) up to nearly complete systems (e.g. a markup editor that only lacks accessibility checking functionality). </p> <p>The level of conformance (A, AA, or AAA) is determined as above except that, for any "no" answers, the tool must not prevent the success criteria from being met by another authoring process component as part of a complete authoring system.</p> <p> <em>Note 1:</em> Authoring tools would not be able to meet partial conformance if they prevent additional authoring process components from meeting the failed success criteria (e.g. for security reasons).<br /> <em>Note 2:</em> The <a href="#part_a_applic_notes">Part A Conformance Applicability Notes</a> and <a href="#part_b_applic_notes">Part B Conformance Applicability Notes</a> must be applied. </p> <h5><a name="conf-partial-platform-limits" id="conf-partial-platform-limits"></a>Partial ATAG 2.0 Conformance - Platform Limitations (Level A, AA, or AAA)</h5> <p>This conformance option may be selected when an <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> is unable to meet one or more success criteria because of intrinsic limitations of the <a class="termdef" href="#def-Platform" title="definition: platform">platform</a> (e.g. lacking a <a class="termdef" href="#def-Accessibility-Platform-Service" title="definition: accessibility platform architecture">platform accessibility service</a>). The (optional) explanation of conformance claim results should explain what platform features are missing. </p> <h4><a name="conf-techs-produced" id="conf-techs-produced"> </a>Web Content Technologies Produced:</h4> <p><a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">Authoring tools</a> conform to ATAG 2.0 with respect to the production of specific <a class="termdef" href="#def-Web-Content-Technology" title="definition: technology (Web content)">web content technologies</a> (e.g. Level A Conformance with respect to the production of XHTML 1.0).</p> <p>If an authoring tool is capable of producing multiple web content technologies, then the conformance may include only a subset of these technologies as long as the subset includes both any technologies that the <a class="termdef" href="#def-Developer" title="definition: authoring tool developers">developer</a> sets for <a href="#def-Content-Auto-Gen" title="definition: automatically-generated content" class="termdef">automatically-generated content</a> or that the developer sets as the default for <a class="termdef" href="#def-Content-Author-Gen" title="definition: author generated content">author-generated content</a>. The subset may include "interim" formats that are not intended for <a href="#def-Publishing" title="definition: publishing" class="termdef">publishing</a> to <a href="#def-End-Users" title="definition: end user" class="termdef">end users</a>, though this is not required. </p> <h4><a name="conf-live-publishing" id="conf-live-publishing"></a>Live publishing authoring tools: </h4> <p>ATAG 2.0 may be applied to authoring tools with workflows that involve live authoring of web content (e.g. some collaborative tools). Due to the challenges inherent in real-time publishing, conformance to <a href="#part_b">Part B</a> of ATAG 2.0 for these authoring tools may involve some combination of support before (e.g. support in preparing accessible slides), during (e.g. live captioning as WCAG 2.0 requires at Level AA) and after the live <span class="sc"><a href="#def-Authoring-Session" title="definition: authoring session" class="termdef">authoring session</a></span> (e.g. the ability to add a transcript to the archive of a presentation that was initially published in real-time). For more information, see <a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#realtime-production">Implementing ATAG 2.0 - Appendix E: Authoring Tools for Live Web Content</a>.</p> <h3><a name="conf-claim" id="conf-claim"> </a>Conformance Claims (Optional)</h3> <p><em>Note:</em> As with any software application, authoring tools can be collections of components. A conformance claim can only be made by a responsible entity. Any other attempted "claims" are, in fact, reviews.</p> <h4><a name="conf-claim-req-components" id="conf-claim-req-components"> </a>Required Components of a Conformance Claim</h4> <ol> <li><strong>Date</strong> of the claim.</li> <li><strong>ATAG 2.0 </strong> <strong>version </strong>and<strong> URI</strong></li> <li><a href="#conf-levels"><strong>Conformance level</strong></a> satisfied.</li> <li><strong>Authoring tool information:</strong> The name of the <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> and sufficient additional information to specify the version (e.g. vendor name, version number (or version range), required patches or updates, <a class="termdef" href="#def-Human-Language" title="definition: human language">human language</a> of the user interface or <a class="termdef" href="#def-Documentation" title="definition: documentation">documentation</a>). <ul> <li><em>Note:</em> If the authoring tool is a collection of software applications (e.g. a <a href="#def-Markup" title="definition: markup" class="termdef">markup</a> editor, an image editor, and a validation tool), then information must be provided separately for each application, although the conformance claim will treat them as a whole.</li> </ul> </li> <li><strong>Platform(s):</strong> The <a class="termdef" href="#def-Platform" title="definition: platform">platform(s)</a> upon which the authoring tool operates: <ul> <li><a name="conf-user-agents" id="conf-user-agents"></a>For <strong><a href="#def-User-Agent" title="definition: user agent" class="termdef">user agent</a> platform(s)</strong> (used to evaluate <a class="termdef" href="#def-Web-Based-UI" title="definition: authoring tool user interface (Web-based)">web-based authoring tool user interfaces</a>): provide the name and version information of the user agent(s).</li> <li> <a name="conf-not-user-agents" id="conf-not-user-agents"></a>For <strong>platforms that are not <a href="#def-User-Agent" title="definition: user agent" class="termdef">user agents</a></strong> (used to evaluate <a class="termdef" href="#def-Non-Web-Based" title="definition: authoring tool user interface (non-Web-Based)">non-web-based authoring tool user interfaces</a>): provide the name and version information of the platform(s) (e.g. desktop operating system, mobile operating system, cross-OS environment) and the name and version of the <a href="#def-Accessibility-Platform-Service" title="definition: platform accessibility architectur" class="termdef">platform accessibility service(s)</a> employed.</li> </ul> </li> <li>A list of the <strong>web content technologies produced by the authoring tool that are included in the claim</strong>. If there are any <a class="termdef" href="#def-Web-Content-Technology" title="definition: technology (Web content)">web content technologies</a> <a href="#conf-techs-produced">produced</a> by the authoring tool that are not included in the conformance claim, these must be listed separately. If the authoring tool produces any web content technologies by default, then these must be included.</li> <li><strong> Results for each of the success criteria:</strong> Yes, No, <a href="#conf-applic">Not Applicable</a></li> </ol> <h4><a name="conf-claim-optional-components" id="conf-claim-optional-components"> </a>Optional Components of a Conformance Claim</h4> <p>In addition to the required components of a conformance claim above, consider providing additional information to assist authors. Recommended additional information includes:</p> <ol> <li><a name="conf-explanation-results" id="conf-explanation-results"></a> An <strong>explanation of the success criteria results</strong> (Yes, No). (strongly recommended)</li> <li>Information about how the web content technologies produced can be used to create <a class="termdef" href="#def-Accessible-Web-Content" title="definition: accessible Web content">accessible web content</a> (e.g. links to technology-specific WCAG 2.0 techniques).</li> <li>Information about any additional steps taken that go beyond the success criteria to enhance accessibility.</li> <li>A machine-readable metadata version of the conformance claim. </li> <li>A description of the authoring tool that identifies the types of editing-views that it includes.</li> </ol> <h3><a name="conf-disclaimer" id="conf-disclaimer"> </a>Disclaimer</h3> <p>Neither W3C, WAI, nor AUWG take any responsibility for any aspect or result of any ATAG 2.0 <a href="#conf-claim">conformance claim</a> that has not been published under the authority of the W3C, WAI, or AUWG. </p> </div>  <hr />      <div id="sect-definitions"> <h2><a id="glossary" name="glossary"></a>Appendix <span class="gl-only">A</span>: Glossary</h2> <div class="gl-only"> <p>This section is <a class="termdef" href="#def-Normative" title="definition: normative">normative</a>.</p> <p>This appendix contains definitions for all of the significant/important/unfamiliar terms used in the normative parts of this standard, including terms used in the <a href="#Conformance">Conformance</a> section. Please consult <a href="https://www.w3.org/TR/qaframe-spec/">http://www.w3.org/TR/qaframe-spec/</a> for more information on the role of definitions in standards quality.</p> </div>  <dl> <dt><dfn><a id="def-Accessibility-Problem" name="def-Accessibility-Problem"></a>accessibility problems</dfn></dt> <dd>ATAG 2.0 recognizes two types of accessibility problems: <ul> <li><dfn><a id="def-Authoring-Interface-Accessibility-Problem" name="def-Authoring-Interface-Accessibility-Problem"></a>authoring tool user interface accessibility problems:</dfn> Aspects of an <a class="termdef" href="#def-Authoring-Tool-Interface" title="definition: authoring tool user interface">authoring tool user interface</a> that does not meet a success criterion in <a href="#part_a">Part A</a> of ATAG 2.0.</li> <li><a id="def-Web-Content-Accessibility-Problem" name="def-Web-Content-Accessibility-Problem"></a><dfn>web content accessibility problems (WCAG):</dfn> Aspects of <a href="#def-Web-Content" title="definition: web content" class="termdef">web content</a> that does not meet a <a href="#conf-rel-wcag">WCAG 2.0</a> success criterion (Level A, AA or AAA).</li> </ul></dd> <dt><a id="def-Accessibility-Information" name="def-Accessibility-Information"><dfn>accessibility information (WCAG)</dfn></a> </dt> <dd>Information that <a href="#def-Web-Content" title="definition: web content" class="termdef">web content</a> must contain in order to meet a <a href="#conf-rel-wcag">WCAG 2.0</a> success criterion (Level A, AA or AAA). Examples include: <a href="#def-Associated-Alternative-Content" title="definition: alternative content" class="termdef">programmatically associated alternative content</a> (e.g. text alternatives for images), <a href="#def-Role" title="definition: role" class="termdef">role</a>, and state information for widgets, <a href="#def-Relationships" title="definition: relationships" class="termdef">relationships</a> within complex tables).<br /> <em>Note:</em> For the purposes of ATAG 2.0, only <a class="termdef" href="#def-Programmatically-Determined" title="definition: programmatically determined">programmatically determinable</a> accessibility information qualifies. For additional examples, see <a href="https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#prompting-types">Appendix A of the Implementing ATAG 2.0 document</a>.</dd> <dt><a id="def-Accessible-Content-Support-Features" name="def-Accessible-Content-Support-Features"><dfn>accessible content support features</dfn></a></dt> <dd>Any features of an <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> that directly support <a href="#def-Author" title="definition: authors" class="termdef">authors</a> in increasing the accessibility of the <a href="#def-Web-Content" title="definition: web content" class="termdef"> </a><a class="termdef" href="#def-Content-Being-Edited" title="definition: web content being edited">web content being edited</a>. These are features that must be present to meet the success criteria in <a href="#part_b">Part B</a> of ATAG 2.0.</dd> <dt><a id="def-Alternative-Content" name="def-Alternative-Content"></a><dfn>alternative content</dfn></dt> <dd><a href="#def-Web-Content" title="definition: web content" class="termdef">Web content</a> that is used 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. <a href="#conf-rel-wcag">WCAG 2.0</a> recognizes several general types of alternative content: <ul> <li><dfn><a id="def-Text-Alternatives" name="def-Text-Alternatives"></a>text alternatives for non-text content:</dfn> Text that is <a href="#def-Associated-Alternative-Content" title="definition: alternative content" class="termdef">programmatically associated</a> with <a class="termdef" href="#def-Non-Text-Objects" title="definition: non-text objects">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 description in the paragraph after the chart and a short text alternative for the chart indicating in words that a description follows.</li> <li><dfn><a id="def-Time-Based-Alternatives" name="def-Time-Based-Alternatives"></a>alternatives for time-based media:</dfn> <a href="#def-Web-Content" title="definition: web content" class="termdef">Web content</a> that serves the same function or purpose as one or more tracks in a time-based media presentation. This includes: captions, audio descriptions, extended audio descriptions, sign language interpretation as well as correctly sequenced text descriptions 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-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 may be audio-only, video-only (including sign-language video), or audio-video.</li> </ul> Importantly, from the perspective of authoring tools, alternative content may or may not be: <ul> <li> <a id="def-Associated-Alternative-Content" name="def-Associated-Alternative-Content"></a><dfn>programmatically associated alternative content: </dfn>Alternative content whose location and purpose can be <a class="termdef" href="#def-Programmatically-Determined" title="definition: programmatically determined">programmatically determined</a> from the original content for which it is serving as an alternative. For example, a paragraph might serve as a text alternative for an image, but it is only programmatically associated if this relationship is properly encoded (e.g. by "aria-labeledby"). <br /> <em>Note:</em> ATAG 2.0 typically refers to programmatically associated alternative content.</li> </ul></dd> <dt><a id="def-Assistive-Technology" name="def-Assistive-Technology"><dfn>assistive technology</dfn></a> </dt> <dd>Software (or hardware), separate from the <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a>, that provides functionality to meet the requirements of people with disabilities (<a href="#def-Author" title="definition: authors" class="termdef">authors</a> and <a class="termdef" href="#def-End-Users" title="definition: end user">end users</a>). Some authoring tools may also provide <a href="#def-Direct-Accessibility" title="definition: direct accessibility features" class="termdef">direct accessibility features</a>. Examples include: <ul> <li>screen magnifiers, and other visual reading assistants, which are used by people with visual, perceptual, and physical print disabilities to change text font, size, spacing, color, synchronization with speech, etc. in order improve the visual readability of rendered text and images;</li> <li>screen readers, which are used by people who are blind to read textual information through synthesized speech or Braille;</li> <li>text-to-speech software, which is used by some people with cognitive, language, and learning disabilities to convert text into synthetic speech;</li> <li>speech recognition software, which are used by some people who have some physical disabilities;</li> <li>alternative keyboards, which are used by some people with physical disabilities to simulate the keyboard (including alternate keyboards that use head pointers, single switches, sip/puff, and other special input devices);</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><a id="def-Audio" name="def-Audio"><dfn>audio</dfn></a> </dt> <dd>The technology of sound reproduction. Audio can be created synthetically (including speech synthesis), recorded from real-world sounds, or both.</dd> <dt><a id="def-Author-Actions-Prevent" name="def-Author-Actions-Prevent"><dfn>author actions preventing generation of accessible web content</dfn></a></dt> <dd>When the actions of <a href="#def-Author" title="definition: authors" class="termdef">authors</a> prevent <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tools</a> from generating <a class="termdef" href="#def-Accessible-Web-Content" title="definition: accessible web content">accessible web content (WCAG)</a>. Examples include: turning off <a class="termdef" href="#def-Accessible-Content-Support-Features" title="definition: accessible content support features"> accessible content support features</a>, ignoring <a href="#def-Prompt" title="definition: prompt" class="termdef">prompts</a> for <a class="termdef" href="#def-Accessibility-Information" title="definition: accessibility information">accessibility information (WCAG)</a>, providing faulty accessibility information (WCAG) at prompts, modifying the authoring tool (e.g. via scripting, macros), and installing <a href="#def-Plugin" title="definition: plug-in" class="termdef">plug-ins</a>.</dd> <dt><dfn><a id="def-Author" name="def-Author"></a>authors</dfn></dt> <dd>People who use <a href="#def-Authoring-Tool" title="definition: authoring tool" class="termdef">authoring tools</a> to create or modify <a class="termdef" href="#def-Web-Content" title="definition: web content">web content</a>. The term may cover roles such as content authors, designers, programmers, publishers, testers, etc. (see <a href="#part_b_applic_note_6">Part B Conformance Applicability Note 6: Multiple authoring roles</a>). Some authoring tools control who may be an author by managing <a href="#def-Authoring-Permission" title="definition: author permission" class="termdef">author permissions</a>.</dd> <dt><a id="def-Authoring-Permission" name="def-Authoring-Permission"><dfn>author permission</dfn></a></dt> <dd>Authorization that allows modification of given <a href="#def-Web-Content" title="definition: web content" class="termdef">web content</a>.</dd> <dt><a name="def-Authoring-Action" id="def-Authoring-Action"></a><dfn>authoring action</dfn></dt> <dd>Any action that <a class="termdef" href="#def-Author" title="definition: author">authors</a> can take using the <a class="termdef" href="#def-Authoring-Tool-Interface" title="definition: authoring tool user interface">authoring tool user interface</a> that results in editing <a class="termdef" href="#def-Web-Content" title="definition: web content">web content</a> (e.g. typing text, deleting, inserting an <a href="#def-Element" title="definition: element" class="termdef">element</a>, applying a <a href="#def-Template" title="definition: template" class="termdef">template</a>). In contrast, most authoring tool user interfaces also enable actions that do not edit content (e.g. saving, <a href="#def-Publishing" title="definition: publishing" class="termdef">publishing</a>, setting preferences, viewing <a href="#def-Documentation" title="definition: documentation" class="termdef">documentation</a>). <ul> <li><dfn><a name="def-Reversible-Action" id="def-Reversible-Action"></a>reversible authoring action</dfn>: An <a class="termdef" href="#def-Authoring-Action" title="definition: authoring action">authoring action</a> that can be immediately and completely undone by the <a href="#def-Authoring-Tool" title="definition: authoring tool" class="termdef">authoring tool</a> upon a cancel request by an <a class="termdef" href="#def-Author" title="definition: author">author</a>. Examples of cancel requests include: "cancel", "undo", "redo" (when it used to reverse "undo"), "revert", and "roll-back"<br /> <em>Note:</em> It is acceptable for an authoring tool to collect a series of text entry actions (e.g. typed words, a series of backspaces) into a single reversible authoring action.</li> </ul> </dd> <dt><a name="def-Authoring-Outcome" id="def-Authoring-Outcome"></a><dfn>authoring outcome</dfn></dt> <dd>The <a class="termdef" href="#def-Web-Content" title="definition: web content">content</a> or content modifications that result from <a class="termdef" href="#def-Authoring-Action" title="definition: authoring action">authoring actions</a>. Authoring outcomes are cumulative (e.g. text is entered, then styled, then made into a link, then given a title).</dd> <dt><a name="def-Authoring-Practice" id="def-Authoring-Practice"></a><dfn>authoring practice</dfn></dt> <dd>An approach that <a href="#def-Author" title="definition: authors" class="termdef">authors</a> follow to achieve a given <a href="#def-Authoring-Outcome" title="definition: authoring outcome" class="termdef">authoring outcome</a> (e.g. controlling <a href="#def-Presentation" title="definition: presentation" class="termdef">presentation</a> with style sheets). Depending on the design of an <a href="#def-Authoring-Tool" title="definition: authoring tool" class="termdef">authoring tool</a>, authoring practices may be chosen by authors or by the authoring tool. Authoring practices may or may not be: <ul> <li><a name="def-Acc-Auth-Practice" id="def-Acc-Auth-Practice"></a><dfn>accessible authoring practices (WCAG):</dfn> An authoring practice in which the <a href="#def-Authoring-Outcome" title="definition: authoring outcome" class="termdef">authoring outcome</a> conforms to <a href="#conf-rel-wcag">WCAG 2.0</a> at Level A, AA, or AAA. Some accessible authoring practices require <a href="#def-Accessibility-Information" title="definition: accessibility information" class="termdef">accessibility information (WCAG)</a>.</li> </ul></dd> <dt><a name="def-Authoring-Session" id="def-Authoring-Session"></a><dfn>authoring session</dfn></dt> <dd>A state of the <a href="#def-Authoring-Tool" title="definition: authoring tool" class="termdef">authoring tool</a> in which <a href="#def-Web-Content" title="definition: web content" class="termdef">web content</a> can be edited by an <a href="#def-Author" title="definition: authors" class="termdef">author</a>. <ul> <li><a name="def-End-Auth-Session" id="def-End-Auth-Session"></a><dfn>end of an authoring session:</dfn> The point at which the <a href="#def-Author" title="definition: authors" class="termdef">author</a> has no further opportunity to make <a class="termdef" href="#def-Authoring-Action" title="definition: authoring action">authoring actions</a> without starting another <a href="#def-Authoring-Session" title="definition: authoring session" class="termdef">session</a>. The end of an authoring session may be determined by authors (e.g. closing a document, <a href="#def-Publishing" title="definition: publishing" class="termdef">publishing</a>) or by the <a href="#def-Authoring-Tool" title="definition: authoring tool" class="termdef">authoring tool</a> (e.g. when the authoring tool transfers editing permission to another author on a collaborative system). <br /> <em>Note:</em> The end of the authoring session is distinct from <a href="#def-Publishing" title="definition: publishing" class="termdef">publishing</a>. <a href="#def-Content-Auto-Gen" title="definition: automatically-generated content" class="termdef">Automatic content generation</a> may continue after the end of both the authoring session and initial publishing (e.g. content management system updates).</li></ul></dd> <dt><a id="def-Authoring-Tool" name="def-Authoring-Tool"><dfn>authoring tool</dfn></a></dt> <dd>Any web-based or non-web-based application(s) that can be used by <a class="termdef" href="#def-Author" title="definition: author">authors</a> (alone or collaboratively) to create or modify <a class="termdef" href="#def-Web-Content" title="definition: web content">web content</a> for use by other people (other authors or <a class="termdef" href="#def-End-Users" title="definition: end user">end user</a>s). <br /> <em>Note 1: "application(s)": </em>ATAG 2.0 may be conformed to by stand-alone applications or by collections of applications. If a conformance claim is made, then the claim must provide identifying information for each application and also for any required extensions, plug-ins, etc.<em><br /> Note 2: "alone or collaboratively": </em>Multiple authors may contribute to the creation of web content and, depending on the authoring tool, each author may work with different views of the content and different <a href="#def-Authoring-Permission" title="definition: author permission" class="termdef">author permissions</a>.<em> <br /> Note 3: "to create or modify web content": </em>This clause rules out software that collects data from a person for other purposes (e.g. online grocery order form) and then creates web content from that data (e.g. a web-based warehouse order) without informing the person (however, <a href="#conf-rel-wcag">WCAG 2.0</a> would still apply). This clause also rules out software used to create content exclusively in non-web content technologies.<em> <br /> Note 4: "for use by other people": </em>This clause rules out the many web applications that allow people to modify web content that only they themselves experience (e.g. web-based email display settings) or that only provide input to automated processes (e.g. library catalog search page).<em> <br /> </em>Examples of software that are generally considered authoring tools under ATAG 2.0: <ul> <li>web page authoring tools (e.g. <a class="termdef" href="#def-WYSIWYG" title="definition: WYSIWYG">WYSIWYG</a> HTML editors)</li> <li>software for directly editing source code</li> <li>software for converting to <a class="termdef" href="#def-Web-Content-Technology" title="definition: technology (Web content)">web content technologies</a> (e.g. "Save as HTML" features in office document applications) </li> <li>integrated development environments (e.g. for web application development)</li> <li>software that generates web content on the basis of <a href="#def-Template" title="definition: template" class="termdef">templates</a>, scripts, command-line input or "wizard"-type processes</li> <li>software for rapidly updating portions of web pages (e.g. blogging, wikis, online forums)</li> <li>software for generating/managing entire websites (e.g. content management systems, courseware tools, content aggregators)</li> <li>email clients that send messages using web content technologies</li> <li>multimedia authoring tools</li> <li>software for creating mobile web applications</li> </ul> Examples of software that are not considered authoring tools under ATAG 2.0 (in all cases, WCAG 2.0 still applies if the software is web-based): <ul> <li>customizable personal portals: ATAG 2.0 does not apply because the web content being edited is only available to the owner of the portal</li> <li>e-commerce order forms: ATAG 2.0 does not apply because the purpose of an e-commerce order form is to order a product, not communicate with other people via web content, even if the data collected by the form actually does result in web content (e.g. online tracking pages)</li> <li>stand-alone accessibility checkers: ATAG 2.0 does not apply because a stand-alone accessibility checker with no automated or semi-automated repair functionality does not actually modify web content. An accessibility checker with repair functionality or that is considered as part of a larger authoring process would be considered an authoring tool.<br /> </li></ul> </dd> <dt><dfn><a id="def-Authoring-Tool-Interface" name="def-Authoring-Tool-Interface"></a>authoring tool user interface</dfn></dt> <dd> The display and control mechanism that <a href="#def-Author" title="definition: authors" class="termdef">authors</a> use to operate the <a href="#def-Authoring-Tool" title="definition: authoring tool" class="termdef">authoring tool</a> software. User interfaces may be non-web-based or web-based or a combination (e.g. a non-web-based authoring tool might have web-based help pages): <ul> <li><a name="def-Non-Web-Based" id="def-Non-Web-Based"></a><dfn>authoring tool user interface (non-web-based):</dfn> Any parts of an authoring tool user interface that are not implemented as <a href="#def-Web-Content" title="definition: web content" class="termdef">web content</a> and instead run directly on a <a href="#def-Platform" title="definition: platform" class="termdef">platform</a> that is not a <a href="#def-User-Agent" title="definition: user agent" class="termdef">user agent</a> (e.g. Windows, Mac OS, Java Virtual Machine, iOS, Android).</li> <li><a id="def-Web-Based-UI" name="def-Web-Based-UI"></a><dfn>authoring tool user interface (web-based):</dfn> Any parts of an authoring tool user interface that are implemented using <a href="#def-Web-Content-Technology" title="definition: technology (Web content)" class="termdef">web content technologies</a> and are accessed by <a href="#def-Author" title="definition: authors" class="termdef">authors</a> via a <a class="termdef" href="#def-User-Agent" title="definition: user agent">user agent</a>. </li> </ul> Authoring tool user interfaces may or may not be: <ul> <li><dfn><a id="def-Accessible-Authoring-Interface" name="def-Accessible-Authoring-Interface"></a>accessible authoring tool user interfaces:</dfn> Authoring tool user interfaces that meet the success criteria of a level in <a href="#part_a">Part A</a> of ATAG 2.0. </li> </ul></dd> <dt><a id="def-Checking" name="def-Checking"><dfn>checking, accessibility </dfn></a> </dt> <dd>The process by which <a class="termdef" href="#def-Web-Content" title="definition: web content">web content</a> is evaluated for <a class="termdef" href="#def-Web-Content-Accessibility-Problem" title="definition: web content accessibility problem">web content accessibility problems (WCAG)</a>. ATAG 2.0 recognizes three types of checking, based on increasing levels of automation of the tests: <ul><li><a name="def-Manual-Checking" id="def-Manual-Checking"></a><dfn>manual checking:</dfn> Checking in which the tests are carried out by <a href="#def-Author" title="definition: authors" class="termdef">authors</a>. This includes the case where authors are aided by instructions or guidance provided by the <a href="#def-Authoring-Tool" title="definition: authoring tool" class="termdef">authoring tool</a>, but where authors must carry out the actual test procedure.</li> <li><a name="def-Semi-Automated-Checking" id="def-Semi-Automated-Checking"></a><dfn>semi-automated checking:</dfn> Checking in which the tests are partially carried out by the authoring tool, but where authors' input or judgment is still required to decide or help decide the outcome of the tests. </li> <li><a name="def-Automated-Checking" id="def-Automated-Checking"></a><dfn>automated checking:</dfn> Checking in which the tests are carried out automatically by the authoring tool without any intervention by authors. </li> </ul> An authoring tool may support any combination of checking types. </dd> <dt><a name="def-Web-Content" id="def-Web-Content"></a><dfn>content (web content)</dfn> </dt> <dd> Information and sensory experience to be communicated to the <a class="termdef" href="#def-End-Users" title="definition: end user">end user</a> by means of a <a class="termdef" href="#def-User-Agent" title="definition: user agent">user agent</a>, including code or <a href="#def-Markup" title="definition: markup" class="termdef">markup</a> that defines the content's structure, presentation, and interactions. In ATAG 2.0, the term is primarily used to refer to the output that is produced by the <a href="#def-Authoring-Tool" title="definition: authoring tool" class="termdef">authoring tool</a>. Content produced by authoring tools may include web applications, including those that act as <a class="termdef" href="#def-Web-Based-UI" title="definition: authoring tool user interface (Web-based)">web-based</a> authoring tools. Content may or may not be: <ul> <li><dfn><a id="def-Accessible-Web-Content" name="def-Accessible-Web-Content">accessible content (WCAG):</a></dfn> Content that would conform to <a href="#conf-rel-wcag">WCAG 2.0</a>, at either Level A, AA, or AAA, assuming that any <a href="#def-Web-Content-Technology" title="definition: technology (Web content)" class="termdef">web content technologies</a> relied upon to satisfy the WCAG 2.0 success criteria are accessibility supported. <ul> <li><em>Note 1:</em> If accessibility support for the relied upon technologies is lacking, then the content will not conform to WCAG 2.0 and one or more groups of end users with disabilities will likely experience difficulty accessing the content. </li> <li><em>Note 2:</em> Conformance to WCAG 2.0, even at the highest level (i.e. Level AAA), still may not make content "accessible to individuals with all types, degrees, or combinations of disability". </li> </ul> </li> <li><dfn><a id="def-Content-Being-Edited" name="def-Content-Being-Edited">content being edited:</a></dfn> The web content that an <a class="termdef" href="#def-Author" title="definition: author">author</a> can modify during an <a href="#def-Authoring-Session" title="definition: authoring session" class="termdef">authoring session</a>. The content being edited may be a complete piece of content (e.g. image, style sheet) or only part of a larger piece of content (e.g. a status update). The content being edited only includes content in <a href="#def-Web-Content-Technology" title="definition: technology (Web content)" class="termdef">web content technologies</a> that the <a href="#def-Authoring-Tool" title="definition: authoring tool" class="termdef">authoring tool</a> supports (e.g. a WYSIWYG HTML editor allows editing of the HTML content of a web page editable, but not the images).</li> </ul></dd> <dt><dfn><a name="def-Web-Content-Properties" id="def-Web-Content-Properties"></a>content properties</dfn></dt> <dd>The individual pieces of information that make up the <a class="termdef" href="#def-Web-Content" title="definition: web content">web content</a> (e.g. the attributes and contents of elements, style sheet information). </dd> <dt><a name="def-Structured-Web-Content" id="def-Structured-Web-Content"></a><dfn>content (structured)</dfn> </dt> <dd><a class="termdef" href="#def-Web-Content" title="definition: web content">Web content</a> that includes machine-readable internal structure (e.g. <a href="#def-Markup" title="definition: markup" class="termdef">markup</a> <a href="#def-Element" title="definition: element" class="termdef">elements</a>), as opposed to unstructured content, such as raster image formats or plain <a class="termdef" href="#def-Human-Language" title="definition: human language">human language</a> text. </dd> <dt><dfn><a name="def-Content-Generation" id="def-Content-Generation"></a>content generation (content authoring, content editing)</dfn></dt> <dd>The act of specifying the actual <a class="termdef" href="#def-Web-Content" title="definition: web content">web content</a> that will be rendered, played or executed by the <a class="termdef" href="#def-End-Users" title="definition: end user">end user's</a> <a href="#def-User-Agent" title="definition: user agent" class="termdef">user agent</a>. While the precise details of how content is created in any given system may vary widely, responsibility for the generation of content can be any combination of the following: <ul> <li><dfn><a name="def-Content-Author-Gen" id="def-Content-Author-Gen"></a>author generated content:</dfn> <a href="#def-Web-Content" title="definition: web content" class="termdef">Web content</a> for which <a class="termdef" href="#def-Author" title="definition: author">author</a>s are fully responsible. The author may only be responsible down to a particular level (e.g. when asked to type a text label, the author is responsible for the text, but not for how the label is marked up; when typing <a href="#def-Markup" title="definition: markup" class="termdef">markup</a> in a source <a href="#def-Editing-View" title="definition: editing views" class="termdef">editing-view</a>, the author is not responsible for the fact that UNICODE is used to encode the text ).</li> <li><dfn><a name="def-Content-Auto-Gen" id="def-Content-Auto-Gen"></a>automatically-generated content:</dfn> Web content for which <a href="#def-Developer" title="definition: authoring tool developer" class="termdef">developer</a>-programmed functionality is fully responsible (e.g. what markup to output when an author requests to start a new document, automatically correcting markup errors).</li> <li><dfn>third-party content generation:</dfn> Web content for which a third-party author is responsible (e.g. community shared <a href="#def-Template" title="definition: template" class="termdef">templates</a>).</li> </ul> </dd> <dt><a id="def-Content-Renderings" name="def-Content-Renderings"><dfn>content rendering</dfn></a></dt> <dd><a href="#def-Authoring-Tool-Interface" title="definition: authoring tool user interface" class="termdef">User interface</a> functionality that <a href="#def-Authoring-Tool" title="definition: authoring tool" class="termdef">authoring tools</a> present if they render, play or execute the <a class="termdef" href="#def-Content-Being-Edited" title="definition: web content being edited">web content being edited</a>. ATAG 2.0 recognizes several types of content renderings: <ul> <li><dfn><a name="def-WYSIWYG" id="def-WYSIWYG"></a>conventional renderings (or "WYSIWYG"):</dfn> When content is rendered in a way that is similar to the default rendering a <a href="#def-User-Agent" title="definition: user agent" class="termdef">user agent</a> would create from the same content. While "WYSIWYG", standing for "What-you-see-is-what-you-get" is the common term, differences between user agents and end user settings mean that in reality there is no single typical <a href="#def-End-Users" title="definition: end user" class="termdef">end user</a> experience; or </li> <li><dfn><a name="def-Unconventional-Renderings" id="def-Unconventional-Renderings"></a>unconventional renderings:</dfn> When content is rendered differently than it would be in a typical user agent (e.g. rendering an audio file as a graphical waveform); or </li> <li><a name="def-Partial-Rendering" id="def-Partial-Rendering"></a><dfn>partial renderings:</dfn> When some aspects of the content are rendered, played, or executed, but not others (e.g. a frame-by-frame <a href="#def-Video" title="definition: video" class="termdef">video</a> editor renders the graphical, but not the timing aspects, of a video).</li> </ul></dd> <dt><a id="def-Transformation" name="def-Transformation"><dfn>content transformations</dfn></a></dt> <dd>Processes that take <a href="#def-Web-Content" title="definition: web content" class="termdef">content</a> in one <a href="#def-Web-Content-Technology" title="definition: technology (Web content)" class="termdef">web content technology</a> or non-web content technology (e.g. a word processing format) as input and produce content that has been optimized, restructured or recoded: <ul> <li><a id="def-Optimizing-Transformation" name="def-Optimizing-Transformation"><dfn>Optimizing Content Transformations:</dfn></a> Transformations in which the content technology is not changed and the structural features of the content technology that are employed also stay the same. Changes would not be expected to result in information loss (e.g. removing whitespace, replacing in-line styles with an external style sheet).</li> <li><a id="def-Restructuring-Transformation" name="def-Restructuring-Transformation"><dfn>Restructuring Content Transformations:</dfn></a> Transformations in which the content technology stays the same, but the structural features of the technology used to markup the content are changed (e.g. linearizing tables, splitting a document into pages.</li> <li><a id="def-Recoding-Transformation" name="def-Recoding-Transformation"><dfn>Recoding Content Transformations:</dfn></a> Transformations in which the content technology used to encode the content is changed (e.g. HTML to XHTML, a word processing format to HTML).</li> </ul> <em>Note:</em> Clipboard operations, in which content is copied to or pasted from the platform clipboard, are not considered content transformations.</dd> <dt><a id="def-Control-Settings" name="def-Control-Settings"><dfn>control settings</dfn></a></dt> <dd>Settings that relate to how <a class="termdef" href="#def-Author" title="definition: author">authors</a> operate the <a href="#def-Authoring-Tool" title="definition: authoring tool" class="termdef">authoring tool</a>, for example using the keyboard or mouse.</dd> <dt><a id="def-Developer" name="def-Developer"><dfn>developer</dfn></a></dt> <dd>Any entities or individuals responsible for programming the <a href="#def-Authoring-Tool" title="definition: authoring tool" class="termdef">authoring tool</a>. This includes the programmers of any additional software components included by the Claimant in the <a href="#conf-claim">conformance claim</a>. In some cases, development of the authoring tool is complete before <a href="#def-Author" title="definition: authors" class="termdef">authors</a> can use it to <a href="#def-Publishing" title="definition: publishing" class="termdef">publish</a> <a class="termdef" href="#def-Web-Content" title="definition: web content">web content</a>. However, in other cases (e.g. some <a class="termdef" href="#def-Web-Based-UI" title="definition: Web-based authoring tool user interface">web-based authoring tools</a>), the developer may continue to modify the authoring tool even after content has been published, such that the content experienced by the <a href="#def-End-Users" title="definition: end user" class="termdef">end user</a> is modified. </dd> <dt><a id="def-Direct-Accessibility" name="def-Direct-Accessibility"><dfn>direct accessibility features</dfn></a> </dt> <dd>Features of an <a href="#def-Authoring-Tool" title="definition: authoring tool" class="termdef">authoring tool</a> that provide functionality to meet the requirements of <a href="#def-Author" title="definition: authors" class="termdef">authors</a> with disabilities (e.g. keyboard navigation, zoom features, text-to-speech). Additional or specialized functionality may still be provided by external <a href="#def-Assistive-Technology" title="definition: assistive technology" class="termdef">assistive technology</a>.</dd> <dt><a id="def-Display-Settings" name="def-Display-Settings"><dfn>display settings</dfn></a></dt> <dd>Settings that relate to how <a class="termdef" href="#def-Author" title="definition: author">authors</a> perceive the authoring tool. These include: <ul> <li><a id="def-Display-Settings-Audio" name="def-Display-Settings-Audio"><dfn>audio display settings:</dfn></a> the characteristics of <a href="#def-Audio" title="definition: audio" class="termdef">audio</a> output of music, sounds, and speech. Examples include volume, speech voices, voice speed, and voice emphasis.</li> <li><a id="def-Display-Settings-Visual" name="def-Display-Settings-Visual"><dfn>visual display settings:</dfn></a> the characteristics of the on-screen rendering of text and graphics. Examples include fonts, sizes, colors, spacing, positioning, and contrast.</li> <li><a id="def-Display-Settings-Tactile" name="def-Display-Settings-Tactile"><dfn>tactile display settings:</dfn></a> the characteristics of haptic output. Examples include the magnitude of the haptic forces and the types of vibration. </li> </ul> </dd> <dt><a id="def-Documentation" name="def-Documentation"></a><dfn>documentation</dfn></dt> <dd>Any information that supports the use of an <a href="#def-Authoring-Tool" title="definition: authoring tool" class="termdef">authoring tool</a>. This information may be provided electronically or otherwise and includes help, manuals, installation instructions, sample <a class="termdef" href="#def-Workflow" title="definition: workflow">work flows</a>, <a href="#def-Tutorial" title="definition: tutorial" class="termdef">tutorials</a>, etc.</dd> <dt><a id="def-Document-Object" name="def-Document-Object"></a><dfn>document object</dfn></dt> <dd>The internal representation of data in the <a class="termdef" title="definition: source content" href="#def-Instruction-Level">source</a> by a <a href="#def-Non-Web-Based" title="definition: authoring tool user interface (non-Web-Based)" class="termdef">non-web based authoring tool</a> or <a href="#def-User-Agent" title="definition: user agent" class="termdef">user agent</a>. The document object may form part of a <a href="#def-Accessibility-Platform-Service" title="definition: platform accessibility architecture" class="termdef">platform accessibility service </a> that enables communication with <a href="#def-Assistive-Technology" title="definition: assistive technology" class="termdef">assistive technologies</a>. <a href="#def-Web-Based-UI" title="definition: authoring tool user interface (Web-based)" class="termdef">Web-based authoring tools</a> are considered to make use of the document object that is maintained by the <a class="termdef" href="#def-User-Agent" title="definition: user agent">user agent</a>.</dd> <dt><a id="def-Element" name="def-Element"><dfn>element</dfn></a></dt> <dd>A pair of <a href="#def-Markup" title="definition: markup" class="termdef">markup</a> tags and its content, or an "empty tag" (one that requires no closing tag or content). </dd> <dt><a name="def-End-Users" id="def-End-Users"></a><dfn>end user</dfn></dt> <dd>A person who interacts with <a class="termdef" href="#def-Web-Content" title="definition: web content">web content</a> once it has been authored. This includes people using <a href="#def-Assistive-Technology" title="definition: assistive technology" class="termdef">assistive technologies</a>. </dd> <dt><a id="def-Human-Language" name="def-Human-Language"><dfn>human language</dfn></a> </dt> <dd>Language that is spoken, written or signed (through visual or tactile means) to communicate with humans.</dd> <dt><dfn><a name="def-Informative" id="def-Informative"></a>informative</dfn> </dt> <dd> For information purposes and not required for conformance.</dd> <dt><dfn><a name="def-Keyboard-Interface" id="def-Keyboard-Interface"></a>keyboard interface</dfn>  </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 operating system to support onscreen keyboards as well as external keyboards that may 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><dfn><a name="def-Keyboard-Trap" id="def-Keyboard-Trap"></a>keyboard trap</dfn></dt> <dd>A user interface situation in which a <a class="termdef" href="#def-Keyboard-Interface" title="definition: keyboard interface">keyboard interface</a> may be used to move focus to, but not from, a <a class="termdef" href="#def-UI-Component" title="definition: user interface component">user interface component</a> or group of components.</dd> <dt><dfn><a id="def-Label" name="def-Label"></a>label</dfn> </dt> <dd>Text or other <a class="termdef" href="#def-UI-Component" title="definition: user interface component">component</a> with a text alternative that is presented to users to identify a component. A label is presented to all users whereas the <a href="#def-Name" title="definition: name" class="termdef">name</a> may be hidden and only exposed by <a href="#def-Assistive-Technology" title="definition: assistive technology" class="termdef">assistive technology</a>. In many (but not all) cases the name and the label are the same.</dd> <dt><dfn><a id="def-Live" name="def-Live"></a>live</dfn> </dt> <dd>Information captured from a real-world event that is <a href="#def-Publishing" title="definition: publishing" class="termdef">published</a> with no more than a broadcast delay. <br /> <em> Note:</em> A broadcast delay is a short (usually automated) delay, for example used in order to give the broadcaster time to queue or censor the audio (or video) feed, but not sufficient to allow significant editing.</dd> <dt><dfn><a name="def-Markup-Language" id="def-Markup-Language"></a>markup language</dfn></dt> <dd>A system of text annotations (e.g. <a href="#def-Element" title="definition: element" class="termdef">elements</a> in HTML) and processing rules that may be used to specify the structure, presentation or semantics of <a class="termdef" href="#def-Web-Content" title="definition: web content">content</a>. Examples of markup languages include HTML and SVG. <ul><li><a name="def-Markup" id="def-Markup"></a><dfn>markup</dfn> of some content is the set of annotations that appear in the content.</li></ul></dd> <dt><a name="def-Name" id="def-Name"></a><dfn>name</dfn> </dt> <dd>Text by which software can identify a <a class="termdef" href="#def-UI-Component" title="definition: user interface component">user interface component</a> to the <a href="#def-Author" title="definition: authors" class="termdef">author</a> or <a href="#def-End-Users" title="definition: end user" class="termdef">end user</a>. The name may be hidden and only exposed by <a href="#def-Assistive-Technology" title="definition: assistive technology" class="termdef">assistive technology</a>, whereas a <a title="definition: label" class="termdef" href="#def-Label">label</a> is presented to all users. In many (but not all) cases, the label and the name are the same.</dd> <dt><dfn><a id="def-Non-Text-Objects" name="def-Non-Text-Objects"></a>non-text content</dfn> </dt> <dd>Any <a class="termdef" href="#def-Web-Content" title="definition: web content">content</a> that is not a sequence of characters that can be <a class="termdef" href="#def-Programmatically-Determined" title="definition: programmatically determined">programmatically determined</a> or where the sequence is not expressing something in <a title="definition: human language" class="termdef" href="#def-Human-Language">human language</a>. This includes ASCII Art (which is a pattern of characters), emoticons, and images representing text.</dd> <dt><dfn><a id="def-Normative" name="def-Normative"></a>normative</dfn> </dt> <dd>Required for conformance. One may conform in a variety of well-defined ways to ATAG 2.0. Content identified as "<a title="definition: informative" class="termdef" href="#def-Informative">informative</a>" or "non-normative" is never required for conformance.</dd> <dt><dfn><a id="def-Option" name="def-Option"></a>option</dfn></dt> <dd>When an <a href="#def-Author" title="definition: authors" class="termdef">author</a> is presented with choices. <ul> <li><dfn><a id="def-Default-Option" name="def-Default-Option"></a>default option:</dfn> A setting or value for an <a href="#def-Option" title="definition: option" class="termdef">option</a> that is assigned automatically by the <a href="#def-Authoring-Tool" title="definition: authoring tool" class="termdef">authoring tool</a> and remains in effect unless canceled or changed by the <a href="#def-Author" title="definition: authors" class="termdef">author</a>.</li> </ul></dd> <dt><dfn><a name="def-Platform" id="def-Platform"></a>platform</dfn></dt> <dd> The software environment within which the <a href="#def-Authoring-Tool" title="definition: authoring tool" class="termdef">authoring tool</a> operates. Platforms provide a consistent operational environment on top of lower level software platforms or hardware. For <a href="#def-Web-Based-UI" title="definition: authoring tool user interface (Web-based)" class="termdef">web-based authoring user interfaces</a>, the most relevant platform will be a <a href="#def-User-Agent" title="definition: user agent" class="termdef">user agent</a> (e.g. browser). For <a href="#def-Non-Web-Based" title="definition: authoring tool user interface (non-Web-Based)" class="termdef">non-web-based user interfaces</a>, the range of platforms includes, but may not be limited to, desktop operating systems (e.g. GNOME desktop on Linux, Mac OS, Windows), mobile operating systems (e.g. Android, BlackBerry, iOS, Windows Phone), or cross-OS environments (e.g. Java), etc.<br /> <em> Note 1:</em> Many platforms mediate communication between applications operating on the platform and assistive technology via a <a class="termdef" href="#def-Accessibility-Platform-Service" title="definition: accessibility platform architecture">platform accessibility service</a>. <br /> <em> Note 2:</em> Accessibility guidelines for <a href="#def-Developer" title="definition: authoring tool developer" class="termdef">developers</a> exist for many platforms.</dd> <dt><dfn><a id="def-Accessibility-Platform-Service" name="def-Accessibility-Platform-Service"></a>platform accessibility service</dfn></dt> <dd>A programmatic interface that is specifically engineered to provide communication between applications and <a href="#def-Assistive-Technology" title="definition: assistive technology" class="termdef">assistive technologies</a> (e.g. MSAA, IAccessible2 and UI Automation for Windows applications, AXAPI for Mac OS X applications, GNOME Accessibility Toolkit API for GNOME applications, Java Access for Java applications). On some <a href="#def-Platform" title="definition: platform" class="termdef">platforms</a>, it may be conventional to enhance communication further by implementing a <a href="#def-Document-Object" title="definition: document object" class="termdef">document object</a>.</dd> <dt><dfn><a name="def-Plugin" id="def-Plugin"></a>plug-in</dfn>  </dt> <dd>A program that runs as part of the <a href="#def-Authoring-Tool" title="definition: authoring tool" class="termdef">authoring tool</a> (e.g. a third-party checking and <a href="#def-Repairing" title="definition: repairing" class="termdef">repair</a> tool) and that is not part of <a class="termdef" href="#def-Content-Being-Edited" title="definition: web content being edited">web content being edited</a>. <a href="#def-Author" title="definition: authors" class="termdef">Authors</a> generally choose to include or exclude plug-ins from their authoring tool. </dd> <dt><a id="def-Preauthored-Content" name="def-Preauthored-Content"><dfn>pre-authored content</dfn></a></dt> <dd>Pieces of <a href="#def-Web-Content" title="definition: web content" class="termdef">web content</a>, created prior to an<a href="#def-Authoring-Session" title="definition: authoring session" class="termdef"> authoring session</a>, that the authoring tool <a href="#def-Developer" title="definition: authoring tool developer" class="termdef">developer</a> makes available to <a href="#def-Author" title="definition: authors" class="termdef">authors</a> to use in the <a class="termdef" href="#def-Content-Being-Edited" title="definition: web content being edited">content being edited</a>. Examples include clip art, sample videos, user interface widgets.<br /> <em>Note 1:</em> For <a href="#def-Template" title="definition: template" class="termdef">templates</a>, an incomplete form of pre-authored content, see <a href="#gl_b24">Guideline B.2.4</a>.<br /> <em>Note 2:</em> If the authoring tool uses pre-authored content automatically, see <a href="#gl_b11">Guideline B.1.1</a>. <ul> <li><dfn><a id="def-Accessible-Preauthored-Content" name="def-Accessible-Preauthored-Content"></a>accessible pre-authored content (WCAG):</dfn> <a href="#def-Preauthored-Content" title="definition: pre-authored content" class="termdef">Pre-authored content</a> that is either already <a class="termdef" href="#def-Accessible-Web-Content" title="definition: accessible Web content">accessible web content (WCAG)</a> or would be accessible, if it was appropriately inserted into an empty document. <br /> <em> Note:</em> If extensive <a href="#def-Author" title="definition: authors" class="termdef">author</a> input is required to make use of pre-authored content, then the content may in fact be a <a href="#def-Template" title="definition: template" class="termdef">template</a>.</li> </ul> </dd> <dt><a id="def-Preauthored-Content-Selection-Mechanism" name="def-Preauthored-Content-Selection-Mechanism"><dfn>pre-authored content selection mechanism</dfn></a></dt> <dd>A function beyond standard file selection that allows <a href="#def-Author" title="definition: authors" class="termdef">authors</a> to select <a href="#def-Preauthored-Content" title="definition: pre-authored content" class="termdef">pre-authored content</a> to use in an <a href="#def-Authoring-Session" title="definition: authoring session" class="termdef">authoring session</a> (e.g. clip art gallery, widget palette).</dd> <dt><dfn><a name="def-Presentation" id="def-Presentation"></a>presentation</dfn> </dt> <dd>Rendering of the <a href="#def-Web-Content" title="definition: web content" class="termdef">content</a> in a form to be perceived by <a class="termdef" href="#def-Author" title="definition: authors">authors</a> or <a href="#def-End-Users" title="definition: end user" class="termdef">end users</a>.</dd> <dt><dfn><a name="def-Programmatically-Determined" id="def-Programmatically-Determined"></a>programmatically determined (programmatically determinable)</dfn> </dt> <dd>Information that is encoded in a way that allows different software, including <a href="#def-Assistive-Technology" title="definition: assistive technology" class="termdef">assistive technologies</a>, to extract and present the information in different modalities. ATAG 2.0 uses this term in two contexts:<br /> <ul> <li>Processing content: Whether the <a href="#def-Authoring-Tool" title="definition: authoring tool" class="termdef">authoring tool</a> is able to extract information from the <a class="termdef" href="#def-Web-Content" title="definition: web content">web content</a> (e.g. to extract the language of content from the <a href="#def-Markup" title="definition: markup" class="termdef">markup</a>). </li> <li>Communication between the authoring tool and assistive technology: For <a href="#def-Non-Web-Based" title="definition: authoring tool user interface (non-Web-Based)" class="termdef">non-web-based user interfaces</a>, this means making use of <a class="termdef" href="#def-Accessibility-Platform-Service" title="definition: accessibility platform architecture">platform accessibility services</a>, APIs, and, in some cases, document object models. For <a class="termdef" href="#def-Web-Based-UI" title="definition: Web-based authoring tool user interface">web-based user interfaces</a>, this means ensuring that the <a href="#def-User-Agent" title="definition: user agent" class="termdef">user agent</a> can pass on the information (e.g. through the use of WAI-ARIA). <br/> </li> </ul> </dd> <dt><dfn><a id="def-Prominence" name="def-Prominence"></a>prominence</dfn></dt> <dd>A heuristic measure of how likely <a href="#def-Author" title="definition: authors" class="termdef">authors</a> are to notice a <a class="termdef" href="#def-UI-Component" title="definition: user interface component">user interface component</a> in a user interface that they are operating. Prominence is affected by numerous factors, including: the number of navigation steps required, the reading order position, visual properties (e.g. size, spacing, color), and even the modality of use (e.g. mouse vs. keyboard use). <ul> <li><dfn><a name="def-At-Least-As-Prominent" id="def-At-Least-As-Prominent"></a>at least as prominent:</dfn> For ATAG 2.0, a <a class="termdef" href="#def-UI-Component" title="definition: user interface component">user interface component</a> A is considered to be "at least as prominent" as another component B when, from a default state, component A becomes displayed (and enabled) with the same number or less "opening" actions than are required for component B to become displayed (and enabled).<br /> <em>Note 1:</em> When a container is open, all of the enabled components in the container (e.g. items in a list, items in a menu, buttons in a toolbar, all components in a dialog box) are considered to be displayed (and therefore are at least as prominent as each other), even if the container must be scrolled for them to become visible. This takes into account that different screen sizes and <a href="#def-Author" title="definition: authors" class="termdef">author</a> settings will affect which components are visible at a given time.<br /> <em> Note 2:</em> "Opening actions" are actions made by authors on components within the user interface that result in new components becoming displayed or enabled. For example: (a) keyboard shortcut to a top-level menu item to display a sub-menu, (b) keyboard selection on a button to display a dialog box, (c) mouse click on a checkbox to enable previously disabled sub-items, etc. Actions that do not cause new components to become actionable (e.g. moving focus, scrolling a list), are not counted as "opening actions".<br /> <em> Note 3:</em> Keyboard shortcuts to components in closed containers are not counted as "opening actions" because the components have no prominence when they are not displayed. The same is true when authors must use "search" to reveal components in closed containers.<br /> <em> Note 4:</em> The "default state" is the state of the <a href="#def-Authoring-Tool" title="definition: authoring tool" class="termdef">authoring tool</a> at the beginning of an authoring session as set by the developer. The default state of many document authoring tools is an <a href="#def-Editing-View" title="definition: editing views" class="termdef">editing-view</a>. </li> </ul> </dd> <dt><a id="def-Prompt" name="def-Prompt"><dfn>prompt</dfn></a></dt> <dd>Any <a href="#def-Authoring-Tool" title="definition: authoring tool" class="termdef">authoring tool</a> initiated request for a decision or piece of information from <a href="#def-Author" title="definition: authors" class="termdef">authors</a>. The term covers both requests that must be responded to immediately (e.g. modal dialog boxes) as well as less urgent requests (e.g. underlining a misspelled word).</dd> <dt><dfn><a name="def-Publishing" id="def-Publishing"></a>publishing</dfn></dt> <dd>Any point at which the <a href="#def-Author" title="definition: authors" class="termdef">authors</a> or <a href="#def-Authoring-Tool" title="definition: authoring tool" class="termdef">authoring tool</a> make <a href="#def-Web-Content" title="definition: web content" class="termdef"> web content</a> available to <a href="#def-End-Users" title="definition: end user" class="termdef">end users</a> (e.g. uploading a web page, committing a change in a wiki, live streaming). </dd> <dt><a name="def-Range" id="def-Range"></a><dfn>range</dfn></dt> <dd>More than one item within a multi-item set.<br/> <em>Informative Note:</em> ATAG 2.0 uses the term "range" where absolute measurements may not be practical (e.g. the set of all help <a href="#def-Documentation" title="definition: documentation" class="termdef">documentation</a> examples, the set of all <a href="#def-Template" title="definition: template" class="termdef">templates</a>). While the strict testable requirement is the definition "More than one item within a multi-item set", implementers are strongly encouraged to implement the success criteria more broadly.</dd> <dt><a name="def-Relationships" id="def-Relationships"></a><dfn>relationships</dfn> </dt> <dd>Meaningful associations between distinct pieces of <a href="#def-Web-Content" title="definition: web content" class="termdef"> content</a>.</dd> <dt><a id="def-Repairing" name="def-Repairing"></a><dfn>repair (accessibility) </dfn> </dt> <dd>The process by which <a class="termdef" href="#def-Web-Content-Accessibility-Problem" title="definition: web content accessibility problem">web content accessibility problems</a> that have been identified within <a class="termdef" href="#def-Web-Content" title="definition: web content"> web content</a> are resolved. ATAG 2.0 recognizes three types of repair, based on increasing levels of automation: <ul> <li><a name="def-Manual-Repairing" id="def-Manual-Repairing"></a><dfn>manual repair:</dfn> Where the repairs are carried out by <a href="#def-Author" title="definition: authors" class="termdef">authors</a>. This includes the case where authors are aided by instructions or guidance provided by the <a href="#def-Authoring-Tool" title="definition: authoring tool" class="termdef">authoring tool</a>, but where authors carry out the actual repair procedure; </li> <li><a name="def-Semi-Automated-Repairing" id="def-Semi-Automated-Repairing"></a><dfn>semi-automated repair:</dfn> Where the repairs are partially carried out by the authoring tool, but where authors' input or judgment is still required to complete the repair; and</li> <li><a name="def-Automated-Repairing" id="def-Automated-Repairing"></a><dfn>automated repair:</dfn> Where the repairs are carried out automatically by the authoring tool without any intervention by authors.</li> </ul> </dd> <dt><a name="def-Restrictions" id="def-Restrictions"></a><dfn>restrictions, restricted web content authoring</dfn></dt> <dd>When the <a href="#def-Web-Content" title="definition: web content" class="termdef">web content</a> that <a href="#def-Author" title="definition: authors" class="termdef">authors</a> can specify with an<a href="#def-Authoring-Tool" title="definition: authoring tool" class="termdef"> authoring tool</a> either must include or must not include certain content (e.g. elements, attributes, widgets). Many authoring tools restrict authoring in some way, which can either benefit accessibility (e.g. if text alternatives for non-text content are required) or detract from accessibility (e.g. if attributes for defining text alternatives are not available). In contrast, authoring tools that allow unrestricted web content authoring do not require any particular content to be included or not included (e.g. many <a href="#def-Instruction-Level" title="definition: View - Source view" class="termdef">source editing-views</a>).</dd> <dt><a name="def-Role" id="def-Role"></a><dfn>role</dfn> </dt> <dd>Text or a number by which software can identify the function of a component within <a href="#def-Web-Content" title="definition: web content" class="termdef">web content</a> (e.g. a string that indicates whether an image functions as a hyperlink, command button, or check box).</dd> <dt><dfn><a name="def-Sequential-Keyboard-Access" id="def-Sequential-Keyboard-Access"></a>sequential keyboard access </dfn>  </dt> <dd>Using a <a class="termdef" href="#def-Keyboard-Interface" title="definition: keyboard interface">keyboard interface</a> to navigate the focus one-by-one through all of the items in an ordered set (e.g. menu items, form fields) until the desired item is reached and activated. This is in contrast to direct keyboard access methods such as keyboard shortcuts and the use of bypass links.</dd> <dt><a id="def-Web-Content-Technology" name="def-Web-Content-Technology"><dfn>technology (web content)</dfn></a> </dt> <dd>A mechanism for encoding instructions to be rendered, played or executed by <a href="#def-User-Agent" title="definition: user agent" class="termdef">user agents</a>. Web content technologies may include <a href="#def-Markup-Language" title="definition: markup language" class="termdef">markup languages</a>, data formats, or programming languages that <a href="#def-Author" title="definition: authors" class="termdef">authors</a> may use alone or in combination to create <a class="termdef" href="#def-End-Users" title="definition: end user">end user</a> 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, Silverlight, Flex, and JavaScript.</dd> <dt><a id="def-Template" name="def-Template"><dfn>template</dfn></a></dt> <dd>Content patterns that are filled in by <a href="#def-Author" title="definition: authors" class="termdef">authors</a> or the <a href="#def-Authoring-Tool" title="definition: authoring tool" class="termdef">authoring tool</a> to produce <a href="#def-Web-Content" title="definition: web content" class="termdef">web content</a> for <a href="#def-End-Users" title="definition: end user" class="termdef">end users</a> (e.g. document templates, content management templates, presentation themes). Often templates will pre-specify at least some authoring decisions. <ul> <li><dfn><a id="def-Accessible-Template" name="def-Accessible-Template"></a>accessible templates (WCAG):</dfn> Templates that can be filled in to create web content that meets the <a href="#conf-rel-wcag">WCAG 2.0</a> success criteria (Level A, AA or AAA), when both of the following are true: <ol type="a"> <li>The author correctly follows any instructions provided (e.g. correctly responding to <a href="#def-Prompt" title="definition: prompt" class="termdef">prompts</a>, correctly replacing highlighted placeholders); and </li> <li>No further authoring occurs </li> </ol> <em>Note:</em> Under these conditions, some templates will result in completely empty documents, which are considered accessible by default.</li> </ul> </dd> <dt><a id="def-Template-Selection-Mechanism" name="def-Template-Selection-Mechanism"><dfn>template selection mechanism</dfn></a></dt> <dd>A function beyond standard file selection that allows <a href="#def-Author" title="definition: authors" class="termdef">authors</a> to select <a href="#def-Template" title="definition: template" class="termdef">templates</a> to use as the basis for new <a href="#def-Web-Content" title="definition: web content" class="termdef">content</a> or to apply to existing content.</dd> <dt><a name="def-Time-Limit" id="def-Time-Limit"></a><dfn>time limit</dfn></dt> <dd>The amount of time that an <a href="#def-Authoring-Tool" title="definition: authoring tool" class="termdef">authoring tool</a> provides to <a href="#def-Author" title="definition: authors" class="termdef">authors</a> to perform a task (e.g. read a message, select an item, save a change). Examples include: authoring session timeouts, time-based presentations (e.g. tutorial video).</dd> <dt><a name="def-Tutorial" id="def-Tutorial"></a><dfn>tutorial</dfn></dt> <dd>A type of <a href="#def-Documentation" title="definition: documentation" class="termdef">documentation</a> that provides step-by-step instructions for performing multi-part tasks. </dd> <dt><a id="def-User-Agent" name="def-User-Agent"><dfn>user agent</dfn></a> </dt> <dd>Any software that retrieves, renders and facilitates <a href="#def-End-Users" title="definition: end user" class="termdef">end user</a> interaction with <a href="#def-Web-Content" title="definition: web content" class="termdef">web content</a> (e.g. web browsers, browser plug-ins, media players) <ul> <li><a id="def-Inmarket-User-Agent" name="def-Inmarket-User-Agent"></a><dfn>In-Market User Agent:</dfn> A user agent that can be procured by members of the public (free or otherwise). Usually, an in-market user agent will be a separate software from the <a href="#def-Authoring-Tool" title="definition: authoring tool" class="termdef">authoring tool</a>; however, sometimes a software may combine user agent and authoring tool functionality. These cases include: <ul> <li><dfn>Preview-Only:</dfn> If the user agent can only render web content that it receives from the associated authoring functionality, then the software is an authoring tool with a <a class="termdef" href="#def-Preview" title="definition: preview">preview</a> feature. Such preview-only features are <em>not considered in-market user agents</em>.</li> <li><a id="def-ua-with-authoring-tool-role" name="def-ua-with-authoring-tool-role"></a><dfn>User Agent with Authoring Tool Mode:</dfn> If the user agent functionality must retrieve and open web content before it can be sent to the authoring tool functionality, then the software is a user agent with an authoring tool mode. If the user agent is used to preview content produced by the authoring tool mode, then it is to be considered an in-market user agent.</li> <li><a id="def-comb-ua-authoring-tool" name="def-comb-ua-authoring-tool"></a><dfn>Combined User Agent/Authoring Tool:</dfn> A user agent in which the default mode of user interaction enables editing the web content. These tools do not need previews because the author is already experiencing the content in the same way as end users. </li> </ul> </li> </ul> </dd> <dt><a id="def-UI-Component" name="def-UI-Component"><dfn>user interface component</dfn></a> </dt> <dd>A part of the <a href="#def-Authoring-Tool-Interface" title="definition: authoring tool user interface" class="termdef">user interface</a> or content display (including <a href="#def-Content-Renderings" title="definition: content rendering" class="termdef">content renderings</a>) that is perceived by <a href="#def-Author" title="definition: authors" class="termdef">authors</a> as a single control for a distinct function. </dd> <dt><a name="def-Video" id="def-Video"><dfn>video</dfn></a> </dt> <dd>The technology of moving pictures or images. Video can be made up of animated or photographic images, or both.</dd> <dt><a id="def-View" name="def-View"><dfn>view</dfn></a></dt> <dd>A user interface function that <a href="#def-Author" title="definition: authors" class="termdef">authors</a> use to interact with the <a class="termdef" href="#def-Content-Being-Edited" title="definition: web content being edited">web content being edited</a>. ATAG 2.0 categorizes views according to whether they support editing: <ul> <li><a name="def-Editing-View" id="def-Editing-View"></a><dfn>editing-views:</dfn> Views in which some or all of the content is editable; or </li> <li><a name="def-Preview" id="def-Preview"></a><dfn>previews:</dfn> Views in which no <a href="#def-Authoring-Action" title="definition: authoring actions" class="termdef">authoring actions</a> are provided (i.e. the view is not editable). Previews are provided to present the web content being edited by the <a href="#def-Authoring-Tool" title="definition: authoring tool" class="termdef">authoring tool</a> as it would appear to <a href="#def-End-Users" title="definition: end user" class="termdef">end users</a> of <a class="termdef" href="#def-User-Agent" title="definition: user agent">user agents</a>. Previews may be implemented using actual <a class="termdef" href="#def-Inmarket-User-Agent" title="definition: in-market user agent">in-market user agents</a>, but this is not necessary.</li> </ul> ATAG 2.0 also recognizes several approaches to presenting the content in a view: <ul> <li><a name="def-Instruction-Level" id="def-Instruction-Level"></a><dfn>source views</dfn><dfn>:</dfn> The content is presented in unrendered form (e.g. plain text editors); or </li> <li><a name="def-Rendered-View" id="def-Rendered-View"></a><dfn>rendered views:</dfn> <a href="#def-Content-Renderings" title="definition: content rendering" class="termdef">Content renderings</a> (conventional, unconventional or partial) are presented; or </li> <li><a name="def-Meta-Content" id="def-Meta-Content"></a><dfn>property views: </dfn>Only properties of the content are presented. The authoring tool then uses these properties to <a href="#def-Content-Auto-Gen" title="definition: content generation" class="termdef">automatically generate</a> the content to be <a href="#def-Publishing" title="definition: publishing" class="termdef">published</a> (e.g. CMS calendar widget that generates a calendar from the numeric month and year).</li> </ul> </dd> <dt><a id="def-Workflow" name="def-Workflow"></a><dfn>workflow</dfn></dt> <dd>A customary sequence of steps or tasks that <a href="#def-Author" title="definition: authors" class="termdef">authors</a> follow to produce a <a href="#def-Web-Content" title="definition: web content" class="termdef">content</a> deliverable. If an <a href="#def-Authoring-Tool" title="definition: authoring tool" class="termdef">authoring tool</a> is composed of a collection of applications (e.g. <a href="#def-Markup" title="definition: markup" class="termdef">markup</a> editor, image editor, and validation tool), then its workflows may include use of one or more of the applications. </dd> </dl> <hr /> </div>  <div id="sect-references"> <h2><a id="references" name="references"></a>Appendix <span class="gl-only">B</span>: References</h2> <p>For the <strong>latest version</strong> of any <acronym title="the World Wide Web Consortium">W3C</acronym> standards please consult the list of <a href="https://www.w3.org/TR/">W3C Technical Reports</a> at http://www.w3.org/TR/. Some documents listed below may have been superseded since the publication of this document.</p> <p>This section is <a href="#def-Normative" title="definition: normative" class="termdef">normative</a></p> <dl> <dt><a name="ref-UAAG10" id="ref-UAAG10">[UAAG10]</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, and E. Hansen, eds.17 December 2002.</dd> <dt><a name="ref-WCAG20" id="ref-WCAG20"></a>[WCAG20]</dt> <dd>"<a href="https://www.w3.org/TR/2008/REC-WCAG20-20081211/">Web Content Accessibility Guidelines 2.0 </a>", B. Caldwell, M. Cooper, L. Guarino Reid, and G. Vanderheiden, eds. 11 December 2008.</dd> </dl> <p>This section is <a href="#def-Informative" title="definition: informative" class="termdef">informative</a>.</p> <dl><dt><a name="ref-ATAG10" id="ref-ATAG10">[ATAG10]</a></dt> <dd>"<a href="https://www.w3.org/TR/2000/REC-ATAG10-20000203/">Authoring Tool Accessibility Guidelines 1.0</a>", J. Treviranus, C. McCathieNevile, I. Jacobs, and J. Richards, eds., 3 February 2000.</dd> </dl> </div>  <hr /> <div id="sect-acknowledgments"> <h2><a id="acknowledgments" name="acknowledgments"></a>Appendix <span class="gl-only">C</span>: Acknowledgments</h2> <h3><a name="active-participants" id="active-participants"></a>Participants active in the AUWG at the time of publication:</h3> <ul> <li>Tom Babinszki (IBM)</li> <li>Tim Boland (National Institute for Standards and Technology)</li> <li>Alastair Campbell (Nomensa) </li> <li>Alessandro Miele (Invited Expert) </li> <li>Jan Richards (Inclusive Design Institute, OCAD University)</li> <li>Jeanne Spellman (W3C) </li> <li>Jutta Treviranus (WG Chair; Inclusive Design Institute, OCAD University)</li> </ul> <h3 id="atag-testers">ATAG Candidate Recommendation Testing Volunteers</h3> <ul> <li>Victoria Clark</li> <li>Maria Carmen C. Cruz</li> <li>Emanuela Gorla</li> <li>Michael Gower</li> <li>Anne Jackson</li> <li>Taliesin Love Smith</li> </ul> <h3><a name="previous-participants" id="previous-participants"></a>Other previously active AUWG participants and other contributors to ATAG 2.0:</h3> <dl> <dt>Previous Editors:</dt> <dd>Tim Boland, NIST</dd> <dd>Matt May (until June 2005 while at <acronym title="World Wide Web Consortium">W3C</acronym>)</dd> </dl> <p>Kynn Bartlett, Giorgio Brajnik, Judy Brewer, Wendy Chisholm, Daniel Dardailler, Geoff Deering, Cherie Ekholm, Barry A. Feigenbaum, Katie Haritos-Shea, Kip Harris, Phill Jenkins, Len Kasday, Marjolein Katsma, Alex Li, William Loughborough, Karen Mardahl, Matt May, Charles McCathieNevile, Ann McMeekin, Matthias Müller-Prove, Liddy Nevile, Sueann Nichols, Graham Oliver, Greg Pisocky, Wendy Porch, Sarah Pulis, Bob Regan, Chris Ridpath, Andrew Ronksley, Gregory Rosmaita, Roberto Scano, Dana Simberkoff, Reed Shaffner, Michael Squillace, Heather Swayne, Gregg Vanderheiden, Carlos Velasco, and Jason White.</p> <p>This document would not have been possible without the work of <a href="https://www.w3.org/TR/ATAG10/#acknowledgments">those who contributed to ATAG 1.0</a>.</p> <p>This publication has been funded in part with Federal funds from the U.S. Department of Education, National Institute on Disability and Rehabilitation Research (NIDRR) under contract number ED-OSE-10-C-0067. The content of this publication does not necessarily reflect the views or policies of the U.S. Department of Education, nor does mention of trade names, commercial products, or organizations imply endorsement by the U.S. Government. </p> <hr /> </div>  <div class="gl-only"> <p align="center"> [<a href="#contents">Contents</a>] </p> </div>  <script src="https://www.w3.org/scripts/TR/fixup.js"></script></body> </html>