discontinued / server · Files

index.html 456 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 2119 2120 2121 2122 2123 2124 2125 2126 2127 2128 2129 2130 2131 2132 2133 2134 2135 2136 2137 2138 2139 2140 2141 2142 2143 2144 2145 2146 2147 2148 2149 2150 2151 2152 2153 2154 2155 2156 2157 2158 2159 2160 2161 2162 2163 2164 2165 2166 2167 2168 2169 2170 2171 2172 2173 2174 2175 2176 2177 2178 2179 2180 2181 2182 2183 2184 2185 2186 2187 2188 2189 2190 2191 2192 2193 2194 2195 2196 2197 2198 2199 2200 2201 2202 2203 2204 2205 2206 2207 2208 2209 2210 2211 2212 2213 2214 2215 2216 2217 2218 2219 2220 2221 2222 2223 2224 2225 2226 2227 2228 2229 2230 2231 2232 2233 2234 2235 2236 2237 2238 2239 2240 2241 2242 2243 2244 2245 2246 2247 2248 2249 2250 2251 2252 2253 2254 2255 2256 2257 2258 2259 2260 2261 2262 2263 2264 2265 2266 2267 2268 2269 2270 2271 2272 2273 2274 2275 2276 2277 2278 2279 2280 2281 2282 2283 2284 2285 2286 2287 2288 2289 2290 2291 2292 2293 2294 2295 2296 2297 2298 2299 2300 2301 2302 2303 2304 2305 2306 2307 2308 2309 2310 2311 2312 2313 2314 2315 2316 2317 2318 2319 2320 2321 2322 2323 2324 2325 2326 2327 2328 2329 2330 2331 2332 2333 2334 2335 2336 2337 2338 2339 2340 2341 2342 2343 2344 2345 2346 2347 2348 2349 2350 2351 2352 2353 2354 2355 2356 2357 2358 2359 2360 2361 2362 2363 2364 2365 2366 2367 2368 2369 2370 2371 2372 2373 2374 2375 2376 2377 2378 2379 2380 2381 2382 2383 2384 2385 2386 2387 2388 2389 2390 2391 2392 2393 2394 2395 2396 2397 2398 2399 2400 2401 2402 2403 2404 2405 2406 2407 2408 2409 2410 2411 2412 2413 2414 2415 2416 2417 2418 2419 2420 2421 2422 2423 2424 2425 2426 2427 2428 2429 2430 2431 2432 2433 2434 2435 2436 2437 2438 2439 2440 2441 2442 2443 2444 2445 2446 2447 2448 2449 2450 2451 2452 2453 2454 2455 2456 2457 2458 2459 2460 2461 2462 2463 2464 2465 2466 2467 2468 2469 2470 2471 2472 2473 2474 2475 2476 2477 2478 2479 2480 2481 2482 2483 2484 2485 2486 2487 2488 2489 2490 2491 2492 2493 2494 2495 2496 2497 2498 2499 2500 2501 2502 2503 2504 2505 2506 2507 2508 2509 2510 2511 2512 2513 2514 2515 2516 2517 2518 2519 2520 2521 2522 2523 2524 2525 2526 2527 2528 2529 2530 2531 2532 2533 2534 2535 2536 2537 2538 2539 2540 2541 2542 2543 2544 2545 2546 2547 2548 2549 2550 2551 2552 2553 2554 2555 2556 2557 2558 2559 2560 2561 2562 2563 2564 2565 2566 2567 2568 2569 2570 2571 2572 2573 2574 2575 2576 2577 2578 2579 2580 2581 2582 2583 2584 2585 2586 2587 2588 2589 2590 2591 2592 2593 2594 2595 2596 2597 2598 2599 2600 2601 2602 2603 2604 2605 2606 2607 2608 2609 2610 2611 2612 2613 2614 2615 2616 2617 2618 2619 2620 2621 2622 2623 2624 2625 2626 2627 2628 2629 2630 2631 2632 2633 2634 2635 2636 2637 2638 2639 2640 2641 2642 2643 2644 2645 2646 2647 2648 2649 2650 2651 2652 2653 2654 2655 2656 2657 2658 2659 2660 2661 2662 2663 2664 2665 2666 2667 2668 2669 2670 2671 2672 2673 2674 2675 2676 2677 2678 2679 2680 2681 2682 2683 2684 2685 2686 2687 2688 2689 2690 2691 2692 2693 2694 2695 2696 2697 2698 2699 2700 2701 2702 2703 2704 2705 2706 2707 2708 2709 2710 2711 2712 2713 2714 2715 2716 2717 2718 2719 2720 2721 2722 2723 2724 2725 2726 2727 2728 2729 2730 2731 2732 2733 2734 2735 2736 2737 2738 2739 2740 2741 2742 2743 2744 2745 2746 2747 2748 2749 2750 2751 2752 2753 2754 2755 2756 2757 2758 2759 2760 2761 2762 2763 2764 2765 2766 2767 2768 2769 2770 2771 2772 2773 2774 2775 2776 2777 2778 2779 2780 2781 2782 2783 2784 2785 2786 2787 2788 2789 2790 2791 2792 2793 2794 2795 2796 2797 2798 2799 2800 2801 2802 2803 2804 2805 2806 2807 2808 2809 2810 2811 2812 2813 2814 2815 2816 2817 2818 2819 2820 2821 2822 2823 2824 2825 2826 2827 2828 2829 2830 2831 2832 2833 2834 2835 2836 2837 2838 2839 2840 2841 2842 2843 2844 2845 2846 2847 2848 2849 2850 2851 2852 2853 2854 2855 2856 2857 2858 2859 2860 2861 2862 2863 2864 2865 2866 2867 2868 2869 2870 2871 2872 2873 2874 2875 2876 2877 2878 2879 2880 2881 2882 2883 2884 2885 2886 2887 2888 2889 2890 2891 2892 2893 2894 2895 2896 2897 2898 2899 2900 2901 2902 2903 2904 2905 2906 2907 2908 2909 2910 2911 2912 2913 2914 2915 2916 2917 2918 2919 2920 2921 2922 2923 2924 2925 2926 2927 2928 2929 2930 2931 2932 2933 2934 2935 2936 2937 2938 2939 2940 2941 2942 2943 2944 2945 2946 2947 2948 2949 2950 2951 2952 2953 2954 2955 2956 2957 2958 2959 2960 2961 2962 2963 2964 2965 2966 2967 2968 2969 2970 2971 2972 2973 2974 2975 2976 2977 2978 2979 2980 2981 2982 2983 2984 2985 2986 2987 2988 2989 2990 2991 2992 2993 2994 2995 2996 2997 2998 2999 3000 3001 3002 3003 3004 3005 3006 3007 3008 3009 3010 3011 3012 3013 3014 3015 3016 3017 3018 3019 3020 3021 3022 3023 3024 3025 3026 3027 3028 3029 3030 3031 3032 3033 3034 3035 3036 3037 3038 3039 3040 3041 3042 3043 3044 3045 3046 3047 3048 3049 3050 3051 3052 3053 3054 3055 3056 3057 3058 3059 3060 3061 3062 3063 3064 3065 3066 3067 3068 3069 3070 3071 3072 3073 3074 3075 3076 3077 3078 3079 3080 3081 3082 3083 3084 3085 3086 3087 3088 3089 3090 3091 3092 3093 3094 3095 3096 3097 3098 3099 3100 3101 3102 3103 3104 3105 3106 3107 3108 3109 3110 3111 3112 3113 3114 3115 3116 3117 3118 3119 3120 3121 3122 3123 3124 3125 3126 3127 3128 3129 3130 3131 3132 3133 3134 3135 3136 3137 3138 3139 3140 3141 3142 3143 3144 3145 3146 3147 3148 3149 3150 3151 3152 3153 3154 3155 3156 3157 3158 3159 3160 3161 3162 3163 3164 3165 3166 3167 3168 3169 3170 3171 3172 3173 3174 3175 3176 3177 3178 3179 3180 3181 3182 3183 3184 3185 3186 3187 3188 3189 3190 3191 3192 3193 3194 3195 3196 3197 3198 3199 3200 3201 3202 3203 3204 3205 3206 3207 3208 3209 3210 3211 3212 3213 3214 3215 3216 3217 3218 3219 3220 3221 3222 3223 3224 3225 3226 3227 3228 3229 3230 3231 3232 3233 3234 3235 3236 3237 3238 3239 3240 3241 3242 3243 3244 3245 3246 3247 3248 3249 3250 3251 3252 3253 3254 3255 3256 3257 3258 3259 3260 3261 3262 3263 3264 3265 3266 3267 3268 3269 3270 3271 3272 3273 3274 3275 3276 3277 3278 3279 3280 3281 3282 3283 3284 3285 3286 3287 3288 3289 3290 3291 3292 3293 3294 3295 3296 3297 3298 3299 3300 3301 3302 3303 3304 3305 3306 3307 3308 3309 3310 3311 3312 3313 3314 3315 3316 3317 3318 3319 3320 3321 3322 3323 3324 3325 3326 3327 3328 3329 3330 3331 3332 3333 3334 3335 3336 3337 3338 3339 3340 3341 3342 3343 3344 3345 3346 3347 3348 3349 3350 3351 3352 3353 3354 3355 3356 3357 3358 3359 3360 3361 3362 3363 3364 3365 3366 3367 3368 3369 3370 3371 3372 3373 3374 3375 3376 3377 3378 3379 3380 3381 3382 3383 3384 3385 3386 3387 3388 3389 3390 3391 3392 3393 3394 3395 3396 3397 3398 3399 3400 3401 3402 3403 3404 3405 3406 3407 3408 3409 3410 3411 3412 3413 3414 3415 3416 3417 3418 3419 3420 3421 3422 3423 3424 3425 3426 3427 3428 3429 3430 3431 3432 3433 3434 3435 3436 3437 3438 3439 3440 3441 3442 3443 3444 3445 3446 3447 3448 3449 3450 3451 3452 3453 3454 3455 3456 3457 3458 3459 3460 3461 3462 3463 3464 3465 3466 3467 3468 3469 3470 3471 3472 3473 3474 3475 3476 3477 3478 3479 3480 3481 3482 3483 3484 3485 3486 3487 3488 3489 3490 3491 3492 3493 3494 3495 3496 3497 3498 3499 3500 3501 3502 3503 3504 3505 3506 3507 3508 3509 3510 3511 3512 3513 3514 3515 3516 3517 3518 3519 3520 3521 3522 3523 3524 3525 3526 3527 3528 3529 3530 3531 3532 3533 3534 3535 3536 3537 3538 3539 3540 3541 3542 3543 3544 3545 3546 3547 3548 3549 3550 3551 3552 3553 3554 3555 3556 3557 3558 3559 3560 3561 3562 3563 3564 3565 3566 3567 3568 3569 3570 3571 3572 3573 3574 3575 3576 3577 3578 3579 3580 3581 3582 3583 3584 3585 3586 3587 3588 3589 3590 3591 3592 3593 3594 3595 3596 3597 3598 3599 3600 3601 3602 3603 3604 3605 3606 3607 3608 3609 3610 3611 3612 3613 3614 3615 3616 3617 3618 3619 3620 3621 3622 3623 3624 3625 3626 3627 3628 3629 3630 3631 3632 3633 3634 3635 3636 3637 3638 3639 3640 3641 3642 3643 3644 3645 3646 3647 3648 3649 3650 3651 3652 3653 3654 3655 3656 3657 3658 3659 3660 3661 3662 3663 3664 3665 3666 3667 3668 3669 3670 3671 3672 3673 3674 3675 3676 3677 3678 3679 3680 3681 3682 3683 3684 3685 3686 3687 3688 3689 3690 3691 3692 3693 3694 3695 3696 3697 3698 3699 3700 3701 3702 3703 3704 3705 3706 3707 3708 3709 3710 3711 3712 3713 3714 3715 3716 3717 3718 3719 3720 3721 3722 3723 3724 3725 3726 3727 3728 3729 3730 3731 3732 3733 3734 3735 3736 3737 3738 3739 3740 3741 3742 3743 3744 3745 3746 3747 3748 3749 3750 3751 3752 3753 3754 3755 3756 3757 3758 3759 3760 3761 3762 3763 3764 3765 3766 3767 3768 3769 3770 3771 3772 3773 3774 3775 3776 3777 3778 3779 3780 3781 3782 3783 3784 3785 3786 3787 3788 3789 3790 3791 3792 3793 3794 3795 3796 3797 3798 3799 3800 3801 3802 3803 3804 3805 3806 3807 3808 3809 3810 3811 3812 3813 3814 3815 3816 3817 3818 3819 3820 3821 3822 3823 3824 3825 3826 3827 3828 3829 3830 3831 3832 3833 3834 3835 3836 3837 3838 3839 3840 3841 3842 3843 3844 3845 3846 3847 3848 3849 3850 3851 3852 3853 3854 3855 3856 3857 3858 3859 3860 3861 3862 3863 3864 3865 3866 3867 3868 3869 3870 3871 3872 3873 3874 3875 3876 3877 3878 3879 3880 3881 3882 3883 3884 3885 3886 3887 3888 3889 3890 3891 3892 3893 3894 3895 3896 3897 3898 3899 3900 3901 3902 3903 3904 3905 3906 3907 3908 3909 3910 3911 3912 3913 3914 3915 3916 3917 3918 3919 3920 3921 3922 3923 3924 3925 3926 3927 3928 3929 3930 3931 3932 3933 3934 3935 3936 3937 3938 3939 3940 3941 3942 3943 3944 3945 3946 3947 3948 3949 3950 3951 3952 3953 3954 3955 3956 3957 3958 3959 3960 3961 3962 3963 3964 3965 3966 3967 3968 3969 3970 3971 3972 3973 3974 3975 3976 3977 3978 3979 3980 3981 3982 3983 3984 3985 3986 3987 3988 3989 3990 3991 3992 3993 3994 3995 3996 3997 3998 3999 4000 4001 4002 4003 4004 4005 4006 4007 4008 4009 4010 4011 4012 4013 4014 4015 4016 4017 4018 4019 4020 4021 4022 4023 4024 4025 4026 4027 4028 4029 4030 4031 4032 4033 4034 4035 4036 4037 4038 4039 4040 4041 4042 4043 4044 4045 4046 4047 4048 4049 4050 4051 4052 4053 4054 4055 4056 4057 4058 4059 4060 4061 4062 4063 4064 4065 4066 4067 4068 4069 4070 4071 4072 4073 4074 4075 4076 4077 4078 4079 4080 4081 4082 4083 4084 4085 4086 4087 4088 4089 4090 4091 4092 4093 4094 4095 4096 4097 4098 4099 4100 4101 4102 4103 4104 4105 4106 4107 4108 4109 4110 4111 4112 4113 4114 4115 4116 4117 4118 4119 4120 4121 4122 4123 4124 4125 4126 4127 4128 4129 4130 4131 4132 4133 4134 4135 4136 4137 4138 4139 4140 4141 4142 4143 4144 4145 4146 4147 4148 4149 4150 4151 4152 4153 4154 4155 4156 4157 4158 4159 4160 4161 4162 4163 4164 4165 4166 4167 4168 4169 4170 4171 4172 4173 4174 4175 4176 4177 4178 4179 4180 4181 4182 4183 4184 4185 4186 4187 4188 4189 4190 4191 4192 4193 4194 4195 4196 4197 4198 4199 4200 4201 4202 4203 4204 4205 4206 4207 4208 4209 4210 4211 4212 4213 4214 4215 4216 4217 4218 4219 4220 4221 4222 4223 4224 4225 4226 4227 4228 4229 4230 4231 4232 4233 4234 4235 4236 4237 4238 4239 4240 4241 4242 4243 4244 4245 4246 4247 4248 4249 4250 4251 4252 4253 4254 4255 4256 4257 4258 4259 4260 4261 4262 4263 4264 4265 4266 4267 4268 4269 4270 4271 4272 4273 4274 4275 4276 4277 4278 4279 4280 4281 4282 4283 4284 4285 4286 4287 4288 4289 4290 4291 4292 4293 4294 4295 4296 4297 4298 4299 4300 4301 4302 4303 4304 4305 4306 4307 4308 4309 4310 4311 4312 4313 4314 4315 4316 4317 4318 4319 4320 4321 4322 4323 4324 4325 4326 4327 4328 4329 4330 4331 4332 4333 4334 4335 4336 4337 4338 4339 4340 4341 4342 4343 4344 4345 4346 4347 4348 4349 4350 4351 4352 4353 4354 4355 4356 4357 4358 4359 4360 4361 4362 4363 4364 4365 4366 4367 4368 4369 4370 4371 4372 4373 4374 4375 4376 4377 4378 4379 4380 
<!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>Implementing 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"> 

 <!-- gl-only -->
<div class="techs-only"> 
 <p align="center">[<a href="#contents">Contents</a>] [<a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/Overview.html">Guidelines</a>]</p> 
    <p><a href="http://www.w3.org/"><img height="48" width="72" alt="W3C" src="http://www.w3.org/Icons/w3c_home"/></a></p> 
 
    <h1><a name="title" id="title"></a>Implementing ATAG 2.0</h1>
	<h2><a id="subtitle" name="subtitle"></a>A guide to understanding and implementing Authoring Tool Accessibility Guidelines 2.0</h2>
    <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-IMPLEMENTING-ATAG20-20110721/">http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/</a></dd> 
  <dt>Latest version:</dt> 
  <dd><a href="http://www.w3.org/TR/IMPLEMENTING-ATAG20/">http://www.w3.org/TR/IMPLEMENTING-ATAG20/</a></dd> 
  <dt>Previous version:</dt> 
  <dd><a href="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110426/">http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110426/</a></dd> 
      <dt>Editors:</dt> 
      <dd>Jutta Treviranus, <abbr title="Adaptive Technology Research Center">Inclusive Design Institute, OCAD University </abbr></dd> 
      <dd>Jan Richards, <abbr title="Adaptive Technology Research Center">Inclusive Design Institute, OCAD University </abbr></dd> 
      <dd>Jeanne Spellman, W3C</dd> 
      <dt>Previous Editors:</dt> 
      <dd>Tim  Boland, NIST</dd> 
      <dd>Matt May (until June 2005 while at <acronym title="World Wide Web Consortium">W3C</acronym>)</dd> 
      <dt>&nbsp;</dt> 
    </dl> 
	 <p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright"> Copyright</a> &#xa9;2011 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>&#xae;</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> <!-- techs-only -->

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

<div id="sect-abstract"> 
  <h2><a id="abstract" name="abstract">Abstract</a></h2> 
 <!-- gl-only -->
<div class="techs-only"> 
<p>This document provides non-normative information
    to authoring tool developers who wish to satisfy the success criteria in the  <a href="http://www.w3.org/TR/ATAG20/">Authoring
    Tool Accessibility Guidelines (ATAG) 2.0</a> <a href="#ref-ATAG20" title="reference: ATAG20"><cite>[ATAG20]</cite></a>.    This document  includes additional information about the intent of the success criteria, examples of how the success criteria might be satisfied, and
    references to other related resources.</p> 

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

<div class="techs-only"> 
<!-- COMMENT OUT FOR EDITORS' DRAFT  -->

<h3><a name="status-status" id="status-status"></a>W3C Public Draft of Implementing 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 Public Working Draft. </p>
  <p>The Working Group seeks feedback on the following points for this draft:</p>
  <ul>
    <li>Is the overall document a useful resource for implementers to apply ATAG 2.0 to your product? </li>
    <li>Are the sections describing the intent of each success criteria clear? </li>
    <li>Do you have any suggestions for examples that should be added, modified      or removed?</li>
  </ul>

<p>The <a href="http://www.w3.org/WAI/AU/">Authoring Tool Accessibility  Guidelines Working Group (AUWG)</a> intends to publish &quot;<em>Implementing ATAG  2.0</em>&quot; as a <acronym title="the World Wide Web Consortium">W3C</acronym> Note. The Working Group will continue to update this document   periodically in response to queries  raised by implementers of the   Guidelines, for example, to cover new  technologies. Suggestions for   additional examples or related resources are  welcome.</p>
  <p>Comments on the draft are welcome at <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>). Comments on this working draft are <strong>due on or before 15 September 2011</strong>. </p>
<!-- END COMMENT OUT FOR EDITOR'S DRAFT -->
</div> <!-- 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>. <span class="techs-only">The group does not expect this document to become a W3C Recommendation.</span> 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> 
 <!-- gl-only -->
<div class="techs-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">Implementing 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">Implementing ATAG 2.0 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></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="#prompting-types">Appendix A: Gathering Accessibility Information from Authors</a></li> 
<li><a href="#checking-types">Appendix B: Levels of Checking Automation</a></li> 
<li><a href="#repair-types">Appendix C: Levels of Repair Automation</a></li> 

<li><a href="#timing-options">Appendix D: Author Interruption Timing Options</a></li> 
<li><a href="#realtime-production">Appendix E: Authoring Tools for Live Web Content</a></li> 
<li><a href="#glossary">Appendix F: Glossary</a></li> 
<li><a href="#references">Appendix G: References</a></li> 
<li><a href="#acknowledgments">Appendix H: Acknowledgements</a></li> 
</ul> 
</div> <!-- techs-only -->
</div> <!-- toc -->
<hr /> 
<div id="sect-intro"> 
  <h2><a id="intro" name="intro">Introduction</a></h2> 

 <!-- gl-only -->
<div class="techs-only"> 
  <p>Implementing ATAG 2.0 is an essential guide to understanding and using <a href="http://www.w3.org/TR/ATAG20/">Authoring
    Tool Accessibility Guidelines (ATAG) 2.0</a> <a href="#ref-ATAG20" title="reference: ATAG20"><cite>[ATAG20]</cite></a>. Although the normative definitions and requirements for ATAG 2.0 can all  be found in the ATAG 2.0 document itself, the concepts and provisions may be new to some people. Implementing ATAG 2.0 provides a non-normative extended commentary on each guideline and each success  criterion to help readers better understand the intent and how the guidelines and success criteria work together. It also provides  illustrative examples for each success  criterion.</p>
  <p>This is not an introductory document. It is a detailed technical description of the guidelines and their success criteria. See <a href="http://www.w3.org/WAI/intro/atag.php">Authoring Tool Accessibility Guidelines (ATAG) Overview</a> for an introduction to ATAG 2.0, supporting  technical documents, and educational material. </p>

  <p>Implementing ATAG 2.0 is organized by guideline. There is an <em>Implementing Guideline X.X.X</em> section for each guideline. The rationale for the guideline is listed there. </p>
  <p>Each <em>Implementing Guideline X.X.X</em> section is then followed by an <em>Implementing Success Criterion X.X.X.X</em> section for each success criterion of that guideline. Each of these sections contains:</p>
  <ul>

    <li>Success criterion as it appears in ATAG 2.0</li>
    <li>Intent of the success criterion</li>
    <li>Examples</li>
    <li>Related resources</li>
  </ul>
  <p>Links are provided from each Guideline in ATAG 2.0 directly to each <em>Implementing Guideline X.X.X</em> in this document.  Similarly, there is a link from each success criterion in ATAG 2.0 to the <em>Implementing Success Criterion X.X.X.X</em> section in this document. </p>

  <h4 id="Notes-Intro"><a id="intro-notes" name="intro-notes"></a>Notes:</h4>
  <ol>
    <li>The Working Group encourages <a class="termdef" href="#def-Developer" title="definition: authoring tool developers">authoring tool developers</a> to carefully consider the examples provided, where appropriate. However, these examples do not provide a final definition of ATAG 2.0 conformance and it is possible to meet the guideline requirements without implementing these examples. <strong>The Working Group encourages implementers to submit example implementations. These examples will be considered for inclusion in future versions of this document.</strong></li>
    <li>Some &quot;Examples&quot; include &quot;mock ups&quot;. These are for informative purposes only and do not imply any endorsement of similar tools and they do not imply that the mock ups represent the best or only implementations.</li>

    <li> &quot;Related Resources&quot; are for information  purposes only, no endorsement is implied.</li>
    <li>For links to information on different disabilities and assistive technologies, see <a href="http://en.wikipedia.org/wiki/Disabilities">Disabilities on Wikipedia</a>. </li>
  </ol>
  </div> <!-- 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><span class="techs-only">Understanding </span>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). </p>

  <div class="techs-only">
  <p>As with <a href="#conf-rel-wcag">WCAG 2.0</a>, there are a number of conditions that must be met for a success criterion to be included in ATAG 2.0. These include:</p>
  <ol>
    <li> For <a href="#part_a">Part A</a>, all success criteria must present <strong>authoring tool user interface-related accessibility issues</strong>. In other words, the user interface issue must cause a   proportionately greater problem for <a class="termdef" href="#def-Author" title="definition: author">authors</a> with disabilities than it causes authors without disabilities and must be specific to authoring tool software, as opposed to software in general.</li>

    <li>For 
    <a href="#part_b">Part B</a>, all success criteria must present <strong>accessible web content production issues</strong>.  In other words, the issue must be specific to the production of <a class="termdef" href="#def-Accessible-Web-Content" title="definition: accessible web content">accessible web content (WCAG) </a> by authoring tools, as opposed to the production of <a class="termdef" href="#def-Web-Content" title="definition: web content">web content</a> in general.</li>
    <li>All success criteria must also be <strong>testable</strong>. This is important since otherwise   it would not be possible to determine whether an authoring tool met or failed to meet the   success criteria. The success criteria can be tested by a combination of machine and human evaluation as long as it is possible to determine whether a success criterion has been satisfied with a high level of confidence.</li>

  </ol>
  <p>The success criteria were assigned to one of the three levels of conformance by the Working Group after taking into consideration a wide range of interacting issues. Some of the common factors evaluated when setting the level in <a href="#part_a">Part A</a> included:</p>
  <ul>
    <li> whether the success criterion is <strong>essential</strong> (in other words, if the success criterion is not met, then even  <a class="termdef" href="#def-Assistive-Technology" title="definition: assistive technology">assistive
    technology</a> cannot make the authoring tool user interface accessible)</li>

    <li> whether it is possible to satisfy the success criterion for <strong>all types of authoring tools </strong> that the success criteria would apply to (e.g. <a class="termdef" href="#def-WYSIWYG" title="definition: WYSIWYG">WYSIWYG</a> editors, wikis, content management systems, etc.)</li>
    <li>whether the success criterion would impose limits on the &quot;look-and-feel&quot; and/or function of authoring tools (e.g. limits on the function, design, aesthetic or freedom of expression of <a class="termdef" href="#def-Developer" title="definition: authoring tool developers">authoring tool developers</a>)</li>

    <li> whether there are workarounds for authors with disabilities if the success criterion is not met</li>
  </ul>
  <p>Some of the common factors evaluated when setting the level   in <a href="#part_b">Part B</a> included:</p>
  <ul>
    <li> whether the success criterion is <strong>essential</strong> (in other words, if the success criterion is not met, then even authors with a high degree of accessibility expertise would be unlikely to produce <a class="termdef" href="#def-Accessible-Web-Content" title="definition: accessible web content">accessible  content (WCAG) </a> using an authoring tool) </li>

    <li> whether it is possible to satisfy the success criterion for the production of <strong>all <a href="#def-Web-Content-Technology" title="definition: technology (Web content)" class="termdef">web content technologies</a> </strong>that the success criteria would apply to.</li>
    <li> whether the success criterion requires features that would <strong>reasonably be used by authors</strong>.</li>
    <li>whether the success criterion would impose limits on the &quot;look-and-feel&quot; and/or function of authoring tools (e.g. limits on the function, design, aesthetic or freedom of expression of <a class="termdef" href="#def-Developer" title="definition: authoring tool developers">authoring tool developers</a>)</li>

  </ul> 
  </div>
  
  <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><span class="techs-only">Implementing ATAG 2.0 </span>Guidelines</h2> 
 
  <!-- gl-only -->
  <div class="techs-only"> 
    <p>The success criteria and the conformance applicability notes are included here for <a class="termdef" href="#def-Informative" title="definition: informative">informative</a> purposes. See Authoring Tool Accessibility Guidelines 2.0 <a href="#ref-ATAG20" title="reference: ATAG20"><cite>[ATAG20]</cite></a> for the normative version of this information.</p> 
  </div> <!-- techs-only -->

<div id="subsect-tool-accessible">
<h2><a name="part_a" id="part_a"></a><span class="techs-only">Implementing </span>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><span class="techs-only">Implementing </span>PRINCIPLE A.1: Authoring tool user interfaces must follow applicable accessibility guidelines </h2> 
 
    <h3 class="guideline"><a name="gl_a11" id="gl_a11"> </a><span class="techs-only">Implementing</span> Guideline A.1.1: (For the authoring tool user interface) Ensure that web-based functionality is accessible. 


