discontinued / server · Files

index.html 225 KB
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 944 945 946 947 948 949 950 951 952 953 954 955 956 957 958 959 960 961 962 963 964 965 966 967 968 969 970 971 972 973 974 975 976 977 978 979 980 981 982 983 984 985 986 987 988 989 990 991 992 993 994 995 996 997 998 999 1000 1001 1002 1003 1004 1005 1006 1007 1008 1009 1010 1011 1012 1013 1014 1015 1016 1017 1018 1019 1020 1021 1022 1023 1024 1025 1026 1027 1028 1029 1030 1031 1032 1033 1034 1035 1036 1037 1038 1039 1040 1041 1042 1043 1044 1045 1046 1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 1057 1058 1059 1060 1061 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 1084 1085 1086 1087 1088 1089 1090 1091 1092 1093 1094 1095 1096 1097 1098 1099 1100 1101 1102 1103 1104 1105 1106 1107 1108 1109 1110 1111 1112 1113 1114 1115 1116 1117 1118 1119 1120 1121 1122 1123 1124 1125 1126 1127 1128 1129 1130 1131 1132 1133 1134 1135 1136 1137 1138 1139 1140 1141 1142 1143 1144 1145 1146 1147 1148 1149 1150 1151 1152 1153 1154 1155 1156 1157 1158 1159 1160 1161 1162 1163 1164 1165 1166 1167 1168 1169 1170 1171 1172 1173 1174 1175 1176 1177 1178 1179 1180 1181 1182 1183 1184 1185 1186 1187 1188 1189 1190 1191 1192 1193 1194 1195 1196 1197 1198 1199 1200 1201 1202 1203 1204 1205 1206 1207 1208 1209 1210 1211 1212 1213 1214 1215 1216 1217 1218 1219 1220 1221 1222 1223 1224 1225 1226 1227 1228 1229 1230 1231 1232 1233 1234 1235 1236 1237 1238 1239 1240 1241 1242 1243 1244 1245 1246 1247 1248 1249 1250 1251 1252 1253 1254 1255 1256 1257 1258 1259 1260 1261 1262 1263 1264 1265 1266 1267 1268 1269 1270 1271 1272 1273 1274 1275 1276 1277 1278 1279 1280 1281 1282 1283 1284 1285 1286 1287 1288 1289 1290 1291 1292 1293 1294 1295 1296 1297 1298 1299 1300 1301 1302 1303 1304 1305 1306 1307 1308 1309 1310 1311 1312 1313 1314 1315 1316 1317 1318 1319 1320 1321 1322 1323 1324 1325 1326 1327 1328 1329 1330 1331 1332 1333 1334 1335 1336 1337 1338 1339 1340 1341 1342 1343 1344 1345 1346 1347 1348 1349 1350 1351 1352 1353 1354 1355 1356 1357 1358 1359 1360 1361 1362 1363 1364 1365 1366 1367 1368 1369 1370 1371 1372 1373 1374 1375 1376 1377 1378 1379 1380 1381 1382 1383 1384 1385 1386 1387 1388 1389 1390 1391 1392 1393 1394 1395 1396 1397 1398 1399 1400 1401 1402 1403 1404 1405 1406 1407 1408 1409 1410 1411 1412 1413 1414 1415 1416 1417 1418 1419 1420 1421 1422 1423 1424 1425 1426 1427 1428 1429 1430 1431 1432 1433 1434 1435 1436 1437 1438 1439 1440 1441 1442 1443 1444 1445 1446 1447 1448 1449 1450 1451 1452 1453 1454 1455 1456 1457 1458 1459 1460 1461 1462 1463 1464 1465 1466 1467 1468 1469 1470 1471 1472 1473 1474 1475 1476 1477 1478 1479 1480 1481 1482 1483 1484 1485 1486 1487 1488 1489 1490 1491 1492 1493 1494 1495 1496 1497 1498 1499 1500 1501 1502 1503 1504 1505 1506 1507 1508 1509 1510 1511 1512 1513 1514 1515 1516 1517 1518 1519 1520 1521 1522 1523 1524 1525 1526 1527 1528 1529 1530 1531 1532 1533 1534 1535 1536 1537 1538 1539 1540 1541 1542 1543 1544 1545 1546 1547 1548 1549 1550 1551 1552 1553 1554 1555 1556 1557 1558 1559 1560 1561 1562 1563 1564 1565 1566 1567 1568 1569 1570 1571 1572 1573 1574 1575 1576 1577 1578 1579 1580 1581 1582 1583 1584 1585 1586 1587 1588 1589 1590 1591 1592 1593 1594 1595 1596 1597 1598 1599 1600 1601 1602 1603 1604 1605 1606 1607 1608 1609 1610 1611 1612 1613 1614 1615 1616 1617 1618 1619 1620 1621 1622 1623 1624 1625 1626 1627 1628 1629 1630 1631 1632 1633 1634 1635 1636 1637 1638 1639 1640 1641 1642 1643 1644 1645 1646 1647 1648 1649 1650 1651 1652 1653 1654 1655 1656 1657 1658 1659 1660 1661 1662 1663 1664 1665 1666 1667 1668 1669 1670 1671 1672 1673 1674 1675 1676 1677 1678 1679 1680 1681 1682 1683 1684 1685 1686 1687 1688 1689 1690 1691 1692 1693 1694 1695 1696 1697 1698 1699 1700 1701 1702 1703 1704 1705 1706 1707 1708 1709 1710 1711 1712 1713 1714 1715 1716 1717 1718 1719 1720 1721 1722 1723 1724 1725 1726 1727 1728 1729 1730 1731 1732 1733 1734 1735 1736 1737 1738 1739 1740 1741 1742 1743 1744 1745 1746 1747 1748 1749 1750 1751 1752 1753 1754 1755 1756 1757 1758 1759 1760 1761 1762 1763 1764 1765 1766 1767 1768 1769 1770 1771 1772 1773 1774 1775 1776 1777 1778 1779 1780 1781 1782 1783 1784 1785 1786 1787 1788 1789 1790 1791 1792 1793 1794 1795 1796 1797 1798 1799 1800 1801 1802 1803 1804 1805 1806 1807 1808 1809 1810 1811 1812 1813 1814 1815 1816 1817 1818 1819 1820 1821 1822 1823 1824 1825 1826 1827 1828 1829 1830 1831 1832 1833 1834 1835 1836 1837 1838 1839 1840 1841 1842 1843 1844 1845 1846 1847 1848 1849 1850 1851 1852 1853 1854 1855 1856 1857 1858 1859 1860 1861 1862 1863 1864 1865 1866 1867 1868 1869 1870 1871 1872 1873 1874 1875 1876 1877 1878 1879 1880 1881 1882 1883 1884 1885 1886 1887 1888 1889 1890 1891 1892 1893 1894 1895 1896 1897 1898 1899 1900 1901 1902 1903 1904 1905 1906 1907 1908 1909 1910 1911 1912 1913 1914 1915 1916 1917 1918 1919 1920 1921 1922 1923 1924 1925 1926 1927 1928 1929 1930 1931 1932 1933 1934 1935 1936 1937 1938 1939 1940 1941 1942 1943 1944 1945 1946 1947 1948 1949 1950 1951 1952 1953 1954 1955 1956 1957 1958 1959 1960 1961 1962 1963 1964 1965 1966 1967 1968 1969 1970 1971 1972 1973 1974 1975 1976 1977 1978 1979 1980 1981 1982 1983 1984 1985 1986 1987 1988 1989 1990 1991 1992 1993 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 2026 2027 2028 2029 2030 2031 2032 2033 2034 2035 2036 2037 2038 2039 2040 2041 2042 2043 2044 2045 2046 2047 2048 2049 2050 2051 2052 2053 2054 2055 2056 2057 2058 2059 2060 2061 2062 2063 2064 2065 2066 2067 2068 2069 2070 2071 2072 2073 2074 2075 2076 2077 2078 2079 2080 2081 2082 2083 2084 2085 2086 2087 2088 2089 2090 2091 2092 2093 2094 2095 2096 2097 2098 2099 2100 2101 2102 2103 2104 2105 2106 2107 2108 2109 2110 2111 2112 2113 2114 2115 2116 2117 2118 
<!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"> 