<span class="techs-only">[<a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/Overview.html#gl_a11">Return to Guideline</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-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><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_a111">Return to A.1.1.1 in Guidelines</a></div>
	   </div>
<!--@@@-->	
	  
     <div class="techs-only">
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a111-i" name="sc_a111-i"></a>Intent of Success Criterion A.1.1.1:</h5> 
		<p>The intent of this success criterion is to ensure that authoring tool user interfaces that are fully or partially web-based  are accessible to authors with disabilities. Since WCAG 2.0 already provides requirements for the accessibility of web content, including web applications, those guidelines are referenced to avoid duplication of requirements.</p>
		</div>  
      <!-- techs-only -->

      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a111-e" name="sc_a111-e"></a>Examples of Success Criterion A.1.1.1:</h5>
            <ul>
              <li><strong class="handle">Wiki:</strong> A web-based wiki application is designed to conform to WCAG 2.0 Level A. During development, all parts of the user interface (including editing-views rendering test content) are tested by the developer using an accessibility evaluation harness for web applications. Periodically, the application is also tested by authors using assistive
    technologies.</li>
              <li><strong class="handle">Web-based help system:</strong> A non-web-based authoring tool includes a web-based help system. Each page in the help system is based on a template that was designed to conform to WCAG 2.0 Level A (when used) and the developer ensures that each help page passes an accessibility checker before being published. The developer confirms the accessibility of the final help system by spot-checking sample pages.</li>

            </ul>
      </div>  <!-- implementing-section -->
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a111-r" name="sc_a111-r"></a>Related Resources for Success Criterion A.1.1.1:</h5>
            <ul>
              <li><a href="#conf-rel-wcag">WCAG 2.0</a> (including <a href="http://www.w3.org/TR/2008/NOTE-UNDERSTANDING-WCAG20-20081211/">Understanding WCAG 2.0</a> and <a href="http://www.w3.org/WAI/WCAG20/quickref/Overview.php">How to Meet WCAG 2.0</a>)</li>

            </ul>
		</div> <!-- implementing-section -->
    </div> <!-- techs-only -->
	</div> <!-- sc-level -->
	<h3 class="guideline"><a name="gl_a12" id="gl_a12"> </a><span class="techs-only">Implementing</span> Guideline A.1.2: (For the authoring tool user interface) Ensure that non-web-based functionality is accessible. 
 

<span class="techs-only">[<a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/Overview.html#gl_a12">Return to Guideline</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><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_a121">Return to A.1.2.1 in Guidelines</a></div>
	   </div>
	   
      <div class="techs-only">
       <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a121-i" name="sc_a121-i"></a>Intent of Success Criterion A.1.2.1:</h5> 
		<p>The intent of this success criterion is to ensure that authoring tool user interfaces that are not web applications are accessible to authors with disabilities. Existing accessibility guidelines are referenced because:</p>
		<ol type="a">
          <li>accessibility guidelines already exist for many platforms, </li>
		  <li>this  wording allows developers the flexibility to conform with accessibility legislation in their markets.</li>
		  <li>the note that conformance claims must cite the accessibility guidelines that were followed should encourage developers to refrain from implementing obscure or weak requirements.</li>
		  </ol>
		<p><em>Note:</em> Developers should see the documents listed in the &quot;<a href="#sc_a121-r">Related Resources for Success Criterion A.1.2.1</a>&quot; section. Unless extenuating circumstances exist (e.g. a document has been superseded, the platform has undergone major architectural changes), the listed resources should be assumed to be relevant to the platforms listed. </p>
       </div> 
       <!-- implementing-section -->
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a121-e" name="sc_a121-e"></a>Examples of Success Criterion A.1.2.1:</h5>
            <ul>
              <li><strong class="handle">Mobile authoring tool:</strong> The developer of an authoring tool on the iPhone platform follows the guidance in the &quot;Accessibility Programming Guide for iPhone OS&quot;. </li>
            </ul>
        </div> <!-- implementing-section -->
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a121-r" name="sc_a121-r"></a>Related Resources for Success Criterion A.1.2.1:</h5>

          <ul>
              <li>The following is a non-exhaustive list of accessibility guidelines for various platforms (for additional information related to keyboard shortcuts on various platforms, see the Related Resources for <a href="#sc_a313">Success Criterion A.3.1.3</a>):
                <ul>
                    <li>Desktop OS
                      <ul>
                        <li><strong class="handle">Gnome Desktop on Linux:</strong> <a href="http://developer.gnome.org/accessibility-devel-guide/">GNOME Accessibility Developers Guide</a></li>
                        <li><strong class="handle">KDE  Desktop on Linux:</strong> <a href="http://accessibility.kde.org/developer/">Developer's Information</a></li>
                        <li><strong class="handle">Mac OS:</strong> <a href="http://developer.apple.com/library/mac/documentation/Accessibility/Conceptual/AccessibilityMacOSX/OSXAXIntro/OSXAXintro.html">Accessibility Overview</a></li>
                        <li><strong class="handle">Microsoft Windows:</strong> <a href="http://msdn.microsoft.com/en-us/windows/bb735024.aspx">Accessibility Overview</a></li>
                      </ul>
                    </li>
                    <li>Mobile OS
                      <ul>
                        <li><strong class="handle">Android:</strong> <a href="http://developer.android.com/guide/practices/design/accessibility.html">Android Developers: Designing for Accessibility</a></li>
                        <li><strong class="handle">BlackBerry:</strong> <a href="http://us.blackberry.com/support/devices/blackberry_accessibility/">BlackBerry Accessibility</a> </li>
                        <li><strong class="handle"></strong><strong class="handle">iPhone OS:</strong> <a href="http://developer.apple.com/library/ios/documentation/UserExperience/Conceptual/iPhoneAccessibility/Accessibility_on_iPhone/Accessibility_on_iPhone.html">Accessibility Programming Guide for iPhone OS</a></li>
                      </ul>
                    </li>
                    <li>Cross-OS environments
                      <ul>
                        <li><strong class="handle">Eclipse:</strong> <a href="http://www.eclipse.org/articles/article.php?file=Article-Accessibility/index.html">Designing Accessible Plug-ins in Eclipse</a></li>
                        <li><strong class="handle">Java SE:</strong> <a href="http://java.sun.com/javase/technologies/accessibility/index.jsp">Java SE Desktop Accessibility</a></li>
                        <li><strong class="handle">Lotus Notes:</strong> <a href="http://www-03.ibm.com/able/guidelines/notes/accessr5.html">Lotus Notes Checklist</a></li>
                      </ul>
                    </li>
                </ul>
</li>
              <li>The following is a non-exhaustive list of general software accessibility guidelines:
                <ul>
                  <li><a href="http://www.iso.org/iso/iso_catalogue/catalogue_ics/catalogue_detail_ics.htm?csnumber=39080">ISO 9241-171:2008 Ergonomics of human-system interaction - Part 171: Guidance on software accessibility</a></li>
                  <li><a href="http://www-03.ibm.com/able/guidelines/software/accesssoftware.html">Software Checklist (IBM)</a> </li>
                  <li><a href="http://www.section508.gov/index.cfm?fuseAction=stdsdoc#Software">Section 508 §1194.21 Software applications and operating systems</a> </li>

                  <li>The WAI <a href="http://www.w3.org/WAI/Policy/">International Policies Relating to Web Accessibility </a>resource includes links to various international legislation and other policies that may include applicable accessibility guidelines for non-web-based functionality.</li>
                </ul>
              </li>
          </ul>
</div> <!-- implementing-section -->
      </div> <!-- techs-only -->

      <h4 class="sc-title"><a id="sc_a122" name="sc_a122"></a><span class="techs-only">Implementing Success Criterion </span>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> 
      <div class="techs-only">
	   
	   <div class="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_a122">Return to A.1.2.2 in Guidelines</a></div>
	   </div>
	   
       <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a122-i" name="sc_a122-i"></a>Intent of Success Criterion A.1.2.2:</h5> 
		<p>The intent of this success criterion is to ensure that authoring tool user interfaces that are not web applications are accessible to authors with disabilities who use assistive technologies that communicate with software via platform accessibility services. The requirement is stated generally because the specifics of what constitutes a platform accessibility service will differ on each platform. </p>
		<p>The note that conformance claims must cite  the platform accessibility service(s) implemented should encourage developers to refrain from implementing services that are not supported by assistive technologies.</p>
       </div> <!-- implementing-section -->
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a122-e" name="sc_a122-e"></a>Examples of Success Criterion A.1.2.2:</h5>

            <ul>
              <li><strong class="handle">WYSIWYG editor on Mac OS:</strong> A WYSIWYG text editor is designed in Cocoa following the Mac OS X accessibility framework including using Accessibility Objects setting   attributes for Role, Role Description, Description, Title, Relationship and Value. The conformance claim includes links to the Accessibility Programming Guidelines for Cocoa.<br />
              </li>
              <li><strong class="handle">Content management system on Windows:</strong> Content management system on Windows: A content management system is written to operate on the Windows operating systems following Microsoft Windows' accessibility API, UI Automation, Microsoft Active Accessibility, or IAccessible 2. The conformance claim includes links to the applicable Microsoft Developer Network documents. </li>
            </ul>
        </div> <!-- implementing-section -->

      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a122-r" name="sc_a122-r"></a>Related Resources for Success Criterion A.1.2.2:</h5>
          <ul>
              <li>The following is a non-exhaustive list of documents related to communication with platform accessibility services for various platforms:
                <ul>
                    <li>Desktop OS
                      <ul>
                          <li><strong class="handle">Gnome Desktop on Linux:</strong> <a href="http://developer.gnome.org/accessibility-devel-guide/">GNOME Accessibility Developers Guide</a></li>
                        <li><strong class="handle">KDE  Desktop on Linux:</strong> <a href="http://accessibility.kde.org/developer/">Developer's Information</a></li>
                        <li><strong class="handle">Mac OS:</strong> <a href="http://developer.apple.com/library/mac/documentation/Accessibility/Conceptual/AccessibilityMacOSX/OSXAXIntro/OSXAXintro.html">Accessibility Overview</a></li>
                        <li><strong class="handle">Microsoft Windows:</strong> <a href="http://msdn.microsoft.com/en-us/windows/bb735024.aspx">Accessibility Overview</a></li>
                      </ul>
                    </li>
                    <li>Mobile OS
                      <ul>
                          <li><strong class="handle">Android:</strong> <a href="http://developer.android.com/reference/android/accessibilityservice/package-summary.html">Example from Android Developer Reference</a><a href="http://developer.android.com/guide/practices/design/accessibility.html"></a></li>
                        <li><strong class="handle">BlackBerry:</strong> <a href="http://us.blackberry.com/support/devices/blackberry_accessibility/">BlackBerry Accessibility</a> </li>
                        <li><strong class="handle"></strong><strong class="handle">iPhone OS:</strong> <a href="http://developer.apple.com/library/ios/documentation/UserExperience/Conceptual/iPhoneAccessibility/Accessibility_on_iPhone/Accessibility_on_iPhone.html">Accessibility Programming Guide for iPhone OS</a></li>
                      </ul>
                    </li>
                    <li>Cross-OS environments
                      <ul><li><strong class="handle">Java SE:</strong> <a href="http://java.sun.com/javase/technologies/accessibility/index.jsp">Java SE Desktop Accessibility</a></li>
                      </ul>
                    </li>
                </ul>
</li>
</ul>
</div> <!-- implementing-section -->
      </div> <!-- techs-only -->
    </div>  <!-- sc-level -->
    <h2 class="principle"><a name="principle_a2" id="principle_a2"></a><span class="techs-only">Implementing </span>PRINCIPLE A.2: Editing-views must be perceivable </h2> 
    
    <h3 class="guideline"><a name="gl_a21" id="gl_a21"> </a><span class="techs-only">Implementing</span> Guideline A.2.1: (For the authoring tool user interface) Make alternative content available to authors. 

 
<span class="techs-only">[<a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/Overview.html#gl_a21">Return to Guideline</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><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_a211">Return to A.2.1.1 in Guidelines</a></div>
	   </div>

	  <div class="techs-only"> 
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a211-i" name="sc_a211-i"></a>Intent of Success Criterion A.2.1.1: </h5>
		<p>The intent of this success criterion is to ensure that authors with disabilities have access to text alternatives for non-text content within the web content that they are editing, because this information can help  authors orient and navigate as they edit. </p>
		<p>The term &quot;programmatically associated&quot;  is simply a reminder that text alternatives may appear within  web content in ways that authoring tools are not able to detect (e.g. when the information conveyed by an image is described in an adjacent paragraph).</p>
		</div> 
      <!-- implementing-section -->

      <div class="implementing-section">		
        <h5 class="implementing-heading"><a id="sc_a211-e" name="sc_a211-e"></a>Examples of Success Criterion A.2.1.1:</h5>
            <ul>
              <li><strong class="handle">WYSIWYG editing-view:</strong> A WYSIWYG editing-view renders images in the content being edited. If an image includes alternative text, this information is exposed to assistive technologies via the platform accessibility service. </li>
            </ul>
        </div>  <!-- implementing-section -->
      <div class="implementing-section">

        <h5 class="implementing-heading"><a id="sc_a211-r" name="sc_a211-r"></a>Related Resources for Success Criterion A.2.1.1:</h5>
            <ul>
              <li><a href="http://www.w3.org/TR/UAAG10/">User Agent Accessibility Guidelines (UAAG) 1.0</a>.</li>
              <li><a href="#conf-rel-wcag">WCAG 2.0</a> (including <a href="http://www.w3.org/TR/2008/NOTE-UNDERSTANDING-WCAG20-20081211/">Understanding WCAG 2.0</a> and <a href="http://www.w3.org/WAI/WCAG20/quickref/Overview.php">How to Meet WCAG 2.0</a>), especially <a href="http://www.w3.org/TR/WCAG20/#text-equiv">WCAG 2.0 Guideline 1.1</a> and the section <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance.html#uc-text-alternatives-head">Understanding &quot;Text Alternatives&quot;</a>. </li>

            </ul>
        </div>  <!-- implementing-section -->
      </div> <!-- techs-only -->

	  <h4 class="sc-title"><a id="sc_a212" name="sc_a212"></a><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_a212">Return to A.2.1.2 in Guidelines</a></div>
	   </div>

	  <div class="techs-only"> 
      <div class="implementing-section">

        <h5 class="implementing-heading"><a id="sc_a212-i" name="sc_a212-i"></a>Intent of Success Criterion A.2.1.2: </h5>
		<p>The intent of this success criterion is to ensure that authors with disabilities have access to alternatives for rendered time-based content in the web content that they are editing, because this information can help  authors orient and navigate as they edit.</p>
		<p>There are two ways to meet this success criterion. </p>

		<p>Option (a) is to render the alternatives in conjunction with the rendered time-based content. For example, a captioned video would have its captions displayed when it played. This approach is preferable, since it does not require authors to switch applications. </p>
		<p>Option (b) is to instead provide authors with the option of rendering their content in a user agent that is able to render the alternatives. While this is not ideal from a usability perspective, it is necessary because alternatives are sometimes provided in different modalities that authoring tools are not equipped to render. For example, an audio editor might allow authors to edit the waveform of the audio file and render (i.e., play) the resulting audio files. However, the audio editor might not be equipped to render video, so if an audio file includes an alternative that is a sign language file in video format, the audio editor will need assistance in rendering the file.</p>
      </div> 
      <!-- implementing-section -->

      <div class="implementing-section">		
        <h5 class="implementing-heading"><a id="sc_a212-e" name="sc_a212-e"></a>Examples of Success Criterion A.2.1.2:</h5>
            <ul>
              <li><strong class="handle">Web-based WYSIWYG:</strong> A web-based WYSIWYG editing-view is implemented so that videos placed into the content are rendered. If the videos include captions these are displayed, meeting (a).</li>
              <li><strong class="handle">Audio editor:</strong> An audio editor allows authors to edit audio tracks using the audio waveform. At any time, authors can play the audio file. Sometimes the audio files include a link to a video file that contains an alternative version (e.g. sign language). Although the audio editor does not include the functionality to natively render the video it provides the option to launch the video in a user agent specified by the author, meeting (b). </li>
            </ul>

        </div>  <!-- implementing-section -->
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a212-r" name="sc_a212-r"></a>Related Resources for Success Criterion A.2.1.2:</h5>
            <ul>
              <li><a href="http://www.w3.org/TR/UAAG10/">User Agent Accessibility Guidelines (UAAG) 1.0</a>.</li>
              <li><a href="#conf-rel-wcag"></a><a href="#conf-rel-wcag">WCAG 2.0</a> (including <a href="http://www.w3.org/TR/2008/NOTE-UNDERSTANDING-WCAG20-20081211/">Understanding WCAG 2.0</a> and <a href="http://www.w3.org/WAI/WCAG20/quickref/Overview.php">How to Meet WCAG 2.0</a>), especially <a href="http://www.w3.org/TR/WCAG20/#media-equiv">WCAG 2.0 Guideline 1.2</a>. </li>

            </ul>
        </div>  <!-- implementing-section -->
      </div> <!-- techs-only -->
	  
    </div> <!-- sc-level -->
    <h3 class="guideline"><a name="gl_a22" id="gl_a22"> </a><span class="techs-only">Implementing</span> Guideline A.2.2: (For the authoring tool user interface) Editing-view presentation can be programmatically determined. 
 

<span class="techs-only">[<a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/Overview.html#gl_a22">Return to Guideline</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><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_a221">Return to A.2.2.1 in Guidelines</a></div>
	   </div>
	   
        <div class="techs-only"> 
      <div class="implementing-section">

        <h5 class="implementing-heading"><a id="sc_a221-i" name="sc_a221-i"></a>Intent of Success Criterion A.2.2.1: </h5>
		<p>The intent of this success criterion is to ensure that, if the authoring tool makes changes to the display of the web content being edited in order to communicate status information with authors (e.g. to highlight spelling errors, identify the location of markup tags, etc.), then authors with disabilities will have the same access to that information  as other authors.</p>
		</div>  <!-- implementing-section -->
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a221-e" name="sc_a221-e"></a>Examples of Success Criterion A.2.2.1:</h5>
            <ul>
              <li><strong class="handle">Change tracking feature:</strong> A web-based authoring tool includes a change tracking feature that displays inserted text in green and deleted text in red with a strike-through style. Instead of implementing this using simple CSS selectors, the authoring tool uses the XHTML elements <code>ins</code> and <code>del</code>, since these have semantic meaning.</li>

            </ul>
        </div>  <!-- implementing-section -->
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a221-r" name="sc_a221-r"></a>Related Resources for Success Criterion A.2.2.1:</h5>
            <ul>
              <li>For web-based authoring tools, see <a href="#conf-rel-wcag">WCAG 2.0</a> (including <a href="http://www.w3.org/TR/2008/NOTE-UNDERSTANDING-WCAG20-20081211/">Understanding WCAG 2.0</a> and <a href="http://www.w3.org/WAI/WCAG20/quickref/Overview.php">How to Meet WCAG 2.0</a>), especially <a href="http://www.w3.org/TR/2008/REC-WCAG20-20081211/#content-structure-separation-programmatic">WCAG 2.0 Success Criterion 1.3.1</a>.</li>

            </ul>
        </div>  <!-- implementing-section -->
        </div>  <!-- techs-only -->
        <h4 class="sc-title"><a id="sc_a222" name="sc_a222"> </a><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_a222">Return to A.2.2.2 in Guidelines</a></div>
	   </div>

        <div class="techs-only"> 
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a222-i" name="sc_a222-i"></a>Intent of Success Criterion A.2.2.2: </h5>
		<p>The intent of this success criterion is to ensure that authors with disabilities have access to text presentation information when this information is already made available to other authors by editing-views. This is important because this type of rendering acts as a type of preview to help authors understand how their content may appear to end users, once it is published. Authors who cannot see also need to understand how their web content will be experienced by end users who can see. </p>
		<p><em>Note:</em> This success criterion pertains to the rendered properties of text on the screen, even if the properties differ from the  content being edited (e.g. when authors chose custom display settings as per <a href="#sc_a361">Success Criterion A.3.6.1</a>). In this way, the views provided on screen and via any assistive technologies can remain synchronized. </p>
      </div>  <!-- implementing-section -->

      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a222-e" name="sc_a222-e"></a>Examples of Success Criterion A.2.2.2:</h5>
            <ul>
              <li><strong class="handle">Non-web-based authoring tool:</strong>
			  A non-web-based authoring tool includes a WYSIWYG editing-view that implements the appropriate platform accessibility service. Included in the information passed to the platform accessibility service is information on the size, font, foreground and background color, font weight, and position of any rendered text.</li>
              <li><strong class="handle">Web-based authoring tool:</strong>
			  A web-based WYSIWYG authoring tool uses style sheets to control text presentation, enabling the presentation information to be programmatically determined by the user agent, which then passes it on to the appropriate platform accessibility service.  The user agent is cited in any <a href="#conf-claim">conformance claim</a>.</li>

            </ul>
        </div> <!-- implementing-section -->
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a222-r" name="sc_a222-r"></a>Related Resources for Success Criterion A.2.2.2:</h5>
            <ul>
              <li>N/A</li>
            </ul>

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

<h2 class="principle"><a name="principle_a3" id="principle_a3"> </a><span class="techs-only">Implementing </span>PRINCIPLE A.3: Editing-views must be operable</h2> 
    
    <h3 class="guideline"><a name="gl_a31" id="gl_a31"> </a><span class="techs-only">Implementing</span> Guideline A.3.1: (For the authoring tool user interface) Provide keyboard access to authoring features. <span class="techs-only">[<a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/Overview.html#gl_a31">Return to Guideline</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><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_a311">Return to A.3.1.1 in Guidelines</a></div>
	   </div>
	   
      <div class="techs-only">
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a311-i" name="sc_a311-i"></a>Intent of Success Criterion A.3.1.1 (Based on WCAG 2.0, Success Criterion 2.1.1):</h5> 
		<p>The intent of this success criterion is to ensure that almost all authoring tool functionality can be operated using a keyboard or an assistive technology that makes use of a keyboard interface, such as onscreen scanning keyboards and voice recognition systems. </p>

		<p>The only exemption at Level A to this requirement involves functions that require input that depends on the path of the user's movement and not just the endpoints. This is a very narrow exception that relates to authoring web content properties that contain hundreds or thousands of numerical values. The exception exists because it is not reasonable to expect that authors using only a keyboard would be prepared to hand-code so many data points. The exception  does not apply simply because the developers of an authoring tool have decided to use mouse input to control functionality in the past (e.g. setting the endpoints for straight lines, rectangles and circles). The exception also does not apply simply because a functionality is related to graphics. Also, the exception applies to the editing of particular properties. While editing the path of a freehand curve may be exempt, setting the line color and thickness likely would not be exempt. Finally, this is a Level A exception only. There is no exception for the Level AAA requirement (<a href="#sc_a314">Success Criterion A.3.1.4</a>).</p>
		<p>Note 1 clarifies that the exception applies to the underlying function and that pointing device input variables, such as pressure, speed and angle, are also covered.</p>
		<p>Note 2 clarifies that rather than replacing other types of interaction, the keyboard access requirement is to provide an alternative.</p>
		<p>Web-based authoring tools will already  be required to meet this success criterion as part of <a href="#sc_a111">Success Criterion A.1.1.1</a>.</p>
      </div> <!-- implementing-section -->

      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a311-e" name="sc_a311-e"></a>Examples of Success Criterion A.3.1.1:</h5>
            <ul>
              <li><strong class="handle">Drag-and-drop feature:</strong> An authoring tool allows authors to open documents by dragging them into the authoring tool window. The same operation can be performed from the menus using the keyboard.</li>
              <li><strong class="handle">Keyboard manipulation of drawing objects:</strong> A multimedia authoring tool allows authors to navigate the selection focus between all of the drawing objects on the canvas. Once an object is selected, it can be manipulated with keyboard-driven menu commands, some of which have keyboard shortcuts (e.g. arrow keys to move the object, etc.). New drawing objects can also be added from the keyboard-driven menus.</li>

              <li><strong class="handle">Keyboard manipulation of drawing object properties:</strong> A multimedia authoring tool does not include keyboard access to the drawing canvas directly, but instead provides a keyboard accessible list of drawing objects that allows a keyboard editable property page to be brought up. The property pages include properties such as &quot;top&quot;, &quot;left&quot;, &quot;width&quot;, &quot;height&quot;, &quot;rotation&quot;, and &quot;label&quot;. When these properties are adjusted, the objects on the canvas are updated accordingly. New drawing objects can be added   from the keyboard-driven menus. </li>

              <li><strong class="handle">Select and operate:</strong> An authoring tool provides editing functionality in which authors can select content in the editing-view (e.g. select text) and then perform an operation (i.e. authoring action) on that selection (e.g. formatting, deletion, etc.). Keyboard access to this functionality is enabled by the fact that the selection can be made using the keyboard and that the selection is maintained while the author uses the keyboard to navigate the authoring tool user interface to arrive at the operation they want to perform.<br />
              </li>
            </ul>
        </div> <!-- implementing-section -->
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a311-r" name="sc_a311-r"></a>Related Resources for Success Criterion A.3.1.1:</h5>

            <ul>
              <li>For web-based authoring tools, see <a href="#conf-rel-wcag">WCAG 2.0</a> (including <a href="http://www.w3.org/TR/2008/NOTE-UNDERSTANDING-WCAG20-20081211/">Understanding WCAG 2.0</a> and <a href="http://www.w3.org/WAI/WCAG20/quickref/Overview.php">How to Meet WCAG 2.0</a>), especially <a href="http://www.w3.org/TR/2008/REC-WCAG20-20081211/#keyboard-operation-keyboard-operable">WCAG 20 Success Criterion 2.1.1</a>. </li>
            </ul>

        </div> <!-- implementing-section -->
      </div>

      <h4 class="sc-title"><a id="sc_a312" name="sc_a312"></a><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_a312">Return to A.3.1.2 in Guidelines</a></div>
	   </div>
	   
      <div class="techs-only">
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a312-i" name="sc_a312-i"></a>Intent of Success Criterion A.3.1.2 (Modified from WCAG 2.0, Success Criterion 2.1.2):</h5> 
		<p>The intent of this success criterion is to ensure that neither the authoring tool's own user interface nor any rendered web content within editing-views &quot;traps&quot; keyboard focus. This problem may occur when an interactive object is  embedded in   content. Authors might be able to move focus to the object (e.g. by using the &quot;tab&quot; key) within a WYSIWYG editing-view, but  they are unable to move the focus out using the keyboard, because keyboard control has passed to the embedded object.</p>
		<p>The first requirement (a) applies only to the authoring tool user interface, which is the part of the authoring tool that developers have the most control over. In this case, there  must not be any keyboard traps. If authors can move focus to a component using standard keyboard navigation commands (e.g. using the tab key), then they must be able to move focus out of the component in the same way or be advised of the method. </p>

		<p>The second requirement (b) applies to renderings of  content. Because the  content may contain keyboard handlers, the authoring tool may not be able to prevent keyboard traps entirely. Therefore, the requirement is only that the authoring tool be able to restore the keyboard focus to some known location.</p>
      </div> <!-- implementing-section -->
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a312-e" name="sc_a312-e"></a>Examples of Success Criterion A.3.1.2:</h5>
            <ul>
              <li><strong class="handle">Non-web-based authoring tool:</strong> A non-web-based authoring tool has a user interface that has been thoroughly tested by the developer to ensure that no keyboard traps exist, meeting (a). If authors open web content containing keyboard traps in the WYSIWYG editing-view, the authoring tool allows authors to restore keyboard focus to the top of the editing-view at any time by pressing the &quot;Home&quot; key, which the authoring tool never passes to the content being edited, meeting (b).</li>

              <li><strong class="handle">Web-based authoring tool:</strong> A web-based authoring tool has a user interface that has been thoroughly tested by the developer to ensure that no keyboard traps exist, meeting (a). If authors open  content containing keyboard traps, the authoring tool relies on a feature in the authors' user agent that always restores keyboard focus to the address bar, meeting (b). The user agent is cited in any <a href="#conf-claim">conformance claim</a>.</li>
            </ul>
        </div> <!-- implementing-section -->
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a312-r" name="sc_a312-r"></a>Related Resources for Success Criterion A.3.1.2:</h5>

            <ul>
              <li>For web-based authoring tools, see <a href="#conf-rel-wcag">WCAG 2.0</a> (including <a href="http://www.w3.org/TR/2008/NOTE-UNDERSTANDING-WCAG20-20081211/">Understanding WCAG 2.0</a> and <a href="http://www.w3.org/WAI/WCAG20/quickref/Overview.php">How to Meet WCAG 2.0</a>), especially <a href="http://www.w3.org/TR/2008/REC-WCAG20-20081211/#keyboard-operation-trapping">WCAG 2.0 Success Criterion 2.1.2</a>. </li>
            </ul>

        </div> <!-- implementing-section -->
      </div>
    </div><!-- sc-level -->
		
    <div class="sc-level">
      <h4 class="sc-title"><a id="sc_a313" name="sc_a313"></a><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_a313">Return to A.3.1.3 in Guidelines</a></div>
	   </div>

      <div class="techs-only">
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a313-i" name="sc_a313-i"></a>Intent of Success Criterion A.3.1.3:</h5> 
		<p>The intent of this success criterion is to introduce a Level AA requirement to strengthen the requirement of Success Criterion A.3.1.1. That success criterion would be met even by a keyboard access mechanism in which users had to sequentially navigate through every available user interface component in order to reach their intended destination. This success criterion (A.3.1.3) introduces the additional requirement that keyboard access must include mechanisms to make it more efficient that this type of purely sequential keyboard access. </p>
		<p>The wording is intentionally general because the appropriate mechanisms available for increasing the efficiency of keyboard access vary according to the operating environment and the design of the authoring tool:</p>
		<ol type="a">
		  <li>In desktop environments with a full keyboard, there is generally some set of keys available for developers to use as shortcut keys that directly link to particular functionality (e.g. the &quot;ctrl&quot; + &quot;S&quot; key combination can be directly mapped to the &quot;Save&quot; function). </li>

		  <li>In web-based environments very few direct shortcut keys are available, once the potential keys used by the various operating systems, user agents and assistive technologies are taken into account. In this case, bypass links are useful mechanisms for making keyboard access more efficient.</li>
		  <li>In mobile environments, the situation is variable. Some mobile environments include full, physical keyboards and support keyboard shortcuts. Other mobile environments do not enable keyboard shortcuts, but often increase keyboard navigation efficiency via recommending the use of tabs and other organizational mechanisms. </li>
		</ol>
		</div> 
      <!-- implementing-section -->
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a313-e" name="sc_a313-e"></a>Examples of Success Criterion A.3.1.3:</h5>
            <ul>

              <li><strong class="handle">In a desktop environment:</strong> A non-web-based authoring tool provides   keyboard shortcuts for its menu functions as well as access keys in the   design of its menus and dialog boxes. The choice of shortcut keys   follows platform conventions where applicable, for example for open   document, save document, cut, copy, paste, etc. </li>
              <li><strong class="handle">In a mobile environment:</strong> A social networking application on a   mobile device has only a very few keyboard shortcuts available on its   targeted devices. These few keyboard shortcuts are used for the most   commonly accessed functions of the application (e.g. home, list of   friends). </li>
              <li><strong class="handle">In a web-based environment:</strong> A web-based CMS uses links to allow   authors to skip between the toolbars and directly to the content editing   area.</li>
            </ul>

        </div> <!-- implementing-section -->
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a313-r" name="sc_a313-r"></a>Related Resources for Success Criterion A.3.1.3:</h5>
            <ul>
              <li>The following is a non-exhaustive list of keyboard shortcut conventions for various platforms:
                <ul>
                  
                  <li>Desktop OS
                      <ul>
                          <li><strong class="handle">Gnome Desktop on Linux:</strong> <a href="http://developer.gnome.org/hig-book/stable/input-keyboard.html.en">GNOME Human Interface Guidelines 2.2 - Keyboard Interaction</a><a href="http://developer.gnome.org/accessibility-devel-guide/"></a></li>
                        <li><strong class="handle">Mac OS:</strong> <a href="http://support.apple.com/kb/HT1343">Mac OS X keyboard shortcuts</a><a href="http://developer.apple.com/library/mac/documentation/Accessibility/Conceptual/AccessibilityMacOSX/OSXAXIntro/OSXAXintro.html"></a></li>
                        <li><strong class="handle">Microsoft Windows:</strong> <a href="http://support.microsoft.com/kb/126449">Keyboard Shortcuts for Windows</a><a href="http://msdn.microsoft.com/en-us/windows/bb735024.aspx"></a></li>
                      </ul>
                  </li>
                    <li>Mobile OS
                      <ul>
                          <li><strong class="handle">BlackBerry:</strong> <a href="http://docs.blackberry.com/en/developers/deliverables/17965/Shortcut_keys_1152021_11.jsp#BP_Implementing_shortcut_keys_1152022_11">UI Guidelines - BlackBerry Smartphones - Best practice: Implementing shortcut keys</a><a href="http://us.blackberry.com/support/devices/blackberry_accessibility/"></a></li>
                      </ul>
                    </li>
                    <li>Cross-OS environments
                      <ul>
                          <li><strong class="handle">Eclipse:</strong> <a href="http://eclipse-tools.sourceforge.net/shortcuts.html">Eclipse Keyboard Shortcuts</a><a href="http://www.eclipse.org/articles/article.php?file=Article-Accessibility/index.html"></a></li>
                        <li><strong class="handle">Java SE:</strong> <a href="http://java.sun.com/products/jlf/ed2/book/HIG.Behavior3.html">Java  Look and Feel Design Guidelines: Keyboard Operations</a><a href="http://java.sun.com/javase/technologies/accessibility/index.jsp"></a></li>
                        <li><strong class="handle">Lotus Notes:</strong> <a href="http://www-01.ibm.com/support/docview.wss?uid=swg21164659">Keyboard shortcuts in Notes 6.x and Notes 7.x</a><a href="http://www-03.ibm.com/able/guidelines/notes/accessr5.html"></a></li>
                      </ul>
                    </li>
                </ul>
              </li>
            </ul>
        </div> <!-- implementing-section -->

      </div>
    </div><!-- sc-level -->
		
    <div class="sc-level">
      <h4 class="sc-title"><a id="sc_a314" name="sc_a314"> </a><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_a314">Return to A.3.1.4 in Guidelines</a></div>
	   </div>
	   
      <div class="techs-only">
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a314-i" name="sc_a314-i"></a>Intent of Success Criterion A.3.1.4  (Based on WCAG 2.0, Success Criterion 2.1.3):</h5> 
		<p>The intent of this success criterion is to establish an enhanced requirement for keyboard access at Level AAA, without any exceptions. While some &quot;high-end&quot; drawing features, such as a &quot;watercolor painting&quot; tool that continuously sampled the path, pressure and angle of a stylus would be very challenging to make fully keyboard accessible, other less complex functions might be practical. </p>
		<p>Web-based authoring tools will already  be required to meet this success criterion as part of <a href="#sc_a111">Success Criterion A.1.1.1</a>.</p>

      </div> <!-- implementing-section -->
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a314-e" name="sc_a314-e"></a>Examples of Success Criterion A.3.1.4:</h5>
            <ul>
              <li><strong class="handle">Keyboard-driven &quot;freehand&quot; drawing:</strong> A multimedia authoring tool has a mode that allows &quot;freehand&quot; lines to be drawn in increments, letting authors use the keyboard to choose the angle and length of the next increment, after which the shape is smoothed.</li>

            </ul>
        </div> <!-- implementing-section -->
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a314-r" name="sc_a314-r"></a>Related Resources for Success Criterion A.3.1.4:</h5>
            <ul>
              <li>N/A</li>
            </ul>

        </div> <!-- implementing-section -->
      </div>
	  
<h4 class="sc-title"><a id="sc_a315" name="sc_a315"> </a><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_a315">Return to A.3.1.5 in Guidelines</a></div>
	   </div>

       <div class="techs-only">
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a315-i" name="sc_a315-i"></a>Intent of Success Criterion A.3.1.5:</h5> 
		<p>The intent of this success criterion is to ensure that authors using a keyboard interface have the ability to remap the authoring tool's keyboard shortcuts in order to avoid keystroke conflicts, use familiar keystroke combinations and optimize keyboard layout (e.g. for one-handed use).</p>
		</div> <!-- implementing-section -->
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a315-e" name="sc_a315-e"></a>Examples of Success Criterion A.3.1.5:</h5>

            <ul>
              <li><strong class="handle">Non-web-based authoring tool:</strong> A non-web-based authoring tool has a keyboard setup utility that lists all  of the available keyboard shortcuts and allows authors to associate each shortcut with any of the authoring tool's commands (e.g. all of the menu commands). </li>
              <li><strong class="handle">Web-based content management system:</strong> A web-based content management system has a keyboard setup utility that allows authors to change the access keys that are available during authoring. These access key rebindings are for the authors' use only and do not affect the web content being edited.</li>
              <li><strong class="handle">Social networking application on a mobile device:</strong> A social networking application has a keyboard setup utility that allows authors to change their keyboard shortcuts for the site. The remapping is saved in site cookies.</li>

            </ul>
        </div> <!-- implementing-section -->
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a315-r" name="sc_a315-r"></a>Related Resources for Success Criterion A.3.1.5:</h5>
            <ul>
              <li>N/A </li>
            </ul>

        </div> <!-- implementing-section -->
      </div>

	        <h4 class="sc-title"><a id="sc_a316" name="sc_a316"> </a><span class="techs-only">Implementing Success Criterion</span> 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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_a316">Return to A.3.1.6 in Guidelines</a></div>
	   </div>

            <div class="techs-only">
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a316-i" name="sc_a316-i"></a>Intent of Success Criterion A.3.1.6:</h5> 
		<p>The intent of this success criterion is to ensure that authors using a keyboard interface have the ability to both discover and be reminded of keyboard shortcuts, while they are using the authoring tool. </p>
		</div> <!-- implementing-section -->
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a316-e" name="sc_a316-e"></a>Examples of Success Criterion A.3.1.6:</h5>            
          <ul>

            <li><strong class="handle">Non-web-based authoring tool:</strong> An authoring tool on Windows includes a feature that allows authors to press a modifier key (e.g. the &quot;Alt&quot; key) to display all of the keyboard shortcuts in the current authoring tool user interface on top of the components to which they relate.</li>
          </ul>
        </div> <!-- implementing-section -->
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a316-r" name="sc_a316-r"></a>Related Resources for Success Criterion A.3.1.6:</h5>            
          <ul>

            <li>N/A</li>
          </ul>
        </div> <!-- implementing-section -->
      </div>
    </div><!-- sc-level -->
    <h3 class="guideline"><a name="gl_a32" id="gl_a32"> </a><span class="techs-only">Implementing</span> Guideline A.3.2: (For the authoring tool user interface) Provide authors with enough time.


<span class="techs-only">[<a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/Overview.html#gl_a32">Return to Guideline</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><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_a321">Return to A.3.2.1 in Guidelines</a></div>
	   </div>
	   	  
      <div class="techs-only"> 
      <div class="implementing-section">

        <h5 class="implementing-heading"><a id="sc_a321-i" name="sc_a321-i"></a>Intent of Success Criterion A.3.2.1:</h5> 
		<p>The intent of this success criterion is to ensure that the work of authors is saved in the event that an authoring session is ended due to a time limit (e.g. the timeout of an authenticated authoring session). Reducing the likelihood of lost content edits will benefit all authors, but especially authors with disabilities who may take longer to accomplish authoring tasks. </p>
		<p>For web-based authoring tools, this applies to any web content that has already been submitted to the server by the user agent. </p>
      </div> <!-- implementing-section -->
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a321-e" name="sc_a321-e"></a>Examples of Success Criterion A.3.2.1:</h5>
            <ul>

              <li><strong class="handle">Save and continue:</strong> A web-based content management system has a &quot;Save and Continue&quot; button that allows authors to continually submit their content edits without requiring them to re-enter the editing-view afterwards.</li>
              <li><strong class="handle">Wiki:</strong> A wiki has an auto-save feature that can be  turned on by authors. The auto-save feature always saves before a  system timeout.</li>
            </ul>
        </div> <!-- implementing-section -->

      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a321-r" name="sc_a321-r"></a>Related Resources for Success Criterion A.3.2.1:</h5>
            <ul>
              <li>N/A</li>
            </ul>
        </div> <!-- implementing-section -->
      </div> 

      <h4 class="sc-title"><a id="sc_a322" name="sc_a322"> </a><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_a322">Return to A.3.2.2 in Guidelines</a></div>
	   </div>

	  <div class="techs-only">   
      <div class="implementing-section">

        <h5 class="implementing-heading"><a id="sc_a322-i" name="sc_a322-i"></a>Intent of Success Criterion A.3.2.2 (Based on WCAG 2.0, Success Criterion 2.2.1):</h5> 
		<p>The intent of this success criterion is to ensure that authoring tools provide authors with disabilities adequate time to perform their tasks. Any process that happens without author initiation after a set time or on a periodic basis is a time limit. This includes partial or full updates of the screen (for example, page refresh), or the expiration of a window of opportunity for authors to react to a request for input. It also includes user interface functionality that is advancing or updating at a rate beyond the  ability of authors to read and/or understand it. In other words, animated, moving or scrolling information introduces a time limit. </p>
		<p>Generally, turning off time limits is better than customizing the length of time limits, which is better than requesting more time before a time limit occurs. In some cases, however, it is not possible to change the time limit (e.g. a collaborative authoring session) and exceptions are therefore provided for those cases.</p>
		<p> Web-based authoring tools will already be required to meet this success criterion as part of a <a href="#sc_a111">Success Criterion A.1.1.1</a>.</p>
      </div> <!-- implementing-section -->

      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a322-e" name="sc_a322-e"></a>Examples of Success Criterion A.3.2.2:</h5>
            <ul>
              <li><strong class="handle">Web-based content management system:</strong> A web-based content management system has a login timeout function that  automatically logs authors out after 20 minutes of inactivity. One minute before the automatic log out, the system notifies authors that they will be logged out unless they cancel the notification, meeting (c). The system also includes a preference setting that lets authors set the timing of the notification up to 10 minutes before the automatic logout, meeting (b).</li>
              <li><strong class="handle">Real-time collaborative editing system:</strong> A real-time collaborative editing system allows multiple authors to edit the same web content simultaneously. An integral part of the real-time collaborative activity is that any author may edit or delete what others have just authored, meeting (d). </li>

            </ul>
        </div> <!-- implementing-section -->
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a322-r" name="sc_a322-r"></a>Related Resources for Success Criterion A.3.2.2:</h5>
            <ul>
              <li>For web-based authoring tools, see <a href="#conf-rel-wcag">WCAG 2.0</a> (including <a href="http://www.w3.org/TR/2008/NOTE-UNDERSTANDING-WCAG20-20081211/">Understanding WCAG 2.0</a> and <a href="http://www.w3.org/WAI/WCAG20/quickref/Overview.php">How to Meet WCAG 2.0</a>), especially <a href="http://www.w3.org/TR/2008/REC-WCAG20-20081211/#time-limits-required-behaviors">WCAG 2.0 Success Criterion 2.2.1</a>.</li>

            </ul>
        </div> <!-- implementing-section -->
      </div> 

      
      <h4 class="sc-title"><a id="sc_a323" name="sc_a323"> </a><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_a323">Return to A.3.2.3 in Guidelines</a></div>
	   </div>
	   
	  <div class="techs-only"> 
      <div class="implementing-section">

        <h5 class="implementing-heading"><a id="sc_a323-i" name="sc_a323-i"></a>Intent of Success Criterion A.3.2.3:</h5> 
		<p>The intent of this success criterion is to ensure that authors are not prevented from using the authoring tool by a requirement for fast reactions.</p>
		</div> <!-- implementing-section -->
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a323-e" name="sc_a323-e"></a>Examples of Success Criterion A.3.2.3:</h5>
            <ul>
              <li><strong class="handle">Timeline-based authoring tool:</strong> A timeline-based interactive web content editor has an indicator  of the current position on the timeline that authors can click and drag. When the interactive  content is being previewed, the indicator moves along the timeline, which can make it difficult to target with the mouse. Authors can stop the indicator from moving by selecting the &quot;Stop&quot; or &quot;Pause&quot; buttons.</li>

            </ul>
        </div> <!-- implementing-section -->
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a323-r" name="sc_a323-r"></a>Related Resources for Success Criterion A.3.2.3:</h5>
            <ul>
              <li>For web-based authoring tools, see <a href="#conf-rel-wcag">WCAG 2.0</a> (including <a href="http://www.w3.org/TR/2008/NOTE-UNDERSTANDING-WCAG20-20081211/">Understanding WCAG 2.0</a> and <a href="http://www.w3.org/WAI/WCAG20/quickref/Overview.php">How to Meet WCAG 2.0</a>), especially <a href="http://www.w3.org/TR/2008/REC-WCAG20-20081211/#time-limits-pause">WCAG 2.0 Success Criterion 2.2.2</a>.</li>

            </ul>
        </div> <!-- implementing-section -->
      </div> 
    </div><!-- sc-level -->
	
 <div class="sc-level">
   <h4 class="sc-title"><a id="sc_a324" name="sc_a324"> </a><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_a324">Return to A.3.2.4 in Guidelines</a></div>
	   </div>

	<div class="techs-only">     
      <div class="implementing-section">
      <h5 class="implementing-heading"><a id="sc_a324-i" name="sc_a324-i"></a>Intent of Success Criterion A.3.2.4:</h5> 
	  <p>The intent of this success criterion is to ensure that the work of authors is saved in the event that an authoring session is ended due to a time limit. Reducing the likelihood of lost content edits will benefit all authors, but especially authors with disabilities who may take longer to accomplish authoring tasks. Increasing the frequency with which content edits are saved also helps authors recover more easily from inadvertent actions. </p>
	  </div> <!-- implementing-section -->
      <div class="implementing-section">
      <h5 class="implementing-heading"><a id="sc_a324-e" name="sc_a324-e"></a>Examples of Success Criterion A.3.2.4:</h5>
          <ul>
            <li><strong class="handle">Web-based content management system:</strong>
			The system includes an option to turn on asynchronous server communication to constantly save authoring actions into a backup file. If the authoring session ends unexpectedly, authors can retrieve  backups during their next authoring session.</li>
          </ul>
      </div> <!-- implementing-section -->
      <div class="implementing-section">
      <h5 class="implementing-heading"><a id="sc_a324-r" name="sc_a324-r"></a>Related Resources for Success Criterion A.3.2.4:</h5>
          <ul>
            <li>N/A</li>
          </ul>
      </div> <!-- implementing-section -->
    </div>
	</div> <!-- sc-level -->
	<h3 class="guideline"><a name="gl_a33" id="gl_a33"> </a><span class="techs-only">Implementing</span> Guideline A.3.3: (For the authoring tool user interface) Help authors avoid flashing that could cause seizures.


<span class="techs-only">[<a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/Overview.html#gl_a33">Return to Guideline</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><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_a331">Return to A.3.3.1 in Guidelines</a></div>
	   </div>
	   
      <div class="techs-only">
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a331-i" name="sc_a331-i"></a>Intent of Success Criterion A.3.3.1:</h5> 
		<p>The intent of this success criterion is to ensure that  authors with photosensitive seizure disorder can use the authoring tool to open visual time-based web content (e.g. animations) without risk. Some people with seizure disorders can have a seizure triggered by flashing visual content.</p>
		</div> <!-- implementing-section -->
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a331-e" name="sc_a331-e"></a>Examples of Success Criterion A.3.3.1:</h5>
            <ul>

              <li><strong class="handle">Blog:</strong> 
			  A blogging tool allows authors to import  video files. Authors have the option to turn off an auto-play feature, so that the video files are not played until a  &quot;Play&quot; button is activated.</li>
              <li><strong class="handle">WYSIWYG web page editor:</strong>
			  A WYSIWYG editing-view is capable of rendering JavaScript in real-time. Authors have the option to turn off the real-time rendering feature, so that the JavaScript is not rendered until a &quot;Play&quot; button is activated.</li>

            </ul>
        </div> <!-- implementing-section -->
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a331-r" name="sc_a331-r"></a>Related Resources for Success Criterion A.3.3.1:</h5>
            <ul>
              <li>For web-based authoring tools, see <a href="#conf-rel-wcag">WCAG 2.0</a> (including <a href="http://www.w3.org/TR/2008/NOTE-UNDERSTANDING-WCAG20-20081211/">Understanding WCAG 2.0</a> and <a href="http://www.w3.org/WAI/WCAG20/quickref/Overview.php">How to Meet WCAG 2.0</a>), especially <a href="http://www.w3.org/TR/2008/REC-WCAG20-20081211/#seizure">WCAG 2.0 Guideline 2.3</a>.</li>

            </ul>
        </div> <!-- implementing-section -->
      </div>
    </div> <!-- sc-level -->
    <h3 class="guideline"><a name="gl_a34" id="gl_a34"> </a><span class="techs-only">Implementing</span> Guideline A.3.4: (For the authoring tool user interface) Enhance navigation and editing via content structure. 


<span class="techs-only">[<a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/Overview.html#gl_a34">Return to Guideline</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><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_a341">Return to A.3.4.1 in Guidelines</a></div>
	   </div>

      <div class="techs-only">
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a341-i" name="sc_a341-i"></a>Intent of Success Criterion A.3.4.1:</h5> 
		<p>The intent of this success criterion is to help authors using keyboard interfaces to navigate more efficiently using the structure of the web content being edited.</p>
		</div> 
      <!-- implementing-section -->
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a341-e" name="sc_a341-e"></a>Examples of Success Criterion A.3.4.1:</h5>

          <ul>
              <li><strong class="handle">Source editing-view:</strong> A source editing-view supports authors by providing the ability to use  keyboard shortcuts to select the current element (e.g. table row) and other keyboard shortcuts to move the focus to:
                <ul>
                    <li>the element immediately above (e.g. table),</li>
                    <li>the first element immediately below (e.g. table data cell), </li>
                    <li> the element immediately preceding it at the same level (e.g. previous table row), and </li>
                    <li>the element immediately following it at the same level (e.g. next table row).</li>
                </ul>
            </li>
              <li><strong class="handle">Search by headings:</strong> An authoring tool includes a search function mode that enables authors to search forwards or backwards by &quot;any header element&quot;. For example, in HTML4 this would be <code>h1</code>...<code>h6</code>. When a searched-for header element exists, it is selected in the editing-view, enabling authors to immediately edit the element.              </li>

              <li><strong class="handle">Search by element:</strong> An authoring tool includes a search function mode that enables authors to search forwards or backwards by the names of elements. When a searched-for element exists, it is selected in the editing-view, enabling authors to immediately edit  the element. In addition, the search can be customized to search by attributes, etc.<br />
                <span class="figure"><strong>Figure:</strong> A &quot;Find and Replace&quot; dialog box is shown configured to find the &quot;element&quot; with the name &quot;img&quot;, &quot;with attribute&quot; &quot;height&quot; &quot;=&quot; &quot;100&quot; (where each value in quotation marks is editable). The replacement action is to &quot;set attribute&quot; &quot;height&quot; to &quot;50&quot;. The following checkbox options are available &quot;match case&quot;, &quot;ignore white space&quot; and &quot;search text alternatives&quot;. The dialog box also includes the following buttons &quot;Find Next&quot;, &quot;Find all&quot;, &quot;Replace&quot;, &quot;Replace All&quot;, &quot;Close&quot; and &quot;Help&quot;. (Source: mock up by AUWG)<br />

                <img src="tech_images/a_3.png" alt="See the example caption above for description." width="504" height="254" /></span></li>
              <li><strong class="handle">Outline view:</strong> An &quot;outline&quot; or &quot;structure&quot; editing-view is provided that organizes structured element sets being edited into a document tree. In this editing-view, only the arrow keys are required for navigation between the parent, child and sibling elements. </li>
              <li><strong class="handle">Customizing widgets:</strong> An authoring tool enables authors to add and customize JavaScript widgets in its WYSIWYG editing-view. Authors can use the keyboard to navigate through the elements that make up the widget in order to set the properties or appearance of the widget. For example, in a slider widget, the keyboard can be used to select the background, the line, the line ticks or the thumb marker of the slider.</li>

              <li><strong class="handle">WYSIWYG web page editor:</strong> A WYSIWYG editing-view allows authors to select and manipulate elements as objects. When an element is selected, any content (including sub-elements) of the element are also selected. When authors perform a function on a selected element, the scope of the function and the resulting outcome depends on the nature of the function.
                <ul>
                  <li>Some functions target the entire selection (i.e. the element, content and sub-elements). For example, when a <code>&lt;table&gt;</code> element is selected and the &quot;delete&quot; operation is performed, the entire table is deleted, including sub-elements (<code>tr</code> and <code>td</code>) and any text content etc. within the table.</li>

                  <li>Some functions only target the top level element of the selection. For example, the &quot;strip element tag&quot; function deletes the markup of the top level element without affecting its sub-elements or content. </li>
                  <li>Some functions only target the content, including sub-elements of the top level element of the selection without having any affect on the markup of that top level element. For example, the “replace contents” function is a variant of &quot;paste&quot; in which the sub-elements and content of the selected element are replaced.</li>
                </ul>
              </li>
          </ul>

        </div> <!-- implementing-section -->
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a341-r" name="sc_a341-r"></a>Related Resources for Success Criterion A.3.4.1:</h5>
            <ul>
              <li>N/A </li>
            </ul>
        </div> <!-- implementing-section -->

      </div>
    </div>  <!-- sc-level -->
    <div class="sc-level">
      <h4 class="sc-title"><a id="sc_a342" name="sc_a342"> </a><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_a342">Return to A.3.4.2 in Guidelines</a></div>
	   </div>

      <div class="techs-only">
        <div class="implementing-section">
          <h5 class="implementing-heading"><a id="sc_a342-i" name="sc_a342-i"></a>Intent of Success Criterion A.3.4.2:</h5>
          <p>The intent of this success criterion is to help authors using keyboard interfaces to navigate more efficiently using the programmatic relationships that may exist in many types of web content. </p>
        </div>
        <!-- implementing-section -->
        <div class="implementing-section">
          <h5 class="implementing-heading"><a id="sc_a342-e" name="sc_a342-e"></a>Examples of Success Criterion A.3.4.2:</h5>

          <ul>
            <li><strong class="handle">JavaScript editor:</strong> When a method is used, authors can navigate directly to where that method is defined. </li>
            <li><strong class="handle">HTML/CSS editor:</strong> When a style is used in content being edited, authors can navigate directly to where that style is defined, even if an external style sheet must be opened. </li>
            <li><strong class="handle">HTML editor:</strong> When an ID is used in content being edited, authors can navigate directly to where that ID is defined.</li>
            <li><strong class="handle">ARIA editor:</strong> Authors can navigate directly via ARIA relationships, such as &quot;aria-labeledby&quot; and &quot;aria-describedby&quot;.</li>
          </ul>
        </div>
        <!-- implementing-section -->
        <div class="implementing-section">

          <h5 class="implementing-heading"><a id="sc_a342-r" name="sc_a342-r"></a>Related Resources for Success Criterion A.3.4.2:</h5>
          <ul>
            <li>N/A</li>
          </ul>
        </div>
        <!-- implementing-section -->
      </div>
    </div>

    <h3 class="guideline"><a name="gl_a35" id="gl_a35"> </a><span class="techs-only">Implementing</span> Guideline A.3.5: (For the authoring tool user interface) Provide text search of the content. 

<span class="techs-only">[<a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/Overview.html#gl_a35">Return to Guideline</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><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_a351">Return to A.3.5.1 in Guidelines</a></div>
	   </div>
	   
      <div class="techs-only"> 
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a351-i" name="sc_a351-i"></a>Intent of Success Criterion A.3.5.1:</h5> 
		<p>The intent of this success criterion is to ensure that authors can efficiently find the web content that they wish to edit.</p>
		</div> 
      <!-- implementing-section -->
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a351-e" name="sc_a351-e"></a>Examples of Success Criterion A.3.5.1:</h5>
            <ul>

              <li><strong class="handle">Basic text search:</strong> An authoring tool provides both WYSIWYG and source editing-views. The authoring tool provides two-way, case sensitive searching for plain text sequences within both editing-views. The default search option is to search only within the editing-view that the author is currently working within. However, there is an option to search both editing-views simultaneously. When this option is selected, the search results are all displayed in a selectable list that labels each as &quot;Text&quot; or &quot;Source Code&quot;, reflecting which editing-view will become active when the author selects the search result. </li>
              <li><strong class="handle">Advanced text search:</strong> An authoring tool's basic text search feature is augmented by more advanced search options, such as:
<ul>
                  <li>replacement, </li>
                  <li>wildcard characters, </li>
                  <li>whole word matching, </li>
                  <li>search repetition, and </li>
                  <li>highlighting of all occurrences. </li>
                </ul>
              </li>
              <li><strong class="handle">Metadata editor:</strong> A metadata editor provides two-way, case sensitive searching for plain text sequences within textual metadata fields (e.g. title, description, author, etc.).</li>

            </ul>
        </div> <!-- implementing-section -->
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a351-r" name="sc_a351-r"></a>Related Resources for Success Criterion A.3.5.1:</h5>
            <ul>
              <li>N/A </li>
            </ul>

        </div> <!-- implementing-section -->
      </div> 
    </div><!-- sc-level -->
    <h3 class="guideline"><a name="gl_a36" id="gl_a36"> </a><span class="techs-only">Implementing</span> Guideline A.3.6: (For the authoring tool user interface) Manage preference settings. 

<span class="techs-only">[<a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/Overview.html#gl_a36">Return to Guideline</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><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_a361">Return to A.3.6.1 in Guidelines</a></div>
	   </div>

      <div class="techs-only">
        <div class="implementing-section">
          <h5 class="implementing-heading"><a id="sc_a361-i" name="sc_a361-i"></a>Intent of Success Criterion A.3.6.1: </h5>
          <p>The intent of this success criterion is to ensure that the preference display settings that authors set for their own use while they are editing web content are independent of the display settings that are encoded (and eventually published) in the  content being edited.</p>
          <p>When &quot;WYSIWYG authoring tools&quot; are referred to in the examples, it is with the understanding that browsers will differ in rendering of the same content and that end users are often free to override the default presentation of web content. </p>
        </div> <!-- implementing-section -->

        <div class="implementing-section">
          <h5 class="implementing-heading"><a id="sc_a361-e" name="sc_a361-e"></a>Examples of Success Criterion A.3.6.1:</h5>
          <ul>
            <li><strong class="handle">Editing-view preferences:</strong> A non-web-based WYSIWYG authoring tool has preference settings that enable authors to override the default rendering styles used in the WYSIWYG  editing-view with the display settings that they have already set in the operating system (e.g. large fonts, high contrast mode, etc.). The preference settings have absolutely no effect on the web content being edited.</li>
            <li><strong class="handle">Setting an authoring style sheet:</strong> A WYSIWYG authoring tool has preference settings that enable authors to set an &quot;authoring&quot; style sheet. This style sheet is only used to control the rendering of the web content in the author's editing-view. The stylesheet does not make changes to the  content markup being edited and is not published to end users.</li>

            <li><strong class="handle">Web-based authoring tool:</strong> A web-based authoring tool lets authors customize the appearance of editing-views using the preference display settings of the user agent. The user agent is cited in any <a href="#conf-claim">conformance claim</a>.</li>
          </ul>
        </div> <!-- implementing-section -->
        <div class="implementing-section">
          <h5 class="implementing-heading"><a id="sc_a361-r" name="sc_a361-r"></a>Related Resources for Success Criterion A.3.6.1:</h5>

          <ul>
            <li>N/A </li>
          </ul>
        </div> <!-- implementing-section -->
      </div>
    </div> <!-- sc-level -->
	
    <div class="sc-level">

      <h4 class="sc-title"><strong class="handle"><a id="sc_a362" name="sc_a362"> </a></strong><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_a362">Return to A.3.6.2 in Guidelines</a></div>
	   </div>
	   	  
      <div class="techs-only"> 
      <div class="implementing-section">

        <h5 class="implementing-heading"><a id="sc_a362-i" name="sc_a362-i"></a>Intent of  Success Criterion A.3.6.2:</h5> 
		<p>The intent of this success criterion is to ensure that authors' preference settings for keyboard and display settings do not need to be re-entered at the beginning of each authoring session.</p> 
		</div> <!-- implementing-section -->
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a362-e" name="sc_a362-e"></a>Examples of Success Criterion A.3.6.2:</h5>
            <ul>
              <li><strong class="handle">Storing preferences with author account:</strong> A web-based authoring tool requires that authors log in to their accounts before authoring sessions can begin. Because preference settings are associated with  author accounts, the settings are applied as soon as  authors log in.</li>

            </ul>
        </div> <!-- implementing-section -->
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a362-r" name="sc_a362-r"></a>Related Resources for Success Criterion A.3.6.2:</h5>
            <ul>
              <li>N/A </li>
            </ul>

        </div> <!-- implementing-section -->
      </div> 

      <h4 class="sc-title"><strong class="handle"><a id="sc_a363" name="sc_a363"> </a></strong><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_a363">Return to A.3.6.3 in Guidelines</a></div>
	   </div>
	   
      <div class="techs-only"> 
      <div class="implementing-section">

        <h5 class="implementing-heading"><a id="sc_a363-i" name="sc_a363-i"></a>Intent of Success Criterion A.3.6.3:</h5> 
		<p>The intent of this success criterion is to encourage authoring tools to respect the display and control settings that authors have already specified at the platform level. This reduces the need for authors to repeatedly specify the same preferences. It also means that when authors first open the authoring tool, they can more easily use the tool.</p>
		</div>
      <!-- implementing-section -->
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a363-e" name="sc_a363-e"></a>Examples of Success Criterion A.3.6.3:</h5>
            <ul>
              <li><strong class="handle">Desktop high contrast mode:</strong> A non-web-based authoring tool defaults to high contrast mode when it detects that the platform is set to high contrast mode.</li>

              <li><strong class="handle">Web-based authoring tool:</strong> A web-based authoring tool respects the display and control settings of the user agent on which it is running.</li>
            </ul>
        </div> <!-- implementing-section -->
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a363-r" name="sc_a363-r"></a>Related Resources for Success Criterion A.3.6.3:</h5>
            <ul>

              <li>For web-based authoring tools, see Related Resources for <a href="#sc_a111-r">Success Criteria A.1.1.1</a>.</li>
              <li>For non-web-based authoring tools, see Related Resources for  <a href="#sc_a121-r">Success Criterion A.1.2.1</a>. </li>
            </ul>
        </div> <!-- implementing-section -->
      </div> 
</div>  <!-- sc-level -->
 
    <div class="sc-level">
      <h4 class="sc-title"><a id="sc_a364" name="sc_a364"> </a><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_a364">Return to A.3.6.4 in Guidelines</a></div>
	   </div>
	   
      <div class="techs-only"> 
      <div class="implementing-section">

        <h5 class="implementing-heading"><a id="sc_a364-i" name="sc_a364-i"></a>Intent of Success Criterion A.3.6.4:</h5>
		<p>The intent of this success criterion is to ensure that authors whose personal preferences vary over time (e.g. due to fatigue) can easily select from a series of pre-set preferences for display and control settings.</p>
		</div> <!-- implementing-section -->
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a364-e" name="sc_a364-e"></a>Examples of Success Criterion A.3.6.4:</h5>
            <ul>
              <li><strong class="handle">Basic multiple profiles:</strong> An authoring tool allows the various configurations of preference settings to be stored as different profiles that authors can switch between at any time. The stored preference settings include all display and control settings that are specific to the authoring tool (i.e. are not controlled by the platform). </li>

              <li><strong class="handle">Portable profiles:</strong> An authoring tool's basic multiple profiles feature is augmented by  the ability for authors to save the profiles as separate files. This allows authors to move configurations between instances of the authoring tool on different systems or to share the configuration files with other authors with similar requirements.</li>
            </ul>
        </div> <!-- implementing-section -->
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a364-r" name="sc_a364-r"></a>Related Resources for Success Criterion A.3.6.4:</h5>
            <ul>

              <li>N/A </li>
            </ul>
        </div> <!-- implementing-section -->
      </div> 
	  
      <h4 class="sc-title"><a id="sc_a365" name="sc_a365"> </a><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_a365">Return to A.3.6.5 in Guidelines</a></div>
	   </div>
	   
      <div class="techs-only"> 
      <div class="implementing-section">

        <h5 class="implementing-heading"><a id="sc_a365-i" name="sc_a365-i"></a>Intent of Success Criterion A.3.6.5:</h5>
		<p>The intent of this success criterion is to ensure that authoring tools provide assistance to authors in configuring any options related to the accessibility of the user interface. This assistance should include extra assistance resolving any incompatibilities between options (e.g. prevent the same color being used for both the foreground and background). </p>
		</div> <!-- implementing-section -->
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a365-e" name="sc_a365-e"></a>Examples of Success Criterion A.3.6.5:</h5>
            <ul>
              <li><strong class="handle">Options setting wizard:</strong> An authoring tool includes a wizard that takes authors step-by-step through the accessibility options, providing explanations and previews of how the options will change the display. The wizard follows an interview format, first asking authors about general areas (e.g. seeing the screen, using the keyboard) and then becoming more detailed (e.g. text size, text color, etc.).</li>
            </ul>
        </div> <!-- implementing-section -->
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a365-r" name="sc_a365-r"></a>Related Resources for Success Criterion A.3.6.5:</h5>
            <ul>
              <li>N/A </li>

            </ul>
        </div> <!-- implementing-section -->
      </div> 
    </div> <!-- sc-level -->
    <h3 class="guideline"><a name="gl_a37" id="gl_a37"> </a><span class="techs-only">Implementing</span> Guideline A.3.7: (For the authoring tool user interface) Ensure that previews are as accessible as existing user agents. 


<span class="techs-only">[<a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/Overview.html#gl_a37">Return to Guideline</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><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_a371">Return to A.3.7.1 in Guidelines</a></div>
	   </div>
	   
      <div class="techs-only"> 
      <div class="implementing-section">

        <h5 class="implementing-heading"><a id="sc_a371-i" name="sc_a371-i"></a>Intent of Success Criterion A.3.7.1:</h5> 
		<p>The intent of this success criterion is to ensure that preview features strike a balance between giving authors with disabilities an accessible  means of previewing the web content that they are editing and not giving  those authors an unrealistic impression of how end users with similar  disabilities will actually experience that  content in their own user  agents (e.g. browser, video player, etc.). In other words, it is not necessarily useful to present a user  experience with  content as a &quot;preview&quot; when it is much more  accessible than the actual end user experience of the  content would be in a  pre-existing user agent.</p>
		<p>There are two ways to meet this success criterion: </p>
		<p>Option (a)  is to  implement preview features using user agents that are  already in use by end users, which is the most straightforward way to meet this success criterion. This might be done in several  ways, including by opening the  content in the author's default user agent or by making  use of a user agent widget nested within the authoring tool's own user  interface. The user agent is cited in any <a href="#conf-claim">conformance claim</a>. </p>
		<p>Option (b) requires that if a preview is being developed that is already a  departure from existing user agents, then the W3C User Agent Accessibility  Guidelines (UAAG) must be followed. At the time of publication, UAAG  version 1.0 is a W3C Recommendation and version 2.0 is under  development.</p>

		<p><em>Note:</em> Developers may create a preview feature from scratch that does not meet  (b), as long as authors retain the option to preview using their own user agent, since this meets (a).</p>
      </div> <!-- implementing-section -->
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a371-e" name="sc_a371-e"></a>Examples of Success Criterion A.3.7.1:</h5>
            <ul>
              <li><strong class="handle">Preview in a user agent:</strong>

			  A web-based authoring tool performs previews by opening the web content in a new user agent tab or window, meeting (a).  </li>
              <li><strong class="handle">Preview in an external user agent:</strong>
			  A non-web-based authoring tool performs previews by opening the web content to be previewed in the user's default browser, meeting (a).</li>
              <li><strong class="handle">Preview in a user agent component:</strong>
			  A non-web-based authoring tool performs previews using a user agent component that is built directly into the authoring tool, meeting (a).</li>
              <li><strong class="handle">Custom built preview:</strong>

			  An authoring tool makes use of a custom built preview feature. The preview feature conforms to User Agent Accessibility Guidelines (UAAG) 1.0 at Level &quot;A&quot;, meeting (b).</li>
            </ul>
        </div> <!-- implementing-section -->
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a371-r" name="sc_a371-r"></a>Related Resources for Success Criterion A.3.7.1:</h5>
            <ul>

              <li><a href="http://www.w3.org/TR/UAAG10/">User Agent Accessibility Guidelines (UAAG) 1.0</a>. </li>
            </ul>
        </div> <!-- implementing-section -->
      </div> 
    </div> <!-- sc-level -->

    <div class="sc-level">
      <h4 class="sc-title"><a id="sc_a372" name="sc_a372"> </a><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_a372">Return to A.3.7.2 in Guidelines</a></div>
	   </div>

      <div class="techs-only">
        <div class="implementing-section">
          <h5 class="implementing-heading"><a id="sc_a372-i" name="sc_a372-i"></a>Intent of Success Criterion A.3.7.2:</h5>
          <p>The intent of this success criterion is to provide an enhanced Level AAA requirement for preview features, in which authors have the flexibility to choose their preferred user agent for performing previews. </p>
        </div>
        <!-- implementing-section -->
        <div class="implementing-section">
          <h5 class="implementing-heading"><a id="sc_a372-e" name="sc_a372-e"></a>Examples of Success Criterion A.3.7.2:</h5>

          <ul>
            <li><strong class="handle">Non-web-based authoring tool:</strong> A non-web-based authoring tool gives authors the option of choosing from any of the user agents installed on their computer to perform the preview.</li>
            <li><strong class="handle">Web-based authoring tool:</strong> A web-based authoring tool provides authors with a URI that can be entered into another user agent to perform the preview.</li>
          </ul>
        </div>
        <!-- implementing-section -->

        <div class="implementing-section">
          <h5 class="implementing-heading"><a id="sc_a372-r" name="sc_a372-r"></a>Related Resources for Success Criterion A.3.7.2:</h5>
          <ul>
            <li>N/A</li>
          </ul>
        </div>
        <!-- implementing-section -->
      </div>

    </div>
    <!-- sc-level -->
    <h2 class="principle"><a name="principle_a4" id="principle_a4"> </a><span class="techs-only">Implementing </span>PRINCIPLE A.4: Editing-views must be understandable </h2> 
	  
    <h3 class="guideline"><a name="gl_a41" id="gl_a41"> </a><span class="techs-only">Implementing</span> Guideline A.4.1: (For the authoring tool user interface) Help authors avoid and correct mistakes. 
 

<span class="techs-only">[<a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/Overview.html#gl_a41">Return to Guideline</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><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_a411">Return to A.4.1.1 in Guidelines</a></div>
	   </div>
	   
      <div class="techs-only"> 
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a411-i" name="sc_a411-i"></a>Intent of Success Criterion A.4.1.1:</h5> 
		<p>The intent of this success criterion is to help authors with disabilities avoid serious consequences in the web content that they are editing as the result of a mistake while performing authoring actions. Everyone makes mistakes, but people with some disabilities have more difficulty creating error-free input. </p>

		<p>Note 1 makes it clear that &quot;undo&quot; functions, themselves, are authoring actions that authors may need to undo.</p>
		<p>Note 2 acknowledges that some implementations of &quot;undo&quot; may group text entry actions.</p>
		<p>Note 3 makes it clear that this success criterion does not require authoring actions made in one authoring session to be reversible in subsequent authoring sessions.</p>
		</div> 
      <!-- implementing-section -->

      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a411-e" name="sc_a411-e"></a>Examples of Success Criterion A.4.1.1:</h5>
            <ul>
              <li><strong class="handle">Non-web-based authoring tool:</strong> An authoring tool has an &quot;Undo&quot; action under the &quot;Edit&quot; menu. Activating the &quot;Undo&quot; action reverses the previous  authoring action, meeting (a). Activating &quot;Undo&quot; again undoes the previous authoring action and so on.</li>
              <li><strong class="handle">Web-based content management system:</strong> A web-based content management system supports two types of reversible actions. Firstly, text entry actions into text fields can be reversed using the &quot;Undo&quot; feature of the user agent.  Secondly, &quot;Cancel&quot; buttons are available within the web-based authoring tool user interface that allow authors to reverse changes that have already been committed. However, to avoid the &quot;Cancel&quot; button being pressed accidentally, authors have the option of having confirmation dialogs displayed when &quot;Cancel&quot; is activated (see <a href="#sc_a413">Success Criterion A.4.1.3</a>), meeting (a). The user agent is cited in any <a href="#conf-claim">conformance claim</a>.</li>

            </ul>
        </div> <!-- implementing-section -->
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a411-r" name="sc_a411-r"></a>Related Resources for Success Criterion A.4.1.1:</h5>
            <ul>
              <li>For web-based authoring tools, see <a href="#conf-rel-wcag">WCAG 2.0</a> (including <a href="http://www.w3.org/TR/2008/NOTE-UNDERSTANDING-WCAG20-20081211/">Understanding WCAG 2.0</a> and <a href="http://www.w3.org/WAI/WCAG20/quickref/Overview.php">How to Meet WCAG 2.0</a>), especially <a href="http://www.w3.org/TR/2008/REC-WCAG20-20081211/#minimize-error">WCAG 2.0 Guideline 3.3</a>. </li>
            </ul>
        </div> <!-- implementing-section -->
      </div> 

      <h4 class="sc-title"><a id="sc_a412" name="sc_a412"> </a><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_a412">Return to A.4.1.2 in Guidelines</a></div>
	   </div>
	    
      <div class="techs-only"> 
      <div class="implementing-section">

        <h5 class="implementing-heading"><a id="sc_a412-i" name="sc_a412-i"></a>Intent of Success Criterion A.4.1.2: </h5>
		<p>The intent of this success criterion is to help authors with disabilities avoid  making the authoring tool unusable to them as the result of making a mistake while installing the program or modifying preference settings. Everyone makes mistakes, but people with some disabilities have more difficulty creating error-free input. In addition, it may be harder for some people with disabilities to detect that they have made an error.</p>
		</div> 
      <!-- implementing-section -->
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a412-e" name="sc_a412-e"></a>Examples of Success Criterion A.4.1.2:</h5>
            <ul>
              <li><strong class="handle">Cancel:</strong> On each preference settings page are two options, OK and Cancel. Canceling prevents the setting changes from being applied, meeting (a). </li>

              <li><strong class="handle">All reversible:</strong> All of the preference setting changes in an authoring tool can be reversed by revisiting the preference setting utility and adjusting the settings, meeting (a).</li>
              <li><strong class="handle">Restore defaults:</strong> In a preference setting utility, a &quot;restore default settings&quot; button is always available, meeting (a).</li>
            </ul>
        </div> <!-- implementing-section -->

      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a412-r" name="sc_a412-r"></a>Related Resources for Success Criterion A.4.1.2:</h5>
            <ul>
<li>For web-based authoring tools, see <a href="#conf-rel-wcag">WCAG 2.0</a> (including <a href="http://www.w3.org/TR/2008/NOTE-UNDERSTANDING-WCAG20-20081211/">Understanding WCAG 2.0</a> and <a href="http://www.w3.org/WAI/WCAG20/quickref/Overview.php">How to Meet WCAG 2.0</a>), especially <a href="http://www.w3.org/TR/2008/REC-WCAG20-20081211/#minimize-error">Guideline 3.3</a>. </li>

</ul>
        </div> <!-- implementing-section -->
      </div> 
</div> <!-- sc-level -->
	
    <div class="sc-level">
      <h4 class="sc-title"><a id="sc_a413" name="sc_a413"> </a><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_a413">Return to A.4.1.3 in Guidelines</a></div>
	   </div>
	   
      <div class="techs-only">
        <div class="implementing-section">
          <h5 class="implementing-heading"><a id="sc_a413-i" name="sc_a413-i"></a>Intent of Success Criterion A.4.1.3:</h5>

          <p>The intent of this success criterion is to establish an enhanced Level AAA requirement for reversing inadvertent actions that modify the content being edited. Everyone makes mistakes, but some people with some disabilities have more difficulty creating error-free input. In addition, it may be harder for some people with disabilities to detect and rectify errors, so it is more likely that they will benefit from the ability to reverse a series of actions once an error is discovered.</p>
          <p>The note is a reminder that the three notes from <a href="#sc_a411">Success Criterion A.4.1.1</a> also apply. </p>
        </div>
        <!-- implementing-section -->
        <div class="implementing-section">
          <h5 class="implementing-heading"><a id="sc_a413-e" name="sc_a413-e"></a>Examples of Success Criterion A.4.1.3:</h5>

          <ul>
            <li><strong class="handle">Undo queue:</strong> An authoring tool saves author actions in a &quot;last-in-last-out&quot; queue.</li>
          </ul>
        </div>
        <!-- implementing-section -->
        <div class="implementing-section">

          <h5 class="implementing-heading"><a id="sc_a413-r" name="sc_a413-r"></a>Related Resources for Success Criterion A.4.1.3:</h5>
          <ul>
            <li>N/A</li>
          </ul>
        </div><!-- implementing-section -->
      </div><!-- techs-only -->
    </div><!-- sc-level -->
    <h3 class="guideline"><a name="gl_a42" id="gl_a42"> </a><span class="techs-only">Implementing</span> Guideline A.4.2: (For the authoring tool user interface) Document the user interface including all accessibility features. 

 
<span class="techs-only">[<a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/Overview.html#gl_a42">Return to Guideline</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><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_a421">Return to A.4.2.1 in Guidelines</a></div>
	   </div> 

        <div class="techs-only"> 
      <div class="implementing-section">
          <h5 class="implementing-heading"><a id="sc_a421-i" name="sc_a421-i"></a>Intent of Success Criterion A.4.2.1:</h5> 
		  <p>The intent of this success criterion is to ensure that authors with disabilities that need to use the accessibility features of the authoring tool user interface can easily find specific instruction in the documentation. </p>

		  <p>The note is a reminder that 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>.</p>
      </div> <!-- implementing-section -->
      <div class="implementing-section">
          <h5 class="implementing-heading"><a id="sc_a421-e" name="sc_a421-e"></a>Examples of Success Criterion A.4.2.1:</h5>
              <ul>

                <li><strong class="handle">Accessibility features documented:</strong> An authoring tool includes a help system that is always available to authors, is searchable by keyword and is also linked in context from the various features within the authoring tool. The documentation conforms to WCAG 2.0 Level A and includes the following topics grouped together into an &quot;Accessibility Features&quot; chapter in the help system:
                  <ul>
  <li>how to customize display settings</li>
  <li>what keyboard shortcuts are available, including navigation keys </li>
  <li>how to customize keyboard shortcuts</li>

  <li>how to avoid keyboard traps in content </li>
  <li>how to extend time limits</li>
  <li>how to use the search features </li>
  <li>how to undo/redo</li>
  <li>how to set accessibility-related options, such as turning off auto-play</li>
  </ul>

                </li>
              </ul>
          </div> <!-- implementing-section -->
      <div class="implementing-section">
          <h5 class="implementing-heading"><a id="sc_a421-r" name="sc_a421-r"></a>Related Resources for Success Criterion A.4.2.1:</h5>
              <ul>
                <li>N/A </li>

              </ul>
          </div> <!-- implementing-section -->
        </div> 
    </div> <!-- sc-level -->

    <div class="sc-level">
      <h4 class="sc-title"><a id="sc_a422" name="sc_a422"> </a><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_a422">Return to A.4.2.2 in Guidelines</a></div>
	   </div> 
	   
      <div class="techs-only">
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a422-i" name="sc_a422-i"></a>Intent of Success Criterion A.4.2.2:</h5> 
		<p>The intent of this success criterion is to ensure that authors who need additional support to learn to operate an authoring tool can easily access instructions. </p>

		<p>The note is a reminder that 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>.</p>
      </div> <!-- implementing-section -->
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a422-e" name="sc_a422-e"></a>Examples of Success Criterion A.4.2.2:</h5>
            <ul>
              <li><strong class="handle">All features documented:</strong> An authoring tool includes  documentation for all of its available features. The documentation conforms to WCAG 2.0 Level A.</li>
            </ul>
        </div> <!-- implementing-section -->
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_a422-r" name="sc_a422-r"></a>Related Resources for Success Criterion A.4.2.2:</h5>
            <ul>
              <li><a href="http://en.wikipedia.org/wiki/Software_documentation">&quot;Software Documentation&quot; on Wikipedia </a></li>
            </ul>
        </div> <!-- implementing-section -->
      </div>
    </div> <!-- sc-level -->
  </div> <!-- subsect-tool-accessible -->

<div id="subsect-support-production"> 

<h2><a id="part_b" name="part_b"> </a><span class="techs-only">Implementing </span>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><span class="techs-only">Implementing </span>PRINCIPLE B.1: Fully automatic processes must produce accessible content</h2> 
      
<h3 class="guideline"><a name="gl_b11" id="gl_b11"> </a><span class="techs-only">Implementing</span> Guideline B.1.1: Ensure automatically specified content is accessible.  <span class="techs-only">[<a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/Overview.html#gl_b11">Return to Guideline</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><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_b111">Return to B.1.1.1 in Guidelines</a></div>
	   </div>
	   
  <div class="techs-only">
    <div class="implementing-section">
      <h5 class="implementing-heading"><a id="sc_b111-i" name="sc_b111-i"></a>Intent of Success Criterion B.1.1.1:</h5>
      <p>The intent of this success criterion is to ensure that when authoring tools have been designed to generate web content that is published directly to end users without an opportunity for author action, the default option should be for that web content to be accessible.</p>
      <p>The note acknowledges that there are automatic behaviors that may be specified by other parties, and that author actions may purposefully or inadvertently affect the accessibility of the content generated later. </p>
      <p><a href="#conf-rel-wcag">WCAG 2.0</a> is referenced because it provides testable success criteria to measure web content accessibility. </p>

    </div>
    <!-- implementing-section -->
    <div class="implementing-section">
      <h5 class="implementing-heading"><a id="sc_b111-e" name="sc_b111-e"></a>Examples of Success Criterion B.1.1.1:</h5>
      <ul>
        <li><strong class="handle">Email archive:</strong> An automatic email archiving system automatically creates web pages from each email message that it receives. It has been designed to generate accessible markup, but if email messages contain accessibility problems, the archiving system is not able to rectify them. </li>
        <li><strong class="handle">Social networking application:</strong> A social networking application collects some limited information from authors (e.g. name, gender, status updates, etc.) which it uses to personalize an automatically generated web application that meets the requirements of WCAG.</li>

        </ul>
    </div>
    <!-- implementing-section -->
    <div class="implementing-section">
      <h5 class="implementing-heading"><a id="sc_b111-r" name="sc_b111-r"></a>Related Resources for Success Criterion B.1.1.1:</h5>
      <ul>
        <li><a href="#conf-rel-wcag">WCAG 2.0</a> (including <a href="http://www.w3.org/TR/2008/NOTE-UNDERSTANDING-WCAG20-20081211/">Understanding WCAG 2.0</a> and <a href="http://www.w3.org/WAI/WCAG20/quickref/Overview.php">How to Meet WCAG 2.0</a>)</li>

      </ul>
    </div> <!-- implementing-section -->
  </div> <!-- techs-only -->
  
  <h4 class="sc-title"><a id="sc_b112" name="sc_b112"> </a><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_b112">Return to B.1.1.2 in Guidelines</a></div>
	   </div>
	   	
  <div class="techs-only">
    <div class="implementing-section">
      <h5 class="implementing-heading"><a id="sc_b112-i" name="sc_b112-i"></a>Intent of Success Criterion B.1.1.2:</h5>
      <p>The intent of this success criterion is to provide more flexible guidance when authors are available to assist in ensuring the accessibility of content, while also recognizing that authors often will not be able to assist if they are not made aware that web content accessibility problems do or may exist. </p>

      <p>Note 1 highlights the fact that when an authoring tool automatically selects a template for the author to use, the authoring tool is considered to be auto-generating the content in the template. </p>
      <p>Note 2 acknowledges that there are many ways in which the automatic behavior of authoring tools can be modified that are not under the control of the developer.</p>
      <p>There are four ways to meet this success criterion: </p>
      <p>Option (a) is the most straightforward. It requires the authoring tool to generate only accessible content. </p>
      <p>Option (b) takes into account that even more access-aware authoring tools may need to query the author regarding issues that require human judgment, such as whether alternative text is suited to the context.</p>
      <p>Option (c)  takes into account that prompting during the generation process may be contrary to the workflow. Instead, the authoring tool can run a checker on the output.</p>
      <p>Option (d) is similar to (c) but takes into account that ATAG 2.0 allows the option of manual checking.</p>
      <p><a href="#conf-rel-wcag">WCAG 2.0</a> is referenced because it provides testable success criteria to measure web content accessibility. </p>
    </div>
    <!-- implementing-section -->
    <div class="implementing-section">
      <h5 class="implementing-heading"><a id="sc_b112-e" name="sc_b112-e"></a>Examples of Success Criterion B.1.1.2:</h5>

      <ul>
        <li><strong class="handle">Markup behind WYSIWYG:</strong> A WYSIWYG web page authoring tool provides  authors with a toolbar of options for formatting text. Following the WYSIWYG (what-you-see-is-what-you-get) paradigm, the options are labeled with the visual result (e.g. a bold &quot;B&quot; to represent bold, an italicized &quot;I&quot; to represent italics, etc.) of performing the action however, the content that is automatically generated from those actions actually conforms to <a href="#conf-rel-wcag">WCAG 2.0</a> (e.g. using <code>strong</code> for bold and <code>em</code> for emphasis), meeting (a). </li>

        <li><strong class="handle">Automatic generation with author input:</strong> An online photo album allows authors to upload images and then automatically generates content to display the images. Since the album application is not able to automatically generate alternative content for the images that meets <a href="#conf-rel-wcag">WCAG 2.0</a>, authors are prompted for this information, meeting (b).</li>
        <li><strong class="handle">Automatic accessibility checking:</strong> An authoring tool allows images, videos and other multimedia files to be dragged into documents. When this happens, markup is automatically generated that contains accessibility problems. However, the authoring tool includes an &quot;as-you-type&quot; accessibility checker that unobtrusively highlights the problems for author attention, meeting (c).</li>
        <li><strong class="handle">Manual accessibility checking:</strong> An authoring tool allows images, videos and other multimedia files to be dragged into documents. When this happens, markup is automatically generated that contains accessibility problems. Since the authoring tool includes a manual checking wizard instead of an automatic checker, a message appears in a status area of the user interface stating that the author should use the wizard before publishing, meeting (d).</li>

        <li><strong class="handle">Documentation:</strong> An authoring tool that employs automatic  content generation documents the accessibility of this functionality with reference to particular <a href="#conf-rel-wcag">WCAG 2.0</a> techniques.</li>
        </ul>
    </div>
    <!-- implementing-section -->
    <div class="implementing-section">
      <h5 class="implementing-heading"><a id="sc_b112-r" name="sc_b112-r"></a>Related Resources for Success Criterion B.1.1.2:</h5>

      <ul>
        <li><a href="#conf-rel-wcag">WCAG 2.0</a> (including <a href="http://www.w3.org/TR/2008/NOTE-UNDERSTANDING-WCAG20-20081211/">Understanding WCAG 2.0</a> and <a href="http://www.w3.org/WAI/WCAG20/quickref/Overview.php">How to Meet WCAG 2.0</a>)</li>
      </ul>
    </div> <!-- implementing-section -->

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


<h3 class="guideline"><a id="gl_b12" name="gl_b12"> </a><span class="techs-only">Implementing</span> Guideline B.1.2: Ensure accessibility information is preserved.  <span class="techs-only">[<a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/Overview.html#gl_b12">Return to Guideline</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><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_b121">Return to B.1.2.1 in Guidelines</a></div>
	   </div>
  <div class="techs-only">
    <div class="implementing-section">
      <h5 class="implementing-heading"><a id="sc_b121-i" name="sc_b121-i"></a>Intent of Success Criterion B.1.2.1:</h5>
      <p>The intent of this success criterion is to encourage authoring tools to preserve accessibility information  during restructuring or recoding transformations and to ensure authors are made aware when the authoring tool is unable to preserve accessibility information. This may occur when the output format does not support the same accessibility features as the input format (i.e. the example of a vector graphic being saved as a raster image format) or when an authoring tool has not implemented the necessary data mapping. There is no negative connotation intended here. In some cases, the number of source technology possibilities is simply too large to ensure complete mappings are in place for all of them. </p>
      <p>The options available partially mirror the options for <a href="#sc_b112">Success Criterion B.1.1.2</a>, reflecting the similarities between automatic generation and restructuring/re-coding web content transformations:</p>

      <p>Option (a) is the most straightforward. It requires the authoring tool to preserve accessibility information during transformations. </p>
      <p>Option (b) is to warn the author directly that accessibility information may be lost, allowing them to decide whether or not to proceed.</p>
      <p>Option (c)  takes into account that prompting during the transformation process may be contrary to the workflow. Instead, the authoring tool can run a checker on the output.</p>
      <p>Option (d) is similar to (c) but takes into account that ATAG 2.0 allows the option of manual checking.</p>
      <p>See Also: ATAG 2.0 identifies other types of transformations in which the expectation for preserving accessibility information is higher. These are optimizing transformations (<a href="#sc_b122">Success Criterion B.1.2.2</a>) and transformations in which non-text content is preserved (<a href="#sc_b123">Success Criterion B.1.2.3</a>). </p>

      <p><a href="#conf-rel-wcag">WCAG 2.0</a> is referenced because it provides testable success criteria to measure web content accessibility.</p>
    </div>
    <!-- implementing-section -->
    <div class="implementing-section">
      <h5 class="implementing-heading"><a id="sc_b121-e" name="sc_b121-e"></a>Examples of Success Criterion B.1.2.1:</h5>
      <ul>
        <li><strong class="handle">Similar data structures:</strong> A &quot;Save As&quot; feature preserves accessibility information in similar data structures, meeting (a). For example:
          <ul>

              <li>when converting between HTML and SVG, the contents of <code>alt</code> attributes are stored in <code>desc</code> attributes</li>
            <li>when saving a word-processor format to markup, headings and list items are transformed into appropriate structural markup</li>
          </ul>
        </li>
        <li><strong class="handle">Dissimilar but accessible:</strong> A &quot;Save As&quot; feature preserves accessibility information in a dissimilar, but accessible way, when similar data structures are not available, meeting (a). For example:
          <ul>

              <li>when transforming a SMIL presentation with a closed-caption text track into a video-only format, authors have the option of converting the closed captions into open-captions encoded in the video file</li>
            <li>when transforming a table to a list, table headings are transformed into headings and summary or caption information is retained as rendered text content</li>
            <li>when saving a word-processing format to markup, specialized document features (i.e. footnotes, endnotes, call-outs, annotations, references, etc.) are retained as rendered text content with two-way linking.</li>
          </ul>
        </li>
        <li><strong class="handle">Warning when text is converted to graphics):</strong> A &quot;Save As&quot; feature includes the ability to convert textual formats into graphics. However, if this option is selected by authors, they are warned that  the output will have web content accessibility problems. They are also advised that style sheets are preferable for presentation control. If authors continue, there is a suggestion to retain the original text as alternative content for the graphical output, meeting (b).</li>

        <li><strong class="handle">Option to cancel:</strong> A markup editor has a feature that  automatically removes any attributes or elements that do not appear in the defined DTD when content is opened for editing. Upon activation, the feature notifies authors that content will be deleted with unknown effects for end users. The author has the option to cancel the operation, in which case the content will not be opened for editing, meeting (b). </li>
        <li><strong class="handle">Automatic accessibility checking:</strong> An authoring tool allows content to be copy-and-pasted from other applications, including office applications, user agents, etc. When this happens, the source content is recoded into the technology of the current document. While accessibility was considered in the design of the feature, web content accessibility problems may still occur. However, the authoring tool includes an &quot;as-you-type&quot; accessibility checker, meeting (c).</li>
        <li><strong class="handle">Manual accessibility checking:</strong> An authoring tool allows content to be copy-and-pasted from other applications, including office applications, user agents, etc. When this happens, the source content is recoded into the technology of the current document. While accessibility was considered in the design of the feature, web content accessibility problems may still occur. Since the authoring tool includes a manual checking wizard instead of an automatic checker, a message appears in a status area of the user interface stating that the author should use the wizard before publishing, meeting (d).</li>

        </ul>
    </div>
    <!-- implementing-section -->
    <div class="implementing-section">
      <h5 class="implementing-heading"><a id="sc_b121-r" name="sc_b121-r"></a>Related Resources for Success Criterion B.1.2.1:</h5>
      <ul>
        <li><a href="#conf-rel-wcag">WCAG 2.0</a> (including <a href="http://www.w3.org/TR/2008/NOTE-UNDERSTANDING-WCAG20-20081211/">Understanding WCAG 2.0</a> and <a href="http://www.w3.org/WAI/WCAG20/quickref/Overview.php">How to Meet WCAG 2.0</a>)</li>

      </ul>
    </div>
    <!-- implementing-section -->
  </div>
</div>
<!-- sc-level -->
<div class="sc-level">
  <h4 class="sc-title"><a id="sc_b122" name="sc_b122"> </a><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_b122">Return to B.1.2.2 in Guidelines</a></div>
	   </div>
	   
  <div class="techs-only">
    <div class="implementing-section">
      <h5 class="implementing-heading"><a id="sc_b122-i" name="sc_b122-i"></a>Intent of Success Criterion B.1.2.2:</h5>
      <p>The intent of this success criterion is to ensure that web content transformations intended only to optimize content do not result in the introduction of web content accessibility problems.</p>
    </div>
    <!-- implementing-section -->
    <div class="implementing-section">

      <h5 class="implementing-heading"><a id="sc_b122-e" name="sc_b122-e"></a>Examples of Success Criterion B.1.2.2:</h5>
      <ul>
        <li><strong class="handle">Pretty-print:</strong> A &quot;pretty-print&quot; tool reformats markup code to make it easier to read by programmers. The tool never makes changes to the markup tags.</li>
        <li><strong class="handle">Video compression:</strong> A tool that compresses video does not automatically delete text tracks or secondary audio tracks, since these may contain accessibility information.</li>

      </ul>
    </div>
    <!-- implementing-section -->
    <div class="implementing-section">
      <h5 class="implementing-heading"><a id="sc_b122-r" name="sc_b122-r"></a>Related Resources for Success Criterion B.1.2.2:</h5>
      <ul>
        <li><a href="#conf-rel-wcag">WCAG 2.0</a> (including <a href="http://www.w3.org/TR/2008/NOTE-UNDERSTANDING-WCAG20-20081211/">Understanding WCAG 2.0</a> and <a href="http://www.w3.org/WAI/WCAG20/quickref/Overview.php">How to Meet WCAG 2.0</a>)</li>

      </ul>
    </div>
    <!-- implementing-section -->
  </div>

  <h4 class="sc-title"><a id="sc_b123" name="sc_b123"> </a><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_b123">Return to B.1.2.3 in Guidelines</a></div>
	   </div>

  <div class="techs-only">
    <div class="implementing-section">
      <h5 class="implementing-heading"><a id="sc_b123-i" name="sc_b123-i"></a>Intent of Success Criterion B.1.2.3:</h5>
      <p>The intent of this success criterion is to increase the likelihood that text alternatives will be preserved by web content transformations. This is especially important because text alternatives, such as labels and long descriptions, can represent substantial investments of author effort. </p>
    </div>
    <!-- implementing-section -->
    <div class="implementing-section">

      <h5 class="implementing-heading"><a id="sc_b123-e" name="sc_b123-e"></a>Examples of Success Criterion B.1.2.3:</h5>
      <ul>
        <li><strong class="handle">Save as HTML:</strong> A word processor includes a &quot;Save as Simple HTML&quot; feature that re-codes word processor files into HTML where there is a one-to-one correspondence between elements. As a result, some word processor-specific content is lost (e.g. change tracking, footnotes). However, because of the existence of the &lt;img&gt; tag in HTML, images are preserved and, in order to meet this success criterion, the text alternatives associated with the image are also preserved in HTML.</li>
      </ul>

    </div>
    <!-- implementing-section -->
    <div class="implementing-section">
      <h5 class="implementing-heading"><a id="sc_b123-r" name="sc_b123-r"></a>Related Resources for Success Criterion B.1.2.3:</h5>
      <ul>
        <li><a href="#conf-rel-wcag">WCAG 2.0</a> (including <a href="http://www.w3.org/TR/2008/NOTE-UNDERSTANDING-WCAG20-20081211/">Understanding WCAG 2.0</a> and <a href="http://www.w3.org/WAI/WCAG20/quickref/Overview.php">How to Meet WCAG 2.0</a>)</li>

      </ul>
    </div>
    <!-- implementing-section -->
  </div>


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


<span class="techs-only">[<a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/Overview.html#gl_b21">Return to Guideline</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><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_b211">Return to B.2.1.1 in Guidelines</a></div>
	   </div>	
		
        <div class="techs-only">
      <div class="implementing-section">
    <h5 class="implementing-heading"><a id="sc_b211-i" name="sc_b211-i"></a>Intent of Success Criterion B.2.1.1:</h5> 
	<p>The intent of this success criterion is to ensure that authors who have the motivation and knowledge to create accessible web content using an authoring tool are not prevented from doing so by restrictions in the actions that the authoring tool allows them to perform. The subsequent success criteria in Part B will build on this minimal requirement.  </p>
	<p>Note that the term &quot;restricted&quot; is not intended to have any negative connotation. Authoring tools usually restrict web content authoring in order to simplify the production of content that is in fact complex and technical. The accessibility implications of the restrictions may be positive or negative and need to be considered case by case: </p>

	<p>Examples of unrestricted authoring:</p>
	<ol type="a">
	  <li>source code editor: authors can type whatever they like (e.g. <code>&lt;img src=&quot;...&quot; alt=&quot;...&quot; longdesc=&quot;...&quot; /&gt;</code>)</li>

	  <li>WYSIWYG editor for HTML4: the &quot;Insert Image&quot; dialog includes all of the HTML4 attributes for <code>&lt;img&gt;</code> </li>
	  </ol>
	<p>Examples of restricted authoring that does not prevent WCAG 2.0 success criteria from being met:</p>
	<ol type="a">
	  <li>WYSIWYG editor for HTML4: the &quot;Insert Image&quot; dialog includes just some of the HTML4 attributes for <code>&lt;img&gt;</code>, but &quot;alt&quot; and &quot;longdesc&quot; are included in the subset.</li>

	  <li>CMS: authors can only add images that they have previously uploaded to their &quot;Asset Manager&quot;. While alt-text and long description do not appear as options when they choose images from the &quot;Asset Manager&quot; to include on a page, they can add/edit these values at any time within the &quot;Asset Manager&quot;.</li>
	  </ol>
	<p>Examples of restricted authoring that prevents WCAG 2.0 success criteria from being met:</p>
	<ol type="a">
	  <li>WYSIWYG editor for HTML4: the &quot;Insert Image&quot; dialog has only one field &quot;src&quot;. There is no possible way to add other attribute values, including for the &quot;alt&quot; and &quot;longdesc&quot; attributes. </li>

	  <li>CMS: to be saved, each page of content must have a main title, but when the author provides text for the title it is marked up with presentation markup rather than appropriate header markup. </li>
	  </ol>
	<p>See Also: Unrestricted authoring tools entail less author guidance and therefore may allow the introduction of more accessibility problems than authoring tools with restrictions that encourage accessibility. ATAG 2.0 addresses this issue with other success criteria, including <a href="#sc_b311">B.3.1.1 Checking Assistance (WCAG)</a>, which requires an accessibility checking feature.</p>
	<p>See Also: Restrictions on authors may also be related to automatically generated content. ATAG 2.0 addresses the accessibility of automatically generated content in <a href="#gl_b11">Guideline B.1.1: Ensure automatically specified content is accessible</a>.</p>
	<p><a href="#conf-rel-wcag">WCAG 2.0</a> is referenced because it provides testable success criteria to measure web content accessibility.</p>

	</div> <!-- implementing-section -->
      <div class="implementing-section">
    <h5 class="implementing-heading"><a id="sc_b211-e" name="sc_b211-e"></a>Examples of Success Criterion B.2.1.1:</h5>
        <ul>
          <li><strong class="handle">Accessible workflow exists:</strong> An authoring tool is designed such that accessible web content (in this case to <a href="#conf-rel-wcag">WCAG 2.0</a> Level A) will result if authors do all of the following:
            <ul>
              <li>turn on all features that support the production of accessible content; and </li>
              <li>correctly follow all prompts by features that support the production of accessible content; and</li>
              <li>uses the accessibility checker, including a final check prior to publishing; and</li>
              <li>correctly perform any manual checks suggested by the accessibility checker; and</li>
              <li>correctly repair all of the automatically, semi-automatically or manually identified web content accessibility problems using the automated, semi-automated and manual repair assistance that the authoring tool provides.</li>
            </ul>
          </li>
          <li><strong class="handle">Source content editing-view:</strong> An authoring tool is designed around a source editing-view, allowing motivated and knowledgeable authors to control every detail of the  content produced, including following accessible authoring practices.</li>
        </ul>
    </div> <!-- implementing-section -->
      <div class="implementing-section">
    <h5 class="implementing-heading"><a id="sc_b211-r" name="sc_b211-r"></a>Related Resources for Success Criterion B.2.1.1:</h5>
        <ul>
            <li><a href="#conf-rel-wcag">WCAG 2.0</a> (including <a href="http://www.w3.org/TR/2008/NOTE-UNDERSTANDING-WCAG20-20081211/">Understanding WCAG 2.0</a> and <a href="http://www.w3.org/WAI/WCAG20/quickref/Overview.php">How to Meet WCAG 2.0</a>)</li>
          </ul>
    </div> <!-- implementing-section -->

  </div>
</div> <!-- sc-level -->
<h3 class="guideline"><a id="gl_b22" name="gl_b22"> </a><span class="techs-only">Implementing</span> Guideline B.2.2: Guide authors to produce accessible content.
 
<span class="techs-only">[<a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/Overview.html#gl_b22">Return to Guideline</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><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_b221">Return to B.2.2.1 in Guidelines</a></div>
	   </div>
	   
  <div class="techs-only">
    <div class="implementing-section">
      <h5 class="implementing-heading"><a id="sc_b221-i" name="sc_b221-i"></a>Intent of Success Criterion B.2.2.1:</h5>
      <p>The intent of this success criterion is to help ensure that accessible authoring practices are part of the default workflow of authoring tools. This requirement applies when the authoring outcome is predictable by the authoring tool. For example, a generic &quot;insert table&quot; command would not be applicable, despite the fact that an author might misuse it for layout, because the author might be seeking the outcome of adding tabular information. In contrast, a page layout editor is covered by the requirement because the purpose of the feature is to edit the page layout.</p>

      <p><a href="#conf-rel-wcag">WCAG 2.0</a> is referenced because it provides testable success criteria to measure web content accessibility.</p>
    </div>
    <!-- implementing-section -->
    <div class="implementing-section">
      <h5 class="implementing-heading"><a id="sc_b221-e" name="sc_b221-e"></a>Examples of Success Criterion B.2.2.1:</h5>
      <ul>
        <li><strong class="handle">Structural Markup:</strong> A WYSIWYG HTML editor does not include any authoring action options that will necessarily result in web content that will not meet the  <a href="#conf-rel-wcag">WCAG 2.0</a> Level A success criteria. For example:
          <ul>
            <li>a toolbar button that allows text to be marked as bold does so by adding a <code>&lt;strong&gt;</code> element rather than a <code>&lt;span&gt; </code>element with a bold style.</li>
            <li>a the toolbar button for placing text into a bulleted list does so with list markup (<code>&lt;ul&gt;</code> and <code>&lt;li&gt;</code> elements) rather than a <code>&lt;span&gt;</code> element-based implementation.</li>
            <li>a page layout view makes use of CSS positioning rather than table markup. </li>
          </ul>
        </li>
        <li><strong class="handle">De-emphasizing problematic options:</strong> A WYSIWYG   editing-view emphasizes more accessible choices with a higher position in the menus and a position in user interface shortcuts, such as toolbars. Choices that always lead to less accessible web content are de-emphasized with lower menu positions.<br />
            <span class="figure"><strong>Figure:</strong> An authoring tool that supports two methods for setting text color: using CSS and using <code>font</code>. Since using CSS is the more accessible option, it is given a higher prominence within the authoring interface by: (1) the &quot;CSS Styling&quot; option appearing above the &quot;FONT Styling&quot; option in the drop down Text menu, and (2) the CSS styling option being used to implement the one-click text color formatting button in the tool bar. The association is made clear because the toolbar button has the same icon (an &quot;A&quot; beside a color spectrum) as the &quot;Color&quot; sub-menu item under the &quot;CSS Styling&quot; menu option.). (Source: mock up by AUWG) <br />
            <img src="tech_images/b_30.png" width="417" height="171" alt="See the example caption above for description." /></span></li>
      </ul>
    </div>
    <!-- implementing-section -->
    <div class="implementing-section">
      <h5 class="implementing-heading"><a id="sc_b221-r" name="sc_b221-r"></a>Related Resources for Success Criterion B.2.2.1:</h5>
      <ul>
        <li><a href="#conf-rel-wcag">WCAG 2.0</a> (including <a href="http://www.w3.org/TR/2008/NOTE-UNDERSTANDING-WCAG20-20081211/">Understanding WCAG 2.0</a> and <a href="http://www.w3.org/WAI/WCAG20/quickref/Overview.php">How to Meet WCAG 2.0</a>)</li>

      </ul>
    </div><!-- implementing-section -->
  </div>
<h4 class="sc-title"><a id="sc_b222" name="sc_b222"> </a><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_b222">Return to B.2.2.2 in Guidelines</a></div>
	   </div>
	   
<div class="techs-only">
    <div class="implementing-section">
      <h5 class="implementing-heading"><a id="sc_b222-i" name="sc_b222-i"></a>Intent of Success Criterion B.2.2.2:</h5>
      <p>The intent of this success criterion is to ensure that if authoring tools provide authors with content authoring support that goes beyond source editing (e.g. property dialogs, etc.) then accessibility information that is required for the content are similarly supported. In many cases, authoring tools support a subset of all of the possible properties that technologies might offer. This success criterion requires that the subset  of supported properties must include properties required for conformance to <a href="#conf-rel-wcag">WCAG 2.0</a>.</p>
      <p>The note is a reminder that the mechanisms for adding accessibility information properties must have prominence that is at least comparable with the other mechanisms for other properties. </p>
    </div>
    <!-- implementing-section -->
    <div class="implementing-section">
      <h5 class="implementing-heading"><a id="sc_b222-e" name="sc_b222-e"></a>Examples of Success Criterion B.2.2.2:</h5>
      <ul>
        <li><strong class="handle">Context sensitive properties:</strong> A markup authoring tool includes a context sensitive properties pane that displays property fields for the most common subset of attributes  associated with the markup element that currently has focus in the editing-view. The attributes that are required for <a href="#conf-rel-wcag">WCAG 2.0</a> are included in the subset. <br />
            <span class="figure"><strong>Figure:</strong> An &quot;Image Properties&quot; dialog box in which the input fields are ordered (from top to bottom, left to right): source (&quot;src&quot;), short label (&quot;alt&quot;), long description (&quot;longdesc&quot;), height, and width. The buttons at the bottom are &quot;More...&quot;, &quot;OK&quot; and &quot;Cancel&quot;. (Source: mock up by AUWG) <br />
            <img src="tech_images/b_33.png" alt="See the example caption above for description." width="333" height="171" /></span></li>
        <li><strong class="handle">Time-based media alternatives:</strong> A SMIL authoring tool  lets authors create multimedia presentations by pulling together video, audio and timed text objects on to a timeline, even though the tool has no built-in ability to edit these objects. When  authors specify information about video to be inserted, they are also provided with the opportunity to associate a timed text object (for captions), an audio object (for audio description), and a secondary video (for sign language interpretation). When  authors specify information about audio to be inserted, they are also provided with the opportunity to associate a timed text object (for captions) and a video (for sign language interpretation).</li>
        <li><strong class="handle">Data table for a bar graph:</strong> A learning content management system has a feature that lets authors insert figures. The feature accepts images, even though the authoring tool has no built-in ability to edit images, but as part of the &quot;figure properties&quot; the authors can identify the figure as a graph. If they choose this option, then the system assists them in creating an accompanying data table using the values used to create the graph. </li>
      </ul>
    </div>
    <!-- implementing-section -->
    <div class="implementing-section">
      <h5 class="implementing-heading"><a id="sc_b222-r" name="sc_b222-r"></a>Related Resources for Success Criterion B.2.2.2:</h5>
      <ul>
        <li><a href="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#prompting-types">Appendix A: Gathering Accessibility Information from Authors</a></li>
        <li><a href="#conf-rel-wcag">WCAG 2.0</a> (including <a href="http://www.w3.org/TR/2008/NOTE-UNDERSTANDING-WCAG20-20081211/">Understanding WCAG 2.0</a> and <a href="http://www.w3.org/WAI/WCAG20/quickref/Overview.php">How to Meet WCAG 2.0</a>)</li>
      </ul>
    </div>
    <!-- implementing-section -->
  </div>
  </div>
<!-- sc-level -->
<div class="sc-level">
  <h4 class="sc-title"><a id="sc_b223" name="sc_b223"> </a><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_b223">Return to B.2.2.3 in Guidelines</a></div>
	   </div>
	   		
      <div class="techs-only">

      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_b223-i" name="sc_b223-i"></a>Intent of Success Criterion B.2.2.3:</h5> 
		<p>The intent of this success criterion is to inform authors as early as possible about the degree to which the authoring tool will be able to provide accessible web content production support for the web content technologies that it is capable of producing. If accessibility is part of early decision-making, it will reduce the likelihood that retrofits for accessibility will be required later on. </p>
		<p>The success criterion makes no judgment or assumption about the accessibility of web content technologies. Instead, it is assumed that any technology can be made accessible if used properly. For example, a technology with no intrinsic accessibility features can be made accessible in conjunction with another technology (e.g. bitmap images may be made more accessible via HTML text labels).</p>
		<p>Instead, the success criterion depends on whether the authoring tool in question actually supports the production of accessible content in the technology through features such as checking and repair or does not. The choice of which technologies to provide accessible content production support for is left completely to the developer (e.g. a developer might decide to begin by adding support to a less-popular technology because a major customer has requested it). </p>
		<p>The wording &quot;provides the option of producing&quot; is intended to rule out situations in which authors make technology choices without guidance by the authoring tool (e.g. by hand coding, by specifying a DTD). </p>
		<p>The wording &quot;for publishing&quot; is intended to rule out situations in which incomplete content is created in interim formats that are not intended for publishing. </p>
		<p>Requirement (a) is that there be a warning before authors have progressed too far with a technology option lacking support for the production of accessible content in the authoring tool. The warning may appear before authors make a selection or after. </p>
		<p>Requirement (b) is simply to inform the user, who has now just received a warning that the authoring tool lacks accessibility support for a given technology, that one or more other web content technologies produced by the authoring tool are supported by such accessibility support features. The list may be a partial or complete list of the technologies for which support for the production of accessible content is provided. In either case, it is left to authors, to decide whether any of the listed technologies might be appropriate for the task or whether they will continue on with their original selection.</p>
      </div> <!-- implementing-section -->
      <div class="implementing-section">

        <h5 class="implementing-heading"><a id="sc_b223-e" name="sc_b223-e"></a>Examples of Success Criterion B.2.2.3:</h5>
          <ul>
            <li><strong class="handle">Choosing video formats:</strong> A video authoring tool allows authors to save into several video file formats. However, the authoring tool includes a built-in closed-caption editor that only works with one of the file formats. While there is nothing intrinsically &quot;inaccessible&quot; about any of these three video formats, when the option to save is presented, the formats that are not supported by the authoring tool's own closed-caption editor include warnings that caption support is not provided. In the warning's explanation, the video format that is supported by the closed-caption editor is identified. </li>
          </ul>
        </div> <!-- implementing-section -->

      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_b223-r" name="sc_b223-r"></a>Related Resources for Success Criterion B.2.2.3:</h5>
          <ul>
            <li>N/A</li>
          </ul>
        </div> <!-- implementing-section -->
      </div> <!-- techs-only -->

</div><!-- sc-level -->
<h3 class="guideline"><a id="gl_b23" name="gl_b23"> </a><span class="techs-only">Implementing</span> Guideline B.2.3: Assist authors with managing alternative content for non-text content. 
 
<span class="techs-only">[<a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/Overview.html#gl_b23">Return to Guideline</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><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_b231">Return to B.2.3.1 in Guidelines</a></div>
	   </div>
	   		
		<div class="techs-only"> 
      <div class="implementing-section">
            <h5 class="implementing-heading"><a id="sc_b231-i" name="sc_b231-i"></a>Intent of Success Criterion B.2.3.1:</h5> 
			<p>The intent of this success criterion is to ensure that authors can add alternative content for non-text content and modify that alternative content in the future. </p>
			<p>If the type of alternative content (e.g. alternative text) is not typically displayed on screen by user agents, then WYSIWYG editing-views may not display it. This is acceptable as long as another mechanism is provided for modifying that alternative content (e.g. an &quot;Image Properties&quot; dialog).</p>

      </div> <!-- implementing-section -->
      <div class="implementing-section">
          <h5 class="implementing-heading"><a id="sc_b231-e" name="sc_b231-e"></a>Examples of Success Criterion B.2.3.1:</h5>
              <ul>
                <li><strong class="handle">Source content editing-view:</strong>
				In a source editing-view, alternative content within the source is always available, regardless of what user agents might render. If alternative content is referenced from an external location (e.g. HTML4 <code>longdesc</code>), then that resource can be opened for editing.</li>

                <li><strong class="handle">Properties dialog:</strong>
				In a WYSIWYG editing-view, alternative content is not displayed, since the editing-view is designed to mimic typical user agents. However, the alternative content can be accessed and edited via a properties editor that displays the properties for the content that currently has focus.</li>
              </ul>
          </div> <!-- implementing-section -->
      <div class="implementing-section">
          <h5 class="implementing-heading"><a id="sc_b231-r" name="sc_b231-r"></a>Related Resources for Success Criterion B.2.3.1:</h5>
            <ul>

              <li><a href="http://www.w3.org/TR/2008/NOTE-UNDERSTANDING-WCAG20-20081211/">Understanding WCAG 2.0</a>, especially the section <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance.html#uc-text-alternatives-head">Understanding &quot;Text Alternatives&quot;</a>. </li>
            </ul>
          </div> <!-- implementing-section -->
        </div> 

        <h4 class="sc-title"><a id="sc_b232" name="sc_b232"> </a><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_b232">Return to B.2.3.2 in Guidelines</a></div>
	   </div>
	   		  
        <div class="techs-only"> 
      <div class="implementing-section">

        <h5 class="implementing-heading"><a id="sc_b232-i" name="sc_b232-i"></a>Intent of Success Criterion B.2.3.2:</h5>
		<p>The intent of this success criterion is to prevent the production of alternative content that is not useful to an end user because it has not been approved by an author and/or it is derived from unreliable sources.</p>
		<p>The requirement  of author control (a) enables knowledgeable authors to have the final say on alternative content suggested by authoring tools.</p>
		<p>The limitation to relevant sources (b) is intended to reduce the possibility that authors who are unfamiliar with accessibility may approve alternative content suggestions without realizing the problems these can cause for end users.</p>
      </div> <!-- implementing-section -->
      <div class="implementing-section">

          <h5 class="implementing-heading"><a id="sc_b232-e" name="sc_b232-e"></a>Examples of Success Criterion B.2.3.2:</h5>
              <ul>
                <li><strong class="handle">Metadata on an archive:</strong> A content management system includes a feature that allows authors to make use of images from an extensive photographic archive. The photographic archive includes metadata for each photograph with title and description fields. The title field is always filled, but the description field is sometimes lacking. When authors select an image for insertion, the metadata title is suggested as the alternative text label and the metadata description (if any) is suggested as the long description. In both cases, some basic guidance on what constitutes correct alternative content is provided to help authors judge the appropriateness of the suggestions. The authors are still given the opportunity to accept, modify, or   reject the suggested alternative content prior to insertion, in case the non-text content is being used in a different context. </li>
                <li><strong class="handle">Alternative content registry:</strong> A web page authoring tool implements an alternative content registry (see also <a href="#sc_b234">Success Criterion B.2.3.4</a>). Since the alternative content was gathered from authors' previous entries into the same fields for the same objects, these are acceptable as relevant sources. The authors are still given the opportunity to accept, modify, or   reject the suggested alternative content prior to insertion, in case the non-text content is being used in a different context. </li>

                <li> <strong class="handle">Accepting patterns:</strong> An authoring tool allows authors to accept patterns of future uses of an alternative content under certain conditions (e.g. whenever the same non-text content is marked with the same semantic role).</li>
              </ul>
        </div> <!-- implementing-section -->
      <div class="implementing-section">
          <h5 class="implementing-heading"><a id="sc_b232-r" name="sc_b232-r"></a>Related Resources for Success Criterion B.2.3.2:</h5>
              <ul>

<li><a href="http://www.w3.org/TR/2008/NOTE-UNDERSTANDING-WCAG20-20081211/">Understanding WCAG 2.0</a>, especially the section <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance.html#uc-text-alternatives-head">Understanding &quot;Text Alternatives&quot;</a>. </li>
</ul>
        </div> <!-- implementing-section -->
        </div> 
		       
        <h4 class="sc-title"><a id="sc_b233" name="sc_b233"> </a><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_b233">Return to B.2.3.3 in Guidelines</a></div>
	   </div>
	   
        <div class="techs-only"> 
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_b233-i" name="sc_b233-i"></a>Intent of Success Criterion B.2.3.3:</h5>
		<p>The intent of this success criterion is to address situations in which authors have either not noticed or ignored opportunities for adding alternative content and have ended their authoring sessions. ATAG 2.0  does not require authoring tools to attempt automated repairs in this  situation because doing so risks misleading accessibility checking tools  and end users into the assumption that the alternative content was  either provided or approved by an  author. However, if developers do want to provide automated assistance to end users, then this success criterion specifies what types of repairs may be provided. Essentially: </p>
        <ol type="a">
          <li> Basic &quot;text&quot; processing repairs using information that is equally  available to user agents (e.g. file name, text metadata within non-text  objects, the title of a linked resource, etc.) are not allowed,  because they are best performed by user agents and assistive technologies. </li>
          <li>Repairs are allowed when authoring tools have contextual information  (e.g. the image is the author's profile picture) that user agents do  not have equal access to.</li>
          <li>Repairs are also allowed that go beyond simple text processing to directly processing images, audio or video. The intent here is to encourage progress in these rapidly advancing fields.</li>
        </ol>
		</div> <!-- implementing-section -->
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_b233-e" name="sc_b233-e"></a>Examples of Success Criterion B.2.3.3:</h5>
            <ul>
              <li><strong class="handle">Contextual information is known:</strong> A social networking authoring tool allows authors to add a description of their profile picture. If an author chooses not to provide a description, the authoring tool labels the image as the author's profile picture.</li>
              <li><strong class="handle">Contextual information is not known:</strong> A web page authoring tool allows authors to insert images. If an author ignores opportunities to add alternative content and then ends the authoring session, the authoring tool has access to information such as the file name of the image, but since this is text information that is equally available to user agents, it is not suggested.</li>
              <li><strong class="handle">Auto-generated transcript:</strong> An on-line video editing and hosting authoring tool has a feature that allows authors to create transcripts or captions for their videos. Authors can begin by copying in a transcript if one is available or the authoring tool can use voice recognition technology to generate a transcript for the authors to correct. While this is preferred, the authoring tool also has a setting in which it will automatically add the auto-generated transcript to the published presentation if the end user requests this and the author has not made an attempt to add their own captions or transcript.</li>
            </ul>

        </div> <!-- implementing-section -->
        <h5 class="implementing-heading"><a id="sc_b233-r" name="sc_b233-r"></a>Related Resources for Success Criterion B.2.3.3:</h5>
            <ul>
              <li><a href="http://www.w3.org/TR/2008/NOTE-UNDERSTANDING-WCAG20-20081211/">Understanding WCAG 2.0</a>, especially the section <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance.html#uc-text-alternatives-head">Understanding &quot;Text Alternatives&quot;</a>. </li>
</ul>
        </div> <!-- implementing-section -->

    </div> <!-- sc-level -->
 
<div class="sc-level">
  <h4 class="sc-title"><a id="sc_b234" name="sc_b234"> </a><span class="techs-only">Implementing Success Criterion </span> 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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_b231">Return to B.2.3.4 in Guidelines</a></div>
	   </div>
	    
        <div class="techs-only"> 
      <div class="implementing-section">
          <h5 class="implementing-heading"><a id="sc_b234-i" name="sc_b234-i"></a>Intent of Success Criterion B.2.3.4:</h5>
		  <p>The intent of this success criterion is to ensure that when authors spend effort providing alternative content, this content is retained by the authoring tool in a form that allows it to be easily reused.</p>
		  <p>The editing requirement (b) allows authors to correct or remove alternatives that are outdated or that contain spelling errors, etc...</p>
		  </div> 
      <!-- implementing-section -->
      <div class="implementing-section">
          <h5 class="implementing-heading"><a id="sc_b234-e" name="sc_b234-e"></a>Examples of Success Criterion B.2.3.4:</h5>
              <ul>
                <li><strong class="handle">Alternative content registry:</strong>
				An authoring tool includes a registry that associates object identity information with alternative content (i.e. text, URIs). Whenever an object is used and any alternative content is collected, the object's identifying information and the alternative content is added to the registry. The stored alternative content is suggested as alternative content for author approval whenever the associated object is inserted. The alternative content registry allows several different versions of alternative content to be associated with a single object (e.g. various translations, various contexts).
				<br />
				<span class="figure"><strong>Figure:</strong> The interface of a sample alternative content registry viewer is shown. The design takes into account multiple non-text content objects of the same name, multiple types of text equivalents for each non-text content object, and multiple versions of each text equivalent type. In the viewer shown here, the author has selected &quot;image&quot; as the &quot;media type&quot; and then selected pic123.gif as the &quot;content&quot; to edit. This has brought up a rendering of the &quot;earthrise&quot; image. The viewer also shows that the content has three text labels. The author has selected one (&quot;An earth rise as seen from the moon&quot;) in order to edit it. In addition some authoring tips are included (&quot;Alternate text should be 10 words or less and should include any text in the image&quot;, &quot;Image buttons should have alternate text that describes the button function.&quot;, and &quot;Image bullets should have &quot;bullet&quot; as alternate text.&quot;(Source: mock up by AUWG)
				<br /><img src="tech_images/b_28.png" alt="See the example caption above for description." width="562" height="373" /></span></li>

                <li><strong class="handle">Interoperability with pre-authored content:</strong>
				An enterprise authoring tool's clip art system is integrated with an alternative content registry so that new alternative content created by any author on the enterprise system is stored along with the pre-authored alternative content for the images in the system. The keyword search feature of the clip art system makes use of any alternative content to retrieve matches.</li>
              </ul>
          </div> <!-- implementing-section -->
      <div class="implementing-section">
          <h5 class="implementing-heading"><a id="sc_b234-r" name="sc_b234-r"></a>Related Resources for Success Criterion B.2.3.4:</h5>
              <ul>

<li><a href="http://www.w3.org/TR/2008/NOTE-UNDERSTANDING-WCAG20-20081211/">Understanding WCAG 2.0</a>, especially the section <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance.html#uc-text-alternatives-head">Understanding &quot;Text Alternatives&quot;</a>. </li>
</ul>
          </div> <!-- implementing-section -->
      </div> 
    </div> <!-- sc-level -->
	  
    <h3 class="guideline"><a id="gl_b24" name="gl_b24"> </a><span class="techs-only">Implementing</span> Guideline B.2.4: Assist authors with accessible templates.

 
<span class="techs-only">[<a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/Overview.html#gl_b24">Return to Guideline</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><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_b241">Return to B.2.4.1 in Guidelines</a></div>
	   </div>

        <div class="techs-only"> 
      <div class="implementing-section">
          <h5 class="implementing-heading"><a id="sc_b241-i" name="sc_b241-i"></a>Intent of Success Criterion B.2.4.1:</h5>
		  <p>The intent of this success criterion is to reduce the possibility that authors will be forced to use inaccessible templates to create web content because accessible templates do not exist.</p>
		  </div> <!-- implementing-section -->
      <div class="implementing-section">
          <h5 class="implementing-heading"><a id="sc_b241-e" name="sc_b241-e"></a>Examples of Success Criterion B.2.4.1:</h5>

              <ul>
                <li><strong class="handle">Variety of accessible templates:</strong> A web page authoring tool provides several template choices for home pages, guest books and on-line albums. For each type of functionality, the basic template option is accessible  (see definition of &quot;<a href="#def-Accessible-Template">accessible template (WCAG)</a>&quot;).</li>
                <li><strong class="handle">Content management system:</strong> A content management system offers a variety of templates to authors for different purposes (e.g. information page, interactive form page, registration page, etc.). All of the templates are accessible.</li>
              </ul>

          </div> <!-- implementing-section -->
      <div class="implementing-section">
          <h5 class="implementing-heading"><a id="sc_b241-r" name="sc_b241-r"></a>Related Resources for Success Criterion B.2.4.1:</h5>
              <ul>
                <li>N/A</li>
              </ul>
          </div> <!-- implementing-section -->

        </div> 
    </div>  <!-- sc-level -->
	
    <div class="sc-level">
      <h4 class="sc-title"><a id="sc_b242" name="sc_b242"> </a><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_b242">Return to B.2.4.2 in Guidelines</a></div>
	   </div>		  

        <div class="techs-only">
      <div class="implementing-section">
          <h5 class="implementing-heading"><a id="sc_b242-i" name="sc_b242-i"></a>Intent of Success Criterion B.2.4.2:</h5>
		  <p>The intent of this success criterion is to ensure that when faced with template options that differ in terms of accessibility, authors can more easily determine the accessibility status of templates prior to selecting them. </p>
		  <p>The note makes it clear that developers have flexibility with respect to implementation. If only a few inaccessible templates exist, it may be preferable to mark the inaccessible ones. If only a few accessible options exist, it may be preferable to mark those. In other cases, the accessibility of every template might be indicated. </p>
		  <p>The mechanism is not specified and might include data in dedicated metadata fields (e.g. a WCAG conformance level), plain text in a description field (e.g., &quot;5-day week calendar template. Meets WCAG Level A&quot;), or on-the-fly checkers, once the technology exists.</p>
      </div> 
      <!-- implementing-section -->
      <div class="implementing-section">
          <h5 class="implementing-heading"><a id="sc_b242-e" name="sc_b242-e"></a>Examples of Success Criterion B.2.4.2:</h5>
              <ul>
                <li><strong class="handle">Accessibility status as metadata:</strong> An HTML editor includes a template selection mechanism that consists of selecting templates from a list. The template list has several sortable fields that are populated from the templates' metadata: the template name, date, popularity and accessibility status. The accessibility status values are: &quot;Level A&quot;, &quot;Level AA&quot;, &quot;Level AAA&quot;, &quot;None&quot; and &quot;Not Available&quot;. By default, the list of templates is sorted alphabetically, but the author has the option to sort by accessibility status instead. The accessibility status values of the developer-provided templates are based on the degree to which <a href="#conf-rel-wcag">WCAG 2.0</a> success criteria are met when the template is used (see definition of &quot;<a href="#def-Accessible-Template">accessible template (WCAG)</a>&quot;). This may have been assessed manually or semi-automatically with an accessibility checker.</li>

                <li><strong class="handle">Accessibility status included in template names/descriptions:</strong> In a wiki system, creating a new page brings up a list of available templates. Each template is only displayed as a name and a short description. When the developer has ensured the accessibility of a template, this is indicated by the template name (e.g. &quot;slide show template (accessible)&quot;) and/or information in the description (&quot;This template meets WCAG 2.0 Level A as provided and should result in an accessible page, if accessible authoring practices are followed.&quot;).</li>
              </ul>
          </div> <!-- implementing-section -->
      <div class="implementing-section">
          <h5 class="implementing-heading"><a id="sc_b242-r" name="sc_b242-r"></a>Related Resources for Success Criterion B.2.4.2:</h5>

              <ul>
                <li>N/A</li>
              </ul>
          </div> <!-- implementing-section -->
        </div>
		
        <h4 class="sc-title"><a id="sc_b243" name="sc_b243"> </a><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_b243">Return to B.2.4.3 in Guidelines</a></div>
	   </div>

        <div class="techs-only">
      <div class="implementing-section">
          <h5 class="implementing-heading"><a id="sc_b255-i" name="sc_b255-i"></a>Intent of Success Criterion B.2.4.3:</h5>
		  <p>The intent of this success criterion is to ensure that new templates that authors create and which might be used by subsequent authors interoperate with the relevant template selection identification mechanism (See <a href="#sc_b242">Success Criterion B.2.4.2</a>).</p>
		  </div> <!-- implementing-section -->
      <div class="implementing-section">

          <h5 class="implementing-heading"><a id="sc_b243-e" name="sc_b243-e"></a>Examples of Success Criterion B.2.4.3:</h5>
              <ul>
                <li><strong class="handle">Save as template:</strong>
				An authoring tool provides a &quot;save as template&quot; feature. When authors activate this feature, the authoring tool automatically runs an accessibility checker on the template with sample data. Once the checker returns a resulting accessibility status, authors have the option of labeling the template with this status. If the template fails to conform to <a href="#conf-rel-wcag">WCAG 2.0</a> with sample data, then authors are advised that templates should be held to a high accessibility standard, since they will be repeatedly reused.</li>

                <li><strong class="handle">Edit template name/description:</strong> When saving templates, an authoring tool provides authors with the ability to add their own name and description, which could potentially include accessibility status information. </li>
              </ul>
          </div> <!-- implementing-section -->
      <div class="implementing-section">
          <h5 class="implementing-heading"><a id="sc_b243-r" name="sc_b243-r"></a>Related Resources for Success Criterion B.2.4.3:</h5>
              <ul>
                <li><a href="#conf-rel-wcag">WCAG 2.0</a> (including <a href="http://www.w3.org/TR/2008/NOTE-UNDERSTANDING-WCAG20-20081211/">Understanding WCAG 2.0</a> and <a href="http://www.w3.org/WAI/WCAG20/quickref/Overview.php">How to Meet WCAG 2.0</a>)</li>

              </ul>
          </div> <!-- implementing-section -->
      </div> 
	  
    </div> 
    <!-- sc-level -->
 
<div class="sc-level">
  <h4 class="sc-title"><a id="sc_b244" name="sc_b244"> </a><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_b244">Return to B.2.4.4 in Guidelines</a></div>
	   </div>

        <div class="techs-only">
      <div class="implementing-section">
          <h5 class="implementing-heading"><a id="sc_b244-i" name="sc_b244-i"></a>Intent of Success Criterion B.2.4.4:</h5>
		  <p>The intent of this success criterion is to ensure that authors using authoring tools that do not include template selection mechanisms are made aware when non-accessible template options are provided. </p>
		  </div> <!-- implementing-section -->
      <div class="implementing-section">

          <h5 class="implementing-heading"><a id="sc_b244-e" name="sc_b244-e"></a>Examples of Success Criterion B.2.4.4:</h5>
              <ul>
                <li><strong class="handle">Warning messages in non-accessible templates :</strong> A web page authoring tool allows templates to be opened using the standard file open mechanism of the operating system. Most of the templates are accessible, but several are not. In these cases, cautionary messages are present at the top of the non-accessible templates informing authors of the issue. </li>
              </ul>
          </div> <!-- implementing-section -->

      <div class="implementing-section">
          <h5 class="implementing-heading"><a id="sc_b244-r" name="sc_b244-r"></a>Related Resources for Success Criterion B.2.4.4:</h5>
              <ul>
                <li>N/A</li>
              </ul>
          </div> <!-- implementing-section -->
        </div> <!-- techs-only -->

</div> <!-- sc-level -->
 
    <h3 class="guideline"><a id="gl_b25" name="gl_b25"> </a><span class="techs-only">Implementing</span> Guideline B.2.5: Assist authors with accessible pre-authored content.  <span class="techs-only">[<a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/Overview.html#gl_b25">Return to Guideline</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><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_b251">Return to B.2.5.1 in Guidelines</a></div>
	   </div>

    <div class="techs-only">
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_b251-i" name="sc_b251-i"></a>Intent of Success Criterion B.2.5.1:</h5>
        <p>The intent of this success criterion is to ensure that authors can easily determine the accessibility status of pre-authored content prior to selecting them and that authors are more likely to notice the accessible pre-authored content options.</p>
      </div>
      <!-- implementing-section -->
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_b251-e" name="sc_b251-e"></a>Examples of Success Criterion B.2.5.1:</h5>

        <ul>
          <li><strong class="handle">Sort by accessibility status:</strong> A clip-art repository lists the available images and provides the alternative text associated with the images in a sortable field.</li>
          </ul>
      </div>
      <!-- implementing-section -->
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_b251-r" name="sc_b251-r"></a>Related Resources for Success Criterion B.2.5.1:</h5>

        <ul>
          <li>N/A</li>
        </ul>
      </div>
      <!-- implementing-section -->
    </div>
    <!-- techs-only -->
	</div> <!-- sc-level -->

<div class="sc-level">

    <h4 class="sc-title"><a id="sc_b252" name="sc_b252"> </a><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_b252">Return to B.2.5.2 in Guidelines</a></div>
	   </div>
	       <div class="techs-only">

      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_b252-i" name="sc_b252-i"></a>Intent of Success Criterion B.2.5.2:</h5>
        <p>The intent of this success criterion is to ensure that all pre-authored content that the authoring tool provides include an accessibility status, which might be used by a pre-authored content selection mechanism (See <a href="#sc_b242">Success Criterion B.2.4.2</a>). This is not a requirement that all pre-authored content meet any particular accessibility level. </p>
      </div>
      <!-- implementing-section -->
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_b252-e" name="sc_b252-e"></a>Examples of Success Criterion B.2.5.2:</h5>

        <ul>
          <li><strong class="handle">Clip art collection:</strong> An authoring tool is shipped with a clip art collection. Each image in the collection has a short text label and long text description and the system is interoperable with the alternative content registry, so that whenever authors insert an image from the clip art collection, its alternative content is automatically retrieved.</li>
        </ul>
      </div>
      <!-- implementing-section -->
      <div class="implementing-section">
        <h5 class="implementing-heading"><a id="sc_b252-r" name="sc_b252-r"></a>Related Resources for Success Criterion B.2.5.2:</h5>

        <ul>
          <li>See <a href="#sc_b244">Success Criterion B.2.4.4</a></li>
        </ul>
      </div><!-- implementing-section -->
    </div> <!-- techs-only -->
	</div> <!-- sc-level -->
	
    <h2 class="principle"><a id="principle_b3" name="principle_b3"> </a><span class="techs-only">Implementing </span>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><span class="techs-only">Implementing</span> Guideline B.3.1: Assist authors in checking for accessibility problems.  <span class="techs-only">[<a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/Overview.html#gl_b31">Return to Guideline</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><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_b311">Return to B.3.1.1 in Guidelines</a></div>
	   </div>  
	   <div class="techs-only">
    <div class="implementing-section">
      <h5 class="implementing-heading"><a id="sc_b311-i" name="sc_b311-i"></a>Intent of Success Criterion B.3.1.1:</h5>
      <p>The intent of this success criterion is to ensure that authors are supported in discovering web content accessibility problems in the  content that they are editing. This is critical if these issues are to be addressed prior to publishing. The requirement to individually check <a href="#conf-rel-wcag">WCAG 2.0</a> success criteria is intended to prevent manual checks from being worded in excessively general ways (e.g. &quot;does the page meet all of the requirements?&quot;). </p>

      <p>The success criterion does not specify how multiple instances of the same problem should be handled, because this will usually depend on the nature of the problem and the degree of automation in the checking and repair features of the authoring tool. Some problems are limited to one or just a few elements and lend themselves to automated or semi-automated reporting of each instance (e.g. missing labels), while other problems extend across many elements and are sometimes best checked globally (e.g. reading level, etc.). </p>
      <p>The note about manual checking acknowledges that the current state of technology does not allow every web content accessibility problem to be identified automatically. </p>
      <p><a href="#conf-rel-wcag">WCAG 2.0</a> is referenced because it provides testable success criteria to measure web content accessibility.</p>
    </div>
    <!-- implementing-section -->
    <div class="implementing-section">

      <h5 class="implementing-heading"><a id="sc_b311-e" name="sc_b311-e"></a>Examples of Success Criterion B.3.1.1:</h5>
      <ul>
        <li><strong class="handle">Markup processing checker:</strong> An accessibility checking tool includes automated checking for web content accessibility problems that can be detected from markup alone. The tool includes semi-automated checking where potential instances can be detected from the markup, but where the author's assessment of the content is required to make a final decision. In cases where markup processing is of little or no use in detecting problems, manual instructions are included for authors to follow in identifying whether the relevant <a href="#conf-rel-wcag">WCAG 2.0</a> success criterion has been met. </li>
        <li><strong class="handle">Content processing checker:</strong> An accessibility checking tool goes beyond markup processing by applying content processing heuristics, such as:
          <ul>
              <li>Image processing to detect whether foreground and background contrast levels are sufficient or whether images are blank.</li>
            <li>Text processing to calculate reading levels and detect changes in human language.</li>
          </ul>
        </li>
      </ul>
    </div>
    <!-- implementing-section -->
    <div class="implementing-section">

      <h5 class="implementing-heading"><a id="sc_bx21-r" name="sc_b311-r"></a>Related Resources for Success Criterion B.3.1.1:</h5>
      <ul>
        <li><a href="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#checking-types">Appendix B: Levels of Checking Automation</a>.</li>
        <li><a href="#conf-rel-wcag">WCAG 2.0</a> (including <a href="http://www.w3.org/TR/2008/NOTE-UNDERSTANDING-WCAG20-20081211/">Understanding WCAG 2.0</a> and <a href="http://www.w3.org/WAI/WCAG20/quickref/Overview.php">How to Meet WCAG 2.0</a>)</li>

      </ul>
    </div><!-- implementing-section -->
  </div><!-- techs-only -->
  </div><!-- sc-level -->
  
  <div class="sc-level">
  
  <h4 class="sc-title"><a id="sc_b312" name="sc_b312"> </a><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_b312">Return to B.3.1.2 in Guidelines</a></div>
	   </div>  
  <div class="techs-only">
    <div class="implementing-section">
      <h5 class="implementing-heading"><a id="sc_b312-i" name="sc_b312-i"></a>Intent of Success Criterion B.3.1.2:</h5>
      <p>The intent of this success criterion is to ensure that authors, who in many cases will lack accessibility knowledge, will be able to make adequate judgments. If this is not the case, authors may miss web content accessibility problems that do exist and/or mistakenly identify problems that do not exist. </p>
    </div>
    <!-- implementing-section -->
    <div class="implementing-section">
      <h5 class="implementing-heading"><a id="sc_b312-e" name="sc_b312-e"></a>Examples of Success Criterion B.3.1.2:</h5>

      <ul>
        <li><strong class="handle">Questions answered:</strong> Instructions are formulated to answer the  questions: &quot;What part of the content should be examined?&quot; and &quot;What is present or absent that is causing the problem?&quot;.</li>
        <li><strong class="handle">Variety of views:</strong> When author judgment would be enhanced by modified views of the web content being edited, an accessibility browser toolbar is used to provide various previews, such as:
          <ul>

              <li>an alternative content view (with images and other multimedia replaced by any alternative content)</li>
            <li>a monochrome view (to test contrast)</li>
            <li>a text to speech view (to test the availability of text alternatives) </li>
            <li>no scripts view</li>
            <li>no frames view</li>
            <li>no style sheet view</li>

          </ul>
        </li>
        <li><strong class="handle">Judgments saved:</strong> An authoring tool saves author judgments for manual checks and only prompts for new judgments after authors have made substantial changes.</li>
      </ul>
    </div>
    <!-- implementing-section -->
    <div class="implementing-section">

      <h5 class="implementing-heading"><a id="sc_b312-r" name="sc_b312-r"></a>Related Resources for Success Criterion B.3.1.2:</h5>
      <ul>
        <li><a href="#conf-rel-wcag">WCAG 2.0</a> (including <a href="http://www.w3.org/TR/2008/NOTE-UNDERSTANDING-WCAG20-20081211/">Understanding WCAG 2.0</a> and <a href="http://www.w3.org/WAI/WCAG20/quickref/Overview.php">How to Meet WCAG 2.0</a>)</li>
      </ul>

    </div>
    <!-- implementing-section -->
  </div>
  <h4 class="sc-title"><a id="sc_b313" name="sc_b313"> </a><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_b313">Return to B.3.1.3 in Guidelines</a></div>
	   </div>  
  <div class="techs-only">
    <div class="implementing-section">
      <h5 class="implementing-heading"><a id="sc_b313-i" name="sc_b313-i"></a>Intent of Success Criterion B.3.1.3:</h5>
      <p>The intent of this success criterion is to increase the accuracy of author judgments by identifying the location of suspected web content accessibility problems as precisely as possible.</p>

      <p>The note acknowledges that there are many ways that this success criterion may be met. </p>
    </div>
    <!-- implementing-section -->
    <div class="implementing-section">
      <h5 class="implementing-heading"><a id="sc_b313-e" name="sc_b313-e"></a>Examples of Success Criterion B.3.1.3:</h5>
      <ul>
        <li><strong class="handle">By line number:</strong> An authoring tool displays potential problems in a separate list by the line number of the first element involved.</li>

        <li><strong class="handle">Underlining:</strong> A source editing-view displays potential problems in-line by underlining all of the markup for the affected span of elements.</li>
        <li><strong class="handle">Outlining:</strong> A WYSIWYG editing-view displays potential problems in-line with the rendered content as blue outlining around the affected span of elements.</li>
        <li><strong class="handle">Site-wide checking:</strong> A web site management software is designed to identify issues on a site-wide scale (e.g. broken links, outdated information). The software also includes a feature to detect site-wide accessibility problems. The feature is able to identify faulty templates, widgets, etc. that can cause systematic problems.</li>
      </ul>

    </div>
    <!-- implementing-section -->
    <div class="implementing-section">
      <h5 class="implementing-heading"><a id="sc_b313-r" name="sc_b313-r"></a>Related Resources for Success Criterion B.3.1.3:</h5>
      <ul>
        <li><a href="#conf-rel-wcag">WCAG 2.0</a> (including <a href="http://www.w3.org/TR/2008/NOTE-UNDERSTANDING-WCAG20-20081211/">Understanding WCAG 2.0</a> and <a href="http://www.w3.org/WAI/WCAG20/quickref/Overview.php">How to Meet WCAG 2.0</a>)</li>

      </ul>
    </div>
    <!-- implementing-section -->
  </div>
</div>
<!-- sc-level -->
<div class="sc-level">
  <h4 class="sc-title"><a id="sc_b314" name="sc_b314"> </a><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_b314">Return to B.3.1.4 in Guidelines</a></div>
	   </div>  
  <div class="techs-only">
    <div class="implementing-section">
      <h5 class="implementing-heading"><a id="sc_b314-i" name="sc_b314-i"></a>Intent of Success Criterion B.3.1.4:</h5>

      <p>The intent of this success criterion is to ensure that authors are able to obtain an overview of the accessibility status of their web content. This information has many uses, including the assessment of repair options, progress monitoring and  performance reporting.</p>
      <p>The note highlights that no particular format is required, since this will depend on the nature of the authoring tool and its checking feature. </p>
    </div>
    <!-- implementing-section -->
    <div class="implementing-section">
      <h5 class="implementing-heading"><a id="sc_b314-e" name="sc_b314-e"></a>Examples of Success Criterion B.3.1.4:</h5>
      <ul>
        <li><strong class="handle">List of accessibility problems:</strong> A step-by-step checking feature  provides a single consolidated list of all of the web content accessibility problems that were detected. Direct links are provided to additional help and repair assistance for each type of accessibility problem.</li>
        <li><strong class="handle">Conformance level report:</strong> A check-as-you-type checking feature highlights accessibility problems that can be automatically detected directly within a WYSIWYG editing-view. The author controls the strictness of the automatic checking from a preferences screen, where they select the target WCAG 2.0 level. The overall status of  accessibility checking is available on the application status bar, which lists the target WCAG 2.0 level and the number of outstanding problems that can be automatically detected. A link to the remaining manual checks is also provided.</li>
      </ul>
    </div>
    <!-- implementing-section -->
    <div class="implementing-section">

      <h5 class="implementing-heading"><a id="sc_b314-r" name="sc_b314-r"></a>Related Resources for Success Criterion B.3.1.4:</h5>
      <ul>
        <li>N/A</li>
      </ul>
    </div>
    <!-- implementing-section -->
  </div>
  <h4 class="sc-title"><a id="sc_b315" name="sc_b315"> </a><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_b315">Return to B.3.1.5 in Guidelines</a></div>
	   </div>  
  <div class="techs-only">
    <div class="implementing-section">
      <h5 class="implementing-heading"><a id="sc_b315-i" name="sc_b315-i"></a>Intent of Success Criterion B.3.1.5:</h5>
      <p>The intent of this success criterion is to facilitate automated use of accessibility checking results, which can benefit both authors and end-users. This can benefit authors and end-users in at least two ways: (a) increasing the interoperability of separated checking and repair tools and (b) supporting accessible resource discovery.  </p>
      <p>Increasing the interoperability of separated checking and repair tools allows authors to choose different checking and repair tools to suit their needs and also allows separation of checking and repair within the same authoring tool. For instance, a CMS with a continuously running web site accessibility checker might automatically queue up issues to be repaired later from within a quality assurance view. </p>
      <p>Systems that support accessible resource discovery take the accessibility preferences of end-users into account when fetching content. This allows authors to offer multiple versions of content with differing accessibility levels while still enabling end-users to receive versions that are accessible to them. </p>
      <p>The success criterion does not specify the format of the programmatic association, which may be specific (e.g. individual check results) or more general (e.g., WCAG 2.0 conformance level). However, formats that include specific checking results are typically more useful for accessible resource discovery because individual end-users may have preferences for certain types of accessibility information (e.g. captions), but not for others (e.g. audio descriptions).</p>
    </div>
    <!-- implementing-section -->
    <div class="implementing-section">
      <h5 class="implementing-heading"><a id="sc_b315-e" name="sc_b315-e"></a>Examples of Success Criterion B.3.1.5:</h5>
      <ul>
        <li><strong class="handle">Saving EARL:</strong> An authoring tool includes an automated/semi-automated accessibility checker, but only manual repair guidance. In order to give authors additional repair options, the checker includes the option of storing the listing of web content accessibility problems using the Evaluation and Repair Language (EARL). This allows the author to use an external automated/semi-automated repair service. </li>
        <li><strong class="handle">Saving AccessForAll:</strong> A learning content management system (LCMS) is implemented with a personalized approach to accessibility. Instead of every version of every web content resource being fully conformant (e.g. every video including captions), several versions of each web content resource are produced (e.g. one with captions and one without) and AccessForAll metadata is associated with each. Then when an end user attempts to access a web content resource, their personal preferences are used by the LCMS to locate and serve out the version of the web content resource that is appropriate to that end user's preferences.</li>

        <li><strong class="handle">Accessibility of legacy web content:</strong> A content management system includes the ability to inventory issues within legacy web content. Running automated checking on legacy web content and storing the results provides decision-makers with potentially useful information.</li>
      </ul>
    </div>
    <!-- implementing-section -->
    <div class="implementing-section">
      <h5 class="implementing-heading"><a id="sc_b315-r" name="sc_b315-r"></a>Related Resources for Success Criterion B.3.1.5:</h5>
      <ul>

        <li>The <a href="http://www.imsglobal.org/accessibility/accmdv1p0/imsaccmd_oviewv1p0.html">IMS AccessForAll Meta-data</a> standard is one way to store the accessibility attributes of web content in order to match them with the preferences of users. This system is also the basis for <a href="http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=41521">ISO 24571 (Individualized adaptability and accessibility in e-learning, education and training)</a>. </li>
        <li>The <a href="http://www.w3.org/WAI/intro/earl.php">Evaluation and Report Language (EARL)</a> is a machine-readable format for expressing test results.</li>
        <li><a href="http://labs.google.com/accessible/">Google Accessible Search</a> is an example of accessible resource   discovery.</li>

      </ul>
    </div>
    <!-- implementing-section -->
  </div>
</div>
<!-- sc-level -->
<h3 class="guideline"><a id="gl_b32" name="gl_b32"> </a><span class="techs-only">Implementing</span> Guideline B.3.2: Assist authors in repairing accessibility problems.  <span class="techs-only">[<a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/Overview.html#gl_b32">Return to Guideline</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><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_b321">Return to B.3.2.1 in Guidelines</a></div>
	   </div>  
  <div class="techs-only">
    <div class="implementing-section">
      <h5 class="implementing-heading"><a id="sc_b321-i" name="sc_b321-i"></a>Intent of Success Criterion B.3.2.1:</h5>
      <p>The intent of this success criterion is to ensure that authors are aided in repairing content accessibility problems that are detectable via the authoring tools own checking system. </p>
      <p>The note allows manual repair assistance to meet this success criterion in order to acknowledge the difficulty of automatically or semi-automatically repairing certain types of accessibility problems. </p>

      <p><a href="#conf-rel-wcag">WCAG 2.0</a> is referenced because it provides testable success criteria to measure web content accessibility.</p>
    </div>
    <!-- implementing-section -->
    <div class="implementing-section">
      <h5 class="implementing-heading"><a id="sc_b321-e" name="sc_b321-e"></a>Examples of Success Criterion B.3.2.1:</h5>
      <ul>
        <li><strong class="handle">Check-as-you-type:</strong> An authoring tool includes a check-as-you-type feature  that provides context sensitive repair. <br />

            <span class="figure"><strong>Figure:</strong> A WYSIWYG editing-view is shown, in which a table is being edited. The first row of the table is highlighted in blue &quot;squiggly&quot; lines because a checking heuristic has detected that it might actually be a header row. The author has right clicked on the outlined area and a pop-up menu gives them several repair options: &quot;Repair: Set as header row&quot;, &quot;Skip&quot;, &quot;Ignore&quot;, &quot;Check Accessibility...&quot; and &quot;Help...&quot;. <br />

            <img src="tech_images/b_13.png" alt="See the example caption above for description." width="417" height="162" /></span></li>
        <li><strong class="handle">Combined check-repair feature:</strong> A WYSIWYG web page authoring tool includes an accessibility check and repair feature that presents web content accessibility problems and repair options in a sequential manner analogous to a typical spelling or grammar checking &quot;wizard&quot;. Each screen provides input field(s) for the information required to address the issue as well as additional information and tips that authors may require in order to properly provide the requested information. <br />
            <span class="figure"><strong>Figure:</strong> A correction interface is shown for repairing missing alternate text label for an image. The interface includes (1) a short description of the problem (here: &quot;Missing Alternate Text Label for an Image&quot;), (2) a preview (here: the &quot;earthrise&quot; image that is missing a label), (3) tips for performing the repair (here: &quot;Alternate text should be 10 words or less and should include any text in the image.&quot;; &quot;Image buttons should have alternate text that describes the button function.&quot;; and &quot;Image bullets should have &quot;bullet&quot; as alternate text.&quot;), and (4) an offered semi-automated repair in an editable drop-down box (here: &quot;An earth rise as seen from the moon&quot;). The global checker controls include a progress indicator (&quot;5 of 25&quot;) and navigation buttons to move backwards (&quot;back&quot;) and forwards (&quot;skip&quot;) through the list of repair tasks. Buttons to &quot;repair&quot;, get &quot;help&quot; and &quot;cancel&quot; are also provided. (Source: mock up by AUWG) <br />

              <img src="tech_images/b_24.png" alt="See the example caption above for description." width="398" height="275" /></span></li>
        <li><strong class="handle">Manual repair instructions:</strong> For each potential accessibility problem identified by the checking function (as required by <a href="#sc_b311">Success Criterion B.3.1.1</a>), documentation with repair instructions is provided that authors (with sufficient skill and knowledge to use the rest of the tool) could follow to correct the problem.</li>
      </ul>
    </div>
    <!-- implementing-section -->
    <div class="implementing-section">

      <h5 class="implementing-heading"><a id="sc_b321-r" name="sc_b321-r"></a>Related Resources for Success Criterion B.2.3.1:</h5>
      <ul>
        <li><a href="http://www.w3.org/TR/2000/WD-AERT-20000426">Techniques For Accessibility Evaluation And Repair Tools (AERT)</a></li>
        <li><a href="#conf-rel-wcag">WCAG 2.0</a> (including <a href="http://www.w3.org/TR/2008/NOTE-UNDERSTANDING-WCAG20-20081211/">Understanding WCAG 2.0</a> and <a href="http://www.w3.org/WAI/WCAG20/quickref/Overview.php">How to Meet WCAG 2.0</a>)</li>

      </ul>
    </div>
    <!-- implementing-section -->
  </div>
</div>
<!-- sc-level -->
<h2 class="principle"><a id="principle_b4" name="principle_b4"> </a><span class="techs-only">Implementing </span>PRINCIPLE B.4: Authoring tools must promote and integrate their accessibility features </h2> 
      
<h3 class="guideline"><a id="gl_b41" name="gl_b41"> </a><span class="techs-only">Implementing</span> Guideline B.4.1: Ensure the availability of features that support the production of accessible content.


<span class="techs-only">[<a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/Overview.html#gl_b41">Return to Guideline</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><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_b411">Return to B.4.1.1 in Guidelines</a></div>
	   </div>  

        <div class="techs-only"> 
      <div class="implementing-section">

          <h5 class="implementing-heading"><a id="sc_b411-i" name="sc_b411-i"></a>Intent of Success Criterion B.4.1.1:</h5>
		  <p>The intent of this success criterion is to help ensure that the accessible content support features are perceived by authors (and developers) as a natural and expected part of the authoring tool workflow, just as features for addressing spelling, grammar and syntax errors already are. </p>
		  </div> <!-- implementing-section -->
      <div class="implementing-section">
          <h5 class="implementing-heading"><a id="sc_b411-e" name="sc_b411-e"></a>Examples of Success Criterion B.4.1.1:</h5>
              <ul>
                <li><strong class="handle">On by default:</strong> A web page authoring tool has all accessible content support features turned on by default within the &quot;Accessibility&quot; tab of its preferences area.
				<br />
				<span class="figure"><strong>Figure:</strong> The preference setting area of an authoring tool, open to an &quot;Accessibility&quot; section, shows the default settings. &quot;W3C-WCAG&quot; and a level (e.g. &quot;Double-A&quot;) are selected as are the following options: &quot;Check accessibility as you type&quot;, &quot;Check accessibility after saving&quot;, &quot;Auto-correct when possible&quot;, &quot;Highlight accessibility related fields&quot;, &quot;Prompt when highlighted fields are left blank&quot;, and &quot;Provide accessibility 'Quick Tips'&quot;. (Source: mock up by AUWG)</span>

				<br /><img src="tech_images/b_31.png" alt="See the example caption above for description." width="284" height="315" /></li>
              </ul>
          </div> <!-- implementing-section -->
      <div class="implementing-section">
          <h5 class="implementing-heading"><a id="sc_b411-r" name="sc_b411-r"></a>Related Resources for Success Criterion B.4.1.1:</h5>
              <ul>
                <li>N/A</li>

              </ul>
          </div> <!-- implementing-section -->
        </div>
		
        <h4 class="sc-title"><a id="sc_b412" name="sc_b412"> </a><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_b412">Return to B.4.1.2 in Guidelines</a></div>
	   </div>  
	   
        <div class="techs-only"> 
      <div class="implementing-section">
          <h5 class="implementing-heading"><a id="sc_b412-i" name="sc_b412-i"></a>Intent of Success Criterion B.4.1.2:</h5>
		  <p>The intent of this success criterion is to ensure that if authors turn off accessible content support features for any reason, they can easily turn them back on.</p>
		  </div> <!-- implementing-section -->
      <div class="implementing-section">
          <h5 class="implementing-heading"><a id="sc_b412-e" name="sc_b412-e"></a>Examples of Success Criterion B.4.1.2:</h5>

              <ul>
                <li><strong class="handle">Toggle in preferences area:</strong>
				A web page authoring tool provides an &quot;Accessibility&quot; tab in its preferences area where any deactivated features can be reactivated.</li>
                <li><strong class="handle">Reminders:</strong>
				An authoring tool has a &quot;wizard&quot;-style accessibility checker and a &quot;check-as-you-type&quot;-style accessibility checker. If the &quot;check-as-you-type&quot;-style checker has been turned off, then authors are reminded about the feature and provided with an option to turn it back on whenever they run the &quot;wizard&quot;-style checker. </li>

              </ul>
          </div> <!-- implementing-section -->
      <div class="implementing-section">
          <h5 class="implementing-heading"><a id="sc_b412-r" name="sc_b412-r"></a>Related Resources for Success Criterion B.4.1.2:</h5>
              <ul>
                <li>N/A</li>
              </ul>

          </div> <!-- implementing-section -->
        </div>
	</div> <!-- sc-level -->
		
<div class="sc-level">
  <h4 class="sc-title"><a id="sc_b413" name="sc_b413"> </a><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_b413">Return to B.4.1.3 in Guidelines</a></div>
	   </div>  

        <div class="techs-only"> 
      <div class="implementing-section">
          <h5 class="implementing-heading"><a id="sc_b413-i" name="sc_b413-i"></a>Intent of Success Criterion B.4.1.3:</h5>
		  <p>The intent of this success criterion is to ensure that if authors attempt to turn off an accessible content support feature for any reason, they will have the opportunity to understand the effect this will have on the accessibility of the web content that they produce.</p>
		  </div> <!-- implementing-section -->
      <div class="implementing-section">
          <h5 class="implementing-heading"><a id="sc_b413-e" name="sc_b413-e"></a>Examples of Success Criterion B.4.1.3:</h5>

              <ul>
                <li><strong class="handle">Warning:</strong> An authoring tool provides authors with a warning whenever an accessible content support feature is turned off (e.g. from the authoring tool preferences area.
				<br />
				<span class="figure"><strong>Figure:</strong> In an authoring tool, the author has unchecked a &quot;highlighting accessibility related fields&quot; feature the tool. As a result the tool displays a warning that reads &quot;You have just turned off the highlighting accessibility related fields feature. This feature is designed to inform you when information must be provided in order for your documents to comply with your target accessibility setting. Turning this feature off could cause your documents to be less accessible to many users. In some jurisdictions accessibility is a legal requirement. Are you sure you want to proceed?&quot;. The author has the option to answer &quot;Yes&quot;, &quot;No&quot; or &quot;Cancel&quot;. (Source: mock up by AUWG)<br />

                <img src="tech_images/b_32.png" alt="See the example caption above for description." width="402" height="216" /></span> </li>
              </ul>
          </div> <!-- implementing-section -->
      <div class="implementing-section">
          <h5 class="implementing-heading"><a id="sc_b413-r" name="sc_b413-r"></a>Related Resources for Success Criterion B.4.1.3:</h5>
              <ul>
                <li>N/A</li>

              </ul>
          </div> <!-- implementing-section -->
        </div>
		
        <h4 class="sc-title"><a id="sc_b414" name="sc_b414"> </a><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_b414">Return to B.4.1.4 in Guidelines</a></div>
	   </div>  
	   
        <div class="techs-only">
      <div class="implementing-section">
          <h5 class="implementing-heading"><a id="sc_b414-i" name="sc_b414-i"></a>Intent of Success Criterion B.4.1.4:</h5>
		  <p>The intent of this success criterion is to help ensure that authors are as likely to notice and use functions for addressing accessibility problems as functions for addressing other web content issues (e.g. invalid markup, syntax errors, spelling and grammar errors).</p>
		  </div> <!-- implementing-section -->
      <div class="implementing-section">
          <h5 class="implementing-heading"><a id="sc_b414-e" name="sc_b414-e"></a>Examples of Success Criterion B.4.1.4:</h5>

              <ul>
                <li><strong class="handle">Prominence of checking and repair:</strong> 
				An authoring tool includes a pane dedicated to  content &quot;Evaluation and Repair&quot;. The pane lists accessibility, grammar, link checking, spelling, and syntax validation. When the various utilities are run, their results are displayed in similar ways within the pane.</li>
                <li><strong class="handle">Prominence of documentation:</strong>
				An authoring tool includes documentation of its accessibility checker as part of the main documentation of an authoring tool, with very similar prominence to that of the spelling-related features.
				<br />
				<span class="figure"><strong>Figure:</strong> A help system is shown. In the right pane is the documentation table of contents, where &quot;Accessibility Features&quot; appears as a top level topic just below &quot;Spelling Features&quot;. In the left panel is the help text, demonstrating a style typical of the rest of the help system: &quot;Checking for Accessibility: A variety of accessibility checking options are available: Accessibility verifier, Check accessibility as you type, Manual test support materials. These are suitable for use at different times during the authoring process and all have options that can be changed with the accessibility preferences. To get more information on accessible web content, see the References.&quot;. (Source: mock up by AUWG)
				<br /><img src="tech_images/b_35.png" alt="See the example caption above for description." width="617" height="209" /></span></li>

                <li><strong class="handle">Check-as-you-type:</strong> An authoring tool continuously checks the web content being edited and highlights problems as the authors work. <br />
                    <span class="figure"><strong>Figure:</strong> A WYSIWYG authoring tool is shown with check-as-you-type accessibility checking activated. Two elements on the page have been highlighted as having problems: an image is surrounded by a blue squiggly line and a line of text is underlined by the same style of blue squiggly line. (Source: mock up by AUWG) <br />
                    <img src="tech_images/b_19.png" alt="See the example caption above for description." width="417" height="194" /></span><br />
                </li>
                <li><strong class="handle">Checking on demand:</strong> An authoring tool provides accessibility checking from a menu item that is always available. </li>

                <li><strong class="handle">Prompt to check before publishing:</strong> An authoring tool automatically performs an accessibility check if authors choose a publishing option and informs  authors of the results. </li>
              </ul>
          </div> <!-- implementing-section -->
      <div class="implementing-section">
          <h5 class="implementing-heading"><a id="sc_b414-r" name="sc_b414-r"></a>Related Resources for Success Criterion B.4.1.4:</h5>
              <ul>

                <li><a href="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#checking-types">Appendix B: Levels of Checking Automation</a></li>
              </ul>
          </div> <!-- implementing-section -->
        </div>
    </div> <!-- sc-level -->
    <h3 class="guideline"><a id="gl_b42" name="gl_b42"> </a><span class="techs-only">Implementing</span> Guideline B.4.2: Ensure that documentation promotes the production of accessible content. 


<span class="techs-only">[<a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/Overview.html#gl_b42">Return to Guideline</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><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_b421">Return to B.4.2.1 in Guidelines</a></div>
	   </div>  

        <div class="techs-only"> 
      <div class="implementing-section">
          <h5 class="implementing-heading"><a id="sc_b421-i" name="sc_b421-i"></a>Intent of Success Criterion B.4.2.1:</h5>
		  <p>The intent of this success criterion is to have accessible authoring practices introduced to authors as naturally integrated common practice. The success criterion is also intended to reduce the chance that authors will copy inaccessible authoring practices from examples in the documentation. Essentially, modelling inaccessible authoring practices in the documentation should be viewed in the same way as modelling invalid markup or spelling/grammar errors.</p>
		  <p><a href="#conf-rel-wcag">WCAG 2.0</a> is referenced because it provides testable success criteria to measure web content accessibility.</p>

      </div> <!-- implementing-section -->
      <div class="implementing-section">
          <h5 class="implementing-heading"><a id="sc_b421-e" name="sc_b421-e"></a>Examples of Success Criterion B.4.2.1:</h5>
              <ul>
                <li><strong class="handle">Reference examples are accessible:</strong> An HTML authoring tool includes an on-line HTML reference guide.   Markup examples within the reference guide are all valid code and they all meet the <a href="#conf-rel-wcag">WCAG 2.0</a> Level A success criteria..<br />
                </li>
                <li> <strong class="handle">Screen shots show accessibility features in use:</strong> A content management system has a help system that includes screen shots of various aspects of the system's user interface. When screen shots show examples of the user interfaces as content is being produced, the user interface is always shown such that the content produced would meet the <a href="#conf-rel-wcag">WCAG 2.0</a> Level A success criteria (e.g. prompts filled in, optional accessibility features turned on, etc.). </li>
              </ul>
          </div> <!-- implementing-section -->
      <div class="implementing-section">

          <h5 class="implementing-heading"><a id="sc_b421-r" name="sc_b421-r"></a>Related Resources for Success Criterion B.4.2.1:</h5>
              <ul><li><a href="#conf-rel-wcag">WCAG 2.0</a> (including <a href="http://www.w3.org/TR/2008/NOTE-UNDERSTANDING-WCAG20-20081211/">Understanding WCAG 2.0</a> and <a href="http://www.w3.org/WAI/WCAG20/quickref/Overview.php">How to Meet WCAG 2.0</a>)</li>
              </ul>
          </div> <!-- implementing-section -->

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

	  
      <div class="sc-level">
        <h4 class="sc-title"><a id="sc_b422" name="sc_b422"> </a><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_b422">Return to B.4.2.2 in Guidelines</a></div>
	   </div>  
	   <div class="techs-only"> 
      <div class="implementing-section">

          <h5 class="implementing-heading"><a id="sc_b422-i" name="sc_b422-i"></a>Intent of Success Criterion B.4.2.2:</h5>
		  <p>The intent of this success criterion is to help ensure that authors are able to find help on how to use  the accessible content support features effectively. </p>
	     </div> <!-- implementing-section -->
      <div class="implementing-section">
          <h5 class="implementing-heading"><a id="sc_b422-e" name="sc_b422-e"></a>Examples of Success Criterion B.4.2.2:</h5>
              <ul>
                <li><strong class="handle">Documentation of accessible content support features:</strong>

				An authoring tool's help system documents the accessible content support features as it would other features of the authoring tool. Since the authoring tool includes context-sensitive help, this is  also provided for the accessible content support features.</li>
                <li><strong class="handle">Short and long versions of help:</strong> 
				During prompting and repairs, an authoring tool provides authors with immediate access to some basic accessibility documentation and one-step access to more comprehensive documentation.
				<br />
				<span class="figure"><strong>Figure:</strong> An accessibility checker includes some limited tips for authoring short text labels listed beneath the text entry area as well as a &quot;Help&quot; button linking to the full documentation. The tips are: &quot;Alternate text should be 10 words or less and should include any text in the image.&quot;, &quot;Image buttons should have alternate text that describes the button function.&quot;, and &quot;Image bullets should have 'bullet' as alternate text.&quot;. The screen shot also includes the name of the problem (&quot;Missing Alternate Text Label for an Image&quot;), a field for adding the short text label and a preview rendering of the image (&quot;earthrise&quot;). At the bottom are five buttons: &quot;Help&quot;, &quot;&lt; Back&quot;, &quot;Repair&quot;, &quot;Skip&quot;, and &quot;Cancel&quot;. (Source: mock up by AUWG)
				<br /><img src="tech_images/b_42.png" width="398" height="247" alt="See the example caption above for description." /></span></li>

              </ul>
         </div> <!-- implementing-section -->
      <div class="implementing-section">
          <h5 class="implementing-heading"><a id="sc_b422-r" name="sc_b422-r"></a>Related Resources for Success Criterion B.4.2.2:</h5>
              <ul>
                <li>N/A</li>
              </ul>

         </div> <!-- implementing-section -->
        </div> 
</div>  <!-- sc-level -->
 
<div class="sc-level">
  <h4 class="sc-title"><a id="sc_b423" name="sc_b423"> </a><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_b423">Return to B.4.2.3 in Guidelines</a></div>
	   </div>  
	           <div class="techs-only"> 
      <div class="implementing-section">
          <h5 class="implementing-heading"><a id="sc_b423-i" name="sc_b423-i"></a>Intent of Success Criterion B.4.2.3:</h5>
		  <p>The intent of this success criterion is to ensure that authors that learn best through tutorials are exposed to accessibility best practices specific to the authoring tool. </p>
		  </div> <!-- implementing-section -->
      <div class="implementing-section">
          <h5 class="implementing-heading"><a id="sc_b423-e" name="sc_b423-e"></a>Examples of Success Criterion B.4.2.3:</h5>
              <ul>
                <li><strong class="handle">Accessibility tutorial:</strong>

				A web page authoring tool includes built-in tutorials demonstrating several multi-step tasks (e.g. setting up the folders and files for the local version of a website, formatting with CSS, etc.). One of the tutorials describes how to use the accessible content support features of the authoring tool to  increase the accessibility of the web content produced. The tutorial begins at the typical starting point for the tool (e.g. empty document). The tutorial also covers when and how checking and repair should be performed. The tutorial includes some basic rationales for accessible content production. These rationales emphasize the importance of accessibility for a wide range of content consumers, from those with disabilities to those with alternative viewers (see <a href="http://www.w3.org/WAI/bcase/benefits.html">&quot;Auxiliary Benefits of Accessibility Features&quot;</a>, a W3C-WAI resource). </li>
              </ul>
          </div> <!-- implementing-section -->
      <div class="implementing-section">
          <h5 class="implementing-heading"><a id="sc_b423-r" name="sc_b423-r"></a>Related Resources for Success Criterion B.4.2.3:</h5>
              <ul>

                <li><a href="http://www.w3.org/WAI/bcase/benefits.html">Auxiliary
          Benefits of Accessibility Features</a></li>
              </ul>
          </div> <!-- implementing-section -->
        </div> 

      <h4 class="sc-title"><a id="sc_b424" name="sc_b424"> </a><span class="techs-only">Implementing Success Criterion </span>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="techs-only">
	    <div class="implementing-link"><a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/#sc_b424">Return to B.4.2.4 in Guidelines</a></div>
	   </div>  

      <div class="techs-only">
        <div class="implementing-section">
          <h5 class="implementing-heading"><a id="sc_b424-i" name="sc_b424-i"></a>Intent of Success Criterion  B.4.2.4:</h5>
          <p>The intent is to help authors discover instructions related to features provided to support the authoring of accessible web content. </p>
        </div>
        <!-- implementing-section -->
        <div class="implementing-section">

          <h5 class="implementing-heading"><a id="sc_b424-e" name="sc_b424-e"></a>Examples of Success Criterion B.4.2.4:</h5>
          <ul>
            <li><strong class="handle">Help chapter:</strong> An authoring tool includes documentation of its accessible content support features (needed to meet <a href="#sc_b422">Success Criterion B.4.2.2</a>). This documentation appears in a chapter of the documentation on accessibility. The documentation is also available via other mechanisms, including context sensitive help from the features themselves and from a help search function.</li>
            <li><strong class="handle">Help index:</strong> An authoring tool includes documentation of its accessible content support features (needed to meet <a href="#sc_b422">Success Criterion B.4.2.2</a>). This documentation is spread throughout the other documentation topics as applicable. In addition, there is a help topic on accessible authoring that includes links to the various pieces of distributed documentation. The documentation is also available via other mechanisms, including context sensitive help from the features themselves and from a help search function.</li>

          </ul>
        </div>
        <!-- implementing-section -->
        <div class="implementing-section">
          <h5 class="implementing-heading"><a id="sc_b424-r" name="sc_b424-r"></a>Related Resources for Success Criterion B.4.2.4:</h5>
          <ul>
            <li>N/A</li>
          </ul>

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

<hr /> 
 

<div id="sect-conformance"> 
  <h2><a id="Conformance" name="Conformance"> </a><span class="techs-only">Implementing ATAG 2.0 </span>Conformance</h2> 
    <!-- gl-only -->

  <div class="techs-only"> 
  <p>This section is included here for <a class="termdef" href="#def-Informative" title="definition: informative">informative</a> purposes. The <a class="termdef" href="#def-Normative" title="definition: normative">normative</a> version appears in the Authoring Tool Accessibility Guidelines 2.0 <a href="#ref-ATAG20" title="reference: ATAG20"><cite>[ATAG20]</cite></a>.</p> 
  </div>  <!-- 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 /> 
<div class="techs-only"> 
  <h2><a name="prompting-types" id="prompting-types"> </a>Appendix A: Gathering Accessibility Information from Authors:</h2>
  <p>This section is <a class="termdef" href="#def-Informative" title="definition: informative">informative</a>. </p>
  <p>In order to produce accessible web content, authoring tools often need authors to provide accessibility
    information such as text alternatives for images, role and state information for widgets, relationships within complex tables, and captions for audio. As for any information to be gathered from authors, there are a range of approaches that a developer might take for gathering accessibility information, from voluntary unobtrusive reminders to intrusive mandatory prompts. While ATAG 2.0 does <strong>not</strong> require any particular approach, author cooperation and goodwill are important considerations in ensuring that the accessibility information that is gathered is <em>correct</em> and <em>complete</em>.</p>

  <p>The following are some techniques that may assist in gathering different types of accessibility information, along with some example implementations.</p>
  <h3><a name="prompt-short-text-labels" id="prompt-short-text-labels"> </a>1. Short text labels (e.g. alternate text, titles,
    short text metadata fields, rubies for ideograms):</h3> 
  <ul> 
    <li> Prompts may be kept short because short text strings are usually entries
      of ten words or less. (see Example
      A-1a)</li> 
    <li>Provide  a rendered view of the object being labeled for the authors to consult. (see Example
      A-1a)</li> 
    <li>Provide the option of automatically retrieving previously used labels as suggestions. (see Example
      A-1a, see Success Criterion B.2.4.2 for more information)</li> 
    <li>If the tool offers  authors previously used labels or special
      function label text, then editable text entry boxes with drop-down lists should be used to allow authors the option of entering different text (see Example
    A-1a).</li> 
    <li>In source editing-views, suggest short text labels that are already marked up appropriately (see
      Example A-1b). </li> 
  </ul> 
  <blockquote> 
    <p class="figure"><a name="Example_B.2_1a" id="Example_B.2_1a"> </a><strong class="handle">Example A-1a:</strong> A dialog box offers short text labels for reuse. It shows an &quot;Insert Image&quot; dialog box a thumbnail image of the &quot;earthrise&quot; graphic along with entry fields for &quot;src&quot;, &quot;alt&quot;, &quot;longdesc&quot;, &quot;height&quot; and &quot;width&quot;. The &quot;alt&quot; entry field is drop-down list that is shown with
      several short labels for the same image. The first is a visual description in English (&quot;An earth rise as seen from the moon&quot;), the second is a visual description in French (&quot;Une vue do la terre de la lune&quot;) and the third is an English functional label used if the image serves as a link (&quot;Go to pictures of the earth&quot;).
      (Source: mock up by AUWG) <br /> 
    <img src="tech_images/b_2.png" width="331" height="171" alt="See the example caption above for description." /></p> 
    <p class="figure"><a id="Example-ShortTextLabels-b"></a><strong class="handle">Example A-1b:</strong> A  source editing-view offers short text labels for reuse. It shows the author midway through adding markup for an image. After adding the <code>src</code> attribute value the author has pressed the spacebar, causing the tool to prompt them with the <code>alt</code> attribute along with several attribute values, including a visual description in English (alt=&quot;An earth rise as seen from the moon&quot;), a visual description in French (alt=&quot;Une vue de la terre de la lune&quot;) and an English functional label used if the image serves as a link (alt=&quot;Go to pictures of the earth&quot;). (Source: mock up by AUWG) <br /> 
    <img src="tech_images/b_3.png" alt="See the example caption above for description." width="417" height="123" /></p> 
  </blockquote> 
  <h3><a name="prompt-multiple-text-labels" id="prompt-multiple-text-labels"></a>2. Multiple text labels (e.g. image map area labels):</h3> 
  <ul> 
    <li>Prompts for multiple text labels may be similar to those for <a href="#prompt-short-text-labels">short
      text labels</a>, with allowance made for rapidly adding several labels (e.g. a spreadsheet type of component). (see Example
      A-2)</li> 
    <li> Provide a rendered view of the various objects being labeled for  authors to consult</li> 
    <li>If the objects have URIs (e.g. image map areas), display these as a hint for the labels. (see Example
    A-2)</li> 
    <li>If the objects have URIs (e.g. image map areas), offer to automatically generate a set of plain text links from the
      labels that the user completes. (see Example
      A-2)</li> 
  </ul> 
  <blockquote> 
    <p class="figure"><a id="Example-MultipleShortTextLabels"></a><strong class="handle">Example A-2:</strong> An interface for image
      map area text labels. It is comprised of a list with two columns.
      In the right-hand column is the URL for each image map area. This can
      be used as a hint by the author as they fill in the text labels (left-hand
      column). A checkbox at the bottom provides the option of using the text
      labels to create a set of text links below the image map. (Source: mock up
      by AUWG) <br /> 
    <img src="tech_images/b_4.png" width="362" height="124" alt="See the example caption above for description." /></p> 
  </blockquote> 
  <h3><a name="prompt-long-description" id="prompt-long-description"></a>(3):
    Long text descriptions (e.g. longdesc text,
    table summaries, site information, long text metadata fields):</h3> 
  <ul> 
    <li>Begin by asking authors whether the inserted object
      is adequately described with an existing short text label. Providing a
      view of the page with rendering of the object turned off may help authors decide. (see
      Example A-3)</li> 
    <li>If the short text label is determined to be inadequate, prompt  authors for the
      location of a pre-existing description. (see
      Example A-3)</li> 
    <li>If  authors need to create a description, provide a special writing
      utility that includes a rendered view of the object and description writing
      advice.</li> 
    <li>Ensure checking can ignore objects
      that do not require long text descriptions (e.g. bullets, spacers, horizontal
      rules) or objects that  authors have previously stated do not require long text descriptions.</li> 
  </ul> 
  <blockquote> 
    <p class="figure"><a id="Exampe-LongTextDesc"></a><strong class="handle">Example A-3:</strong> An interface for long text descriptions. A &quot;description required&quot; checkbox controls whether the rest of the interface is available. If a description is required, the author then has the choice of opening an existing description file or writing (and saving) a new one. If they choose to use an existing file, there is a text entry area for the name along with a button to browse the file system. If they choose to compose a new description, there is a text entry area for the description followed by a text field for the file name and a button to save it to that location. In the situation shown, the author chooses to use an existing description of &quot;earthrise&quot; so the file name containing the description is shown. In addition, the text of the description from the file is loaded into the compose area (&quot;The earth hangs in the pitch black sky above the gray horizon of the moon. The dazzling blue sphere is covered with creamy white  streamers of cloud.&quot;) in case the author would like to use this text as a basis for a new description. (Source: mock up by AUWG) <br /> 
    <img src="tech_images/b_5.png" width="440" height="162" alt="See the example caption above for description." /></p> 
  </blockquote> 
  <h3><a name="prompt-form-control-labels" id="prompt-form-control-labels"></a>(4):
    Form component labels: </h3> 
  <ul> 
    <li>Prompts for form components may be similar to those for <a href="#prompt-short-text-labels">short text labels</a> and/or <a href="#prompt-multiple-text-labels">multiple text labels</a>.</li> 
    <li> For web content technologies in which form component labels are external to the actual form component elements (e.g. HTML), allow  authors to either directly add a form component label or identify pre-existing text
      strings that are already serving implicitly as labels.</li> 
    <li>It may be helpful to render the form components with indicators of label associations or missing labels.</li> 
    <li>It may be helpful to redisplay the components in spreadsheet form to assist  authors in determining which components are lacking labels. (see
      Example A-4)</li> 
  </ul> 
  <blockquote> 
    <p class="figure"><a id="Example-FormFieldLabels"></a><strong class="handle">Example A-4:</strong> A form properties list
      with five columns that allows the author to simultaneously decide the following for each field: the tab
      order, form name, field label, component type, and accesskey. In this example, two form
      field labels are missing, causing yellow highlighting of the cells and red icons to be displayed. &quot;Move up&quot; and &quot;move down&quot; buttons are  provided. (Source: mock up
      by AUWG) <br /> 
    <img src="tech_images/b_6.png" width="519" height="133" alt="See the example caption above for description." /></p> 
  </blockquote> 
  <h3><a name="prompt-form-placeholders" id="prompt-form-placeholders"></a>(5):
    Form field place-holders:</h3> 
  <ul> 
    <li>Prompts for form field place-holders may be similar to those for <a href="#prompt-short-text-labels">short text labels</a>, <a href="#prompt-multiple-text-labels">multiple text labels</a>, and/or <a href="#prompt-form-control-labels">form component labels</a>.</li> 
    <li>Provide authors with the option of directly selecting nearby text
      strings that are serving implicitly as labels and use the text as place-holders. </li> 
  </ul> 
  <h3><a name="prompt-tab-sequence" id="prompt-tab-sequence"></a>(6): Tab orders: </h3> 
  <ul> 
    <li>At the very least, provide a field for entering the tab order number for any element that can appear in the tab order. </li> 
    <li> Manage the tab order  to prevent duplicate tab order  indices and to reduce the need for manual renumbering.</li> 
    <li> Provide contextual information to supplement the basic tab order  numbers, such as the label or name of components.</li> 
    <li> Provide  authors with a point-and-click numbering tool that they can use to select
      components to quickly create a tab order  </li> 
    <li> Provide a list of links and components to check the tab order.</li> 
    <li> Where there are only a few links that change in each page of a collection, ask authors to confirm whether these links receive focus first. If so, then the tool can appropriately update the tab order.</li> 
  </ul> 
  <h3><a name="prompt-nav-shortcuts" id="prompt-nav-shortcuts"></a>(7):
    Navigational shortcuts (e.g. keyboard shortcuts,
    bypass blocks, etc.):</h3> 
  <ul> 
    <li>Suggest repetitive blocks of content that might be candidates for bypass.</li> 
    <li> Prompt authors with a list of links that are candidates for accesskeys,
      because they are common to a number of pages in a site.</li> 
    <li> Manage accesskey lists to ensure consistency across sites and to
      prevent conflicts within pages. (see Example
      A-7)</li> 
  </ul> 
  <blockquote> 
    <p class="figure"><a id="Example-Navshortcuts-b"></a> <strong class="handle">Example A-7:</strong> A source editing-view that suggests accesskey values. The following markup can be seen: &quot;<code>&lt;body&gt;&lt;p&gt;Here is one of the most famous photographs taken from the &lt;a href=&quot;moon.html&quot; &gt; moon.&lt;/a&gt;&lt;/p&gt;&lt;It was taken with a special &lt;a href=&quot;camera.html&quot; accesskey=&quot;c&quot;&gt;camera.&lt;/p&gt;&quot;</code>. A pop-up menu, centered on the word &quot;moon&quot; suggest accesskey=&quot;m&quot;, because &quot;moon&quot; begins with &quot;m&quot;, followed by the rest of the alphabet in order. Accesskey=&quot;c&quot; is missing, however, since it is already
      used as an accesskey later in the document (for the &quot;camera&quot; link).
      (Source: mock up by AUWG) <br /> 
      <img src="tech_images/b_9.png" width="417" height="142" alt="See the example caption above for description." /></p> 
  </blockquote> 
  <h3><a name="prompt-contrasting-colors" id="prompt-contrasting-colors"></a>(8):
    Contrasting colors:</h3> 
  <ul> 
    <li>Assemble color palettes with insufficiently contrasting colors excluded
      or identified. (see Example A-8)</li> 
    <li> To help  authors test contrast, provide gray scale and black and white views or suggest that  they
      activate the operating system high contrast mode.</li> 
  </ul> 
  <blockquote> 
    <p class="figure"><a id="Example-ContrastColors"></a><strong class="handle">Example A-8:</strong> A dialog box for choosing sufficiently contrasting color combinations. The dialog box has two tabs: one for text color and one for background color. A &quot;hide low contrast choices&quot; checkbox has been selected, so the palette of colors has been pre-screened
      so that sufficient contrast between the text and the current background
      color is assured. All other colors have been grayed out. (Source:
      mock up by AUWG) <br /> 
    <img src="tech_images/b_10.png" width="190" height="220" alt="See the example caption above for description." /></p> 
  </blockquote> 
  <h3><a name="prompt-alt-multimedia" id="prompt-alt-multimedia"></a>(9):
    Alternative content for multimedia (transcripts,
    captions, video transcripts, audio descriptions, signed translations, still
    images, etc.): </h3> 
  <ul> 
    <li>Prompt authors for the location of pre-existing alternative
      resources for multimedia. </li> 
    <li> Provide a single utility where the various alternative resources can be managed at the same time. </li> 
    <li> Although producing alternative resource for multimedia can be a
      complex process for long media files, production suites do exist or authoring
      tools can include simple utilities, with built-in media players, for producing
      simple alternative resources.  </li> 
    <li> The tool should make an attempt to access existing alternative resources for multimedia,
      which may be incorporated into media (e.g. as text or secondary audio tracks) or be located separately but nearby within content. </li> 
  </ul> 
  <h3><a name="prompt-metadata" id="prompt-metadata"></a>(10):
    Metadata:</h3> 
  <ul> 
    <li>For metadata information fields requiring information similar to
      that discussed in the other sections of this Appendix, see the relevant
      section. For example: <a href="#prompt-short-text-labels">short text labels</a>, <a href="#prompt-long-description">long text descriptions</a>, and <a href="#prompt-alt-multimedia">alternative resources for multimedia</a>.</li> 
    <li> When prompting for terms in a controlled vocabulary, allow authors
      to choose from lists to prevent spelling errors.</li> 
    <li> Provide the option of automating the insertion of information that
      easily stored and reused (e.g. author name, author organization, date,
      etc.).</li> 
    <li> Automate metadata discovery where possible.</li> 
    <li> Provide the option of storing licensing conditions within metadata
      (e.g. by Creative Commons licenses, GPL, BSD, etc.)</li> 
  </ul> 
  <h3><a id="Prompt-DocStructure"></a>(11):
    Document structure:</h3> 
  <ul> 
    <li> Alert authors to the occurrence of unstructured content in a way
      that is appropriate to the workflow of the tool.</li> 
    <li>  Provide  authors with options for creating new content that is structured,
      such as:
      <ul> 
          <li> templates (with pre-defined structure),</li> 
        <li>wizards (that introduce structure to content through a series of
          system-generated queries), or</li> 
        <li>real-time validators (that may be set by authors to prevent the
          creation of improperly structured content)</li> 
      </ul> 
    </li> 
    <li> Provide  authors with options for imposing structure on existing unstructured
      content.
      <ul> 
          <li> For tools that support explicit structural mechanisms offer authors
            the opportunity to use those mechanisms. For example, for DTD or schema
            based structures, provide validation in accordance to the applicable
            DTD or schema.</li> 
        <li> For tools that do not support explicit structural mechanisms, offer
          authors the option of deriving structure from format styles. For example,
          provide authors a mechanism to map presentation markup that follows
          formatting conventions into structural elements. For example, patterns
          of text formatting may be interpreted as headings (see
          Example A-11) and multiple lines of text beginning items
          with certain typographical symbols, such as &quot;*&quot; or &quot;-&quot;,
          may be interpreted as list items.</li> 
      </ul> 
    </li> 
    <li>  Provide structure-based editing features, such as:
      <ul> 
          <li> hide/show content blocks according to structure,</li> 
        <li>shift content blocks up, down, and sideways through the document
          structure, or</li> 
        <li>hierarchical representation or network diagram view of the document
        structure, as appropriate.</li> 
      </ul> 
    </li> 
    <li>Provide validation
          for structure.</li>

    <li>It is not necessary to prohibit editing in an unstructured mode. However,
      the tool should alert authors to the fact that they are working in an
    unstructured mode.</li> 
  </ul> 
  <blockquote> 
    <p class="figure"><a id="Example-DocStructure"></a><strong class="handle">Example
      A-11:</strong> A WYSIWYG editing-view that detects opportunities
      for enhancing structure and alerts the author. On the left side is the WYSIWYG editing-view with the title of the page (&quot;Mars&quot;) displayed with a blue underline. The author has brought up a pop-up menu for the title and sees the following options: &quot;Repair: Mark as heading (a sub-menu displays the different levels of header (i.e. h1, h2, etc.)) for the author to choose&quot;, &quot;Skip&quot;, &quot;Ignore&quot;, &quot;Check Accessibility...&quot;, and &quot;Help...&quot;. On the right, an element inspector makes clear that the title is currently marked up as a paragraph. (Source: mock up by AUWG) <br /> 
    <img src="tech_images/b_12.png" width="628" height="188" alt="See the example caption above for description." /></p> 
  </blockquote> 
  <h3><a id="Prompt-TableStructure"></a>(12):
    Tabular structure: </h3> 
  <ul> 
    <li>Prompt  authors to identify tables as used for layout or data
      or implement automated detection mechanisms.</li> 
    <li> Differentiate utilities for table structure from utilities for document
      layout - use this when tables are identified as being for layout.</li> 
    <li> Prompt  authors to provide header information. (see
      Example A-12)</li> 
    <li> Prompt  authors to group and split columns, rows, or blocks of
      cells that are related.</li> 
    <li> Provide authors with a linearized view of tables (as <a

              href="http://www.w3.org/WAI/References/Tablin/">tablin</a> does).</li> 
  </ul> 
  <blockquote> 
    <p class="figure"><a id="Example-TableStructure"></a> <strong class="handle">Example A-12:</strong> A WYSIWYG editing-view that
      prompts the author to decide whether the top row of a table contains the table
      header cells. The top row of the rendered table is outlined in blue to indicate an accessibility problem. The author has brought up a pop-up menu for one of the cells in the top row and sees the following options: &quot;Repair: Set as header row&quot;, &quot;Skip&quot;, &quot;Ignore&quot;, &quot;Check Accessibility...&quot;, and &quot;Help...&quot;. (Source: mock up by AUWG) <br /> 
    <img src="tech_images/b_13.png" alt="See the example caption above for description." width="417" height="162" /></p> 
  </blockquote> 
  <h3><a id="Prompt-stylesheets"></a>(13):
    Style sheets:</h3> 
  <ul> 
    <li>Use style sheets, according to specification, as the default mechanism
      for presentation formatting and layout.</li> 
    <li> If content is created with a style sheet format, along with a content
      format, the use of that style format must also meet the requirements of
      WCAG.</li> 
    <li> Conceal the technical details of style sheet usage to a similar
      degree as for usage of other markup formats supported by the tool.</li> 
    <li> Assist authors by detecting structural markup (e.g. header tags, etc.) that has been misused
      to achieve presentation formatting and, with author permission, transforming
      it to use style sheets. </li> 
    <li> Prompt authors to create style classes and rules within and across
      document, rather than using more limited in-line styling.</li> 
    <li> Assist authors by recognizing patterns in style sheet use and
      converting them into style classes and rules.</li> 
    <li> Provide the option of editing text content independently of style
      sheet layout and presentation formatting. </li> 
    <li> Assist authors with the issue of style sheet browser compatibility
      by guiding them toward standard practices and detecting the existence
      of non-standard practices.</li> 
    <li> Assist authors by providing a style sheet validation function.</li> 
    <li> Maintain a registry of styles for ease of re-use.</li> 
    <li> For prompting and assisting with specific types of information required
      by style sheets, see the other sections in this Appendix. For example:
      (8) font/background colors and (11) document structure.</li> 
    <li> Consult <a href="http://www.w3.org/1999/08/NOTE-CSS-access-19990804">Accessibility Features of CSS</a>.</li> 
  </ul> 
  <h3><a id="Prompt-ClearText"></a>(14): Clearly written text: </h3> 
  <ul> 
    <li>Prompt authors to specify a default language of a document.</li> 
    <li> Provide a thesaurus function.</li> 
    <li> Provide a dictionary lookup system that can recognize changes of
      language, terms outside a controlled vocabulary as well as known abbreviation
      or acronym expansions.</li> 
    <li> Provide an automated reading level status. (see
      Example A-14a)</li> 
    <li> Prompt authors for expansions of unknown acronyms, recognizable
      in some languages as collections of uppercase letters. (see Example
      A-14b)</li> 
  </ul> 
  <blockquote> 
    <p class="figure"><a id="Example-ClearText-a"></a> <strong class="handle">Example A-14a:</strong> A source editing-view that indicates the reading level of a page and whether it exceeds
      a limit determined by the author's preference settings. The  editing-view includes the following markup: <code>&lt;body&gt;&lt;h1&gt;Mars&lt;/h1&gt;&lt;p&gt;Mars is the fourth planet in the solar system, orbiting at a distance of 1.5 AU, with a period of 687 days.&lt;/p&gt;&lt;/body&gt;&lt;/html&gt;</code>. Then in a status bar below the text entry area, is a reading level display: &quot;Reading Level: 11.2 (target&lt;8)&quot;. The 11.2 is highlighted with a yellow background and bold text to indicate that the target is exceeded. (Source: mock up
      by AUWG)<br /> 
    <img src="tech_images/b_15.png" alt="See the example caption above for description." width="417" height="164" /> </p> 
    <p class="figure"> <a id="Example-ClearText-b"></a> <strong class="handle">Example
      A-14b:</strong> An authoring interface
      that prompts the author to enter an acronym expansion. The rendered text reads: &quot;The 'habitable zone' around a star is the region of that star’s solar system in which liquid water is possible. The continuous habitable zone (CHZ) is the region of the solar system which has remained in the zone, even during changes in the star’s radiation pattern.&quot; The acronym &quot;CHZ&quot; is identified with a blue underline as an accessibility problem. The author has brought up a pop-up menu for the acronym and sees the following options: &quot;Repair: Enter acronym expansion…&quot;, &quot;Check Accessibility...&quot;, and &quot;Help...&quot;. (Source: mock up by AUWG)<br /> 
    <img src="tech_images/b_16.png" alt="See the example caption above for description." width="417" height="208" /> </p> 
  </blockquote> 
  <h3><a id="Prompt-DIhandlers"></a>(15): Device-independent events:</h3> 
  <ul> 
    <li>Detect mouse-specific events. </li> 
    <li>If paired keyboard events (e.g. <code>onfocus</code> for <code>onmouseover</code>,) exist, suggest they be added.</li>

  </ul> 
  <h3><a id="Prompt-NonTextSupp"></a>(16):
    Non-text supplements to text:</h3> 
  <ul> 
    <li> Prompt authors to provide icons for buttons, illustrations for
      text, graphs for numeric comparisons, etc. (see
      Example A-16) </li> 
    <li> Where subject metadata is available, look up appropriate illustrations.</li> 
    <li> If authors have identified content as instructions, then provide
      templates or automated utilities for extracting flow charts, etc.</li> 
  </ul> 
  <blockquote> 
    <p class="figure"><a id="Example-NonTextSupp"></a> <strong class="handle">Example A-16:</strong> An authoring
      interface for prompting the author about whether a paragraph that contains
      many numbers might be made more clear with the addition of a chart or
      graph. On the left side of the interface is the rendered text: &quot; Planet Orbits: The inner planets orbit the sun relatively quickly with Mercury orbiting  the sun in 88 days, Venus in 224 days, Earth in 365 days, and Mars in 687 days. Compare this to Jupiter’s, 4332 day orbit.&quot; This text is marked with a yellow exclamation mark icon. On the right side is the following explanation of the error icon: &quot;This paragraph contains 5 numbers. Would readers benefit if a chart or graph of this information was added?&quot;. &quot;Yes&quot; and &quot;no&quot; buttons are provided. (Source: mock up by AUWG)<br /> 
    <img src="tech_images/b_17.png" alt="See the example caption above for description." width="417" height="175" /></p> 
  </blockquote> 
  <hr /> 

</div>  
<!-- techs-only -->
<div class="techs-only"> 
<h2><a name="checking-types" id="checking-types"></a>Appendix B: Levels of Checking Automation</h2>
<p>This section is <a class="termdef" href="#def-Informative" title="definition: informative">informative</a>. </p>
<p>This list is representative, but not necessarily complete.</p> 
  <h3><a name="checking-type-automated" id="checking-type-automated"></a>(a) Automated Checking: </h3> 
  <p>In automated checking, the tool is able to check for accessibility problems
    automatically, with no human intervention required. This type of check is
    usually appropriate for checks of a syntactic nature, such as the use of
    deprecated elements or a missing attribute, in which the meaning of text
    or images does not play a role. </p> 
  <blockquote> 
    <p> <span class="figure"><strong class="handle">Example B-1:</strong> A summary interface for a code-based
      authoring tool that displays the results of an automated check. The display is a tree-view where the leftmost nodes are the names of problems (&quot;Image missing alternate text&quot; and &quot;Text boxes missing labels) with number of problems appended (e.g. &quot;[6]&quot;) and the sub-items are the problem instances with line numbers appended (e.g. &quot;(Line:45)&quot;).  (Source:
      mock up by AUWG)<br /> 
      <img src="tech_images/b_18.png" alt="See the example caption above for description." width="294" height="209" /></span></p> 
    <p class="figure"> <strong class="handle">Example B-2:</strong> A WYSIWYG interface that displays the
      results of an automated check in a WYSIWYG authoring view using blue
      highlighting around or under rendered elements (in this case, the &quot;earthrise&quot; image and some &quot;blinking text&quot;), identifying accessibility
      problems for the author to correct. (Source: mock up by AUWG)<br /> 
    <img

src="tech_images/b_19.png"

alt="See the example caption above for description."

width="417" height="194" /></p> 
    <p class="figure"> <strong class="handle">Example B-3:</strong> An authoring interface of an
      automated check in an instruction-level authoring view. The text is: &quot;<code>&lt;body&gt;&lt;p&gt;Image:&lt;/p&gt;&lt;img href=&quot;pic123.gif&quot;/&gt;&lt;hr/&gt;&lt;blink&gt;Blinking text&lt;/blink&gt;&lt;/body&gt;&lt;/html&gt;</code>&quot;.In this view, the text
      of elements with accessibility problems (<code>img</code> and <code>blink</code>) is shown in a blue font, instead
      of the default black font. (Source: mock up by AUWG)<br /> 
    <img src="tech_images/b_20.png" alt="See the example caption above for description." width="417" height="145" /></p> 
  </blockquote> 
  <h3><a name="checking-type-semi" id="checking-type-semi"></a>(b) Semi-Automated Checking: </h3> 
  <p>In semi-automated checking, the tool is able to identify potential problems,
    but still requires human judgment by authors to make a final decision
    on whether an actual problem exists. Semi-automated checks are usually most
    appropriate for problems that are semantic in nature, such as descriptions
    of non-text objects, as opposed to purely syntactic problems, such as missing
    attributes, that lend themselves more readily to full automation.</p> 
  <blockquote> 
    <p class="figure"><strong class="handle">Example B-4:</strong> A dialog box that appears once
      the tool has detected an image without a description attribute. However,
      since not all images require description, the author is prompted to make
      the final decision (&quot;Does this image require descriptive text?&quot;). The author can confirm that this is indeed an accessibility
      problem by choosing and move on to the repair stage by choosing &quot;Yes&quot; or press &quot;No&quot; to mark the potential problem, as not a problem at all. Additional help is available in the form of a tip: &quot;An image requires descriptive text when the information it contains cannot be conveyed in 10 words or less using an alternate text label.&quot; (Source:
      mock up by AUWG)<br /> 
      <img src="tech_images/b_21.png" width="464" height="171" alt="See the example caption above for description." /></p> 
  </blockquote> 
  <h3><a name="checking-type-manual" id="checking-type-manual"></a>(c) Manual Checking: </h3> 
  <p>In manual checking, the tool provides authors with instructions for detecting
    a problem, but does not automate the task of detecting the problem in any
    other way. As a result,  authors must decide on their own whether
    or not a problem exists. Manual checks are discouraged because they are
    prone to human error, especially when the type of problem in question may
    be easily detected by a more automated utility, such as an element missing
    a particular attribute.</p> 
  <blockquote> 
    <p class="figure"><strong class="handle">Example B-5:</strong> A dialog box that reminds the
      author to check if there are any words in other languages in the document with the message: &quot;Does this document contain any words or phrases in a different language than the main content?&quot;.
      The author can move on to the repair stage by pressing &quot;Yes&quot; or press &quot;No&quot; to mark the potential problem, as not a problem at all.
      (Source: mock up by AUWG)<br /> 
      <img src="tech_images/b_22.png" width="334" height="117" alt="See the example caption above for description." /></p> 
  </blockquote> 
  <hr /> 

</div> <!-- techs-only -->
<div class="techs-only"> 
  <h2><a name="repair-types" id="repair-types"></a>Appendix C: Levels of Repair Automation</h2>
  <p>This section is <a class="termdef" href="#def-Informative" title="definition: informative">informative</a>. </p>
  <p>This list is representative, but not necessarily complete.</p> 
  <h3><a id="repairing-type-manual" name="repairing-type-manual"></a>(a) Repair Instructions: </h3> 
  <p>In manual repairing, the tool provides authors with instructions for making the necessary correction, but does not automate the task in any other way. For example, the tool may move the cursor to start of the problem, but since this is not a substantial automation, the repair would still be considered &quot;manual&quot;. Manual correction tools leave it up to authors to follow the instructions and make the repair by themselves. This is the most time consuming option for authors and allows the most opportunity for human error.</p> 
  <blockquote> 
    <p> <span class="figure"><strong class="handle">Example C-1:</strong> Repair instructions in a code level editing-view. In this case, the following markup is being edited: <code>&lt;body&gt;&lt;p&gt;Image:&lt;/p&gt;&lt;img href=&quot;pic123.gif&quot;/&gt;&lt;hr/&gt;&lt;blink&gt;Blinking text&lt;/blink&gt;&lt;/body&gt;&lt;/html&gt;</code>. Since the problems have already been detected in the checking step and the selected offending elements in a code view (<code>&lt;img href=&quot;pic123.gif&quot;/&gt;</code> and <code>&lt;blink&gt;Blinking text&lt;/blink&gt;</code>) have been highlighted in blue text. When the author puts focus on the highlighted text, a short repair instruction (&quot;Repair: Add 'alt' attribute&quot;) appears in a status bar with a button than will open a longer explanation in the help system. (Source: mock up by AUWG) <br /> 
    <img

src="tech_images/b_25.png"

alt="See the example caption above for description."

width="417" height="193" /></span></p> 
  </blockquote> 
  <h3><a name="repairing-type-semi" id="repairing-type-semi"></a>(b) Semi-Automated: </h3> 
  <p>In semi-automated repairing, the tool can provide some automated assistance to  authors in performing corrections, but author input is still required before the repair can be complete. For example, the tool may prompt authors for a plain text string, but then be capable of handling all of the markup required to add the text string to the content. In other cases, the tool may be able to narrow the choice of repair options, but still rely on authors to make the final selection. This type of repair is usually appropriate for corrections of a semantic nature.</p> 
  <blockquote> 
    <p> <span class="figure"><strong class="handle">Example C-2:</strong> A semi-automated repair in a WYSIWYG editing-view. The author has right-clicked on an image of the &quot;earthrise&quot; that has been highlighted with a blue outline by the automated checker system. This has brought up a pop-up menu with the following choices: &quot;Repair: Set Alt -Text: 'An earth rise as seen from the moon'&quot;,
      &quot;Enter different alt-text…&quot;, &quot;

      Skip&quot;, &quot;Ignore&quot;, &quot;Check Accessibility...&quot;, &quot;Help...&quot;. The author must decide whether the label text that the tool suggests is appropriate. Whichever option the author chooses, the tool will handle the details of updating the content. (Source: mock up by AUWG)<br /> 
    <img

src="tech_images/b_26.png"

alt="See the example caption above for description."

width="417" height="194" /></span></p> 
  </blockquote> 
  <h3><a name="repairing-type-automated" id="repairing-type-automated"></a>(c) Automated: </h3> 
  <p>In automated repairing, the tool is able to make repairs automatically, with
    no author input required. For example, a tool may be capable of automatically
    adding a document type to the header of a file that lacks this information.
    In these cases, very little, if any,  author notification
    is required. This type of repair is usually appropriate for corrections
    of a syntactic or repetitive nature.</p> 
  <blockquote> 
    <p> <span class="figure"><strong class="handle">Example C-3:</strong> An announcement
      that an automated repair has been completed (&quot;All instances of &lt;blink&gt; have been replaced with CSS styling according to your preferences.&quot;). The author selects an &quot;ok&quot; to proceed. An &quot;undo&quot; button
      is provided in case the author wishes to reverse the operation. In some
      cases, automated repairs might be completed with no
      author notification at all. (Source: mock up by AUWG)<br /> 
      <img src="tech_images/b_27.png" alt="See the example caption above for description." width="334" height="117" /></span></p> 
  </blockquote> 
  <hr /> 

</div> <!-- techs-only -->
 
<div class="techs-only"> 
<h2><a name="timing-options" id="timing-options"></a>Appendix D: Author Interruption Timing Options</h2>
<p>This section is <a class="termdef" href="#def-Informative" title="definition: informative">informative</a>. </p>
<p>This list is representative, but not necessarily complete.</p> 
  <p><a id="timing-type-negotiated" name="timing-type-negotiated"></a><strong>(a) Negotiated Interruption:</strong> A negotiated interruption is caused by interface mechanisms (e.g. icons or highlighting of the element, audio feedback) that alert the author to a problem, but remain flexible enough to allow the author to decide whether to take immediate action or address the issue at a later time. Since negotiated interruptions are less intrusive than immediate or scheduled interruptions, they can often be better integrated into the design workflow and have the added benefit of informing the author about the distribution of problems within the document. Although some authors may choose to ignore the alerts completely, it is <em>not</em> recommended that authors be forced to fix problems as they occur. Instead, it is recommended that negotiated interruption be supplemented by <a href="#timing-type-scheduled">scheduled interruptions at major editing events</a> (e.g. when publishing), when the tool should alert the author to the outstanding accessibility problems. </p> 
  <blockquote> 
    <p class="figure"> <img src="icons/rendered.gif" alt="Applicable to content-rendering authoring functions" width="16" height="16" border="1" /><strong class="handle">Example D-1:</strong> A WYSIWYG editing-view makes the author of problems detected automatically by means of a blue line under text or around rendered objects with accessibility problems. Here, red lines are also visible, highlighting spelling errors in the text. The author can decide to address the problems at a later time. (Source: mock up by AUWG)<br /> 
    <img

src="tech_images/b_38.png"

alt="See the example caption above for description."

width="417" height="194" /></p> 
  </blockquote> 
  <p><a id="timing-type-scheduled" name="timing-type-scheduled"></a><strong>(b) Scheduled Interruption:</strong> A scheduled interruption is one in which the author has set the tool to alert them of accessibility issues on a configurable schedule. One option for the schedule might be to have prompts associated with the interface mechanisms for significant authoring events, such as opening, saving, closing, committing, or publishing files. At the significant authoring event, the author would be informed of the problem, while at the same time they would <em>not</em> be prevented from saving, publishing, printing, etc. A potential downside of postponing corrective actions is that by the time the prompt is displayed, the author may not have sufficient time or inclination to make the required changes, especially if they are extensive.</p> 
  <blockquote> 
    <p class="figure"><strong class="handle">Example D-2:</strong> A &quot;Publish&quot; dialog box allows the author to publish multiple files at once, however in the case shown here, two of the files have uncorrected accessibility problems which causes them not to meet a &quot;standard of publishing&quot; the author has set for themselves in the options. As a result the files are selected, a message is displayed (&quot;The selected files do not meet your specified standard for publishing.&quot;) and the &quot;publishing&quot; button is grayed out. This standard is referred to generally since it is assumed that it might include spelling and grammar standards as well as accessibility issues. (Source: mock up by AUWG) <br /> 
      <img

src="tech_images/b_39.png" alt="See the example caption above for description." width="377" height="185" /></p> 
  </blockquote> 
  <p><a id="timing-type-immediate" name="timing-type-immediate"></a><strong>(c) Immediate Interruption:</strong> An immediate interruption is the most intrusive timing option because the attention of the author is actively diverted from the current editing task by the notification of some issue. This might be achieved, for instance, by an alert dialog. This type of alert presents multiple usability problems and should be used sparingly because it interferes with the normal design workflow. Intrusive warnings are probably only appropriate when the window of opportunity for correcting a serious accessibility problem is about to close, such as when an author decides to publish the content in question. In general, negotiated and scheduled interruptions are preferred.</p> 
  <blockquote> 
    <p class="figure"><strong class="handle">Example D-3:</strong> A modal dialog box contains the message: &quot;This image is missing alternate text&quot;. The author must press the &quot;OK&quot; button to continue. (Source: mock up by AUWG)<br /> 
      <img

src="tech_images/b_40.png"

alt="See the example caption above for description."

width="266" height="107" /></p> 
  </blockquote> 
  <p>&nbsp;</p> 

</div> 
<!-- techs-only -->
<div class="techs-only"> 
<h2><a name="realtime-production" id="realtime-production"></a>Appendix E: Authoring Tools for Live Web     Content</h2>
<p>This section is <a class="termdef" href="#def-Informative" title="definition: informative">informative</a>. </p>
<p>Supporting the production of <a class="termdef" href="#def-Live" title="definition: live">live</a> web content that is also accessible is a challenge. The immediate and continuous time pressures will limit what can reasonably expect from authors. However, there are potential approaches that developers may take to increase the accessibility of the live content produced by their authoring tools:</p>
<blockquote> 
    <p><strong><a id="need" name="need"></a>(a) Determine Participant Requirements:</strong> Sometimes it may be possible to determine beforehand the accessibility requirements of the end-user audience. In other cases, polling the participants (see &quot;Request whiteboard descriptions&quot; checkbox in the figure) or matching participant profiles might help determine which types of accessibility practices would offer the greatest advantage in the short time available. However, usually it is impossible to know all of the needs of the actual or potential participants.</p> 
    <p><strong><a id="assistant" name="assistant"></a>(b) Assistant/Peer Author:</strong> Consider designating one or more secondary authors, who can receive and respond to prompts for supplemental information generated as the primary author proceeds uninterrupted. The secondary author(s) might be an unrelated specialist, analogous to a sign language interpreter, a co-author (helpful for describing technical drawings, etc.), or in some situations a member of the session audience (e.g. peer descriptions).</p> 
    <p><strong><a id="preptime" name="preptime"></a>(c) Preparation Time:</strong> Consider allowing authors time to pre-assemble materials for a live presentation (e.g. a professor preparing for an online class).</p> 
    <p><strong><a id="archiving" name="archiving"></a>(d) Archiving:</strong> If the session will be archived, there may be other opportunities to increase the accessibility of the content of the archive by guiding  authors through a process to check for and repair accessibility problems after the live session has ended, but prior to archiving.</p> 
  </blockquote> 
  <blockquote> 
    <p class="figure"><strong class="handle">Example E-1:</strong> A live presentation in a whiteboard/chat client environment that has been enhanced to provide real-time descriptions. The example has five panes. On the far left is a list of participants (&quot;Presenter&quot;, &quot;John (You)&quot;, &quot;Jane&quot;, and &quot;Alice&quot;). In the upper-middle is the chat &quot;Presenter&gt; I suggest a space theme for the slide presentation.&quot;, &quot;Image File Inserted (by Presenter)
      Description: An earthrise as seen from the surface of the moon.&quot;, &quot;Presenter&gt; The white text would go...&quot;, &quot;Marker (by Presenter)
      Description&gt; Draws a red box..., and &quot;Presenter&gt; in this area.&quot; Notice that descriptions are appearing here. The lower-middle is the message composition area for this user and is blank. The upper-right is the whiteboard. So far there is an image of &quot;earthrise&quot; and a red hand-drawn rectangle on the  &quot;canvas&quot;. The whiteboard tools are &quot;select box&quot;, &quot;text tool&quot;, &quot;marker&quot;, &quot;eraser&quot;, &quot;insert image&quot;, &quot;line tool&quot;, &quot;rectangle tool&quot;, and an &quot;ellipse tool&quot;. In the lower-right is an area for describing a drawing action - in this case the &quot;Presenter' use of the Marker&quot;. Notice that any participant can describe the events on the whiteboard even as the dialog continues. (Source: mock up by AUWG).<br /> 
    <img src="tech_images/b_41.png" alt="See the example caption above for description." width="558" height="322" /></p> 
  </blockquote> 
  <hr /> 

</div> <!-- techs-only -->
 
<div id="sect-definitions"> 
  <h2><a id="glossary" name="glossary"></a>Appendix <span class="techs-only">F</span>: Glossary</h2> 
   <!-- gl-only -->
  <div class="techs-only"> 
    <p>This section is included here for <a class="termdef" href="#def-Informative" title="definition: informative">informative</a> purposes. The <a class="termdef" href="#def-Normative" title="definition: normative">normative</a> version appears in the Authoring Tool Accessibility Guidelines 2.0 <a href="#ref-ATAG20" title="reference: ATAG20"><cite>[ATAG20]</cite></a>.</p> 
  </div> <!-- 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 -->

 <!-- gl-only -->
<div id="sect-references"> 
  <h2><a id="references" name="references"></a>Appendix <span class="techs-only">G</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 class="techs-only"><a name="ref-ATAG20" id="ref-ATAG20"><strong>[ATAG20]</strong></a></dt> 
    <dd class="techs-only">&quot;<a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/Overview.html">Authoring Tool Accessibility Guidelines
      2.0</a>,&quot; J. Treviranus, J. Richards, C. McCathieNevile, and M. May, eds.
      The latest version is available at http://www.w3.org/TR/ATAG20. The <a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/Overview.html">latest version of ATAG 2.0</a> is available at http://www.w3.org/TR/ATAG20.</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="techs-only">H</span>: Acknowledgments</h2> 
  <!-- 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 -->
 
 <!-- gl-only -->
 

 <!-- gl-only -->
<div class="techs-only"> 
  <p align="center">[<a href="#contents">Contents</a>] [<a href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/Overview.html">Guidelines</a>]</p> 
</div> <!-- techs-only -->
 
</body> 
</html>