/*REMOVE FOR FINAL LAST CALL */
.editornotes {border: red 1px solid}
.new-text {background-color:#FFFF99}
.change-text {background-color:#99FFFF}
.delete-text {
	color: white;
	background-color: black;
	text-decoration:line-through;
}

/* GL vs, TECH Styles */
/* (1) Showing guidelines and Techniques/Understanding together */
/* .techs-only {color:#00CC00}                   */
/* .gl-only{color:gray}                          */
/* END (1)                                        */
 
/* (2) Show guidelines doc only                   */
/* .techs-only{display:none}                      
/* END (2)                                        */

/* (3) Show Techniques/Understanding doc only     */
/*.gl-only{display:none}                          */
/* END (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;
	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; 	
}
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:italic;
}
.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> 
<!--START REMOVE FOR PUBLIC DRAFT--> 
<link href="http://www.w3.org/StyleSheets/TR/W3C-ED.css" type="text/css" rel="stylesheet" />
<!--START REMOVE FOR PUBLIC DRAFT--> 
 
<!--START COMMENT-OUT FOR EDITOR DRAFT--> 
<link href="http://www.w3.org/StyleSheets/TR/W3C-WD.css" type="text/css" rel="stylesheet" />
<!--END COMMENT-OUT FOR EDITOR DRAFT-->
</head> 
<body> 
<div class="head"> 

<div class="gl-only"> 
<p align="center">[<a href="#contents">Contents</a>] [<a href="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/">Implementing</a>]
</p> 
<a href="http://www.w3.org/"><img height="48" src="http://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 Working Draft 21 July 2011</h2> 
  <dl> 
    <dt>This version:</dt> 
    <dd><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/">http://www.w3.org/TR/2011/WD-ATAG20-20110721/</a></dd> 
    <dt>Latest version:</dt> 
    <dd><a href="http://www.w3.org/TR/ATAG20/">http://www.w3.org/TR/ATAG20/</a></dd> 
    <dt>Previous version:</dt> 
    <dd><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110426/">http://www.w3.org/TR/2011/WD-ATAG20-20110426/</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> 
    <dt>Previous Editors:</dt> 
    <dd>Matt May (until June 2005 while at <acronym title="World Wide Web Consortium">W3C</acronym>)</dd> 
  </dl> 
  <p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> &copy; 2011 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>&reg;</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>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p> 

</div> <!-- gl-only -->
 <!-- techs-only -->

</div> <!-- head -->
 
<hr /> 

<div id="sect-abstract"> 
  <h2><a id="abstract" name="abstract">Abstract</a></h2> 
<div class="gl-only"> 
  <p>This specification provides guidelines for designing web content authoring
    tools that are both (1) more accessible to authors with disabilities and (2) designed to enable,
    support, and promote the production of accessible web content by all authors.</p> 
</div> <!-- gl-only -->
 <!-- techs-only -->
  <p>The &quot;Authoring Tool Accessibility Guidelines 2.0&quot; (<acronym title="Authoring Tool Accessibility Guidelines">ATAG</acronym> 2.0)
    is part of a series of accessibility guidelines published by the 
	<acronym title="the World Wide Web Consortium">W3C</acronym> <a href="http://www.w3.org/WAI/" title="Link to W3C-WAI">Web
    Accessibility Initiative</a> (<acronym title="the Web Access Initiative">WAI</acronym>).</p> 

</div> <!-- sect-abstract -->
 
<div id="sect-status"> 
  <h2><a id="status" name="status">Status of This Document</a></h2> 
   <h3><a name="status-superseded" id="status-superseded"></a>May be Superseded</h3> 
  <p><em>This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the <a href="http://www.w3.org/TR/">W3C technical reports index</a>  at http://www.w3.org/TR/.</em></p> 
 
<div class="gl-only">
<!--START COMMENT-OUT FOR EDITOR'S DRAFT--> 
<h3><a name="status-status" id="status-status"></a>W3C Public Working Draft of ATAG 2.0</h3>
<p>This is the W3C Working Draft of 21 July 2011. This draft                integrates changes made as a result of comments received on the 8   July 2010                Last Call  Working Draft. The Authoring Tool Accessibility   Guidelines Working Group (AUWG) has refined ATAG 2.0 with the   contributions of public commenters. Changes in this draft: </p>
  <ol>
    <li><strong>Conformance</strong> - added a <a href="#part_a_applic_note_4">conformance note</a> to clarify that authoring tools may rely on user agent features, and added an explanation to the <a href="#part_a_applic_note_5">exemption to part A</a> for preview features. </li>
    <li><strong>WCAG levels</strong> - success criteria that were identical except for the WCAG level (A, AA, AAA) were merged into one success criterion. </li>
    <li><strong>Document semantics</strong> - changed the underlying semantic structure of the document so that the success criteria short names are coded as headings.</li>
    <li><strong>Autosave</strong> - clarified <a href="#sc_a321">A.3.2.1 Autosave</a> to be specific about web content edits, being set for automatically saving, and only saving edits made by the authoring tool before the session time limits are reached. </li>
    <li><strong>Text search</strong> - simplified the examples of <a href="#sc_a351">A.3.5.1 Text search</a> (a) Editable text, and added a condition (b) Match, which directs the user agent to give focus to the matched text. </li>
    <li><strong>Preference settings</strong> - adjusted all the success criteria in guideline <a href="#gl_a36">A.3.6 Manage preference settings</a> so that each success criterion only applies if the authoring tool has the relevant setting.</li>
    <li><strong>Accessible templates</strong> - adjusted <a href="#sc_b242">B.2.4.2 Identify template</a> and <a href="#sc_b243">B.2.4.3 Author created templates</a> so that the template selection mechanism   displays distinctions between the accessible and  non-accessible templates.</li>
    <li><strong>Results from Accessibility checkers</strong> - provided greater flexibility to <a href="#sc_b315">B.3.1.5 Programmatic association to results</a> by requiring a programmatic association rather than metadata describing the results. </li>
      <li><strong>Definitions</strong> - added a definition of <a href="#def-Range">range</a>, and clarified the definitions of <a href="#def-Sequential-Keyboard-Access">sequential keyboard access</a> and <a href="#def-Accessible-Template">accessible template</a>. </li>
  </ol>
<p>The main purpose of this draft is for commenters to check if their comments have been addressed. We welcome comments on additional issues. </p>

  <p>Comments on this working draft are <strong>due on or before 15 September 2011</strong>. Comments on the draft should be sent to <a href="mailto:public-atag2-comments@w3.org">public-atag2-comments@w3.org</a> (<a href="http://lists.w3.org/Archives/Public/public-atag2-comments/">Public                Archive</a>). </p>
  <p>The <a href="http://www.w3.org/WAI/AU/"> Authoring Tool Accessibility Guidelines Working Group (AUWG)</a> intends to publish ATAG 2.0 as a W3C Recommendation. Until that time <a href="http://www.w3.org/TR/ATAG10/">Authoring Tool Accessibility Guidelines (ATAG) 1.0</a> <a href="http://www.w3.org/TR/2011/WD-ATAG20-20110426/#ref-ATAG10" title="reference: ATAG20"><cite>[ATAG10]</cite></a> is the stable, referenceable version. This Working Draft does not supersede ATAG 1.0.</p>
</div> 
<!-- gl-only -->

 <!-- techs-only -->
 

  <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="http://www.w3.org/WAI/">Web
    Accessibility Initiative</a> (WAI). The goals of the AUWG are discussed
    in the <a href="http://www.w3.org/WAI/AU/charter4.html">Working Group charter</a>.
    The AUWG is part of the <a href="http://www.w3.org/WAI/Technical/Activity">WAI
    Technical Activity</a>.</p> 
  <h3><a name="status-no-endorsement" id="status-no-endorsement"></a>No Endorsement</h3> 

<p>Publication as a Working Draft does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.</p>
  <h3><a name="status-patents" id="status-patents"></a>Patents</h3> 
  <p> This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 W3C Patent Policy</a>.  W3C maintains a <a rel="disclosure" href="http://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="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a> must disclose the information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section 6 of the W3C Patent Policy</a>. </p>

</div> <!-- sect-status -->
<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">Understanding 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 must 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 must be 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) Editing-view presentation can be programmatically determined</a></li>
              </ul>
            </li> 
            <li><a href="#principle_a3">A.3. Editing-views must be 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 as accessible as existing user agents</a></li>
              </ul>
            </li> 
            <li><a href="#principle_a4">A.4. Editing-views must be 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 must produce accessible content </a>
              <ul>
                <li><a href="#gl_b11">B.1.1. Ensure automatically specified content is accessible</a></li>

                <li><a href="#gl_b12">B.1.2. Ensure accessibility information is preserved</a></li>
              </ul>
            </li> 
            <li><a href="#principle_b2">B.2. Authors must be supported in producing accessible content</a> 
              <ul>
                <li><a href="#gl_b21">B.2.1. Ensure 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 must be 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 must promoted 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">Conformance</a> 
      <ul class="toc">
        <li><a href="#conf-rel-wcag">Relationship to the Web Content Accessibility Guidelines (WCAG) 2.0</a></li>
        <li><a href="#conf-req">Conformance Requirements </a><a href="#conf-levels"></a> </li>

        <li><a href="#conf-claim">Conformance Claims</a></li>
        <li><a href="#conf-prog-statement">&quot;Progress Toward Conformance&quot; Statement</a></li> 
        <li><a href="#conf-disclaimer">Disclaimer</a></li> 
      </ul> 
    </li> 
    <li><a href="#glossary">Appendix A: Glossary</a></li> 
    <li><a href="#this-doc-ref">Appendix B: How to refer to ATAG 2.0 from other documents</a> </li> 
    <li><a href="#references">Appendix C: References</a></li> 
    <li><a href="#acknowledgments">Appendix D: Acknowledgments</a></li> 
  </ul> 

</div> <!-- gl-only -->
 <!-- techs-only -->
</div> <!-- toc -->
<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 a Working Draft 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 blindness and low vision, deafness and hearing loss, learning disabilities, cognitive limitations, motor difficulties, speech difficulties, and others. </p>
  <p>Accessibility, from an authoring tool perspective, includes addressing 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 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 
        content</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, they frequently author  content that is then incorporated with other 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 &quot;<a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tools</a>&quot; 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>ATAG 2.0 recommends that authoring tools<a class="termdef" href="#def-Developer" title="definition: authoring tool developers"></a> be capable of producing web content that conforms with <a href="#conf-rel-wcag">WCAG 2.0</a>. However, WCAG 2.0 notes that even  content that conforms to the highest level of WCAG 2.0 (i.e. Level AAA) may not be &quot;accessible to individuals with all types, degrees, or combinations of disability, particularly in the cognitive language and learning areas&quot;. Development of authoring tools that address more specialized needs is encouraged, but is beyond the scope of this document.</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 accessibility and how they work together see:
<ul>
        <li> <a href="http://www.w3.org/WAI/intro/components">Essential Components of Web Accessibility</a></li>
        <li> <a href="http://www.w3.org/WAI/intro/wcag.php">Web Content Accessibility Guidelines (WCAG) Overview</a></li>
        <li> <a href="http://www.w3.org/WAI/intro/uaag.php">User Agent Accessibility Guidelines (UAAG) Overview</a></li>

      </ul>
    </li>
  </ol>
  </div> <!-- gl-only -->
 <!-- techs-only -->
<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 this  audience, 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 accessible authoring tools. <a href="#part_a">Part A</a> relates to ensuring 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 ensuring 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 <a class="termdef" href="#def-Accessible-Web-Content" title="definition: accessible web content">accessible</a> 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> &quot;Conformance Applicability Notes&quot; that apply to all of the success criteria within that part (see <a href="#part_a_applic_notes">Part A Conformance Applicability Notes</a>, <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="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/">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="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/"></a></li>
  </ul>
  <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="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#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 accessible authoring into the same &quot;look-and-feel&quot; 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> <!-- sect-intro -->

<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><!-- gl-only -->
   <!-- techs-only -->

<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 &quot;authoring tool user interface&quot;:</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">&quot;included&quot; 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, such as menus, button bars, status bars, user preferences, <a class="termdef" href="#def-Documentation" title="definition: documentation">documentation</a>, etc. </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 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 proble" class="termdef">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. by plug-ins, user modifications, etc.).</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, etc.) to satisfy success criteria. If a <a href="#conf-claim">conformance claim</a> is made for a web-based authoring tool, the claim must cite the user agent.</li>

      <li><a name="part_a_applic_note_5" id="part_a_applic_note_5"></a><strong class="handle">Features for meeting Part A must be accessible:</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, etc.). 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>
    </ol>
	
    <h2 class="principle"><a name="principle_a1" id="principle_a1"> </a>PRINCIPLE A.1: Authoring tool user interfaces must 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="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#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"><a class="termdef" href="#def-Web-Based-UI" title="definition: authoring tool user interface (Web-based)">Web-based authoring tool user interfaces</a> 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="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#sc_a111">Implementing A.1.1.1</a></div>
	   </div>
	   
<!--@@@-->	
	  
      <!-- techs-only -->
	</div> <!-- sc-level -->
	<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="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#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 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"><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> 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> If a <a href="#conf-claim">conformance claim</a> is made, then the claim  must cite the accessibility guidelines followed.</li>
	</ul>
	
	   <div class="gl-only">
	     <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#sc_a121">Implementing A.1.2.1</a></div>
	   </div>
	   
	   
       <!-- techs-only -->

      <h4 class="sc-title"><a id="sc_a122" name="sc_a122"></a>A.1.2.2 Platform Accessibility Services: </h4><p class="sc-title"><a class="termdef" href="#def-Non-Web-Based" title="definition: authoring tool user interface (non-Web-Based)">Non-web-based authoring tools</a> implement communication with <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> If a <a href="#conf-claim">conformance claim</a> is made, then the claim  must cite the platform accessibility service(s) implemented.</li></ul> 
       <!-- techs-only -->
    </div>  <!-- sc-level -->
    <h2 class="principle"><a name="principle_a2" id="principle_a2"></a>PRINCIPLE A.2: Editing-views must be 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="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#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> with <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</a>, then the text alternatives 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="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#sc_a211">Implementing A.2.1.1</a></div>
	   </div>
	   

	   <!-- techs-only -->

	  <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) Alternatives Rendered:</strong> <a class="termdef" href="#def-Time-Based-Alternatives" title="definition: alternatives for the time-based content">Alternatives for the time-based content</a> are also rendered; 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 <a href="#def-Option" title="definition: option" class="termdef">option</a> to <a class="termdef" href="#def-Preview" title="definition: preview">preview</a> the time-based content 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="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#sc_a212">Implementing A.2.1.2</a></div>
	   </div>
	   

	   <!-- techs-only -->
	  
    </div> <!-- sc-level -->
    <h3 class="guideline"><a name="gl_a22" id="gl_a22"> </a> Guideline A.2.2: (For the authoring tool user interface) Editing-view presentation can be programmatically determined. 
<span class="gl-only">[<a href="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#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 information (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 Information: </h4><p class="sc-title"> If an <a class="termdef" href="#def-Editing-View" title="definition: editing view">editing-view</a> modifies the <a class="termdef" href="#def-Presentation" title="definition: presentation">presentation</a> to convey status information, then that status information can be <a class="termdef" href="#def-Programmatically-Determined" title="definition: programmatically determined">programmatically determined</a>. Status information conveyed by modifying the presentation of editing-views may include, but is not limited to, spelling, grammar and syntax errors. <span class="level">(<strong>Level A</strong>)</span></p>
		
			   <div class="gl-only">
	     <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#sc_a221">Implementing A.2.2.1</a></div>
	   </div>
	   
	   
          <!-- techs-only -->
        <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 a text <a href="#def-Web-Content-Properties" title="definition: content property" class="termdef">property</a> is both <a href="#def-Content-Renderings" title="definition: content rendering" class="termdef">rendered</a> and editable and the text property is supported by the implemented <a class="termdef" href="#def-Accessibility-Platform-Service" title="definition: accessibility platform architecture">platform accessibility service</a>, then the property is <a class="termdef" href="#def-Programmatically-Determined" title="definition: programmatically determined">programmatically determinable</a>.  <span class="level">(<strong>Level A</strong>)</span></p>
		
			   <div class="gl-only">
	     <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#sc_a222">Implementing A.2.2.2</a></div>
	   </div>
	   

         
    </div><!-- sc-level -->

<h2 class="principle"><a name="principle_a3" id="principle_a3"> </a>PRINCIPLE A.3: Editing-views must be 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="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#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 are not able to use a mouse, and instead require keyboard 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-note"><em class="note-handle">Note 1:</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 2:</em> This success criterion does not forbid and should not discourage providing mouse input or other input methods in addition to keyboard operation.</li></ul>		
		<div class="gl-only">
	     <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#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"> <a class="termdef" href="#def-Keyboard-Trap" title="definition: keyboard trap">Keyboard traps</a> are prevented as follows: <span class="level">(<strong>Level A</strong>)</span></p>
     <ul class="sc-bullets">
      <li class="sc-bullet"><strong class="handle">(a) In the <a href="#def-Authoring-Tool-Interface" title="definition: authoring tool user interface" class="termdef">Authoring Tool User Interface</a>:</strong> 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 and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away; and</li>
      <li class="sc-bullet"><strong class="handle">(b) In  <a class="termdef" href="#def-Editing-View" title="definition: editing view">Editing-Views</a> that <a href="#def-Content-Renderings" title="definition: content rendering" class="termdef">Render</a> <a class="termdef" href="#def-Web-Content" title="definition: web content"> Content</a>:</strong> If an editing-view renders  content (e.g. <a class="termdef" href="#def-WYSIWYG" title="definition: WYSIWYG">WYSIWYG</a> view), then a <a class="termdef" href="#def-Documentation" title="definition: documentation">documented</a>  keyboard command is provided that moves the editing-view keyboard focus to a known location (e.g. the start of the editing-view).</li></ul>
	   <div class="gl-only">
	     <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#sc_a312">Implementing A.3.1.2</a></div>
	   </div>
	   
	   
      
    </div><!-- sc-level -->
		
    <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="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#sc_a313">Implementing A.3.1.3</a></div>
	   </div>
	   

      
    </div><!-- sc-level -->
		
    <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="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#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"> Keyboard access to the <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> can be customized. <span class="level">(<strong>Level AAA</strong>)</span></p>
	   <div class="gl-only">
	     <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#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"> <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> can be presented with any associated keyboard commands. <span class="level">(<strong>Level AAA</strong>)</span></p>
		<div class="gl-only">
	     <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#sc_a316">Implementing A.3.1.6</a></div>
	   </div>
	   

            
    </div><!-- sc-level -->
    <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="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#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 time limits 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"> If the <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> includes <a href="#def-Authoring-Session" title="definition: authoring session" class="termdef">authoring session</a> time limits, then the authoring tool 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 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="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#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">If a time limit is set by the <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a>, 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) 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. &quot;press the space bar&quot;), 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="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#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 Pointer Targets: </h4><p class="sc-title"> <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> that accept
pointer input are either stationary or <a class="termdef" href="#def-Author" title="definition: authors">authors</a> can pause the movement. <span class="level">(<strong>Level A</strong>)</span></p>
	   <div class="gl-only">
	     <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#sc_a323">Implementing A.3.2.3</a></div>
	   </div>
	   
	   
	   
    </div><!-- sc-level -->
	
 <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 made using the authoring tool. <span class="level">(<strong>Level AAA</strong>)</span> </p>
   <div class="gl-only">
	     <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#sc_a324">Implementing A.3.2.4</a></div>
      </div>
	   

	
	</div> <!-- sc-level -->
	<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="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#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"> Editing-views that <a href="#def-Content-Renderings" title="definition: content rendering" class="termdef">render</a> visual time-based content can be paused and can be set to not play automatically. <span class="level">(<strong>Level A</strong>)</span> </p>
	  	   <div class="gl-only">
	     <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#sc_a331">Implementing A.3.3.1</a></div>
	   </div>
	   
	   
      
    </div> <!-- sc-level -->
    <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="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#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 the tasks of navigation 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, etc.) 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="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#sc_a341">Implementing A.3.4.1</a></div>
	   </div>
	   

      
    </div>  <!-- sc-level -->
    <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. 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 class="level">(<strong>Level AAA</strong>)</span></p>
	  	  	   <div class="gl-only">
	     <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#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="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#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 <a class="termdef" href="#def-Web-Content" title="definition: web content">web content</a> being authored.</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"> <a class="termdef" href="#def-Editing-View" title="definition: editing view">Editing-views</a> enable 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 made visible 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; and</li>
      <li class="sc-bullet"><strong class="handle">(e) Case Sensitive:</strong> The search can be in both case sensitive and case insensitive modes.</li>
      </ul>
	  <div class="gl-only">
	     <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#sc_a351">Implementing A.3.5.1</a></div>
      </div>
	   
	   
       
    </div><!-- sc-level -->
    <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="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#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 affecting the <a class="termdef" href="#def-Web-Content" title="definition: web content">web content</a> to be <a href="#def-Publishing" title="definition: publishing" class="termdef">published</a>. <span class="level">(<strong>Level A</strong>)</span></p>
	  	  <div class="gl-only">
	     <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#sc_a361">Implementing A.3.6.1</a></div>
	   </div>
	   

      
    </div> <!-- sc-level -->
	
    <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="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#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 platform <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> made by <a class="termdef" href="#def-Author" title="definition: authors">authors</a>. <span class="level">(<strong>Level AA</strong>)</span></p>
	  	  <div class="gl-only">
	     <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#sc_a363">Implementing A.3.6.3</a></div>
	   </div>
	   
	   
       
</div>  <!-- sc-level -->
 
    <div class="sc-level">
      <h4 class="sc-title"><a id="sc_a364" name="sc_a364"> </a>A.3.6.4 Multiple Sets: </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 <a class="termdef" href="#def-Author" title="definition: authors">authors</a> can save and reload multiple sets of these settings. <span class="level">(<strong>Level AAA</strong>)</span></p>
	  	  <div class="gl-only">
	     <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#sc_a364">Implementing A.3.6.4</a></div>
	   </div>
	   
	   
       
	  
      <h4 class="sc-title"><a id="sc_a365" name="sc_a365"> </a>A.3.6.5 Assistance with Preferences: </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 the authoring tool includes a mechanism to help <a href="#def-Author" title="definition: authors" class="termdef">authors</a> configure these settings. <span class="level">(<strong>Level AAA</strong>)</span></p>
	  	  <div class="gl-only">
	     <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#sc_a365">Implementing A.3.6.5</a></div>
	   </div>
	   
	   
       
    </div> <!-- sc-level -->
    <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 as accessible as existing user agents. 
<span class="gl-only">[<a href="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#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 in 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) Pre-existing User Agent:</strong> The preview makes use of a pre-existing <a class="termdef" href="#def-User-Agent" title="definition: user agent">user agent</a>; or </li> 
      <li class="sc-bullet"><strong class="handle">(b) UAAG (Level A):</strong> The preview conforms to the User Agent Accessibility Guidelines Level A <cite>[<a href="#ref-UAAG">UAAG</a>]</cite>.</li>
	  </ul>
	  	  <div class="gl-only">
	     <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#sc_a371">Implementing A.3.7.1</a></div>
	   </div>
	   
	   
       
    </div> <!-- sc-level -->

    <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="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#sc_a372">Implementing A.3.7.2</a></div>
	   </div>
	   

      

    </div>
    <!-- sc-level -->
    <h2 class="principle"><a name="principle_a4" id="principle_a4"> </a>PRINCIPLE A.4: Editing-views must be 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="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#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"> For <a href="#def-Authoring-Action" title="definition: authoring actions" class="termdef">authoring actions</a>, 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) Reversible:</strong> The authoring action can be immediately reversed; or </li>
      <li class="sc-bullet"><strong class="handle">(b) Warn and Confirm:</strong> The authoring tool provides a warning to <a href="#def-Author" title="definition: authors" class="termdef">authors</a> that the action is <a href="#def-Irreversible-Actions" title="definition: irreversible actions" class="termdef">irreversible</a> and requires authors to confirm the action before proceeding.</li>
      </ul>
   <ul class="sc-notes">
    <li class="sc-note"><em class="note-handle">Note 1:</em> Reversing actions (e.g. an &quot;undo&quot; function) are also considered authoring actions, meaning they must also meet this success criterion (e.g. a &quot;redo&quot; function).</li>
	<li class="sc-note"><em class="note-handle">Note 2:</em> It is acceptable to collect a series of text entry actions (e.g. typed words, a series of backspaces) into a single reversible authoring action.</li>
    <li class="sc-note"><em class="note-handle">Note 3:</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="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#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  Setting Changes Reversible: </h4>
      <p class="sc-title"> If actions modify <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> settings, then 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) Reversible:</strong> The authoring tool setting can be reversed by the same mechanism that made the change; or </li>
	  <li class="sc-bullet"><strong class="handle">(b) Warn and Confirm:</strong> The authoring tool provides a warning to <a href="#def-Author" title="definition: authors" class="termdef">authors</a> that the setting change is <a href="#def-Irreversible-Actions" title="definition: irreversible actions" class="termdef">irreversible</a> and requires authors to confirm or save the current settings before proceeding. </li>
      </ul>
	  		<div class="gl-only">
	     <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#sc_a412">Implementing A.4.1.2</a></div>
	   </div>
	   
	    
       
</div> <!-- sc-level -->
	
    <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-Actions" title="definition: reversible actions" class="termdef">reversible</a> <a href="#def-Authoring-Action" title="definition: authoring actions" class="termdef">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> The notes for <a href="#sc_a411">A.4.1.1</a> still apply.</li></ul>
	  	<div class="gl-only">
	     <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#sc_a413">Implementing A.4.1.3</a></div>
	   </div>
	   
	   
      <!-- techs-only -->
    </div><!-- sc-level -->
    <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="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#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 proper <a class="termdef" href="#def-Accessible-Web-Content" title="definition: accessible Web content">accessible</a> <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 Document Accessibility Features: </h4>
      <p class="sc-title"> All features of the <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> that must be present to meet  <a href="#part_a">Part A</a> of ATAG 2.0 (e.g. keyboard shortcuts, text search, etc.) are <a class="termdef" href="#def-Documentation" title="definition: documentation">documented</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 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="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#sc_a421">Implementing A.4.2.1</a></div>
	   </div>
	    

         
    </div> <!-- sc-level -->

    <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"> The <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> includes <a class="termdef" href="#def-Documentation" title="definition: documentation">documentation</a> for its author-level user interface features. <span class="level">(<strong>Level AA</strong>)</span></p>
      <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="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#sc_a422">Implementing A.4.2.2</a></div>
      </div>
	    
	   
      
    </div> <!-- sc-level -->
  </div> <!-- subsect-tool-accessible -->

<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. by plug-ins, user-defined templates, user modifications of default settings, etc.).</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 accessibility 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 has specified, 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 checking tool).</li> 
      <li><strong class="handle"><a name="part_b_applic_note_5" id="part_b_applic_note_5"></a>Features for meeting Part B must be accessible:</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, etc.). </li>

      <li><strong class="handle"><a name="part_b_applic_note_6" id="part_b_applic_note_6"></a>Multiple author 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 author 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 author role where it would be useful.</li>
    </ol> 

<h2 class="principle"><a id="principle_b1" name="principle_b1"></a>PRINCIPLE B.1: Fully automatic processes must produce accessible content</h2> 
      
<h3 class="guideline"><a name="gl_b11" id="gl_b11"> </a> Guideline B.1.1: Ensure automatically specified content is accessible. <span class="gl-only">[<a href="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#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> specify <span class="sc"><a class="termdef" href="#def-Web-Content" title="definition: web content">web content</a></span> that is not accessible, then additional <a href="#def-Repairing" title="definition: repairing" class="termdef">repair</a> tasks are imposed 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"> <a href="#def-Author" title="definition: authors" class="termdef">Authors</a> have the <a class="termdef" href="#def-Default-Option" title="definition: default option" >default option</a> that, when <a class="termdef" href="#def-Web-Content" title="definition: web content">web content</a> is <a href="#def-Content-Auto-Gen" title="definition: automatically-generated content" class="termdef">automatically generated</a> for <a href="#def-Publishing" title="definition: publishing" class="termdef">publishing</a> after the <a href="#def-End-Auth-Session" title="definition: end of an authoring session" class="termdef">end of an authoring session</a>, it is <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</a>.</li></ul>
	   <div class="gl-only">
	     <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#sc_b111">Implementing B.1.1.1</a></div>
	   </div>
	   
	   
   <!-- techs-only -->
  
  <h4 class="sc-title"><a id="sc_b112" name="sc_b112"> </a>B.1.1.2 Content Auto-Generation During Authoring Sessions (WCAG):</h4> <p class="sc-title"><a href="#def-Author" title="definition: authors" class="termdef">Authors</a> have the <a class="termdef" href="#def-Default-Option" title="definition: default option" >default option</a> that, when <a class="termdef" href="#def-Web-Content" title="definition: web content">web content</a> is <a href="#def-Content-Auto-Gen" title="definition: automatically-generated content" class="termdef">automatically generated</a> during an <a href="#def-Authoring-Session" title="definition: authoring session" class="termdef">authoring session</a>, then 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) 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, authors are prompted 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 checking 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 templates 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</a>.</li>
	</ul>
	<div class="gl-only"><div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#sc_b112">Implementing B.1.1.2</a></div></div>
	   
	   	
   <!-- techs-only -->
</div>
<!-- sc-level -->


<h3 class="guideline"><a id="gl_b12" name="gl_b12"> </a> Guideline B.1.2: Ensure accessibility information is preserved. <span class="gl-only">[<a href="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#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</a> is critical to maintaining comparable levels of <a class="termdef" href="#def-Accessible-Web-Content" title="definition: accessible Web content">accessibility</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>, 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 default option to be warned that accessibility information 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 checking is automatically performed; or </li> 
	  <li class="sc-bullet"><strong class="handle">(d) Checking Suggested:</strong> After the transformation, the authoring tool prompts authors to perform accessibility checking. </li></ul>
   <ul class="sc-notes">
    <li class="sc-note"><em class="note-handle">Note:</em> This success criteria only applies to transformations in which the output technology is an &quot;included&quot; technology for conformance.</li></ul>
	  
	  	   <div class="gl-only">
	     <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#sc_b121">Implementing B.1.2.1</a></div>
	   </div>
	   
  
</div>
<!-- sc-level -->
<div class="sc-level">
  <h4 class="sc-title"><a id="sc_b122" name="sc_b122"> </a>B.1.2.2 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="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#sc_b122">Implementing B.1.2.2</a></div>
	   </div>
	   
	   
  

  <h4 class="sc-title"><a id="sc_b123" name="sc_b123"> </a>B.1.2.3 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>
	   <div class="gl-only">
	     <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#sc_b123">Implementing B.1.2.3</a></div>
	   </div>
	   

  


</div>
<!-- sc-level -->
<h2 class="principle"><a id="principle_b2" name="principle_b2"> </a>PRINCIPLE B.2: Authors must be supported in  producing accessible content</h2>
<h3 class="guideline"><a name="gl_b21" id="gl_b21"> </a> Guideline B.2.1: Ensure accessible content production is possible. 

<span class="gl-only">[<a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/Overview.html#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: For the purposes of this document, <a href="#conf-rel-wcag">WCAG 2.0</a> defines the <a class="termdef" href="#def-Accessible-Web-Content" title="definition: accessible Web content">accessible web content (WCAG) </a> requirements. To support accessible web content production, at minimum, it must be 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"> If the <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> places <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, then 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="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#sc_b211">Implementing B.2.1.1</a></div>
	   </div>
	   	
		
        
</div> <!-- sc-level -->
<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="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#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="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#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, etc.), 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> <a href="#sc_b414">Success Criterion B.4.1.4</a> addresses the prominence of the mechanisms.</li></ul>
	  	   <div class="gl-only">
	     <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#sc_b222">Implementing B.2.2.2</a></div>
	   </div>
	   
	   

  </div>
<!-- sc-level -->
<div class="sc-level">
  <h4 class="sc-title"><a id="sc_b223" name="sc_b223"> </a>B.2.2.3 Technology Decision Support: </h4><p class="sc-title"> If the <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> provides the <a class="termdef" title="definition: options" href="#def-Option">option</a> of producing a <a href="#def-Web-Content-Technology" title="definition: technology (Web content)" class="termdef">web content technology</a> for <a href="#def-Publishing" title="definition: publishing" class="termdef">publishing</a> for which the  authoring tool does not <a href="#conf-techs-produced">provide support for the production of  accessible content</a>, then both of the following are true: <span class="level">(<strong>Level A</strong>)</span></p>
  <ul class="sc-bullets">
	    <li class="sc-bullet"><strong class="handle">(a) Warning:</strong> <a class="termdef" href="#def-Author" title="definition: author">Authors</a> are warned that the authoring tool does not provide  support for the production of accessible content for that technology; and </li>
		<li class="sc-bullet"><strong class="handle">(b) List:</strong> From the warning, authors can access a list of technologies for which the authoring tool does <a href="#conf-techs-produced">provide support  for the production of accessible content</a>.</li></ul>
	  	   <div class="gl-only">
	     <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#sc_b223">Implementing B.2.2.3</a></div>
	   </div>
	   
	   		
       <!-- techs-only -->

</div><!-- sc-level -->
<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="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#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">accessibility problems</a> and interfere with accessibility <a href="#def-Checking" title="definition: checking" class="termdef">checking</a>.</p>
	  
      <p class="rationale">See Also: This guideline 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. inserts 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"> <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>
		
	  	   <div class="gl-only">
	     <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#sc_b231">Implementing B.2.3.1</a></div>
	   </div>
	   
	   		
		 

        <h4 class="sc-title"><a id="sc_b232" name="sc_b232"> </a>B.2.3.2 Conditions on Automated Suggestions: </h4><p class="sc-title"> During the <a href="#def-Authoring-Session" title="definition: authoring session" class="termdef">authoring session</a>, the <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> may only automatically suggest <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> under the following conditions: <span class="level">(<strong>Level A</strong>)</span></p>
     <ul class="sc-bullets">
        <li class="sc-bullet"><strong class="handle">(a) Author Control:</strong> <a href="#def-Author" title="definition: authors" class="termdef">Authors</a> have the opportunity to accept, modify, or reject the suggested text alternatives prior to insertion; and </li>
          <li class="sc-bullet"><strong class="handle">(b) Relevant Sources:</strong> The suggested text alternatives are only derived from sources designed to fulfill the same purpose (e.g. suggesting the value of an image's &quot;description&quot; metadata field as a long description).</li></ul>
	  	   <div class="gl-only">
	     <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#sc_b232">Implementing B.2.3.2</a></div>
	   </div>
	   
	   		  
         
		       
        <h4 class="sc-title"><a id="sc_b233" name="sc_b233"> </a>B.2.3.3 Let User Agents Repair: </h4><p class="sc-title"> The <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> avoids <a href="#def-Repairing" title="definition: repairing" class="termdef">repairing</a> <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> using any text value that would also be available to <a href="#def-User-Agent" title="definition: user agent" class="termdef">user agents</a> (e.g. do not use the image filename). <span class="level">(<strong>Level A</strong>)</span></p>
	  	   <div class="gl-only">
	     <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#sc_b233">Implementing B.2.3.3</a></div>
	   </div>
	   
	   
         <!-- implementing-section -->

    </div> <!-- sc-level -->
 
<div class="sc-level">
  <h4 class="sc-title"><a id="sc_b234" name="sc_b234"> </a> B.2.3.4 Save for Reuse: </h4><p class="sc-title"> 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>, 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="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#sc_b231">Implementing B.2.3.4</a></div>
	   </div>
	   
	    
         
    </div> <!-- sc-level -->
	  
    <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="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#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</a> and other pre-authored content (e.g. clip art, synchronized media, widgets, etc.) can have several benefits, including: immediately improving the <a class="termdef" href="#def-Accessible-Web-Content" title="definition: accessible web content">accessibility</a> of <span class="sc"><a class="termdef" href="#def-Content-Being-Edited" title="definition: web content being edited">web content being edited</a></span>, reducing the effort required of <a class="termdef" href="#def-Author" title="definition: author">authors</a>, and demonstrating the importance of <a class="termdef" href="#def-Accessible-Web-Content" title="definition: accessible Web content">accessible web content (WCAG) </a>.</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>
  <ul class="sc-notes">
    <li class="sc-note"><em class="note-handle">Note:</em> It is recommended that the accessible options be identified, but this is not required.</li></ul>
	   <div class="gl-only">
	     <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#sc_b241">Implementing B.2.4.1</a></div>
	   </div>
	   

         
    </div>  <!-- sc-level -->
	
    <div class="sc-level">
      <h4 class="sc-title"><a id="sc_b242" name="sc_b242"> </a>B.2.4.2 Identify Template Accessibility (Minimum): </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 <a href="#def-Template" title="definition: template" class="termdef">templates</a> are provided such that 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="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#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-Create 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, the non-accessible templates or both.</li>
	  </ul>
				<div class="gl-only">
	     <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#sc_b243">Implementing B.2.4.3</a></div>
	   </div>
	   

         
	  
    </div> 
    <!-- sc-level -->
 
<div class="sc-level">
  <h4 class="sc-title"><a id="sc_b244" name="sc_b244"> </a>B.2.4.4 Identify Template Accessibility (Enhanced): </h4>
  <p class="sc-title"> If the <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> provides any non-<a href="#def-Accessible-Template" title="definition: accessible templates" class="termdef">accessible templates (WCAG)</a> <a class="termdef" title="definition: options" href="#def-Option">options</a> and does not include a <a href="#def-Template-Selection-Mechanism" title="definition: template selection mechanism" class="termdef">template selection mechanism</a>, then the non-accessible templates include accessibility warnings within the templates. <span class="level">(<strong>Level AAA</strong>)</span></p>
  		<div class="gl-only">
	     <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#sc_b244">Implementing B.2.4.4</a></div>
	   </div>
	   

         <!-- techs-only -->

</div> <!-- sc-level -->
 
    <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="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#gl_b25">Implementing B.2.5</a>]</span> </h3>
    <p class="rationale">Rationale: Providing accessible <a href="#def-Template" title="definition: template" class="termdef">templates</a> and other pre-authored content (e.g. clip art, synchronized media, widgets, etc.) can have several benefits, including: immediately improving the <a class="termdef" href="#def-Accessible-Web-Content" title="definition: accessible web content">accessibility</a> of <span class="sc"><a class="termdef" href="#def-Content-Being-Edited" title="definition: web content being edited">web content being edited</a></span>, reducing the effort required of <a class="termdef" href="#def-Author" title="definition: author">authors</a>, and demonstrating the importance of <a class="termdef" href="#def-Accessible-Web-Content" title="definition: accessible Web content">accessible web content (WCAG)</a>.</p>

	<div class="sc-level">
    <h4 class="sc-title"><a id="sc_b251" name="sc_b251"> </a>B.2.5.1  Pre-Authored Content Selection Mechanism: </h4><p class="sc-title"> If <a href="#def-Author" title="definition: authors" class="termdef">authors</a> are provided with a selection mechanism for pre-authored content other than <a href="#def-Template" title="definition: template" class="termdef">templates</a> (e.g. clip art gallery, widget repository, design themes), then both 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) Indicate:</strong> The selection mechanism  indicates the accessibility status of the pre-authored content (if known); and </li>
	<li class="sc-bullet"><strong class="handle">(b) Prominence:</strong> Any accessible <a class="termdef" title="definition: options" href="#def-Option">options</a> are <a class="termdef" href="#def-At-Least-As-Prominent" title="definition: At Least As Prominent">at least as prominent</a> as other pre-authored content options.</li></ul>
			<div class="gl-only">
	     <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#sc_b251">Implementing B.2.5.1</a></div>
	   </div>
	   

    
    <!-- techs-only -->
	</div> <!-- sc-level -->

<div class="sc-level">

    <h4 class="sc-title"><a id="sc_b252" name="sc_b252"> </a>B.2.5.2 Pre-Authored Content Accessibility Status: </h4><p class="sc-title"> If the <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> provides a repository of pre-authored content, then each of the content objects has a recorded accessibility status. <span class="level">(<strong>Level AAA</strong>)</span></p>
			<div class="gl-only">
	     <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#sc_b252">Implementing B.2.5.2</a></div>
	   </div>
	   
	        <!-- techs-only -->
	</div> <!-- sc-level -->
	
    <h2 class="principle"><a id="principle_b3" name="principle_b3"> </a>PRINCIPLE B.3: Authors must be 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="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#gl_b31">Implementing B.3.1</a>]</span> </h3>
    <p class="rationale">Rationale: <a href="#def-Checking" title="definition: checking" class="termdef">Accessibility checking</a> as an integrated function of the <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> 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</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> so 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</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 must carry out by themselves. For more  information on checking, see <a href="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#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="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#sc_b311">Implementing B.3.1.1</a></div>
	   </div>
	     
	   <!-- techs-only -->
  </div><!-- sc-level -->
  
  <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">For <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</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>), instructions are provided from the check that describe how to make the decision. <span class="level">(<strong>Level A</strong>)</span></p>

		<div class="gl-only">
	     <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#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"> For <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</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>), the relevant <a class="termdef" href="#def-Web-Content" title="definition: web content">content</a> 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, 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="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#sc_b313">Implementing B.3.1.3</a></div>
	   </div>
	     
  
</div>
<!-- sc-level -->
<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"> <a href="#def-Author" title="definition: authors" class="termdef">Authors</a> can receive an accessibility status report based on the results of the accessibility <a href="#def-Checking" title="definition: checking" class="termdef">checks</a>. <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 is not specified. For example, the status might be 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="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#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">Authoring tools 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="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#sc_b315">Implementing B.3.1.5</a></div>
      </div>
	     
  
</div>
<!-- sc-level -->
<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="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#gl_b32">Implementing B.2.3</a>] </span> </h3>

<p class="rationale">Rationale: <a href="#def-Repairing" title="definition: repairing" class="termdef">Repair</a> as an integral part of the authoring process greatly enhances the utility of <a href="#def-Checking" title="definition: checking" class="termdef">checking</a> and increases the likelihood that <a class="termdef" href="#def-Web-Content-Accessibility-Problem" title="definition: web content accessibility problem">accessibility problems</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 web content accessibility problems. 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 must carry out by themselves. For more information on repair, see <a href="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#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="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#sc_b321">Implementing B.3.2.1</a></div>
	   </div>
	     
  
</div>
<!-- sc-level -->
<h2 class="principle"><a id="principle_b4" name="principle_b4"> </a>PRINCIPLE B.4: Authoring tools must 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="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#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="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#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"> If <a class="termdef" href="#def-Author" title="definition: author">authors</a> can turn off an <a title="definition: accessible content support features" class="termdef" href="#def-Accessible-Content-Support-Features">accessible content support feature</a>, then they can turn the feature back on. <span class="level">(<strong>Level A</strong>)</span></p>
		<div class="gl-only">
	     <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#sc_b412">Implementing B.4.1.2</a></div>
	   </div>
	     
	   
        
	</div> <!-- sc-level -->
		
<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"> If <a href="#def-Author" title="definition: authors" class="termdef">authors</a> turn off an <a title="definition: accessible content support features" class="termdef" href="#def-Accessible-Content-Support-Features">accessible content support feature</a>, then the <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> informs them 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</a>. <span class="level">(<strong>Level AA</strong>)</span></p>	
  <div class="gl-only">
	     <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#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"> <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="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#sc_b414">Implementing B.4.1.4</a></div>
	   </div>
	     
	   
        
    </div> <!-- sc-level -->
    <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="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#gl_b42">Implementing B.4.2</a>]</span>
</h3> 
		
      <p class="rationale">Rationale: Without <a class="termdef" href="#def-Documentation" title="definition: documentation">documentation</a> of the <a class="termdef" href="#def-Accessible-Content-Support-Features" title="definition: accessible content support features">features that support the production of accessible content</a> (e.g. <a href="#def-Prompt" title="definition: prompt" class="termdef">prompts</a> for text alternatives, accessibility <a href="#def-Checking" title="definition: checking" class="termdef">checking</a> tools), some <a class="termdef" href="#def-Author" title="definition: author">authors</a> may not be able to use them. Demonstrating accessible authoring as routine practice will encourage its acceptance by some <a class="termdef" href="#def-Author" title="definition: author">authors</a>.</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 that meet the </a><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="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#sc_b421">Implementing B.4.2.1</a></div>
	   </div>
	     

         
</div> <!-- sc-level -->

	  
      <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 the <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="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#sc_b422">Implementing B.4.2.2</a></div>
	   </div>
	     
	    
</div>  <!-- sc-level -->
 
<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"> A <a href="#def-Tutorial" title="definition: tutorial" class="termdef">tutorial</a> on an accessible authoring process that is specific to the <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> is provided. <span class="level">(<strong>Level AAA</strong>)</span></p>
		<div class="gl-only">
	     <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#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-Documentation" title="definition: documentation">documentation</a> contains an index to the instructions for using the <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="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#sc_b424">Implementing B.4.2.4</a></div>
	   </div>
	     

      
    </div>
    <p>&nbsp;        </p>
</div> <!-- subsect-support-production -->
</div> <!-- sect-guidelines -->

<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>  <!-- gl-only -->

    <!-- techs-only -->

  <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 id="conf-rel-wcag" name="conf-rel-wcag"> </a>Relationship
  to the Web Content Accessibility Guidelines (WCAG) 2.0 </h3>
  <p>Because WCAG 2.0 <cite>[<a href="#ref-WCAG20">WCAG20</a>]</cite> is the most recent W3C Recommendation regarding web content accessibility, ATAG 2.0 frequently refers to WCAG 2.0 in order to set 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 <a class="termdef" href="#def-Web-Content" title="definition: web content">web content</a> that is 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>Whenever success criteria or defined terms in ATAG 2.0 depend on WCAG 2.0, they are marked with &quot;(WCAG)&quot;. </p>
  <h4><a id="conf-note" name="conf-note"></a>Note on &quot;accessibility-supported ways of using technologies&quot;:</h4>
  <p>Part of conformance to WCAG 2.0 is the requirement that &quot;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>.&quot; 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 &quot;accessibility supported&quot; 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, etc.). 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 &quot;conformance&quot;, but instead refer to &quot;meeting WCAG 2.0 success criteria&quot;.</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>
  <h3><a name="conf-applic" id="conf-applic"></a>Applicability of Success Criteria </h3>
  <p>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 <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tools</a> with limited feature sets (e.g. a photo editor, a CSS editor, a status update field in a social networking application, etc.), many of the ATAG 2.0 success criteria are conditional, applying only to authoring tools with the given features(s) (e.g. Success Criterion B.1.1.1 applies only to authoring tools that <span class="sc"><a href="#def-Content-Auto-Gen" title="definition: automatically-generated content" class="termdef">automatically generate</a></span> <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 authoring sessions</a>).</p>

  <p>If a <a href="#conf-claim">conformance claim</a> is made, a declaration that a success criterion is not applicable requires a rationale. </p>
  <h3><a name="conf-req" id="conf-req"></a>Conformance Requirements</h3>
  <p>In order for an <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tool</a> to conform to ATAG 2.0, all of the  following conformance requirements must be satisfied:</p>
  <h4><a name="conf-levels" id="conf-levels"> </a>Conformance Levels:</h4>

  <p><a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">Authoring tools</a> may conform &quot;fully&quot; or &quot;partially&quot; to ATAG 2.0. In  either case, the level of conformance depends on the level of the  success criteria that have been satisfied.</p>
  <p><strong>&quot;Full&quot; ATAG 2.0 Conformance:</strong> This type of conformance is intended to be  used when <a class="termdef" href="#def-Developer" title="definition: authoring tool developers">developers</a> have considered the accessibility of the authoring  tools from both the perspective of <a href="#def-Author" title="definition: authors" class="termdef">authors</a> (<a href="#part_a">Part A: Make the authoring  tool user interface accessible</a>) and the perspective of <a href="#def-End-Users" title="definition: end user" class="termdef">end users</a> of <a class="termdef" href="#def-Web-Content" title="definition: web content">web content</a> produced by the authoring tools (<a href="#part_b">Part B: Support the production  of accessible content</a>):</p>

  <ol>
    <li><strong>Full ATAG 2.0 Conformance at Level A </strong><br />
  The authoring tool satisfies <em>all</em> of
    the <a href="#conf-applic">applicable</a> Level A  success criteria.</li>
    <li><strong>Full ATAG 2.0 Conformance at Level AA </strong><br />

      The authoring tool satisfies <em>all</em> of
      the applicable Level A  and Level
      AA success criteria.</li>
    <li><strong>Full ATAG 2.0 Conformance at Level AAA </strong> <br />
      The authoring tool satisfies <em>all</em> of
      the applicable success criteria.</li>
  </ol>

  <p><em>And</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> have been applied. </p>
  <p><strong>&quot;Partial&quot; ATAG 2.0 Conformance: Authoring Tool User Interface:</strong> This type of conformance  is intended to be used when developers have initially focused on the accessibility of the authoring tool to authors (Part
    A: Make the authoring tool user interface accessible):</p>

  <ol>
    <li><strong>Partial ATAG 2.0 Conformance Level A:
      Authoring Tool User Interface<br />
      </strong>The authoring tool satisfies <em>all</em> of the <a href="#conf-applic">applicable</a> Level
      A success criteria in Part A. Nothing is implied about Part B. </li>
    <li><strong>Partial ATAG 2.0 Conformance Level AA:
      Authoring Tool User Interface<br />

      </strong>The authoring tool satisfies <em>all</em> of the applicable Level
      A and Level AA  success criteria in Part A. Nothing
      is implied about Part B. </li>
    <li><strong>Partial ATAG 2.0 Conformance Level AAA:
      Authoring Tool User Interface<br />
      </strong>The authoring tool satisfies <em>all</em> of the applicable success criteria
      in Part A. Nothing is implied about Part B. </li>
  </ol>

  <p><em>And</em> the <a href="#part_a_applic_notes">Part A Conformance Applicability Notes</a> have been applied. </p>
  <p><strong>&quot;Partial&quot; ATAG 2.0 Conformance: 
      Content Production:</strong> This type of conformance  is intended to be used when developers have initially focused on the accessibility of the web content produced by the authoring tool to end users (Part
    B: Support the production of accessible content):</p>
  <ol>

    <li><strong>Partial ATAG 2.0 Conformance Level A:
      Content Production<br />
    </strong>The authoring tool satisfies <em>all</em> of the <a href="#conf-applic">applicable</a> Level
      A success criteria in Part B. Nothing is implied about Part A. </li>
    <li><strong>Partial ATAG 2.0 Conformance Level AA:
      Content Production<br />
      </strong>The authoring tool satisfies <em>all</em> of the applicable Level
      A and Level AA  success criteria in Part B. Nothing
      is implied about Part A. </li>

    <li><strong>Partial ATAG 2.0 Conformance Level AAA:
      Content Production<br />
      </strong>The authoring tool satisfies <em>all</em> of the applicable success criteria
      in Part B. Nothing is implied about Part A. </li>
  </ol>
  <p><em>And</em> the <a href="#part_b_applic_notes">Part B Conformance Applicability Notes</a> have been applied. </p>

  <p><strong>Note:</strong> The Working Group remains committed to the guiding principle that: &quot;<em>Everyone should have the ability to create and access web content</em>&quot;. Therefore, it is
  recommended that &quot;Partial&quot; Conformance be claimed only as a step toward &quot;Full&quot; Conformance.</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. Full Level A conformance with respect to the production of XHTML 1.0, Partial Level AA Conformance: Content Production with respect to the production of SVG 1.1).</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 any technologies that the <a class="termdef" href="#def-Developer" title="definition: authoring tool developers">developer</a> either sets for <a href="#def-Content-Auto-Gen" title="definition: automatically-generated content" class="termdef">automatically-generated content</a> or 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 &quot;interim&quot; 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>, but this is not required.</p>

  <p>When <a href="#sc_b211">Success Criterion B.2.1.1</a> refers to web content technologies for which the authoring tool <strong>provides support for the production of  accessible content</strong>, it is referring to this subset.</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 the <a href="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#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>If a conformance claim is made, then the conformance claim must meet the following conditions and include the following information (authoring tools can conform to ATAG 2.0 without making a claim). Claimants are encouraged to claim conformance to the most recent version
  of the Authoring Tool Accessibility Guidelines Recommendation.</p>
  <h4><a name="conf-conditions" id="conf-conditions"> </a>Conditions on Conformance Claims </h4> 
  <ol>
    <li>At least one version of the conformance claim must be published on the
      web as a document meeting Level A of WCAG 2.0. A suggested metadata description
      for this document is &quot;ATAG 2.0 Conformance Claim&quot;.</li>
    <li>Whenever the claimed conformance level is published (e.g. product information web site), the URI for the on-line published version of the conformance
      claim must be included.</li>

    <li>The existence of a conformance claim does not imply that the W3C has
      reviewed the claim or assured its validity.</li>
    <li>Claimants are solely responsible for the accuracy of their claims and keeping claims up to date.</li>
  </ol>
  <h4><a name="conf-claim-req-components" id="conf-claim-req-components"> </a>Required Components of an ATAG 2.0 Conformance Claim</h4> 
  <ol> 
    <li><strong>Claimant name</strong> and <strong>affiliation</strong>.</li> 
    <li><strong>Date</strong> of the claim.</li>

    <li><strong>Guidelines title</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><strong class="handle">Note:</strong> If the authoring tool is a <a href="#def-Collection-Software-Components" title="definition: collection of software components" class="termdef">collection
          of software components</a> (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 component, although the conformance claim will treat them
          as a whole. <strong>As stated above, the  Claimant has sole responsibility for the conformance claim, not the developer of any of the software components.</strong></li>

      </ul>
    </li>
    <li><strong><a href="#conf-techs-produced">Web content technologies produced</a></strong>.
    <ul>
      <li>A list of the <a class="termdef" href="#def-Web-Content-Technology" title="definition: technology (Web content)">web content technologies</a>   produced by the authoring tool that the Claimant <strong>is including</strong> in the   conformance claim.      For each web content technology, provide information on how the web content technology might be used to create <a class="termdef" href="#def-Accessible-Web-Content" title="definition: accessible Web content">accessible 
      web content</a> (e.g. provide links to technology-specific techniques).</li>

      <li>A list of any web content technologies  produced by the authoring tool that the Claimant <strong>is not including</strong> in the  conformance claim.</li>
    </ul></li>
    <li><strong>Declarations:</strong> For each success criterion:
        <ul> 
          <li>A declaration of whether or not the success criterion has been satisfied; or </li>
          <li>A declaration that the success criterion is <a href="#conf-applic">not applicable</a> and a rationale for why not. </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 was evaluated:
<ul> 
        <li>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> 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. operating system, etc.) 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>

  </ol>
  <h4><a name="conf-claim-optional-components" id="conf-claim-optional-components"> </a>Optional Components of an ATAG 2.0 Conformance Claim</h4> 
  <ol> 
    <li>A <strong>description of the authoring tool</strong> that identifies the types of <a href="#def-Editing-View" title="definition: editing views" class="termdef">editing-views</a> that it includes.</li> 
    <li>A <strong>description of how the  ATAG 2.0 success criteria were met</strong> where this may not be obvious. </li> 
  </ol> 
  <h3><a name="conf-prog-statement" id="conf-prog-statement"> </a>&quot;Progress Toward Conformance&quot; Statement</h3> 
  <p><a class="termdef" href="#def-Developer" title="definition: authoring tool developers">Developers</a> of <a class="termdef" href="#def-Authoring-Tool" title="definition: authoring tool">authoring tools</a> that do not yet conform fully to a particular
    ATAG 2.0 conformance level are encouraged to publish a statement on progress
    toward conformance. This statement would be the same as a <a href="#conf-claim">conformance
    claim</a> except that this statement would specify an ATAG 2.0 conformance
    level that is being progressed toward, rather than one already satisfied,
    and report the progress on success criteria not yet met. The author of a &quot;Progress
    Toward Conformance&quot; Statement is solely responsible for the accuracy
    of their statement. Developers are encouraged to provide expected timelines
  for meeting outstanding success criteria within the Statement.</p> 
  <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>   
<!-- sect-conformance -->
<hr /> 
  
<!-- techs-only -->
 <!-- techs-only -->
 <!-- techs-only -->
 
 
<!-- techs-only -->
 <!-- techs-only -->
 
<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 specification, including terms used in the <a href="#Conformance">Conformance</a>   section. Please consult <a href="http://www.w3.org/TR/qaframe-spec/">http://www.w3.org/TR/qaframe-spec/</a> for more information on the role of   definitions in specification quality.</p>

  </div> <!-- gl-only -->
   <!-- techs-only -->

  <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>Any 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).</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><span class="sc"><a class="termdef" href="#def-Content-Being-Edited" title="definition: web content being edited">web content being edited</a></span>. 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 (for more information see <a href="#conf-rel-wcag">WCAG 2.0</a>):
      <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> Web content 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 those 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: </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 &quot;aria-labeledby&quot;). </li>
	  </ul>

      <em>Note:</em> ATAG 2.0 typically refers to programmatically associated alternative content.</dd>

    <dt><dfn><a id="def-Ascii-Art" name="def-Ascii-Art"></a>ASCII art</dfn> <!-- [adapted from WCAG 2.0] --></dt> 
    <dd>A picture created by a spatial arrangement of characters or glyphs (typically from the 95 printable characters defined by ASCII). </dd> 
    
	<dt><a id="def-Assistive-Technology" name="def-Assistive-Technology"><dfn>assistive technology</dfn></a> <!-- [adapted from WCAG 2.0] --></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 users with disabilities. 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 may be used by people who have some physical disabilities;</li> 
        <li>alternative keyboards, which are used by people with certain physical disabilities to simulate the keyboard (including alternate keyboards that use head pointers, single switches, sip/puff and other special input devices);</li> 
        <li>alternative pointing devices, which are used by people with certain physical disabilities to simulate mouse pointing and button activations.</li> 
      </ul> 
    </dd> 
    
	<dt><a id="def-Audio" name="def-Audio"><dfn>audio</dfn></a> <!-- [adapted from WCAG 2.0] --></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> prevents <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 accessibility options, ignoring prompts 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, etc.), 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 also <a href="#part_b_applic_note_6">Part B Conformance Applicability Note 6: Multiple author 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 creating or 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>). 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>).</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 the 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:</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>. Some accessible authoring practices require <a href="#def-Accessibility-Information" title="definition: accessibility information" class="termdef">accessibility information</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 changes without starting another session. 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). Note that the end of the authoring session is distinct from publishing. <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 software (or <a href="#def-Collection-Software-Components" title="definition: collection of software components" class="termdef">collection
      of software components</a>) 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: &quot;collection of software components&quot;: </em>Multiple applications, plug-ins,   etc. can be used together to meet ATAG 2.0 (see also note in the   &quot;Required Components of an ATAG 2.0 Conformance Claim&quot;).<em><br />

      Note 2: &quot;alone or collaboratively&quot;: </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: &quot;to create or modify web content&quot;: </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: &quot;for use by other people&quot;: </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. &quot;Save as HTML&quot; 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 &quot;wizard&quot;-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 web sites (e.g. content management systems, courseware tools, content aggregators)</li>
        <li>email clients that send messages in 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, etc.)</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>, such as Windows, Mac OS, Java Virtual Machine, etc.</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> <!-- [harmonized with EARL 1.0] --></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. An authoring tool may support any combination of checking types.</li></ul></dd>
	
    <dt><a name="def-Collection-Software-Components" id="def-Collection-Software-Components"></a><dfn>collection
      of software components</dfn></dt>
    <dd> Any software programs that are used either together (e.g. base tool
      and <a href="#def-Plugin" title="definition: plug-in" class="termdef">plug-in</a>) or separately (e.g. <a href="#def-Markup" title="definition: markup" class="termdef">markup</a> editor,
      image editor, and validation tool), regardless of whether there has been
      any formal collaboration between the <a href="#def-Developer" title="definition: authoring tool developer" class="termdef">developers</a> of the software components.</dd>

    <dt><a name="def-Web-Content" id="def-Web-Content"></a><dfn>content (web content)</dfn> <!-- [adapted from WCAG 2.0] --></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> Web content that meets the <a href="#conf-rel-wcag">WCAG 2.0</a> success criteria (Level A, AA, or AAA).</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 web content (e.g. the attributes and contents of elements,  stylesheet information, etc.). </dd>

    <dt><a name="def-Structured-Web-Content" id="def-Structured-Web-Content"></a><dfn>content (structured)</dfn> </dt>
    <dd>Web content 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 <a class="termdef" href="#def-Web-Content" title="definition: web content">web
      content</a> to be rendered, played or executed  by <a href="#def-User-Agent" title="definition: user agent" class="termdef">user agents</a> (also may be referred to as &quot;content authoring&quot; or &quot;content editing&quot;).
    This may refer to  information perceived by <a href="#def-End-Users" title="definition: end user" class="termdef">end users</a> or to instructions for the user agents. Content may be author generated or automatically generated:
    <ul><li><dfn><a name="def-Content-Author-Gen" id="def-Content-Author-Gen"></a>author generated content:</dfn> When <a class="termdef" href="#def-Author" title="definition: author">authors</a> are fully responsible for the <a href="#def-Web-Content" title="definition: web content" class="termdef">web content</a> (e.g. typing <a href="#def-Markup" title="definition: markup" class="termdef">markup</a> into a source <a href="#def-Editing-View" title="definition: editing views" class="termdef">editing-view</a>, writing captions for audio, etc.).</li>

	<li><dfn><a name="def-Content-Auto-Gen" id="def-Content-Auto-Gen"></a>automatically generated content:</dfn> When programming by the <a href="#def-Developer" title="definition: authoring tool developer" class="termdef">authoring tool developer</a> is responsible for the <a class="termdef" href="#def-Web-Content" title="definition: web content">web
      content</a> (e.g. applying a <a href="#def-Template" title="definition: template" class="termdef">template</a>,
      automatically correcting <a href="#def-Markup" title="definition: markup" class="termdef">markup</a> errors, etc.).  </li></ul>
	  In some cases, responsibility for content generation is shared. For example, an <a class="termdef" href="#def-Author" title="definition: author">author</a> requests an interactive object be placed on their page (e.g. a photo album), the <a href="#def-Authoring-Tool" title="definition: authoring tool" class="termdef">authoring tool</a> applies a <a href="#def-Template" title="definition: template" class="termdef">template</a>, but the template requires input from the author to be complete.</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 <span class="sc"><a class="termdef" href="#def-Content-Being-Edited" title="definition: web content being edited">web content being edited</a></span>. ATAG 2.0 recognizes several types of content renderings:
	  <ul>
	  <li><dfn><a name="def-WYSIWYG" id="def-WYSIWYG"></a>conventional renderings (or &quot;WYSIWYG&quot;):</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 &quot;WYSIWYG&quot;, standing for &quot;What-you-see-is-what-you-get&quot; 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 wavefront); 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 either: 
	  <ul>
	    <li><a id="def-Optimizing-Transformation" name="def-Optimizing-Transformation"><dfn>optimized:</dfn></a> e.g. removing whitespace, re-compressing images; or </li>
	    <li><a id="def-Restructuring-Transformation" name="def-Restructuring-Transformation"><dfn>restructured:</dfn></a> e.g. linearizing tables, splitting a document into pages; or </li> 
	    <li><a id="def-Recoding-Transformation" name="def-Recoding-Transformation"><dfn>re-coded:</dfn></a> e.g. HTML to XHTML, a word processing format to HTML.</li> 
	  </ul></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 <a href="#def-Collection-Software-Components" title="definition: collection of software components" class="termdef">software components</a> 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 &quot;empty tag&quot; 
    (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> <!-- [adapted from WCAG 2.0] --></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> <!-- [adapted from WCAG 2.0] --></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> 
      <!-- [adapted from WCAG 2.0] -->
    </dt>
    <dd>An interface used by software to obtain keystroke input. A keyboard interface can allows keystroke input even if particular devices do not contain a conventional keyboard (e.g. a touchscreen PDA can have a keyboard interface built into its operating system to support onscreen keyboards as well as external keyboards that may be connected). 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> <!-- [adapted from WCAG 2.0] --></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> <!-- [adapted from WCAG 2.0] --></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> <!-- [adapted from WCAG 2.0] --></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> <!-- [adapted from WCAG 2.0] --></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> <!-- [harmonized with WCAG 2.0, UAAG 2.0] --></dt>

    <dd>Required for conformance. One may conform in a variety of well-defined ways to ATAG 2.0. Content identified as &quot;<a title="definition: informative" class="termdef" href="#def-Informative">informative</a>&quot; or &quot;non-normative&quot; 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, MacOS, Windows, etc.), mobile operating systems (e.g. Android, Blackberry, iOS, Windows Phone, etc.), 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 developers 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 OSX applications, Gnome Accessibility Toolkit API for Gnome applications, Java Access for Java applications, etc.). 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> <!-- [adapted from UAAG 2.0] --> </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 <span class="sc"><a class="termdef" href="#def-Content-Being-Edited" title="definition: web content being edited">web content being edited</a></span>. <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><dfn><a name="def-Presentation" id="def-Presentation"></a>presentation</dfn> <!-- [adapted from WCAG 2.0] --></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> <!-- [adapted from WCAG 2.0] --></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><strong class="handle">Processing content:</strong> 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><strong class="handle">Communication between the authoring tool and assistive technology:</strong> 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 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 users 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 &quot;at least as prominent&quot; as another component B when, from a default state, component A becomes displayed (and enabled) with the same number or less &quot;opening&quot; 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 on a dialog box, etc.) 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> &quot;Opening actions&quot; 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 &quot;opening actions&quot;.<br />

	    <em> Note 3:</em> Keyboard shortcuts to components in closed containers are not counted as &quot;opening actions&quot; because the components have no prominence when they are not displayed. The same is true when authors must use &quot;search&quot; to reveal components in closed containers.<br />
	    <em> Note 4:</em> The &quot;default state&quot; 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>. Well designed
      prompting will urge, suggest, and encourage authors.</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" in several success criteria in which absolute measurements may not be practical (e.g. the set of all help documentation examples, the set of all templates, etc.). 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> <!-- [adapted from WCAG 2.0] --></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>repairing (accessibility) </dfn> <!-- [harmonized with EARL 1.0] --></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 repairing,
      based on increasing levels of automation:
      <ul>

        <li><a name="def-Manual-Repairing" id="def-Manual-Repairing"></a><dfn>manual repairing:</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 repairing:</dfn> Where the repairs are partially carried out by the <a href="#def-Authoring-Tool" title="definition: authoring tool" class="termdef">authoring tool</a>, but where <a href="#def-Author" title="definition: authors" class="termdef">authors</a>' 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 repairing:</dfn> Where the repairs are carried out automatically by the <a href="#def-Authoring-Tool" title="definition: authoring tool" class="termdef">authoring tool</a> without any intervention by <a href="#def-Author" title="definition: authors" class="termdef">authors</a>.</li>
      </ul>
    </dd>
    <dt><a name="def-Restrictions" id="def-Restrictions"></a><dfn>restrictions, restricted web content authoring</dfn></dt>

    <dd>When the web content that authors can specify with an authoring tool either must include or must not include certain content (e.g. elements, attributes, widgets, etc). 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-Reversible-Actions" id="def-Reversible-Actions"></a><dfn>reversible
      actions</dfn></dt>
    <dd><a href="#def-Authoring-Action" title="definition: authoring actions" class="termdef">Authoring actions</a> that, by their nature, can be completely undone so that the system returns to the state it was
      in before the action. The opposite of reversible actions are:
	  <ul>
	    <li><dfn><a name="def-Irreversible-Actions" id="def-Irreversible-Actions"></a>irreversible actions:</dfn> Actions that cannot be reversed and may  include certain save and delete actions as well as actions made in a  collaborative environment that another <a href="#def-Author" title="definition: authors" class="termdef">author</a> has begun to work with.</li>
	  </ul></dd>
	  
    <dt><a name="def-Role" id="def-Role"></a><dfn>role</dfn> <!-- [adapted from WCAG 2.0] --></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>
        <!-- [adapted from UAAG 1.0] -->
    </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, etc.) 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> <!-- [harmonized with WCAG 2.0] --></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 end-user experiences that range from static web  pages to multimedia presentations to dynamic web applications.  Some common examples of web content technologies include  HTML, CSS, SVG, PNG, PDF, Flash, Silverlight, Flex and JavaScript.</dd>

    <dt><a id="def-Template" name="def-Template"><dfn>template</dfn></a>s</dt>
    <dd>Content patterns that are filled in by <a href="#def-Author" title="definition: authors" class="termdef">authors</a> or the authoring tool to produce  content 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 <a href="#def-Web-Content" title="definition: web content" class="termdef">web content</a> 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 <a href="#def-Author" title="definition: authors" class="termdef">author</a> 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 templates 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-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> <!-- [adapted from WCAG 2.0] --></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>. Examples include web browsers, browser plug-ins, and media players. </dd>
    <dt><a id="def-UI-Component" name="def-UI-Component"><dfn>user interface component</dfn></a> <!-- [adapted from WCAG 2.0] --></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> <!-- [adapted from WCAG 2.0] --></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 <span class="sc"><a class="termdef" href="#def-Content-Being-Edited" title="definition: web content being edited">web content being edited</a></span>. 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> View 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 none of the content is editable. Often the purpose is to present content as it would appear in a <a class="termdef" href="#def-User-Agent" title="definition: user agent">user
          agent</a>. </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 <a href="#def-Web-Content" title="definition: web content" class="termdef">content</a> is presented in unrendered form (e.g. plain text editors); or </li>
        <li><a name="def-Rendered-View" id="def-Rendered-View"></a><a href="#def-Content-Renderings" title="definition: content rendering" class="termdef"><dfn>rendered views:</dfn></a> <a href="#def-Content-Renderings" title="definition: content rendering" class="termdef">Content renderings (conventional, unconventional or partial)</a> 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 <a href="#def-Authoring-Tool" title="definition: authoring tool" class="termdef">authoring tool</a> then uses these properties to <a href="#def-Content-Auto-Gen" title="definition: content generation" class="termdef">automatically generate</a> the  <a href="#def-Web-Content" title="definition: web content" class="termdef">content</a> 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 <a href="#def-Collection-Software-Components" title="definition: collection of software components" class="termdef">collection
    of software components</a>, then its workflows may include use of one or more of the components. </dd>
  </dl>
  <hr /> 
</div> <!-- sect-definitions -->

<div class="gl-only"> 
<div id="sect-this-doc-ref"> 
  <h2><a id="this-doc-ref" name="this-doc-ref"></a>Appendix B: How to refer to ATAG 2.0 from other documents</h2> 
  <p>This section is <a href="#def-Informative" title="definition: informative" class="termdef">informative</a>. </p> 
  <p>There are two recommended ways to refer to the &quot;Authoring Tool Accessibility
    Guidelines 2.0&quot; (and to W3C documents in general):</p> 
  <ol> 
    <li>References to a specific version of &quot;Authoring Tool Accessibility
      Guidelines 2.0.&quot; For example, use the &quot;this version&quot; <acronym>URI</acronym> to
      refer to the current document:<br /> 
      <a href="http://www.w3.org/TR/2009/WD-ATAG20-20090521/">http://www.w3.org/TR/2011/WD-ATAG20-20110721/</a></li> 
    <li>References to the latest version of &quot;Authoring Tool Accessibility
      Guidelines 2.0.&quot; Use the &quot;latest version&quot; URI to refer to
      the most recently published document in the series: <br /> 
      <a href="http://www.w3.org/TR/ATAG20/">http://www.w3.org/TR/ATAG20/</a>.</li> 
  </ol> 
  <p>In almost all cases, references (either by name or by link) should be to
    a specific version of the document. W3C will make every effort to make this
 
    document indefinitely available at its original address in its original form.
    The top of this document includes the relevant catalog metadata for specific
    references (including title, publication date, &quot;this version&quot; <acronym>URI</acronym>,
    editors' names, and copyright information).</p> 
  <div id="example"> 
    <p>An XHTML 1.0 paragraph including a reference to this specific document
      might be written: </p> 
    <blockquote> 
      <p><code>&lt;p&gt;<br /> 
        &lt;cite&gt;&lt;a href=&quot;http://www.w3.org/TR/2011/WD-ATAG20-20110721/&quot;&gt;<br /> 
        &quot;Authoring Tool Accessibility Guidelines 2.0,&quot;&lt;/a&gt;&lt;/cite&gt;<br /> 
        J. Richards, J. Spellman, J. Treviranus, eds.,<br /> 
        W3C Recommendation, http://www.w3.org/TR/ATAG20/.<br /> 
        The &lt;a href=&quot;http://www.w3.org/TR/ATAG20/&quot;&gt;latest version&lt;/a&gt; of this document is available at http://www.w3.org/TR/ATAG20/.&lt;/p&gt; </code></p> 
    </blockquote> 
  </div> <!-- example -->

  
  <p>For very general references to this document (where stability of content
    and anchors is not required), it may be appropriate to refer to the latest
    version of this document. Other sections of this document explain how to build a <a href="#Conformance">conformance
    claim</a>.</p> 
  <hr /> 
</div> <!-- sect-this-doc-ref -->
</div> <!-- gl-only -->
<div id="sect-references"> 
  <h2><a id="references" name="references"></a>Appendix <span class="gl-only">C</span>: References</h2> 
  <p>This section is <a href="#def-Informative" title="definition: informative" class="termdef">informative</a>.</p> 
  <p>For the <strong>latest version</strong> of any <acronym title="the World Wide Web Consortium">W3C</acronym> specification please consult the list of <a href="http://www.w3.org/TR/"><acronym title="the World Wide Web Consortium">W3C</acronym> Technical Reports</a> at http://www.w3.org/TR/. Some documents listed below may have been superseded since the publication of this document.</p> 
  <dl><dt><a name="ref-ATAG10" id="ref-ATAG10"><strong>[ATAG10]</strong></a></dt> 
    <dd>&quot;<a href="http://www.w3.org/TR/2000/REC-ATAG10-20000203/">Authoring Tool Accessibility Guidelines 1.0</a>&quot;, J. Treviranus, C. McCathieNevile, I. Jacobs, and J. Richards, eds., 3 February 2000. This W3C Recommendation is available at http://www.w3.org/TR/2000/REC-ATAG10-20000203/.</dd> 
     
     
    <dt><a name="ref-UAAG" id="ref-UAAG"><strong>[UAAG]</strong></a></dt> 
    <dd>&quot;<a href="http://www.w3.org/TR/2002/REC-UAAG10-20021217/">User Agent Accessibility Guidelines
      1.0</a>,&quot; I. Jacobs, J. Gunderson, E. Hansen, eds.17 December 2002. This W3C Recommendation is available at http://www.w3.org/TR/2002/REC-UAAG10-20021217/. </dd> 
    <dt><a name="ref-WCAG20" id="ref-WCAG20"></a><strong>[WCAG20]</strong></dt> 
    <dd>&quot;<a href="http://www.w3.org/TR/WCAG20/">Web Content Accessibility Guidelines 2.0 </a>&quot;, B. Caldwell, M. Cooper, L. Guarino Reid, and G. Vanderheiden.</dd> 
  </dl> 

</div> <!-- sect-references -->
<hr /> 
 
<div id="sect-acknowledgments"> 
  <h2><a id="acknowledgments" name="acknowledgments"></a>Appendix <span class="gl-only">D</span>: Acknowledgments</h2> 
  <div class="gl-only"> 
  <h3><a name="appendix-editors" id="appendix-editors"></a>Appendix Editors:</h3> 
  <ul> 
    <li>Jan Richards (Adaptive Technology Resource Centre, University of Toronto)</li> 
    <li>Jeanne Spellman (W3C)</li>

    <li>Roberto Scano (IWA/HWG)</li> 
  </ul> 
</div><!-- gl-only --> 
  <h3><a name="active-participants" id="active-participants"></a>Participants active in the AUWG at the time of publication:</h3> 
  <ul> 
    <li>Tim Boland (National Institute for Standards and Technology)</li> 
    <li>Alastair Campbell (Nomensa) </li>
    <li>Cherie Ekholm (Microsoft)</li>
    <li>Alex Li (Microsoft) </li>

    <li>Alessandro Miele (Invited Expert) </li>
    <li>Sueann Nichols (IBM)</li>
    <li>Greg Pisocky (Adobe)</li> 
    <li>Sarah Pulis (Media Access Australia)</li>
    <li>Jan Richards (Inclusive Design Institute, OCAD University)</li> 
    <li>Andrew Ronksley (Royal National Institute for the Blind)</li> 
    <li>Roberto Scano (IWA/HWG)</li>

    <li>Jeanne Spellman (W3C) </li> 
    <li>Jutta Treviranus (WG Chair; Inclusive Design Institute, OCAD University)</li> 
  </ul> 
  <h3><a name="previous-participants" id="previous-participants"></a>Other previously active AUWG participants and other contributors to ATAG 2.0:</h3> 
  <p>Kynn Bartlett, Giorgio Brajnik, Judy Brewer, Wendy Chisholm, Daniel Dardailler, Geoff Deering, Barry A. Feigenbaum, Katie Haritos-Shea, Kip Harris, Phill Jenkins, Len Kasday, Marjolein Katsma, William Loughborough, Karen Mardahl, Matt May, Charles McCathieNevile, Ann McMeekin, Matthias M&uuml;ller-Prove, Liddy Nevile, Graham Oliver, Wendy Porch, Bob Regan, Chris Ridpath, Gregory Rosmaita, 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="http://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> <!-- sect-acknowledements -->
 

 

<div class="gl-only"> 
  <p align="center"> [<a href="#contents">Contents</a>] </p> 

</div> <!-- gl-only -->
 <!-- techs-only -->
 
</body> 
</html>