discontinued / server · Files

WD-AERT-20000426 141 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 
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"
                      "http://www.w3.org/TR/REC-html40/loose.dtd">
<html>
<head>
  <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
  <!--Started by Chris Ridpath, summer 1999-->
  <title>Techniques For Accessibility Evaluation And Repair Tools</title>
  <link rel="stylesheet" type="text/css"
  href="http://www.w3.org/StyleSheets/TR/W3C-WD">
</head>

<body lang="en">

<div class="navbar">
[<a accesskey="c" href="#TOC">contents</a>]  
<hr class="navbar" title="Navigation area separator">
</div>

<div class="head">
<p><a href="http://www.w3.org/" title="Go to W3C Home Page"><img height="48"
width="72" alt="W3C" src="http://www.w3.org/Icons/w3c_home"></a></p>

<h1 class="notoc">Techniques For Accessibility Evaluation And Repair
Tools</h1>

<h2 class="notoc">W3C Working Draft, 26 April 2000</h2>
<dl>
  <dt>This version:</dt>
    <dd><a
      href="http://www.w3.org/TR/2000/WD-AERT-20000426">http://www.w3.org/TR/2000/WD-AERT-20000426</a></dd>
  <dt>Latest version:</dt>
    <dd><a href="http://www.w3.org/TR/AERT">http://www.w3.org/TR/AERT</a></dd>
  <dt>Editors:</dt>
    <dd><a href="mailto:chris.ridpath@utoronto.ca">Chris Ridpath</a>, <a
      href="http://www.utoronto.ca/atrc/">Adaptive Technology Resource
      Centre</a>, <a href="http://www.utoronto.ca">University of Toronto</a>
      -- Canada<br>
      <a href="mailto:wendy@w3.org">Wendy Chisholm</a>, W3C</dd>
</dl>

<p class="copyright"><a
href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a>
©2000 <a href="http://www.w3.org/"><abbr title="World Wide Web
Consortium">W3C</abbr></a><sup>®</sup> (<a
href="http://www.lcs.mit.edu/"><abbr title="Massachusetts Institute of
Technology">MIT</abbr></a>, <a href="http://www.inria.fr/"><abbr lang="fr"
title="Institut National de Recherche en Informatique et
Automatique">INRIA</abbr></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>,
<a
href="http://www.w3.org/Consortium/Legal/copyright-documents-19990405">document
use</a> and <a
href="http://www.w3.org/Consortium/Legal/copyright-software-19980720">software
licensing</a> rules apply.</p>
</div>
<hr title="Separator from Header">

<h2><a name="Abstract">Abstract</a></h2>

<p>This document describes techniques that Web accessibility validation tools
may use to evaluate the conformance of HTML documents to the <a
href="http://www.w3.org/TR/WAI-WEBCONTENT/">Web Content Accessibility
Guidelines 1.0 (WCAG 1.0)</a>.  This document also describes techniques that
Web authoring tools may use to help authors modify HTML documents to conform
to WCAG 1.0. We anticipate that tool developers may develop accessibility
validation and/or repair modules to be incorporated into commercial authoring
tools, validation tools, and perhaps user agents.</p>

<h2><a name="Status" id="Status">Status Of This Document</a></h2>

<p>This section describes the status of this document at the time of its
publication. Other documents may supersede this document. The <a
href="http://www.w3.org/WAI/ER/IG/Overview.html#ert-history">latest status of
this document series</a> is maintained at the W3C.</p>

<p>This is a W3C Working Draft produced by the <a
href="http://www.w3.org/WAI/ER/IG/">Evaluation and Repair Tools Working
Group</a>. The working group encourages</p>
<ul>
  <li>feedback on existing techniques discussed in this document,</li>
  <li>suggestions for new techniques,</li>
  <li>implementation and testing of the techniques discussed in this
  document.</li>
</ul>

<p>The working group expects to collect and test new and existing techniques
in the next few months. The document will be updated to reflect the group's
findings.</p>

<p>Information about existing Evaluation, Repair, and Transformation Tools for
Web Content Accessibility is available from the working group's home page.</p>

<p>This is a draft document and may be updated, replaced, or obsoleted by
other documents at any time. It is inappropriate to use W3C Working Drafts as
reference material or to cite them as other than "work in progress". A list of
current W3C Recommendations and other technical documents can be found at <a
href="http://www.w3.org/TR/">http://www.w3.org/TR/</a>.</p>

<p>Please send comments on this document to <a
href="mailto:w3c-wai-er-ig@w3.org">w3c-wai-er-ig@w3.org.</a> The <a
href="http://lists.w3.org/Archives/Public/w3c-wai-er-ig/">archives for this
list</a> are publicly available.</p>

<h3><a name="q4">To do</a></h3>
<ul>
  <li>Clean up all of the @@'s (open issues, questions and comments).</li>
  <li>Check for consistent language usage.</li>
  <li>Link to WCAG, AU and UA Techniques and EO Curriculum where
  appropriate.</li>
  <li>Use WCAG notes or rationale as example language where possible or
    appropriate.</li>
  <li>Inherit reference info between checkpoints from WCAG (e.g., at the end
    of Checkpoint 10.1, "refer also to Checkpoint 12.4").</li>
  <li>Determine if we want to use "author" or "user." Then check for
    consistent usage.</li>
  <li>Determine if we want to use "document" or "page." Then check for
    consistent usage.</li>
  <li>Ensure that "Web" is capitalized consistently.</li>
  <li>Update and finish creating test files.  Upload the images associated
    with the test files.</li>
  <li>Resolve open issues both listed in this document as well as in the<a
    href="http://www.w3.org/WAI/ER/IG/ert/ert-open-issues.html"> list of open
    issues</a>.</li>
</ul>

<div class="toc">
<h2><a name="TOC">Table of Contents</a></h2>
<ul class="toc">
  <li class="tocline2"><a href="#Abstract" name="toc-Abstract"
    class="tocxref">Abstract</a></li>
  <li class="tocline2"><a href="#Status" name="toc-Status"
    class="tocxref">Status Of This Document</a></li>
  <li class="tocline2"><a href="#TOC" name="toc-TOC" class="tocxref">Table of
    Contents</a></li>
  <li class="tocline2"><a href="#Introduction" name="toc-Introduction"
    class="tocxref">Introduction</a></li>
  <li class="tocline2"><a href="#q7" name="toc-q7" class="tocxref">Structure
    Of This Document</a></li>
  <li class="tocline2"><a href="#provide-equivalents" name="toc-q8"
    class="tocxref">Guideline 1. Provide equivalent alternatives to auditory
    and visual content.</a></li>
  <li class="tocline2"><a href="#color" name="toc-color"
    class="tocxref">Guideline 2. Don't rely on color alone.</a></li>
  <li class="tocline2"><a href="#structure-presentation"
    name="toc-structure-presentation" class="tocxref">Guideline 3. Use markup
    and style sheets and do so properly</a></li>
  <li class="tocline2"><a href="#abbreviated-and-foreign"
    name="toc-abbreviated-and-foreign" class="tocxref">Guideline 4. Clarify
    natural language usage</a></li>
  <li class="tocline2"><a href="#table-markup" name="toc-table-markup"
    class="tocxref">Guideline 5. Create tables that transform
  gracefully</a></li>
  <li class="tocline2"><a href="#new-technologies" name="toc-new-technologies"
    class="tocxref">Guideline 6. Ensure that pages featuring new technologies
    transform gracefully</a></li>
  <li class="tocline2"><a href="#movement" name="toc-movement"
    class="tocxref">Guideline 7. Ensure user control of time-sensitive content
    changes</a></li>
  <li class="tocline2"><a href="#own-interface" name="toc-own-interface"
    class="tocxref">Guideline 8. Ensure direct accessibility of embedded user
    interfaces</a></li>
  <li class="tocline2"><a href="#device-independence"
    name="toc-device-independence" class="tocxref">Guideline 9. Design for
    device-independence</a></li>
  <li class="tocline2"><a href="#interim-accessibility"
    name="toc-interim-accessibility" class="tocxref">Guideline 10. Use interim
    solutions</a></li>
  <li class="tocline2"><a href="#use-w3c" name="toc-use-w3c"
    class="tocxref">Guideline 11. Use W3C technologies and guidelines</a></li>
  <li class="tocline2"><a href="#complex-elements" name="toc-complex-elements"
    class="tocxref">Guideline 12. Provide context and orientation
    information</a></li>
  <li class="tocline2"><a href="#facilitate-navigation"
    name="toc-facilitate-navigation" class="tocxref">Guideline 13. Provide
    clear navigation mechanisms</a></li>
  <li class="tocline2"><a href="#facilitate-comprehension"
    name="toc-facilitate-comprehension" class="tocxref">Guideline 14. Ensure
    that documents are clear and simple</a></li>
  <li class="tocline2"><a href="#AppendixA" name="toc-AppendixA"
    class="tocxref">Appendix A - Placeholder text</a></li>
  <li class="tocline2"><a href="#AppendixB" name="toc-AppendixB"
    class="tocxref">Appendix B - Image File Suffixes</a></li>
  <li class="tocline2"><a href="#AppendixC" name="toc-AppendixC"
    class="tocxref">Appendix C - Placeholder OBJECT text equivalent</a></li>
  <li class="tocline2"><a href="#AppendixD" name="toc-AppendixD"
    class="tocxref">Appendix D - Sound File Suffixes</a></li>
  <li class="tocline2"><a href="#AppendixE" name="toc-AppendixE"
    class="tocxref">Appendix E - Placeholder <code>NOSCRIPT</code>
  text</a></li>
  <li class="tocline2"><a href="#AppendixF" name="toc-AppendixF"
    class="tocxref">Appendix F - Placeholder <code>TABLE "summary"</code>
    text</a></li>
  <li class="tocline2"><a href="#AppendixG" name="toc-AppendixG"
    class="tocxref">Appendix G - Placeholder table header "<code>abbr</code>"
    text</a></li>
  <li class="tocline2"><a href="#AppendixH" name="toc-AppendixH"
    class="tocxref">Appendix H - Placeholder <code>FRAME "title"</code>
    text</a></li>
  <li class="tocline2"><a href="#AppendixI" name="toc-AppendixI"
    class="tocxref">Appendix I - Applet Executable Suffix</a></li>
  <li class="tocline2"><a href="#AppendixJ" name="toc-AppendixJ"
    class="tocxref">Appendix J - Bullet Identification</a></li>
  <li class="tocline2"><a href="#AppendixK" name="toc-AppendixK"
    class="tocxref">Appendix K - Horizontal Rule Identification</a></li>
  <li class="tocline2"><a href="#AppendixL" name="toc-AppendixL"
    class="tocxref">Appendix L - Links To Associated Sites</a></li>
  <li class="tocline2"><a href="#q456" name="toc-q456"
    class="tocxref">Glossary</a></li>
</ul>
</div>
<hr title="Separator from Table Of Contents">

<h2><a name="Introduction">Introduction</a></h2>

<p>The Web Accessibility Initiative (WAI) has produced a foundation document,
<a href="http://www.w3.org/TR/WAI-WEBCONTENT/">The W3C Web Content
Accessibility Guidelines</a> (WCAG 1.0), that describes what must be done to
make a Web page accessible to all. Tools are needed to help authors determine
if a web site is accessible to everyone and to help repair it if it is
not.</p>

<p>This document builds on the WCAG 1.0 foundation by outlining techniques
that evaluation and repair tools may use to uncover accessibility problems and
possibly repair them. These techniques may be used by those who create web
authoring tools or by anyone interested in creating accessible Web
documents.</p>

<p>It is important that people with disabilities are included in the "anyone
interested in creating accessible Web content." Creating accessible Web
content is as important as accessing Web content. Therefore, evaluation and
repair tools themselves need to be accessible to people with disabilities.
However, this document does not describe how to make the user interface
accessible. Please refer to the <a href="http://www.w3.org/TR/UAAG10/">User
Agent Accessibility Guidelines</a> for information on making the user
interface accessible.</p>

<p>Many people using evaluation and repair tools may be new to the Web and
will not be familiar with the various markup languages that are used. Many
others will not know about Web accessibility. Tools should be intuitive and
easy to use and available at a minimal cost. Tools should not generate
excessive warnings or false positive accessibility errors.</p>

<p>Some of the web-content accessibility checkpoints cannot be checked
successfully by software algorithms alone. There will still be a dependence on
the user's ability to exercise human judgment to determine conformance to the
guidelines. It is imperative that any tool have features that assist in
reminding, without nagging; in helping, without demeaning; in suggesting,
without demanding. We hope that the techniques in this document, implemented
in software programs, will gently guide authors along the path to more
accessible documents.</p>

<h2><a name="q7">Structure Of This Document</a></h2>

<p>This document is based on <a
href="http://www.w3.org/TR/WAI-WEBCONTENT/">The W3C Web Content Accessibility
Guidelines</a>. It lists each guideline and checkpoint in in that document.
Under each checkpoint it lists one or more techniques for evaluating and, in
some cases, repair.  Each technique comprises the following subsections:</p>
<dl>
  <dt><strong>Open issues for this technique</strong></dt>
    <dd>This section lists open issues and questions about a particular
      technique.  </dd>
  <dt><strong>Evaluation:</strong></dt>
    <dd>The algorithmic and heuristic tests that will be applied. consisting
      of
      <ul>
        <li><strong>Elements</strong> - the elements to which this test
          applies, e.g. <code>IMG</code> etc. If it only applies to an element
          of a particular type, this is noted (e.g. <code>INPUT
           TYPE="image"</code>></li>
        <li><strong>Requirements</strong> - the conditions which will be
          tested for by means of algorithms and heuristics.</li>
      </ul>
      <p><br>
      Note: in a few cases, the warning is always presented.</p>
    </dd>
  <dt><strong>Suggested message:</strong></dt>
    <dd>Messages displayed to the author if the element is found and the
      requirement is not satisfied.</dd>
  <dt><strong>Suggested repair:</strong></dt>
    <dd>Actions that may be required to repair the accessibility problem.</dd>
  <dt><strong>Test files:</strong></dt>
    <dd>Used to test evaluation tools to see if they find the accessibility
      problem. <em>These are under construction!!</em></dd>
  <dt><strong>Discussion files:</strong></dt>
    <dd>Discussion and comments on the technique.</dd>
</dl>

<p><strong>Note</strong>. This document specifies only the function of
evaluation and repair tools. Nothing in this document should be taken to imply
a particular user interface.</p>
<hr title="Separator from Document Structure">

<h2><a name="provide-equivalents">Guideline 1</a>. Provide equivalent
alternatives to auditory and visual content.</h2>
<ul>
  <li><a href="#text-equivalent">Checkpoint 1.1</a> - Provide a text
    equivalent for every non-text element</li>
  <li><a href="#redundant-server-links">Checkpoint 1.2</a> - Provide redundant
    text links for each active region of a server-side image map</li>
  <li><a href="#auditory-descriptions">Checkpoint 1.3</a> - Until user agents
    can automatically read aloud the text equivalent of a visual track,
    provide an auditory description of the important information of the visual
    track of a multimedia presentation</li>
  <li><a href="#av-in-dynamic-objects">Checkpoint 1.4</a> - For any time-based
    multimedia presentation (e.g., a movie or animation), synchronize
    equivalent alternatives (e.g., captions or auditory descriptions of the
    visual track) with the presentation</li>
  <li><a href="#client-side">Checkpoint 1.5</a> - Until user agents render
    text equivalents for client-side image map links, provide redundant text
    links for each active region of a client-side image map</li>
</ul>
<hr>

<h3><a name="text-equivalent">Checkpoint 1.1 - Provide a text equivalent for
every non-text element</a></h3>

<h4><a name="check-img-for-alt">Technique 1.1.1</a> [priority 1] Check
<code>IMG</code> elements for valid "<code>alt</code>" attribute</h4>

<h5>Open issues for this technique:</h5>
<ul>
  <li>@@WCAG issue: final word on null and blank alt-text. See discussion at
    <a
    href="http://lists.w3.org/Archives/Public/w3c-wai-er-ig/1999Jun/0050.html">http://lists.w3.org/Archives/Public/w3c-wai-er-ig/1999Jun/0050.html</a>
    especially part about null or blank alt-text for links.  Awaiting results
    of survey</li>
</ul>

<h5>Evaluation:</h5>
<ul>
  <li>Element: <code>IMG</code></li>
  <li>Requirement: Valid "<code>alt</code>" attribute.</li>
</ul>

<p>Valid "<code>alt</code>" attribute:</p>
<ul>
  <li>"<code>alt</code>" attribute must exist</li>
  <li>Not allowed - NULL "<code>alt</code>" value (<code>alt=""</code>)</li>
  <li>Allowed - "<code>alt</code>" value of 1 or more spaces ("<code>alt="
    "</code>") but only if image is not within an "<code>A<code>
    element</code></code>"</li>
  <li>Suspicious - "<code>alt</code>" attribute value could be file size (ends
    with "bytes")</li>
  <li>Suspicious - "<code>alt</code>" attribute value ends with <a
    href="#AppendixB">image file suffix</a>.</li>
  <li>Suspicious - "<code>alt</code>" attribute value is <a
    href="#AppendixA">placeholder text</a>.</li>
  <li>Suspicious - "<code>alt</code>" attribute value is longer than 150
    characters. Suggest that a description file be created.</li>
</ul>

<h5>Suggested message:</h5>
<ul>
  <li>Missing text equivalent: Missing text equivalent for image.</li>
  <li>Suspicious "<code>alt</code>" attribute: Suspicious text equivalent for
    image: [current "<code>alt</code>" text] - [could be file size | could be
    file name | could be placeholder text | text equivalent should be short,
    perhaps this could be a "<code>longdesc</code>"].</li>
  <li>Invalid "<code>alt</code>" attribute: Invalid text equivalent for image:
    [text equivalents can not be empty].</li>
</ul>

<h5>Suggested repair:</h5>
<ul>
  <li>Prompt the user for a text equivalent for the image.</li>
  <li>If the document contains another instance of the image and that image
    contains an "<code>alt</code>" attribute, suggest that "<code>alt</code>"
    attribute value.</li>
  <li>If the image is <a href="#AppendixJ">assumed to be a bullet</a>,
    suggested text should be "bullet".</li>
  <li>If the image is <a href="#AppendixK">assumed to be a horizontal
    rule</a>, suggested text should be "horizontal rule".</li>
  <li><a href="http://www.w3.org/WAI/ER/text-equiv.htm">Other suggestions by
    Daniel Dardailler</a></li>
  <li><a href="http://www.vorburger.ch/projects/alt/index.html">Suggestions by
    Michael Vorburger</a></li>
  <li>After user has entered an <code>"alt"</code> attribute for the image,
    check the site for other instances of the image. If the site contains
    other images that are the same and they do not have a text equivalent,
    suggest that all same images without an "<code>alt</code>" attribute use
    the new "<code>alt</code>" attribute value.</li>
</ul>

<h5>Test Files and Discussion Files:</h5>
<ul>
  <li><a href="http://www.w3.org/WAI/ER/IG/ert/test11A.htm">Test file -
    alt-text</a></li>
</ul>

<h4><a name="verify-img-descriptions">Technique 1.1.2</a> [priority 1] Verify
that valid <code>IMG</code> element descriptions (<code>"longdesc"</code>
attribute or d-link) are provided where necessary.</h4>

<h5>Open issues for this technique:</h5>
<ul>
  <li>Daniel D. on May 19, 1999 suggested that we could check for the
    complexity of the image by looking for a "<code>caption</code>"
  attribute.</li>
</ul>

<h5><a name="q15">Evaluation:</a></h5>
<ul>
  <li>Element: <code>IMG</code></li>
  <li>Requirements:
    <ul>
      <li>Valid "<code>longdesc</code>" attribute or a d-link required if
        describing the image will add information not given in the text of the
        page. The amount of information in the image and the context in which
        it is used will determine how detailed the description should be.
        Note: d-link now deprecated.</li>
      <li>Cases where a description is not required:
        <ul>
          <li><a href="#AppendixJ">bullets - refer to Appendix J.</a></li>
          <li><a href="#AppendixK">horizontal rules - refer to Appendix
          K.</a></li>
        </ul>
      </li>
    </ul>
  </li>
</ul>

<p>Valid "<code>longdesc</code>" attribute:</p>
<ul>
  <li>any valid URI</li>
</ul>

<h5><a name="q16">Suggested message:</a></h5>
<ul>
  <li>If describing the image will add information not given in the text of
    the page, you need to provide a description of the image. The amount of
    information in the image and the context in which it is used will
    determine how detailed the description should be.</li>
</ul>

<h5><a name="q17">Suggested repair:</a></h5>
<ul>
  <li>Ask user if the image presents information that is not included in the
    page or in the text equivalent for the image. Allow the user to create or
    associate a description.
    <ul>
      <li>with the "<code>longdesc</code>" attribute on an <code>IMG</code>
        element</li>
      <li>via a D-link</li>
    </ul>
  </li>
  <li>If another document on the same site uses the same image and has a
    "<code>longdesc</code>", suggest that "<code>longdesc</code>" file.</li>
</ul>

<h5><a name="q18">Test Files and Discussion Files:</a></h5>
<ul>
  <li><a href="http://www.w3.org/WAI/ER/IG/ert/test11B.htm">Test file -
    longdesc.</a></li>
</ul>

<h4><a name="check-input-for-alt">Technique 1.1.3</a> [priority 1] Check
<code>INPUT</code> elements of <code>type="image"</code> for valid
"<code>alt</code>" attribute</h4>

<h5><a name="q20">Evaluation:</a></h5>
<ul>
  <li>Element: <code>INPUT type="image"</code></li>
  <li>Requirement: Valid "<code>alt</code>" attribute.</li>
</ul>

<p>Valid "<code>alt</code>" attribute:</p>
<ul>
  <li>"<code>alt</code>" attribute must exist</li>
  <li>Not valid - NULL "<code>alt</code>" value (<code>alt=""</code>)</li>
  <li>Not valid - "<code>alt</code>" value of 1 or more spaces (<code>alt="
    "</code>)</li>
  <li>Suspicious - "<code>alt</code>" attribute value could be file size (ends
    with "bytes")</li>
  <li>Suspicious - "<code>alt</code>" attribute value ends with <a
    href="#AppendixB">image file suffix</a>.</li>
  <li>Suspicious - "<code>alt</code>" attribute value is <a
    href="#AppendixA">placeholder text</a>.</li>
</ul>

<h5><a name="q21">Suggested message:</a></h5>
<ul>
  <li>Missing text equivalent: Missing text equivalent for this button.</li>
  <li>Suspicious text equivalent: Suspicious text equivalent for button:
    [current "<code>alt</code>" attribute] - [could be file size | could be
    file name | could be placeholder text].</li>
  <li>Invalid text equivalent: Invalid text equivalent for button: [
    "<code>alt</code>" attribute can not be empty | text equivalent can not
    contain only 'spaces'].</li>
</ul>

<h5><a name="q22">Suggested repair:</a></h5>
<ul>
  <li>Prompt the user for text equivalent.</li>
  <li>If another document on the same site has an INPUT element with the same
    TYPE value, suggest that type value.</li>
</ul>
<!-- <h5><a name="q23">Test Files and Discussion Files:</a></h5>
<ul>
<li><a href="http://www.w3.org/WAI/ER/IG/ert/test11C.htm">Link to test files
for this technique.</a></li>
</ul> -->

<h4><a name="check-applet-for-equiv">Technique 1.1.4</a> [priority 1] Check
<code>APPLET</code> elements for valid HTML equivalent</h4>

<h5><a name="q25">Evaluation:</a></h5>
<ul>
  <li>Element: <code>APPLET</code></li>
  <li>Requirements:
    <ul>
      <li>Valid "<code>alt</code>" attribute OR</li>
      <li>accessible  HTML within <code>APPLET</code> element</li>
    </ul>
  </li>
</ul>

<p>Valid <code>"alt"</code> attribute values:</p>
<ul>
  <li>Not allowed - NULL "<code>alt</code>" attribute value
    (<code>alt=""</code>)</li>
  <li>Not allowed - "<code>alt</code>" attribute value of 1 or more spaces
    (<code>alt=" "</code>)</li>
  <li>Suspicious - "<code>alt</code>" attribute value could be file size (ends
    with "bytes")</li>
  <li>Suspicious - "<code>alt</code>" attribute value ends with <a
    href="#AppendixB">image file suffix</a>.</li>
  <li>Suspicious - "<code>alt</code>" attribute value is <a
    href="#AppendixA">placeholder alt-text text</a>.</li>
  <li>Suspicious - "<code>alt</code>" attribute ends with <a
    href="#AppendixI">applet executable suffix</a>.</li>
  <li>Allowed - no "<code>alt</code>" attribute if text is provided within the
    content of the <code>APPLET</code> element.</li>
</ul>

<h5><a name="q26">Suggested message:</a></h5>
<ul>
  <li>Missing text equivalent: Applet must have valid a valid
    "<code>alt</code>" attribute or accessible HTML content."</li>
  <li>Suspicious text equivalent: Suspicious text equivalent for applet:
    [current "<code>alt</code>" attribute value] - [could be file size | could
    be image file name | could be placeholder text | could be applet
    executable name].</li>
  <li>Invalid text equivalent: Invalid "<code>alt</code>" attribute for applet
    - [text equivalent can not be empty | text equivalent can not be all
    'spaces'].</li>
</ul>

<h5><a name="q27">Suggested repair:</a></h5>
<ul>
  <li>Prompt the user for text equivalent.</li>
  <li>If the same applet is used on the same site and has an
    "<code>alt</code>" attribute, suggest that "<code>alt</code>" attribute
    value.</li>
</ul>

<h5><a name="q28">Test Files and Discussion Files:</a></h5>
<ul>
  <li><a href="http://www.w3.org/WAI/ER/IG/ert/test11E.htm">Test file - alt
    for applets.</a></li>
</ul>

<h4><a name="check-object-for-equiv">Technique 1.1.5</a> [priority 1] Check
<code>OBJECT</code> elements of
<code>type="</code><em><code>image_MIME_types</code></em><code>"</code> for
valid text equivalents and descriptions (where necessary)</h4>

<h5>Open issues for this technique:</h5>
<ul>
  <li>This only covers text equivalents. Where is non-text covered if not
    here?</li>
</ul>

<h5><a name="q30">Evaluation:</a></h5>
<ul>
  <li>Element: <code>OBJECT</code></li>
  <li>Requirement: Between <code>OBJECT</code> start element and
    <code>OBJECT</code> end element must be a valid alternative representation
    element.</li>
</ul>

<p>Valid alternative representation element:</p>
<ul>
  <li>A text element with at least one word of text.</li>
  <li>An <code>IMG</code> element with valid alt- text</li>
  <li>A valid URI</li>
  <li>Suspicious - "<code>alt</code>" attribute value is <a
    href="#AppendixC">placeholder <code>OBJECT</code> text equivalent</a></li>
</ul>

<h5><a name="q31">Suggested message:</a></h5>
<ul>
  <li>Missing alternative representation: Missing alternative representation
    for this object.</li>
  <li>Suspicious alternative representation: Suspicious alternative
    representation for this object: [current alternative representation] -
    [could be placeholder text]</li>
</ul>

<h5><a name="q32">Suggested repair:</a></h5>
<ul>
  <li>Prompt user for new alternative representation.</li>
  <li>If the site contains a document that contains the same object and that
    object contains a valid alternative representation, suggest that
    alternative representation.</li>
</ul>

<h5><a name="q33">Test Files and Discussion Files:</a></h5>

<p><a href="http://www.w3.org/WAI/ER/IG/ert/test11F.htm">Test file - OBJECT
text equivalent.</a></p>

<h4><a name="equivs-for-audio">Technique 1.1.6</a> [priority 1] Verify that
text equivalents are provided for <em>linked</em> audio files where
necessary</h4>

<h5><a name="q35">Evaluation:</a></h5>
<ul>
  <li>Elements: <code>A href=<a
    href="#AppendixD"><em>soundFile</em></a></code></li>
  <li>Requirement: Audio file must be described within the document or
    document must contain a link to a text equivalent file.</li>
</ul>

<h5><a name="q36">Suggested message:</a></h5>
<ul>
  <li>Audio files require a text equivalent. Is there an associated text
    equivalent for this audio file: [audio file name]?</li>
</ul>

<h5><a name="q37">Suggested repair:</a></h5>
<ul>
  <li>Prompt user for text transcript of audio file.</li>
</ul>

<h5><a name="q38">Test Files and Discussion Files:</a></h5>

<p><a href="http://www.w3.org/WAI/ER/IG/ert/test11I.htm">Test file - text for
sound files.</a></p>

<h4><a name="equivs-for-embedded-audio">Technique 1.1.7</a> [priority 1]
Verify that text equivalents are provided for <em>embedded</em> audio files
where necessary</h4>

<h5>Evaluation:</h5>
<ul>
  <li>Elements: <code>OBJECT
  type=<em>Audio_or_Video_MIME_type</em></code></li>
  <li>Requirement: Audio file must be described within the document or
    document must contain a link to a text equivalent file.</li>
</ul>

<h5><a name="q40">Suggested message:</a></h5>
<ul>
  <li>Audio and video files require a text equivalent. Is there an associated
    text equivalent for this audio/video file: [audio/video file name]?</li>
</ul>

<h5><a name="q41">Suggested repair:</a></h5>
<ul>
  <li>Prompt user for text transcript of audio/video file and embed it between
    start and end tag.</li>
</ul>

<h4><a name="frame-for-longdesc">Technique 1.1.8</a> [priority 1] Check
<code>FRAME</code> elements for valid "<code>longdesc</code>" attribute</h4>

<h5><a name="q44">Evaluation:</a></h5>
<ul>
  <li>Element: <code>FRAME</code></li>
  <li>Requirement: Valid "<code>longdesc</code>" attribute (refer to
    checkpoint 12.1 for information about titling frames).</li>
  <li>If a <code>FRAMESET</code> has three or more frames and at least one of
    the frames does not have a "<code>longdesc</code>" attribute, ask the user
    if the relationships between frames are not apparent in the titles for
    each frame.</li>
</ul>

<p>Valid "<code>longdesc</code>" attribute:</p>
<ul>
  <li>Must not be NULL</li>
  <li>Must be a valid URI</li>
  <li>The file pointed to by the URI must be accessible HTML</li>
</ul>

<h5><a name="q45">Suggested message:</a></h5>
<ul>
  <li>Missing "<code>longdesc</code>": Missing description for this
  frame.</li>
  <li>Invalid "<code>longdesc</code>" URI: Invalid 'long description' file
    name for this frameset: [current "<code>longdesc</code>" URI] - [can not
    be empty].</li>
</ul>

<h5><a name="q46">Suggested repair:</a></h5>
<ul>
  <li>If the relationships between frames are not obvious then ask that they
    provide a description of the relationships. Allow the user to create a
    "<code>longdesc</code>" file or associate an existing
    "<code>longdesc</code>" file. It is suggested that each <code>FRAME</code>
    in the reference the same "<code>longdesc</code>" as the description of
    the relationships should be available from each <code>FRAME</code>.</li>
</ul>

<h5><a name="q47">Test Files and Discussion Files:</a></h5>
<ul>
  <li><a href="http://www.w3.org/WAI/ER/IG/ert/test11G.htm">Test file -
    longdesc for FRAMEs.</a></li>
</ul>

<h4><a name="area-for-alt">Technique 1.1.9</a> [priority 1] Check
<code>AREA</code> elements for valid "<code>alt</code>" attribute</h4>

<h5><a name="q49">Evaluation:</a></h5>
<ul>
  <li>Element:<code>AREA</code></li>
  <li>Requirement: Elements must have a valid "<code>alt</code>"
  attribute.</li>
</ul>

<p>Valid "<code>alt</code>" attribute:</p>
<ul>
  <li>Not allowed - NULL "<code>alt</code>" value (<code>alt=""</code>)</li>
  <li>Suspicious - "<code>alt</code>" attribute value is <a
    href="#AppendixA">placeholder text</a>.</li>
  <li>@@is this complete?</li>
</ul>

<h5><a name="q50">Suggested message:</a></h5>
<ul>
  <li>Missing text equivalent: Missing text equivalent for this image map
    area.</li>
  <li>Suspicious "<code>alt</code>": Suspicious "<code>alt</code>" attribute
    for this image map area: [current alt text].</li>
</ul>

<h5><a name="q51">Suggested repair:</a></h5>

<p>Prompt user for "<code>alt</code>" text for the <code>AREA</code>
element.</p>

<h5><a name="q52">Test Files and Discussion Files:</a></h5>
<ul>
  <li><a href="http://www.w3.org/WAI/ER/IG/ert/test11H.htm">Test file - alt on
    AREA.</a></li>
</ul>

<h4><a name="script-for-equiv">Technique 1.1.10</a> [priority 1] Check
<code>SCRIPT</code> elements for valid equivalents where necessary</h4>

<h5><a name="q54">Evaluation:</a></h5>
<ul>
  <li>Element: <code>SCRIPT</code></li>
  <li>Requirements:
    <ul>
      <li><code>NOSCRIPT</code> section must follow the <code>SCRIPT</code>
        end element AND</li>
      <li><code>NOSCRIPT</code> section must contain Accessible HTML</li>
      <li><code>NOSCRIPT</code> section must not contain <a
        href="#AppendixE">placeholder text</a></li>
    </ul>
  </li>
</ul>

<h5>Suggested message:</h5>
<ul>
  <li>Language for missing <code>NOSCRIPT</code>: Missing
    <code>NOSCRIPT</code> element for this <code>SCRIPT</code> element.</li>
  <li>If contained HTML not accessible: <code>NOSCRIPT</code> section contains
    inaccessible HTML: [description of problems].</li>
</ul>

<h5><a name="q55">Suggested repair:</a></h5>
<ul>
  <li>Insert <code>NOSCRIPT</code> section</li>
  <li>Allow user to insert text or link to text equivalent file that describes
    the <code>SCRIPT</code></li>
</ul>

<h5><a name="q56">Test Files and Discussion Files:</a></h5>
<ul>
  <li><a href="http://www.w3.org/WAI/ER/IG/ert/test11J.htm">Test file - text
    for SCRIPT.</a></li>
</ul>

<h4><a name="A-for-text">Technique 1.1.11 [priority 1] Check <code>A
</code>elements for valid text content</a></h4>

<p>@@handled by technique 13.1.1 - verify that targets are clearly identified?
What else do we need to check for?</p>

<h4><a name="ascii-equiv">Technique 1.1.12</a> [priority 1] Verify that valid
text equivalents are provided for <code>PRE</code> and <code>XMP</code>
elements used to create ASCII art.</h4>

<h5>Open issues for this technique:</h5>
<ul>
  <li>A-Prompt has been using an algorithm to detect ASCII art (There must be
    5 or more lines of text and there must be 5 or more same characters in a
    sequence). This works quite well but detects things such as code samples
    (don't require text equiv.) and guitar tabulature (do require text equiv.)
    Should we suggest this algorithm in the evaluation?</li>
  <li>What about ASCII art that is interspersed in text, such as in
    <code>P</code> elements?</li>
  <li>Bill Shackleton suggested that a tool use a library of well-known ascii
    art to detect some ascii art such as emoticons. <a
    href="http://dir.yahoo.com/Arts/Visual_Arts/Computer_Generated/ASCII_Art/">Yahoo
    maintains a list of ascii art</a> one list is specifically about <a
    href="http://dir.yahoo.com/Arts/Visual_Arts/Computer_Generated/ASCII_Art/Smileys/">smileys</a>.</li>
</ul>

<h5><a name="q59">Evaluation:</a></h5>
<ul>
  <li>Elements: <code>PRE</code> and <code>XMP</code></li>
  <li>Requirement: ASCII art has an associated text equivalent.</li>
</ul>

<h5><a name="q60">Suggested message:</a></h5>
<ul>
  <li>Character based artwork (ASCII art) requires a textual description.</li>
</ul>

<h5><a name="q61">Suggested repair:</a></h5>
<ul>
  <li>Ask user for a description of the ASCII art or allow them to add a link
    to a text equivalent file.</li>
</ul>

<h5><a name="q62">Test Files and Discussion Files:</a></h5>
<ul>
  <!-- <li><a href="http://www.w3.org/WAI/ER/IG/ert/test11K.htm">Link to test files
  for this technique.</a></li> -->
  <li><a href="http://www.w3.org/WAI/ER/IG/ert/AsciiArt.htm">ASCII Art
    Discussion Page</a> - Yun Jo.</li>
</ul>
<hr title="Separator from Checkpoint 1.1">

<h3><a name="redundant-server-links">Checkpoint 1.2 - Provide redundant text
links for each active region of a server-side image map</a></h3>

<h4><a name="links-for-server-side">Technique 1.2.1</a> [priority 1] Verify
that a server-side image map has associated text links.</h4>

<h5>Open issues for this technique:</h5>
<ul>
  <li>WCAG issue: text links are a priority 3 if the same image also has a
    client side map (images can have both a client-side and a
  server-side).</li>
</ul>

<h5><a name="q65">Evaluation:</a></h5>
<ul>
  <li>Element: <code>IMG ISMAP</code></li>
  <li>Requirement: text link for each active area of the image map</li>
</ul>

<h5><a name="q66">Suggested message:</a></h5>
<ul>
  <li>Server-side image maps should have associated text links in the
    document.</li>
</ul>

<h5><a name="q67">Suggested repair:</a></h5>
<ul>
  <li>Prompt the user for associated text links OR</li>
  <li>help the user convert the server-side image map to a client-side image
    map and provide text-equivalents for each link in the client-side image
    map.</li>
  <li>If possible, check the text links against the links contained on the
    server-side image map by
    <ul>
      <li>asking user to upload the server side definition file if it's a
        standard format or</li>
      <li>pinging the image map with random coordinates and seeing if all
        returned pages correspond to the links.</li>
    </ul>
  </li>
</ul>

<h5><a name="q68">Test Files and Discussion Files:</a></h5>
<ul>
  <li><a href="http://www.w3.org/WAI/ER/IG/ert/test12A.htm">Test file -
    server-side image map links.</a></li>
</ul>
<hr title="Separator from Checkpoint 1.2">

<h3><a name="auditory-descriptions">Checkpoint 1.3 - Until user agents can
automatically read aloud the text equivalent of a visual track, provide an
auditory description of the important information of the visual track of a
multimedia presentation</a></h3>

<h4><a name="audio-descript-for-multimedia">Technique 1.3.1</a> [priority 1]
Verify that multimedia have audio descriptions.</h4>

<h5><a name="q71">Evaluation:</a></h5>
<ul>
  <li>Elements:
    <ul>
      <li><em><code>any_tag</code></em><em><code>
        any_attribute=multimedia_uri</code></em><code>,</code></li>
      <li><code>OBJECT
      type=</code><em><code>any_multimedia_type</code></em></li>
    </ul>
  </li>
  <li>Requirement: Multimedia presentations should have an associated audio
    description.</li>
</ul>

<h5><a name="q72">Suggested repair:</a></h5>
<ul>
  <li>Display the multimedia file and allow the user to create an audio
    description of the important information.</li>
  <li>Allow the user to add a link to an existing audio description file.</li>
</ul>
<hr>

<h3><a name="av-in-dynamic-objects">Checkpoint 1.4</a> - For any time-based
multimedia presentation (e.g., a movie or animation), synchronize equivalent
alternatives (e.g., captions or auditory descriptions of the visual track)
with the presentation</h3>

<h4><a name="synch-equiv-for-multimedia">Technique 1.4.1</a> [priority 1]
Verify that multimedia have synchronized equivalents.</h4>

<h5><a name="q76">Evaluation:</a></h5>
<ul>
  <li>Elements:
    <ul>
      <li><em><code>any_tag any_attribute=multimedia_uri</code></em>,</li>
      <li><code>OBJECT
      type=</code><em><code>any_multimedia_type</code></em></li>
    </ul>
  </li>
  <li>Requirement: Multimedia presentations should have synchronized
    equivalents.</li>
</ul>

<h5><a name="q77">Suggested message:</a></h5>
<ul>
  <li>For any time-based multimedia presentation (e.g., a movie or animation),
    synchronize equivalent alternatives</li>
</ul>

<h5><a name="q78">Suggested repair:</a></h5>
<ul>
  <li>Give user option to edit option with editor of their choice (e.g. the
    default editor on their system)</li>
</ul>

<h4><a name="synch-smil">Technique 1.4.2 [priority 1] Check SMIL files for
synchronized media</a></h4>

<h5>Open issues for this technique:</h5>
<ul>
  <li>This technique is a specific example of 1.4.1.  Should it stand on its
    own or be incorporated into 1.4.1?</li>
  <li>This technique is also SMIL specific while the majority of techniques
    are HTML specific.  Should we include a SMIL specific technique?</li>
</ul>

<h5><a name="q81">Evaluation:</a></h5>
<ul>
  <li>SMIL Elements:</li>
  <li>Requirement: SMIL files should have the <code>system-captions</code>
    flag for at least one text stream and one auditory stream.</li>
</ul>
<hr title="Separator from Checkpoint 1.4">

<h3><a name="client-side">Checkpoint 1.5</a> - Until user agents render text
equivalents for client-side image map links, provide redundant text links for
each active region of a client-side image map</h3>

<h4><a name="links-for-client-side">Technique 1.5.1</a> [priority 3] Verify
that text links are provided for client-side image maps.</h4>

<h5><a name="q87">Evaluation:</a></h5>
<ul>
  <li>Element: <code>IMG usemap</code></li>
  <li>Requirement: Document must contain text links for each active area of
    the image map.</li>
  <li>Associated text links may be found by searching the document for anchors
    with <code>href</code> attribute values that correspond to the
    <code>AREA</code> elements in the given <code>usemap</code>.</li>
</ul>

<h5><a name="q88">Suggested message:</a></h5>
<ul>
  <li>Client-side image maps should have associated text links.</li>
</ul>

<h5><a name="q89">Suggested repair:</a></h5>
<ul>
  <li>Allow the user to create associated text links for each active area in
    the image map.</li>
</ul>

<h5><a name="q90">Test Files and Discussion Files:</a></h5>
<ul>
  <li><a href="http://www.w3.org/WAI/ER/IG/ert/test15A.htm">Test file -
    client-side image map links.</a></li>
</ul>
<hr title="Separator from Checkpoint 1.5">

<h2><a name="color">Guideline 2</a>. Don't rely on color alone.</h2>
<ul>
  <li><a href="#color-convey">Checkpoint 2.1</a> - Ensure that all information
    conveyed with color is also available without color, for example from
    context or markup</li>
  <li><a href="#color-contrast">Checkpoint 2.2</a> - Ensure that foreground
    and background color combinations provide sufficient contrast when viewed
    by someone having color deficits or when viewed on a black and white
    screen</li>
</ul>
<hr>

<h3><a name="color-convey">Checkpoint 2.1</a> - Ensure that all information
conveyed with color is also available without color, for example from context
or markup</h3>

<h4><a name="without-color">Technique 2.1.1</a> [priority 1] Verify that
information conveyed with color is available without color</h4>

<h5><a name="q94">Evaluation:</a></h5>
<ul>
  <li>Elements: <code>IMG | </code><code>APPLET | </code><code>OBJECT |
    </code><code>SCRIPT | </code><code>INPUT | </code>as well as the HTML
    elements and attributes listed in the next technique (2.2.1).</li>
</ul>

<h5><a name="q95">Suggested message:</a></h5>
<ul>
  <li>Ensure that information is not conveyed through color alone. For
    example, when asking for input from users, do not write "Please select an
    item from those listed in green." Instead, ensure that information is
    available through other style effects (e.g., a font effect) and through
    context (e.g,. comprehensive text links).</li>
</ul>

<h5><a name="q96">Suggested repair:</a></h5>
<ul>
  <li>Display a user notification if any of the color-possible elements are in
    the document.</li>
</ul>
<hr title="Separator from Checkpoint 2.1">

<h3><a name="color-contrast">Checkpoint 2.2</a> - Ensure that foreground and
background color combinations provide sufficient contrast when viewed by
someone having color deficits or when viewed on a black and white screen</h3>

<h4><a name="test-color-contrast">Technique 2.2.1</a> [priority 3] Test the
color attributes of the following elements for visibility:</h4>

<h5><a name="q100">Evaluation:</a></h5>
<ul>
  <li>Elements:
    <ul>
      <li><code>BODY bgcolor | text | alink | link | vlink | background
        =</code><em><code>anything</code></em><code>  OR</code></li>
      <li><code>TABLE bordercolor | bgcolor
        =</code><em><code>anything</code></em><code>  OR</code></li>
      <li><code>TD | TH    bgcolor
        =</code><em><code>anything</code></em><code>  OR</code></li>
      <li><code>HR color =</code><em><code>anything</code></em><code>
        OR</code></li>
      <li><em><code>any_element</code></em><code>
        style="</code><em><code>any_color_specification</code></em><code>"</code></li>
      <li><code>STYLE <em>"any_color_specification"...</em> STYLE</code></li>
      <li>Where <em>any_color_specification</em> is defined as any CSS
        specification which contains:

        <blockquote>
          <code>color | background-color | background-image |
          background</code></blockquote>
      </li>
    </ul>
  </li>
  <li>Requirement: Determine color visibility.@@needs work?</li>
</ul>

<p>Ideally, images and multimedia object should also be tested for color
visibility but algorithms are beyond the scope of this specification.</p>

<p>Color visibility can be determined according to the following
algorithm:</p>

<p><strong>(This is a suggested algorithm that is still open to
change.)</strong></p>

<p>Two colors provide good color visibility if the brightness difference and
the color difference between the two colors are greater than a set range.</p>

<p>Color brightness is determined by the following formula:<br>
((Red value X 299) + (Green value X 587) + (Blue value X 114)) / 1000<br>
Note: This algorithm is taken from a formula for converting RGB values to YIQ
values. This brightness value gives a perceived brightness for a color.</p>

<p>Color difference is determined by the following formula:<br>
(maximum (Red value 1, Red value 2) - minimum (Red value 1, Red value 2)) +
(maximum (Green value 1, Green value 2) - minimum (Green value 1, Green value
2)) + (maximum (Blue value 1, Blue value 2) - minimum (Blue value 1, Blue
value 2))</p>

<p>The rage for color brightness difference is 125. The range for color
difference is 500.</p>

<h5><a name="q101">Suggested message:</a></h5>
<ul>
  <li>Poor visibility between text and background colors.</li>
</ul>

<h5><a name="q102">Suggested repair:</a></h5>
<ul>
  <li>Allow the user to change the poor color combinations.</li>
  <li>Store any good color combinations entered by the user and use them as
    default prompts in the future.</li>
</ul>

<h5><a name="q103">Test Files and Discussion Files:</a></h5>
<ul>
  <li><a href="http://www.w3.org/WAI/ER/IG/ert/test22A.htm">Test file - color
    contrast.</a></li>
</ul>
<hr title="Separator from Checkpoint 1.2">

<h2><a name="structure-presentation">Guideline 3</a>. Use markup and style
sheets and do so properly</h2>
<ul>
  <li><a href="#text-markup">Checkpoint 3.1</a> - When an appropriate markup
    language exists, use markup rather than images to convey information</li>
  <li><a href="#document">Checkpoint 3.2</a> - Create documents that validate
    to published formal grammars</li>
  <li><a href="#use-stylesheets">Checkpoint 3.3</a> - Use style sheets to
    control layout and presentation</li>
  <li><a href="#relative-units">Checkpoint 3.4</a> - Use relative rather than
    absolute units in markup language attribute values and style sheet
    property values</li>
  <li><a href="#logical-heading">Checkpoint 3.5</a> - Use header elements to
    convey document structure and use them according to specification</li>
  <li><a href="#list-structure">Checkpoint 3.6</a> - Mark up lists and list
    items properly</li>
  <li><a href="#quotes">Checkpoint 3.7</a> - Mark up quotations. Do not use
    quotation markup for formatting effects such as indentation</li>
</ul>
<hr>

<h3><a name="text-markup">Checkpoint 3.1</a> - When an appropriate markup
language exists, use markup rather than images to convey information</h3>

<h4><a name="convert-to-markup">Technique 3.1.1</a> [priority 2] Verify that
elements do not need to be converted to an appropriate markup language.</h4>

<h5><a name="q107">Evaluation:</a></h5>
<ul>
  <li>Elements: <code>PRE | IMG | OBJECT | APPLET</code></li>
</ul>

<h5><a name="q108">Suggested message:</a></h5>
<ul>
  <li>When an appropriate markup language exists, use markup rather than
    images to convey information. For example, use MathML to mark up
    mathematical equations, and style sheets to format text and control
  layout</li>
  <li></li>
</ul>

<h5><a name="q109">Suggested repair:</a></h5>
<ul>
  <li>Display a user notification if any of these possible conversion elements
    are in the document.</li>
  <li>Help authors convert decorative ASCII art in <code>PRE</code> elements
    to SVG or an image format.</li>
  <li>Help authors convert ASCII art representing tables of data in PRE
    elements to TABLE elements.</li>
  <li>Help authors convert images (<code>IMG</code> or <code>OBJECT</code>)
    used to format text to XHTML/XML with style sheets.</li>
  <li>Help authors convert images (<code>IMG</code> or <code>OBJECT</code>)
    used to format mathematical equations to MathML.</li>
</ul>
<hr title="Separator from Checkpoint 3.1">

<h3><a name="document">Checkpoint 3.2</a> - Create documents that validate to
published formal grammars</h3>

<h4><a name="public-text-id">Technique 3.2.1</a> [priority 2] Check document
for public text identifier</h4>

<h5><a name="q112">Open issues for this technique:</a></h5>
<ul>
  <li>Reference BizTalk and OASIS catalogs?</li>
</ul>

<h5><a name="q113">Evaluation:</a></h5>
<ul>
  <li>Element: none  (i.e. applies to all documents)</li>
  <li>Requirements:
    <ul>
      <li>Document must contain a <code>!DOCTYPE ... </code>declaration</li>
      <li>Document type must conform to the <a
        href="http://www.w3.org/TR/html4/struct/global.html">HTML
        specification</a> and the <a
        href="http://validator.w3.org/sgml-lib/catalog">list of public text
        identifiers</a></li>
    </ul>
  </li>
</ul>

<h5><a name="q114">Suggested message:</a></h5>
<ul>
  <li>If no <code>!DOCTYPE</code> at all: Missing language identifier for this
    document.</li>
  <li>If document type is defined in HTML element: "Document type should be in
    the document type definition.  It's use in the HTML element is
  deprecated.</li>
</ul>

<h5><a name="q115">Suggested repair:</a></h5>
<ul>
  <li>If the document type is in the HTML element: move to the
    <code>!DOCTYPE</code> declaration.</li>
  <li>If no valid document type at all: Prompt the user for a public text
    identifier, preferably by offering a menu of choices and explanations</li>
</ul>

<h5><a>Test Files and Discussion Files:</a></h5>
<ul>
  <li><a href="http://www.w3.org/WAI/ER/IG/ert/test32A.htm">Test file - public
    text identifier.</a></li>
</ul>
<hr title="Separator from Checkpoint 3.2">

<h3><a name="use-stylesheets">Checkpoint 3.3</a> - Use style sheets to control
layout and presentation</h3>

<h4><a name="check-for-ss">Technique 3.3.1</a> [priority 2] Check document for
use of style sheets.</h4>

<h5><a name="q119">Evaluation:</a></h5>
<ul>
  <li>Elements: none (i.e. applies to all documents)</li>
  <li>Requirements: Document should contain at least one of the
    following:<code>STYLE</code> or <code>LINK rel="stylesheet"</code>
    elements within the <code>HEAD</code> element | "<code>style</code>"
    attributes on any element | <code>FONT</code> | <code>BASEFONT</code> |
    <code>"text," "vlink," "link," and "alink"</code> attributes on
    <code>BODY</code>.</li>
  <li>If layout tables are identified (see technique 5.1.1), trigger this
    check as well. We will inform user that style sheets can be used instead
    of layout tables in 5.1.1.</li>
</ul>

<h5><a name="q120">Suggested message:</a></h5>
<ul>
  <li>Use style sheets to control layout and presentation. For example, use
    the CSS '<code>font</code>' property instead of the HTML <code>FONT</code>
    and <code>BASEFONT</code> elements to control font styles</li>
</ul>

<h5><a name="q121">Suggested repair:</a></h5>
<ul>
  <li>If style sheets are not used, verify that the author has chosen not to
    modify the presentation in any way.</li>
  <li>If <code>FONT</code> or <code>BASEFONT</code> elements or <code>"text,"
    "vlink," "link," and "alink"</code> attributes on <code>BODY</code>,
    suggest or help the author convert the presentation properties to style
    sheets.</li>
  <li>If the author chooses to convert deprecated markup to style sheets or
    add style sheets, trigger technique 6.1 to verify that the document is
    readable when style sheets are not applied.</li>
</ul>
<hr title="Separator from Checkpoint 3.3">

<h3><a name="relative-units">Checkpoint 3.4</a> - Use relative rather than
absolute units in markup language attribute values and style sheet property
values</h3>

<h4><a name="check-relative-units">Technique 3.4.1</a> [priority 2] Check
document for relative units of measure.</h4>

<h5><a name="q124">Evaluation:</a></h5>
<ul>
  <li>Elements:
    <ul>
      <li>"<code>style</code>" attribute on any element OR</li>
      <li><code>STYLE</code></li>
    </ul>
  </li>
  <li>Requirements For any HTML or CSS element defined to take a
    <code>%LENGTH, %PIXELS, %MULTILENGTH</code>, or
    <code>%MULTILENGTHS</code>,  a validated value should either end with "%"
    or begin with "+" or "-" or use the "em" or "ex" units.</li>
  <li>Exception: "<code>width</code>" and "<code>height</code>" attributes of
    <code>IMG, OBJECT, and APPLET</code> elements.</li>
</ul>

<h5><a name="q125">Suggested message:</a></h5>
<ul>
  <li>This element uses absolute units of measure rather than relative units
    of measure.</li>
</ul>

<h5><a name="q126">Suggested repair:</a></h5>
<ul>
  <li>Allow user to change the units of measure as follows:
    <ol>
      <li>Allow user to specify which of the absolute sizes is the
      default</li>
      <li>Automatically compute all others in terms of the default, with
        choice of %, +/-, or em/ex  </li>
    </ol>
  </li>
</ul>
<hr title="Separator from Checkpoint 3.4">

<h3><a name="logical-heading">Checkpoint 3.5</a> - Use header elements to
convey document structure and use them according to specification</h3>

<h4><a name="header-nesting">Technique 3.5.1</a> [priority 2] Check document
for header nesting</h4>

<h5><a name="q130">Evaluation:</a></h5>
<ul>
  <li>Elements: <code>Header</code> elements (H1-H6)</li>
</ul>
<ul>
  <li>Requirements: Header elements should nest according to the following
    rules
    <ol>
      <li>Header levels must not increase by more than 1 level. Example: H2
        following H1 is good. H3 following H1 is bad.</li>
      <li>Header elements can decrease by any level. Example: H2 following H5
        is OK.</li>
    </ol>
  </li>
</ul>

<h5><a name="q131">Suggested message:</a></h5>
<ul>
  <li>Improper header nesting: Header levels must not increase by more than
    one level per heading. Do not use headings to create font effects; use
    style sheets to change font styles.</li>
</ul>

<h5><a name="q132">Suggested repair:</a></h5>
<ul>
  <li>Allow user to modify the header numbering within the document.</li>
</ul>

<h5><a name="q133">Test Files and Discussion Files:</a></h5>
<ul>
  <li><a href="http://www.w3.org/WAI/ER/IG/ert/test35A.htm">Test file - header
    nesting.</a></li>
</ul>

<h4><a name="missing-header">Technique 3.5.2</a> [priority 2] Check document
for missing header markup</h4>

<h5><a name="q135">Evaluation:</a></h5>
<ul>
  <li>Element:<code>P</code></li>
  <li>Requirement: Paragraphs should be verified that they are not headings.
    Potential headings can be identified by:
    <ol>
      <li>Text elements occur within a paragraph AND</li>
      <li>The paragraph is less than 10 words AND</li>
      <li>The paragraph contains only text items or formatting elements
      AND</li>
      <li>All text in the paragraph is formatted as bold and/or italics and/or
        underline.</li>
    </ol>
  </li>
</ul>

<h5><a name="q136">Suggested message:</a></h5>
<ul>
  <li>Text has been identified that could possibly be a header. Is this text
    used as a header: [potential header text]?</li>
</ul>

<h5><a name="q137">Suggested repair:</a></h5>
<ul>
  <li>Allow user to convert the text to a header.</li>
</ul>

<h5><a name="q138">Test Files and Discussion Files:</a></h5>
<ul>
  <li><a href="http://www.w3.org/WAI/ER/IG/ert/test35B.htm">Test file - header
    markup.</a></li>
</ul>

<h4><a name="headers-not-formatting">Technique 3.5.3</a> [priority 2] Verify
that header elements are not used for formatting.</h4>

<h5><a name="q140">Evaluation:</a></h5>
<ul>
  <li>Elements: <code>Header</code> elements (H1- H6)</li>
  <li>Requirement: If a header element's text content is longer than 20 words,
    query the user.</li>
</ul>

<h5><a name="q141">Suggested message:</a></h5>
<ul>
  <li>Header elements (H1 - H6) should be used to define headers and should
    not be used for formatting text.</li>
</ul>

<h5><a name="q142">Suggested repair:</a></h5>
<ul>
  <li>Allow the user to convert any header text to another type. Possible
    types are:
    <ol>
      <li>Paragraph</li>
      <li>Blockquote</li>
    </ol>
  </li>
</ul>
<hr title="Separator from Checkpoint 3.5">

<h3><a name="list-structure">Checkpoint 3.6</a> - Mark up lists and list items
properly</h3>

<h4><a name="lists-nested">Technique 3.6.1 [priority 2] Check that list
elements are within a list container and well nested.</a></h4>

<h5><a name="q145">Evaluation:</a></h5>
<ul>
  <li>Elements:
    <ul>
      <li><code>UL</code></li>
      <li><code>OL</code></li>
      <li><code>DL</code></li>
    </ul>
  </li>
  <li>Requirements
    <ul>
      <li>Each <code>UL/OL/DL</code> tag must be followed by at least one
        <code>LI</code>. (This avoids the use of lists to create formatting
        e.g. via <code>UL UL UL... </code>)</li>
      <li>Suspicious: a single <code>LI</code>, which may be used merely for
        formatting</li>
    </ul>
  </li>
</ul>

<h5><a name="q146">Suggested message:</a></h5>
<ul>
  <li>List items should not be used for formatting text. Use Style sheets or
    tables for formatting text.</li>
</ul>

<h5><a name="q147">Suggested repair:</a></h5>
<ul>
  <li>Allow the user to format the text within the LI element to another
    element via  a choice of
    <ul>
      <li>Style sheets OR</li>
      <li>Tables  </li>
    </ul>
  </li>
</ul>
<!-- <h5><a name="q148">Test Files and Discussion Files:</a></h5>
<ul>
<li><a href="http://www.w3.org/WAI/ER/IG/ert/issues36.htm">Link to
discussion on this technique.</a></li>
</ul> -->
<hr title="Separator from Checkpoint 3.6">

<h3><a name="quotes">Checkpoint 3.7</a> - Mark up quotations. Do not use
quotation markup for formatting effects such as indentation</h3>

<h4><a name="missing-quotes">Technique 3.7.1</a> [priority 2] Verify instances
where quote markup should be used.</h4>

<h5><a name="q151">Discussion Status:</a></h5>
<ul>
  <li><code>Q</code> is not supported in today's browsers, thus converting
    quotes marks to <code>Q</code> will basically delete the quote marks for
    all users. what do we suggest in the meantime?</li>
</ul>

<h5><a name="q152">Evaluation:</a></h5>
<ul>
  <li>Element: <code>P</code> [list of others?] elements</li>
  <li>Requirement: quote should be marked up with <code>Q</code> or
    <code>BLOCKQUOTE</code>. Potential quotes can be identified by:
    <ol>
      <li>Any text that is enclosed by quote marks (" " or ' ').</li>
      <li>Indented text.</li>
      <li>Lots of emphasized text (greater than x words??@@)</li>
    </ol>
  </li>
</ul>

<h5><a name="q153">Suggested message:</a></h5>
<ul>
  <li>The following text may need to be marked using <code>Q</code> or
    <code>BLOCKQUOTE</code>: [potential quote text].</li>
</ul>

<h5><a name="q154">Suggested repair:</a></h5>
<ul>
  <li>Allow the user to convert blocks of text to <code>Q</code> or
    <code>BLOCKQUOTE</code>.</li>
</ul>

<h5><a name="q155">Test Files and Discussion Files:</a></h5>
<ul>
  <li><a href="http://www.w3.org/WAI/ER/IG/ert/test37A.htm">Test file  - quote
    markup.</a></li>
</ul>

<h4><a name="proper-quotes">Technique 3.7.2</a> [priority 2] Verify that
<code>Q</code> and <code>BLOCKQUOTE</code> are used properly</h4>

<h5><a name="q157">Evaluation:</a></h5>
<ul>
  <li>Elements: <code>Q</code> and <code>BLOCKQUOTE</code></li>
  <li>Requirement:
    <ul>
      <li>Inline quotes (marked with <code>Q</code>) have at least one word in
        front of, or behind, the quote text and are less than 10 words</li>
      <li>Long quotes (marked with <code>BLOCKQUOTE</code>) are greater than
        10 words.</li>
    </ul>
  </li>
</ul>

<h5><a name="q158">Suggested message:</a></h5>
<ul>
  <li>If a block of text is marked as <code>BLOCKQUOTE</code> when it should
    be marked as <code>Q</code>: This text should be marked as <code>Q</code>
    not <code>BLOCKQUOTE</code>: [quote text].</li>
  <li>If a block of text is marked as <code>Q</code> when it should be marked
    as <code>BLOCKQUOTE</code>: This text should be marked as
    <code>BLOCKQUOTE</code> not <code>Q</code>: [quote text].</li>
</ul>

<h5><a name="q159">Suggested repair:</a></h5>
<ul>
  <li>Allow the user to convert blocks of text to <code>Q</code> or
    <code>BLOCKQUOTE </code>or vice versa.</li>
</ul>
<!-- <h5><a name="q160">Test Files and Discussion Files:</a></h5>
<ul>
<li><a href="http://www.w3.org/WAI/ER/IG/ert/test37B.htm">Link to test file
for this technique.</a></li>
</ul> -->

<h4><a name="blockquote-format">Technique 3.7.3</a> [priority 2] Verify that
<code>BLOCKQUOTE</code> is not used for formatting</h4>

<h5><a name="q162">Evaluation:</a></h5>
<ul>
  <li>Element: <code>BLOCKQUOTE</code> unless text content has quote marks (""
    or '').</li>
  <li>Requirement:
    <ul>
      <li>Not allowed: nested <code>BLOCKQUOTE</code>s.</li>
    </ul>
  </li>
</ul>

<h5><a name="q163">Suggested message:</a></h5>
<ul>
  <li>This text should be marked as normal text but formatted using style
    sheets or a table.</li>
  <li><code>BLOCKQUOTE</code>elements should be used to define quotes and
    should not be used for formatting text.</li>
</ul>

<h5><a name="q164">Suggested repair:</a></h5>
<ul>
  <li>Allow the user to transform the text in the <code>BLOCKQUOTE</code>
    element into a <code>P</code> (paragraph) element.</li>
</ul>
<hr title="Separator from Checkpoint 3.7">

<h2><a name="abbreviated-and-foreign">Guideline 4</a>. <a
href="http://www.w3.org/TR/WAI-WEBCONTENT/#gl-abbreviated-and-foreign">Clarify
natural language usage</a></h2>
<ul>
  <li><a href="#language">Checkpoint 4.1</a> - Clearly identify changes in the
    natural language of a document's text and any text equivalents (e.g.,
    captions)</li>
  <li><a href="#expand-abbr">Checkpoint 4.2</a> - Specify the expansion of
    each abbreviation or acronym in a document where it first occurs</li>
  <li><a href="#identify-lang">Checkpoint 4.3</a> - Identify the primary
    natural language of a document</li>
</ul>
<hr>

<h3><a name="language">Checkpoint 4.1</a> - Clearly identify changes in the
natural language of a document's text and any text equivalents (e.g.,
captions)</h3>

<h4><a name="lang-changes" id="Technique4.1.A">Technique 4.1.1 [priority 1]
Verify changes in the natural language of document.</a></h4>

<h5><a name="q168">Evaluation:</a></h5>
<ul>
  <li>Element: none (i.e. applies to all documents that contain text)</li>
  <li>Requirement: The document must contain at least 3 words of text.</li>
</ul>

<h5><a name="q169">Suggested message:</a></h5>
<ul>
  <li>Any words or phrases in a document that are not in the primary language
    of the document should be identified.</li>
</ul>

<h5><a name="q170">Suggested repair:</a></h5>
<ul>
  <li>Display the above user notification and provide the following
    suggestions:
    <ul>
      <li>For blocks of text that are not in the primary language and are
        already enclosed by markup elements such as <code>P</code>aragraph,
        <code>DIV </code>or <code>EM</code>, set the "<code>lang</code>"
        attribute of the markup element.</li>
      <li>For words or phrases that are not in the primary language, enclose
        them with a <code>SPAN</code> element and set the <code>SPAN</code>
        element's "<code>lang</code>" attribute.</li>
      <li>Ensure that all captions and other text equivalents are
      checked.</li>
    </ul>
  </li>
</ul>

<h5><a name="q171">Test Files and Discussion Files:</a></h5>
<hr title="Separator from Checkpoint 4.1">

<h3><a name="expand-abbr">Checkpoint 4.2</a> - Specify the expansion of each
abbreviation or acronym in a document where it first occurs</h3>

<h4><a name="abbr-expanding">Technique 4.2.1</a> [priority 3] Verify that
abbreviations and acronyms need expanding.</h4>

<h5><a name="q174">Evaluation:</a></h5>
<ul>
  <li>Elements: none (i.e. applies to all documents that contain text)</li>
  <li>Requirements:
    <ul>
      <li>Document must contain at least 3 words.</li>
      <li>Document contains a potential abbreviation or acronym.</li>
    </ul>
  </li>
</ul>

<p>Potential abbreviation:</p>
<ul>
  <li>Any word greater than 2 characters that is all capital letters</li>
</ul>

<p>Potential acronym:</p>
<ul>
  <li>Any word that starts with a capital letter, contains lower case
    characters and ends with a period.</li>
</ul>

<h5><a name="q175">Suggested message:</a></h5>
<ul>
  <li>A potential acronym/abbreviation has been discovered: [potential
    acronym/abbreviation].</li>
</ul>

<h5><a name="q176">Suggested repair:</a></h5>
<ul>
  <li>Ask the user if the acronym or abbreviation was defined elsewhere on the
    page and if so give the user the option to re-use it.</li>
  <li>Allow the user to enter a definition for the abbreviation of
  acronym.</li>
</ul>
<!-- <h5><a name="q177">Test Files and Discussion Files:</a></h5>
<ul>
<li><a href="http://www.w3.org/WAI/ER/IG/ert/issues42A.htm">Link to
discussion file for this technique.</a></li>
</ul> -->
<hr title="Separator from Checkpoint 4.2">

<h3><a name="identify-lang">Checkpoint 4.3</a> - Identify the primary natural
language of a document</h3>

<h4><a name="primary-lang">Technique 4.3.1</a> [priority 3] Verify the primary
language of the document</h4>

<h5><a name="q180">Evaluation:</a></h5>
<ul>
  <li>Element: <code>HTML</code></li>
  <li>Requirements: Must contain a valid "<code>lang</code>" attribute</li>
</ul>

<p>Valid "<code>lang</code>" attribute:</p>
<ul>
  <li>Must be one of the <a
    href="http://www.w3.org/WAI/ER/IG/ert/iso639.htm">ISO 639 language
    codes</a>.</li>
</ul>

<h5><a name="q181">Suggested message:</a></h5>
<ul>
  <li>Missing "<code>lang</code>" attribute: The primary language of this
    document has not been set.</li>
  <li>Invalid "<code>lang</code>" attribute: The primary language of this
    document is invalid.</li>
</ul>

<h5><a name="q182">Suggested repair:</a></h5>
<ul>
  <li>Prompt the user for the primary language of the document.</li>
  <li>Ensure that the language entered is one of the <a
    href="http://www.w3.org/WAI/ER/IG/ert/iso639.htm">ISO 639 language
    codes</a>.</li>
  <li>A (somewhat costly) technique for guessing the primary language, is to
    check for the use of common words in a language. For example, if  you find
    "a, the, you, for, is, of, and" then it's English. If you find "le, du,
    la, a, se, pour, aux, des, ne" then it's French, etc.</li>
</ul>

<h5><a name="q183">Test Files and Discussion Files:</a></h5>
<ul>
  <li><a href="http://www.w3.org/WAI/ER/IG/ert/test43A.htm">Test file  -
    primary language.</a></li>
</ul>
<hr title="Separator from Checkpoint 4.3">

<h2><a name="table-markup">Guideline 5</a>. <a
href="http://www.w3.org/TR/WAI-WEBCONTENT/#gl-table-markup">Create tables that
transform gracefully</a></h2>
<ul>
  <li><a href="#table-headers">Checkpoint 5.1</a> - For data tables, identify
    row and column headers</li>
  <li><a href="#table-structure">Checkpoint 5.2</a> - For data tables that
    have two or more logical levels of row or column headers, use markup to
    associate data cells and header cells</li>
  <li><a href="#avoid-table-for-layout">Checkpoint 5.3</a> - Do not use tables
    for layout unless the table makes sense when linearized</li>
  <li><a href="#table-layout">Checkpoint 5.4</a> - If a table is used for
    layout, do not use any structural markup for the purpose of visual
    formatting</li>
  <li><a href="#table-summaries">Checkpoint 5.5</a> - Provide summaries for
    tables</li>
  <li><a href="#abbreviate-labels">Checkpoint 5.6</a> - Provide abbreviations
    for header labels</li>
</ul>
<hr>

<h3><a name="table-headers">Checkpoint 5.1</a> - For data tables, identify row
and column headers</h3>

<h4><a name="table-purpose">Technique 5.1.1</a> Determine the purpose of the
table</h4>

<p>The purpose of the table must be determined before performing an
accessibility evaluation. To help the author make this assessment, the
following language may be used:</p>

<h5><a name="q187">Suggested message:</a></h5>
<ul>
  <li>Data tables present relational data such as a bus schedule, a comparison
    of regional sales figures, or a listing of employee contact information.
    Cells in data tables are related to each other and usually must be
    perceived as a group.</li>
  <li>Layout tables visually format images, text, and other information on the
    page such as a navigation bar, or a newspaper page with stories, links,
    and images. Each cell in a layout table is normally independent and can be
    viewed on its own.</li>
</ul>

<h4><a name="check-table-headers">Technique 5.1.2</a> [priority 1] Check data
table for row and column headers</h4>

<h5><a name="q189">Evaluation:</a></h5>
<ul>
  <li>Element: <code>TABLE</code>.</li>
  <li>Requirement: the table must have at least one complete row of headers or
    one complete column of headers.</li>
  <li>This technique applies only to tables used for data, not to tables used
    for layout purposes.</li>
</ul>

<h5><a name="q190">Suggested message:</a></h5>
<ul>
  <li>If both row and column headers are missing: Table is missing
  headers.</li>
  <li>If either row or column headers are missing: Table has row/column
    headers but may require column/row headers.</li>
</ul>

<h5><a name="q191">Suggested repair:</a></h5>
<ul>
  <li>Allow the user to modify the table to include row headers and/or column
    headers.</li>
  <li>Allow the user to convert the top row and/or the left column to
  headers.</li>
  <li>The user should create at least one complete row or one complete column
    of headers.</li>
</ul>

<h5><a name="q192">Test Files and Discussion Files:</a></h5>
<ul>
  <li><a href="http://www.w3.org/WAI/ER/IG/ert/test51A.htm">Test file - row
    and column headers.</a></li>
</ul>
<hr title="Separator from Checkpoint 5.1">

<h3><a name="table-structure">Checkpoint 5.2</a> - For data tables that have
two or more logical levels of row or column headers, use markup to associate
data cells and header cells</h3>

<h4><a name="multiple-headers">Technique 5.2.1</a> - [Priority 1] Check data
tables for multiple levels of row and column headers</h4>

<h5><a name="q195">Evaluation:</a></h5>
<ul>
  <li>Element: <code>TH span=(2 or more)</code>  and either
    <ul>
      <li>two or more <code>TR</code> elements containing at least one
        <code>TH</code></li>
      <li>two or more <code>TH</code> elements within any <code>TR</code></li>
    </ul>
  </li>
  <li>Requirements:
    <ul>
      <li>use of <code>SCOPE | AXIS | HEADER</code></li>
      <li>two or more rows containing <code>TH</code> OR  </li>
      <li>two or more columns contain <code>TH</code></li>
    </ul>
  </li>
</ul>

<h5><a name="q196">Suggested message:</a></h5>
<ul>
  <li>Your table should identify structural groups of rows and groups of
    columns. Label table elements with the "<code>scope</code>",
    "<code>headers</code>", and "<code>axis</code>" attributes so that future
    browsers and assistive technologies will be able to select data from your
    table by filtering on categories.</li>
</ul>

<h5><a name="q197">Suggested repair:</a></h5>
<ul>
  <li>If the table does contain 2 or more logical levels of row or column
    headers, use <a
    href="http://www.w3.org/TR/html4/struct/tables.html#h-11.4.3 ">the HTML 4
    table algorithm</a> to show the author how the headers are currently
    associated with the cells. If the author determines that the current
    mark-up is not sufficient, allow the author to markup the table
    <code>TD</code> or <code>TH</code> elements with <code>scope</code>,
    <code>axis</code>, or <code>headers</code> attributes.</li>
</ul>
<ul>
  <li><a href="http://www.w3.org/WAI/ER/IG/ert/test52A.htm">Test file - nested
    table headers.</a></li>
</ul>
<hr title="Separator from Checkpoint 5.2">

<h3><a name="avoid-table-for-layout">Checkpoint 5.3</a> - Do not use tables
for layout unless the table makes sense when linearized</h3>

<h4><a name="linearization-ok">Technique 5.3.1</a> [priority 2] Verify that
layout tables make sense when linearized</h4>

<h5><a name="q200">Evaluation:</a></h5>
<ul>
  <li>Element: <code>TABLE</code></li>
  <li>Requirement: Layout tables should make sense when linearized. This
    technique applies only to tables used for layout purposes, not to data
    tables.</li>
</ul>

<h5><a name="q201">Suggested message:</a></h5>
<ul>
  <li>Tables used for layout should make sense when linearized.</li>
  <li>When a table is 'linearized,' the cells are read in the order in which
    they appear in the HTML source.</li>
</ul>

<h5><a name="q202">Suggested repair:</a></h5>
<ul>
  <li>Linearize the table and ask the author to verify that the result is
    understandable.</li>
</ul>

<h5><a name="q203">Test Files and Discussion Files:</a></h5>
<ul>
  <li><a href="http://www.w3.org/WAI/ER/IG/ert/test53A.htm">Test file -
    linearizing tables.</a></li>
</ul>
<hr title="Separator from Checkpoint 5.3">

<h3><a name="table-layout">Checkpoint 5.4</a> - If a table is used for layout,
do not use any structural markup for the purpose of visual formatting</h3>

<h4><a name="table-struct">Technique 5.4.1</a> [priority 2] Check layout
tables for structural markup</h4>

<h5><a name="q206">Evaluation:</a></h5>
<ul>
  <li>Element: <code>TABLE</code></li>
  <li>Requirements: Contains at least one <code>TH</code> element. This
    technique applies only to tables used for layout purposes, not to data
    tables.</li>
</ul>

<h5><a name="q207">Suggested message:</a></h5>
<ul>
  <li>Tables used for layout should not use table headings to create
    formatting effects.</li>
</ul>

<h5><a name="q208">Suggested repair:</a></h5>
<ul>
  <li>Allow user to change appearance of <code>TH</code> cells by
    <ul>
      <li>style sheet properties</li>
      <li><code>EM</code> and/or <code>STRONG</code></li>
    </ul>
  </li>
</ul>

<h5><a name="q209">Test Files and Discussion Files:</a></h5>
<ul>
  <li><a href="http://www.w3.org/WAI/ER/IG/ert/test54A.htm">Test file - table
    headers for formatting.</a></li>
</ul>
<hr title="Separator from Checkpoint 5.4">

<h3><a name="table-summaries">Checkpoint 5.5</a> - Provide summaries for
tables</h3>

<h4><a name="table-valid-summary">Technique 5.5.1</a> [priority 3] Check
<code>TABLE</code> elements for valid "<code>summary</code>" attribute</h4>

<h5><a name="q212">Evaluation:</a></h5>
<ul>
  <li>Element: <code>TABLE</code></li>
  <li>Requirement: Must have valid "<code>summary</code>" attribute.</li>
  <li>If the table has nested headings, cells that span multiple columns or
    rows, or other relationships that may not be obvious from analyzing the
    structure of the table but that may be apparent in a visual rendering of
    the table, a valid "<code>summary</code>" attribute may be provided.</li>
</ul>

<p>Valid "<code>summary</code>" attribute:</p>
<ul>
  <li>Not allowed - NULL "<code>summary</code>" value ("")</li>
  <li>Not allowed - "<code>summary</code>" value of spaces (" ")</li>
  <li>Suspicious - <a href="#AppendixF">placeholder "<code>summary</code>"
    value</a></li>
</ul>

<h5><a name="q213">Suggested message:</a></h5>
<ul>
  <li>For missing summary - "Table is missing a summary." "In the summary,
    describe the purpose of the table (either layout or data). For example
    ''This table charts the number of cups of coffee consumed by each senator,
    the type of coffee (decaf or regular), and whether taken with sugar.</li>
  <li>Additional help text: A summary of the relationships among cells is
    especially important for tables with nested headings, cells that span
    multiple columns or rows, or other relationships that may not be obvious
    from analyzing the structure of the table but that may be apparent in a
    visual rendering of the table. A summary may also describe how the table
    fits into the context of the current document. If no caption is provided,
    it is even more critical to provide a summary.</li>
</ul>

<h5><a name="q214">Suggested repair:</a></h5>
<ul>
  <li>Allow the user to enter a summary of the table.</li>
</ul>

<h5><a name="q215">Test Files and Discussion Files:</a></h5>
<ul>
  <li><a href="http://www.w3.org/WAI/ER/IG/ert/test55A.htm">Test file - Table
    summary.</a></li>
</ul>

<h4>Technique 5.5.2 [priority 2] Check <code>TABLE</code> elements for valid
<code>CAPTION</code> element.</h4>

<h5>Evaluation:</h5>
<ul>
  <li>Element: <code>TABLE</code></li>
  <li>Requirement: @@</li>
</ul>

<h5>Suggested message:</h5>
<ul>
  <li>This table does not have a caption: A table caption describes the nature
    of the table in one to three sentences. For example, "Cups of coffee
    consumed by each senator."</li>
</ul>

<h5>Suggested repair:</h5>
<ul>
  <li>Allow the author to enter a CAPTION</li>
</ul>
<hr title="Separator from Checkpoint 5.5">

<h3><a name="abbreviate-labels">Checkpoint 5.6</a> - Provide abbreviations for
header labels</h3>

<h4><a name="table-header-abbr">Technique 5.6.1</a> [priority 3] Check table
for header abbreviations</h4>

<h5><a name="q222">Discussion Status:</a></h5>
<ul>
  <li>How determine if an abbreviation is pronounceable? ASCII characters
    only?</li>
</ul>

<h5><a name="q223">Evaluation:</a></h5>
<ul>
  <li>Element: <code>TH</code></li>
  <li>Requirement: Valid "<code>abbr</code>" attribute if the header name is
    greater than 15 characters.</li>
</ul>

<p>Valid "<code>abbr</code>" attributes:</p>
<ul>
  <li>Not allowed - NULL "<code>abbr</code>" value ("")</li>
  <li>Not allowed - "<code>abbr</code>" value of spaces (" ")</li>
  <li>Suspicious - <a href="#AppendixG">placeholder "<code>abbr</code>"
    values</a></li>
  <li>"<code>abbr</code>" values should be shorter than 15 characters, but
    still pronounceable.</li>
</ul>

<h5><a name="q224">Suggested message:</a></h5>
<ul>
  <li>Table header is missing an abbreviation.</li>
</ul>

<h5><a name="q225">Suggested repair:</a></h5>
<ul>
  <li>Allow user to enter abbreviations for table header elements.</li>
</ul>

<h5><a name="q226">Test Files and Discussion Files:</a></h5>
<ul>
  <li><a href="http://www.w3.org/WAI/ER/IG/ert/test56A.htm">Test file -  table
    header abbreviations.</a></li>
</ul>
<hr title="Separator from Checkpoint 5.6">

<h2><a name="new-technologies">Guideline 6</a>. Ensure that pages featuring
new technologies transform gracefully</h2>
<ul>
  <li><a href="#style-sheet-guidelines">Checkpoint 6.1</a> - Organize
    documents so they may be read without style sheets</li>
  <li><a href="#frame-has-html-src">Checkpoint 6.2</a> - Ensure that
    equivalents for dynamic content are updated when the dynamic content
    changes</li>
  <li><a href="#scripts">Checkpoint 6.3</a> - Ensure that pages are usable
    when scripts, applets, or other programmatic objects are turned off or not
    supported</li>
  <li><a href="#keyboard-operable">Checkpoint 6.4</a> - For scripts and
    applets, ensure that event handlers are input device-independent</li>
  <li><a href="#fallback-page">Checkpoint 6.5</a> - Ensure that dynamic
    content is accessible or provide an alternative presentation or page</li>
</ul>
<hr>

<h3><a name="style-sheet-guidelines">Checkpoint 6.1</a> - Organize documents
so they may be read without style sheets</h3>

<h4><a name="readable-without-ss">Technique 6.1.1</a> [priority 1] Verify that
the document is readable when style sheets are not applied.</h4>

<h5><a name="q230">Evaluation:</a></h5>
<ul>
  <li>Elements:
    <ul>
      <li><code>LINK  rel="stylesheet"</code></li>
      <li><code>STYLE</code></li>
      <li>At least one "<code>style</code>" attribute used on any
      element.</li>
    </ul>
  </li>
</ul>

<h5>Suggested message:</h5>
<ul>
  <li>Ensure this document can be read without style sheets.</li>
</ul>

<h5>Suggested repair:</h5>
<ul>
  <li>Display a user notification if any use of style sheets is detected.</li>
</ul>
<hr title="Separator from Checkpoint 6.1">

<h3><a name="frame-has-html-src">Checkpoint 6.2</a> - Ensure that equivalents
for dynamic content are updated when the dynamic content changes</h3>

<h4><a name="frame-src-for-markup">Technique 6.2.1</a> [priority 1] Check the
source of <code>FRAME</code> and <code>IFRAME</code> elements for valid markup
files.</h4>

<h5><a name="q234">Evaluation:</a></h5>
<ul>
  <li>Elements: <code>FRAME</code> or <code>IFRAME</code></li>
  <li>Requirements:
    <ul>
      <li>Valid "<code>src</code>" attribute values must have a suffix of
        ".htm," ".html," ".shtm," ".shtml," ".cfm," ".cfml," ".asp," ".cgi,"
        ".pl", ".smil" or target document must have a known public identifier
        at the top of file.</li>
    </ul>
  </li>
</ul>

<h5><a name="q235">Suggested message:</a></h5>
<ul>
  <li>Frame source: [frame source file name] is not a valid markup file.</li>
</ul>

<h5><a name="q236">Suggested repair:</a></h5>
<ul>
  <li>Create an HTML "wrapper" around known object types, e.g. if the target
    is an image, place the image in an HTML file.</li>
  <li>@@Adjust Javascript to point inside the wrapper?</li>
</ul>

<h5><a name="q237">Test Files and Discussion Files:</a></h5>
<ul>
  <li><a href="http://www.w3.org/WAI/ER/IG/ert/test62A.htm">Test file - source
    of frame.</a></li>
  <!-- <li><a href="http://www.w3.org/WAI/ER/IG/ert/issues62A.htm">Link to
  discussion on this technique.</a></li> -->
</ul>

<h4><a name="dynamic-equiv-updated">Technique 6.2.2</a> [priority 1] Verify
that equivalents of dynamic content are updated and available as often as the
dynamic content.</h4>

<h5>Open issues for this technique:</h5>
<ul>
  <li>This is similar to issues related to Guideline 7. do we need to tie them
    together in some way?</li>
</ul>

<h5><a name="q239">Evaluation:</a></h5>
<ul>
  <li>Elements: <code>SCRIPT,</code><code> APPLET<code>, <code>OBJECT
     type=@@?</code>, <em>any_element  event_attribute</em> where
    event_attribute is "onmouseover" etc.</code></code></li>
  <li>Requirements: any actions that change the display must change the
    equivalent @@Is this computable in a practical time (cf. NP complete) .
     Computer science help needed here.  Of course, as in other parts of
    document, the fact that the equivalent changes is no guarantee that
    equivalent is correct than it is guaranteed that <code>"alt"</code> text
    for an image is correct.</li>
</ul>

<h5><a name="q240">Suggested message:</a></h5>
<ul>
  <li>Ensure that the descriptions of dynamic content are updated with changes
    in the dynamic content.</li>
</ul>

<h5><a name="q241">Test Files and Discussion Files:</a></h5>
<ul>
  <li><a href="http://www.w3.org/WAI/ER/IG/ert/test62A.htm">Test file - source
    of frame.</a></li>
  <!-- <li><a href="http://www.w3.org/WAI/ER/IG/ert/issues62A.htm">Link to
  discussion on this technique.</a></li> -->
</ul>
<hr title="Separator from Checkpoint 6.2">

<h3><a name="scripts">Checkpoint 6.3</a> - Ensure that pages are usable when
scripts, applets, or other programmatic objects are turned off or not
supported</h3>

<h4><a name="usable-without-programmatics">Technique 6.3.1</a> [priority 1]
Verify that the page is usable when programmatic objects are disabled.</h4>

<h5><a name="q244">Evaluation:</a></h5>
<ul>
  <li>Elements: <code>SCRIPT, OBJECT type=@@?, EMBED, APPLET</code></li>
  <li>Requirements:
    <ul>
      <li>existence of "<code>alt</code>" and/or <code>"title"</code>
      and/OR</li>
      <li>accessible alternative content in the body of <code>OBJECT,
        NOSCRIPT, NOEMBED, or APPLET</code>.</li>
    </ul>
  </li>
</ul>

<h5><a name="q245">Suggested message:</a></h5>
<ul>
  <li>Ensure that pages are usable when scripts, applets, or other
    programmatic objects are turned off or not supported.</li>
</ul>

<h5><a name="q246">Suggested repair:</a></h5>
<ul>
  <li>Provide means to create an accessible alternative representation or
    provide a link to one.</li>
</ul>
<hr title="Separator from Checkpoint 6.3">

<h3><a name="keyboard-operable-scripts">Checkpoint 6.4</a> - For scripts and
applets, ensure that event handlers are input device-independent</h3>

<h4><a name="device-indie-event-handlers">Technique 6.4.1</a> [priority 2]
Check for device independent event handlers.</h4>

<h5><a name="q249">Evaluation:</a></h5>
<ul>
  <li>Elements: <code>SCRIPT, OBJECT  type=@@?, EMBED, APPLET</code></li>
  <li>Requirements: Objects must not contain device dependent event handlers.
    @@Does this mean checking Java, Flash, etc?  Can we only do this for
    scripting? Or prompt the author to check?</li>
</ul>

<h5><a name="q250">Suggested message:</a></h5>
<ul>
  <li>For scripts and applets, ensure that event handlers are input
    device-independent.</li>
</ul>

<h5><a name="q251">Suggested repair:</a></h5>
<ul>
  <li>Display object source code and suggest device independent replacement
    code.</li>
</ul>
<hr title="Separator from Checkpoint 6.4">

<h3><a name="fallback-page">Checkpoint 6.5</a> - Ensure that dynamic content
is accessible or provide an alternative presentation or page</h3>

<h4><a name="noframe-for-frameset">Technique 6.5.1</a> [priority 2] Check that
a <code>NOFRAMES</code> element exists within each <code>FRAMESET</code>.</h4>

<h5><a name="q255">Evaluation:</a></h5>
<ul>
  <li>Element: <code>FRAMESET</code></li>
  <li>Requirements:
    <ul>
      <li>A valid <code>NOFRAMES</code> section should exist within each
        <code>FRAMESET</code> section</li>
    </ul>
  </li>
</ul>

<p>Valid <code>NOFRAMES</code> section</p>
<ul>
  <li>Must contain at least one word of text or accessible HTML code.</li>
  <li>The contents of the <code>NOFRAMES</code> element must provide the
    necessary links to navigate the site.</li>
  <li>Not allowed: Telling the user that they should upgrade to a browser that
    supports frames. Suspicious words within the text of a
    <code>NOFRAMES</code> element: "upgrade," "full advantage," supports
    frames," "missing" etc.</li>
</ul>

<h5><a name="q256">Suggested message:</a></h5>
<ul>
  <li>Does your page work if frames are not loaded?</li>
</ul>

<h5><a name="q257">Suggested repair:</a></h5>
<ul>
  <li>Allow user to construct a valid <code>NOFRAMES</code>section.</li>
</ul>

<h5><a name="q258">Test Files and Discussion Files:</a></h5>
<ul>
  <li><a href="http://www.w3.org/WAI/ER/IG/ert/test65A.htm">Test file -
    NOFRAMES.</a></li>
</ul>

<h4><a name="q259">Technique 6.5.2 [priority 2] @@Need something for scripts
and programmatic objects?</a></h4>

<p>@@ is this covered by 6.3.1 (Verify that the page is usable when
programmatic objects are disabled)?</p>
<hr title="Separator from Checkpoint 6.5">

<h2><a name="movement">Guideline 7</a>. Ensure user control of time-sensitive
content changes</h2>
<ul>
  <li><a href="#avoid-flicker">Checkpoint 7.1</a> - Until user agents allow
    users to control flickering, avoid causing the screen to flicker.</li>
  <li><a href="#style-text">Checkpoint 7.2</a> - Until user agents allow users
    to control blinking, avoid causing content to blink</li>
  <li><a href="#video-information">Checkpoint 7.3</a> - Until user agents
    allow users to freeze moving content, avoid movement in pages</li>
  <li><a href="#no-periodic-refresh">Checkpoint 7.4</a> - Until user agents
    provide the ability to stop the refresh, do not create periodically
    auto-refreshing pages</li>
  <li><a href="#auto-page-refresh">Checkpoint 7.5</a> - Until user agents
    provide the ability to stop auto-redirect, do not use markup to redirect
    pages automatically</li>
</ul>
<hr>

<h3><a name="avoid-flicker">Checkpoint 7.1</a> - Until user agents allow users
to control flickering, avoid causing the screen to flicker</h3>

<h4><a name="no-flicker">Technique 7.1.1</a> [priority 1] Verify that the page
does not cause flicker.</h4>

<h5><a name="q263">Discussion Status:</a></h5>
<ul>
  <li>It is desirable that a tool be able to measure flicker. This could be
    done by software that renders, takes screenshots and compares. [<a
    href="http://lists.w3.org/Archives/Public/w3c-wai-er-ig/2000Jan/0059.html">Len
    Kasday, 23 January 2000</a>]</li>
</ul>

<h5><a name="q264">Evaluation:</a></h5>
<ul>
  <li>Elements:
    <ul>
      <li><code>SCRIPT</code></li>
      <li><code>OBJECT  type =</code><em>(@@what are the type attribute values
        for Java, etc.?)</em></li>
      <li><code>EMBED</code></li>
      <li><code>APPLET</code></li>
      <li><code>IMG</code> element with "<code>src</code>" name ending with
        '.gif'.</li>
    </ul>
  </li>
</ul>

<h5>Suggested message:</h5>
<ul>
  <li>Display flicker is distracting and may be dangerous to some users.
    Please ensure this element does not cause the display to flicker.</li>
</ul>

<h5>Suggested repair:</h5>
<ul>
  <li>Display the object and allow the user to verify that it does not cause
    display flicker. If object does cause flicker, allow user to modify
    object.</li>
</ul>
<hr title="Separator from Checkpoint 6.6">

<h3><a name="style-text">Checkpoint 7.2</a> - Until user agents allow users to
control blinking, avoid causing content to blink</h3>

<h4><a name="no-blink">Technique 7.2.1</a> [priority 1] Check for
<code>BLINK</code> elements</h4>

<h5><a name="q269">Evaluation:</a></h5>
<ul>
  <li>Element: <code>BLINK</code></li>
</ul>

<h5><a name="q270">Suggested message:</a></h5>
<ul>
  <li>The <code>BLINK</code> element is not defined in any W3C HTML
    specification and should not be used.</li>
</ul>

<h5><a name="q271">Suggested repair:</a></h5>
<ul>
  <li>Allow the user to remove <code>BLINK</code> elements from the
  document.</li>
  <li>Allow the user to replace <code>BLINK</code> elements with any of the
    following elements:
    <ol>
      <li><code>STRONG</code></li>
      <li><code>EM</code></li>
      <li><code>SPAN</code>- allow the user to enter attributes for the
        element.</li>
      <li><code>H1</code></li>
      <li><code>H2</code></li>
      <li><code>H3</code></li>
      <li><code>H4</code></li>
      <li><code>H5</code></li>
      <li><code>H6</code></li>
    </ol>
  </li>
</ul>

<h5><a name="q272">Test Files and Discussion Files:</a></h5>
<ul>
  <li><a href="http://www.w3.org/WAI/ER/IG/ert/test72A.htm">Test file -
    blink.</a></li>
</ul>
<hr title="Separator from Checkpoint 7.1">

<h3><a name="video-information">Checkpoint 7.3</a> - Until user agents allow
users to freeze moving content, avoid movement in pages</h3>

<h4><a name="no-marquee">Technique 7.3.1</a> [priority 1] Check for
<code>MARQUEE</code> elements</h4>

<h5><a name="q275">Evaluation:</a></h5>
<ul>
  <li>Element: <code>MARQUEE</code>.</li>
</ul>

<h5><a name="q276">Suggested message:</a></h5>
<ul>
  <li>The <code>MARQUEE</code> element is not defined in any W3C HTML
    specification and should not be used.</li>
</ul>

<h5><a name="q277">Suggested repair:</a></h5>
<ul>
  <li>Allow the user to remove <code>MARQUEE</code> elements from the
    document.</li>
  <li>Allow the user to replace <code>MARQUEE</code> elements with any of the
    following elements:
    <ol>
      <li><code>STRONG</code></li>
      <li><code>EM</code></li>
      <li><code>SPAN</code> - allow the user to enter attributes for the
        element.</li>
      <li><code>H1</code></li>
      <li><code>H2</code></li>
      <li><code>H3</code></li>
      <li><code>H4</code></li>
      <li><code>H5</code></li>
      <li><code>H6</code></li>
    </ol>
  </li>
</ul>

<h5><a name="q278">Test Files and Discussion Files:</a></h5>
<ul>
  <li><a href="http://www.w3.org/WAI/ER/IG/ert/test73A.htm">Test file -
    marquee.</a></li>
</ul>

<h4><a name="programmatic-movement">Technique 7.3.2</a> [priority 1] Verify
that programmatic objects do not create moving content</h4>

<h5><a name="q280">Evaluation:</a></h5>
<ul>
  <li>Elements:
    <ul>
      <li><code>SCRIPT</code> - distinguished by (<a
        href="http://www.w3.org/WAI/ER/IG/ert/issues73B.htm">see
        discussion</a>)??</li>
      <li><code>OBJECT  type =</code><em>(@@what are the type attribute values
        for Java, etc.?)</em></li>
      <li><code>EMBED</code></li>
      <li><code>APPLET</code></li>
    </ul>
  </li>
</ul>

<h5><a name="q281">Suggested message:</a></h5>
<ul>
  <li>Moving text may be difficult to read and is inaccessible for many
    viewers.</li>
</ul>

<h5><a name="q282">Suggested repair:</a></h5>
<ul>
  <li>Allow the user to remove the <code>SCRIPT</code> from the document or
    create a mechanism to stop the movement.</li>
  <li>@@ what about <code>OBJECT, EMBED, and APPLET</code>?</li>
</ul>

<h5><a name="q283">Test Files and Discussion Files:</a></h5>
<ul>
  <li><a href="http://www.w3.org/WAI/ER/IG/ert/issues73B.htm">Discussion -
    moving content created by programmatic objects.</a></li>
</ul>
<hr title="Separator from Checkpoint 7.3">

<h3><a name="no-periodic-refresh">Checkpoint 7.4</a> - Until user agents
provide the ability to stop the refresh, do not create periodically
auto-refreshing pages</h3>

<h4><a name="no-auto-refresh">Technique 7.4.A</a> [priority 2] Remove
auto-refresh attributes from <code>META</code> elements</h4>

<h5><a name="q286">Evaluation:</a></h5>
<ul>
  <li>Elements: <code>META  http-equiv="refresh"
     content=</code><em><code>integer_greater_than_zero</code></em></li>
  <li>Note:If the "<code>content</code>" attribute is a URI this is an
    auto-redirect page. Refer to technique 7.5.1</li>
</ul>

<h5><a name="q287">Suggested message:</a></h5>
<ul>
  <li>This page uses auto-refresh which can make the page difficult to read
    for some people.</li>
</ul>

<h5><a name="q288">Suggested repair:</a></h5>
<ul>
  <li>Allow user option to either:
    <ul>
      <li>Remove the auto-refresh from the document OR</li>
      <li>Create a page with link to new page.</li>
    </ul>
  </li>
</ul>

<h5><a name="q289">Test Files and Discussion Files:</a></h5>
<ul>
  <li><a href="http://www.w3.org/WAI/ER/IG/ert/test74A.htm">Test file - auto
    refresh.</a></li>
</ul>
<hr title="Separator from Checkpoint 7.4">

<h3><a name="auto-page-refresh">Checkpoint 7.5</a> - Until user agents provide
the ability to stop auto-redirect, do not use markup to redirect pages
automatically</h3>

<h4><a name="auto-redirect">Technique 7.5.1</a> [priority 2] Check
auto-redirect attributes on <code>META</code> elements</h4>

<h5><a name="q292">Evaluation:</a></h5>
<ul>
  <li>Element: <code>META http-equiv="refresh"
    content="</code><em><code>any-URI</code></em><code>"</code>.</li>
</ul>

<h5><a name="q293">Suggested message:</a></h5>
<ul>
  <li>This page uses auto-redirect which can make the page difficult to read
    for some people.</li>
</ul>

<h5><a name="q294">Suggested repair:</a></h5>
<ul>
  <li>Allow the user to remove the auto-redirect from the document and add a
    link to the new document.</li>
</ul>

<h5><a name="q295">Test Files and Discussion Files:</a></h5>
<ul>
  <li><a href="http://www.w3.org/WAI/ER/IG/ert/test75A.htm">Test file -
    redirect.</a></li>
</ul>
<hr title="Separator from Checkpoint 7.5">

<h2><a name="own-interface">Guideline 8</a>. Ensure direct accessibility of
embedded user interfaces</h2>

<h3><a name="directly-accessible">Checkpoint 8.1</a> - Make programmatic
elements such as scripts and applets directly accessible or compatible with
assistive technologies</h3>

<h4><a name="directly-accessible-programmatics">Technique 8.1.1</a> [priority
1 if functionality is important and not presented elsewhere, otherwise
Priority 2] Verify that programmatic objects are directly accessible.</h4>

<h5><a name="q299">Open issues for this technique:</a></h5>
<ul>
  <li>Tools should include means to test the embedded technologies, e.g. java,
    at least by running them, preferably by including any test software
    supplied for the technology. [<a
    href="http://lists.w3.org/Archives/Public/w3c-wai-er-ig/2000Jan/0059.html">Len
    Kasday - 23 January 2000</a>]</li>
</ul>

<h5><a name="q300">Evaluation:</a></h5>
<ul>
  <li>Elements: <code>OBJECT, <code>APPLET</code>, EMBED or
  SCRIPT</code>.</li>
</ul>

<h5><a name="q301">Suggested message:</a></h5>
<ul>
  <li>This element may not be accessible to all users. Please ensure there is
    an accessible interface to this object.</li>
  <li>Ensure that scripts, applets, or other programmatic objects are directly
    accessible</li>
</ul>

<h5><a name="q302">Suggested repair:</a></h5>
<ul>
  <li>Display a user notification if any of the programmatic elements are in
    the document.</li>
</ul>
<hr title="Separator from Checkpoint 8.1">

<h2><a name="device-independence">Guideline 9</a>. Design for
device-independence</h2>
<ul>
  <li><a href="#client-side-maps">Checkpoint 9.1</a> - Provide client-side
    image maps instead of server-side image maps except where the regions
    cannot be defined with an available geometric shape.</li>
  <li><a href="#keyboard-operable">Checkpoint 9.2</a> - Ensure that any
    element that has its own interface can be operated in a device-independent
    manner.</li>
  <li><a href="#device-independent-events">Checkpoint 9.3</a> - For scripts,
    specify logical event handlers rather than device-dependent event
    handlers.</li>
  <li><a href="#forms-keyboard">Checkpoint 9.4</a> - Create a logical tab
    order through links, form controls, and objects.</li>
  <li><a href="#keyboard-shortcuts">Checkpoint 9.5</a> - Provide keyboard
    shortcuts to important links, form controls, and groups of form
  controls</li>
</ul>
<hr>

<h3><a name="client-side-maps">Checkpoint 9.1</a> - Provide client-side image
maps instead of server-side image maps except where the regions cannot be
defined with an available geometric shape</h3>

<h4><a name="server-side-imagemaps">Technique 9.1.1</a> [priority 1] Check for
use of server-side image maps</h4>

<h5>Evaluation:</h5>
<ul>
  <li>Element:<code>IMG  "ismap"</code></li>
</ul>

<h5>Suggested message:</h5>
<ul>
  <li>Use client-side image maps instead of server-side maps.</li>
</ul>

<h5>Suggested repair:</h5>
<ul>
  <li>Allow the user to convert the server-side image map to a client-side
    image map.</li>
</ul>
<!-- <h5><a name="q309">Test Files and Discussion Files:</a></h5>
<ul>
<li><a href="http://www.w3.org/WAI/ER/IG/ert/test91A.htm">Link to test file
for this technique.</a></li>
</ul> -->
<hr title="Separator from Checkpoint 9.1">

<h3><a name="keyboard-operable">Checkpoint 9.2</a> - Ensure that any element
that has its own interface can be operated in a device-independent manner</h3>

<h5>Open issues for this technique:</h5>
<ul>
  <li>This technique is strongly tied to Guideline 8 and checkpoint 1.1 (image
    maps).  Is there redundancy that we can get rid of?</li>
</ul>

<h5>Evaluation:</h5>
<ul>
  <li>Elements:
    <ul>
      <li><code>OBJECT  type =</code><em>(@@what are the type attribute values
        for Java, etc.?)</em></li>
      <li><code>EMBED</code></li>
      <li><code>APPLET</code></li>
    </ul>
  </li>
</ul>

<h5>Suggested message:</h5>
<ul>
  <li>Ensure this programmatic object can be operated in a device independent
    manner.</li>
</ul>

<h5>Suggested repair:</h5>
<ul>
  <li>Display a user notification if any of the programmatic objects are in
    the document.</li>
</ul>
<hr title="Separator from Checkpoint 9.2">

<h3><a name="device-independent-events">Checkpoint 9.3</a> - For scripts,
specify logical event handlers rather than device-dependent event
handlers</h3>

<h4><a name="logical-event-handlers">Technique 9.3.1</a> [priority 2] Check
scripts for logical event handlers</h4>

<h5><a name="q313">Evaluation:</a></h5>
<ul>
  <li>Elements: All elements that can contain event handlers</li>
  <li>Requirement: Elements must have a device independent event handler if
    they have any of the following device dependent event handlers:
    <ul>
      <li><code>onMouseDown()</code></li>
      <li><code>onMouseUp()</code></li>
      <li><code>onClick()</code></li>
      <li><code>onMouseOver()</code></li>
      <li><code>onMouseOut()</code></li>
      <li><code>onMouseMove()</code></li>
    </ul>
  </li>
</ul>

<h5><a name="q314">Suggested message:</a></h5>
<ul>
  <li>For scripts, specify logical event handlers rather than device-dependent
    event handlers.</li>
</ul>

<h5><a name="q315">Suggested repair:</a></h5>

<p>Allow the user to add or replace the event handlers according to the
following list:</p>
<ul>
  <li>"<code>onMouseDown</code>" add or replace with
  "<code>onKeyDown</code>"</li>
  <li>"<code>onMouseUp</code>" add or replace with "<code>onKeyUp</code>"</li>
  <li>"<code>onClick</code>" add or replace with
  "<code>onKeyPress</code>"</li>
  <li>"<code>onMouseOver</code>" add or replace with
  "<code>onFocus</code>"</li>
  <li>"<code>onMouseOut</code>" add or replace with "<code>onBlur</code>"</li>
  <li>"<code>onMouseMove</code>" remove or replace with ??@@</li>
</ul>
<hr title="Separator from Checkpoint 9.3">

<h3><a name="forms-keyboard">Checkpoint 9.4</a> - Create a logical tab order
through links, form controls, and objects</h3>

<h4><a name="tabindex">Technique 9.4.1 [priority 3] Check for
"<code>tabindex</code>" attribute</a></h4>

<h5>Open issues for this technique:</h5>
<ul>
  <li>If the tab order jumps around too much it could be confusing to someone
    using magnification or a cognitive disability. Can we check for this?</li>
</ul>

<h5><a name="q318">Evaluation:</a></h5>
<ul>
  <li>Elements:
    <ul>
      <li><code>A</code></li>
      <li><code>AREA</code></li>
      <li><code>BUTTON</code></li>
      <li><code>INPUT</code></li>
      <li><code>OBJECT</code></li>
      <li><code>SELECT</code></li>
      <li><code>TEXTAREA</code></li>
    </ul>
  </li>
  <li>Requirements:
    <ul>
      <li>May contain a valid "<code>tabindex</code>" attribute.</li>
    </ul>
  </li>
</ul>

<p>Valid "<code>tabindex</code>" attribute:</p>
<ul>
  <li>Must be an integer greater than or equal to zero.</li>
</ul>

<h5><a name="q319">Suggested message:</a></h5>
<ul>
  <li>These controls are missing a tab order. A tab order makes controls
    easier to navigate for many users.</li>
</ul>

<h5><a name="q320">Suggested repair:</a></h5>
<ul>
  <li>Display the controls and allow the user to set the tabindex of
  each.</li>
</ul>
<hr title="Separator from Checkpoint 9.4">

<h3><a name="keyboard-shortcuts">Checkpoint 9.5</a> - Provide keyboard
shortcuts to important links, form controls, and groups of form controls</h3>

<h4><a name="accesskey">Technique 9.5.1 [priority 3] Check for
"<code>accesskey</code>" attribute.</a></h4>

<h5><a name="q323">Evaluation:</a></h5>
<ul>
  <li>Elements:
    <ul>
      <li><code>A</code></li>
      <li><code>AREA</code></li>
      <li><code>BUTTON</code></li>
      <li><code>INPUT</code></li>
      <li><code>LABEL</code></li>
      <li><code>LEGEND</code></li>
      <li><code>TEXTAREA</code></li>
    </ul>
  </li>
  <li>Requirements:
    <ul>
      <li>If any of these elements are present, at least one of them should
        have a valid "<code>accesskey</code>" attribute</li>
    </ul>
  </li>
</ul>

<h5><a name="q324">Suggested message:</a></h5>
<ul>
  <li>There are no keyboard shortcut keys to any of the controls in this
    document. Important links and controls should have shortcut keys.</li>
</ul>

<h5>Suggested repair:</h5>
<ul>
  <li>Display the objects that can contain shortcut keys and allow the user to
    assign shortcut keys to them.</li>
</ul>
<hr title="Separator from Checkpoint 9.5">

<h2><a name="interim-accessibility">Guideline 10</a>. Use interim
solutions</h2>
<ul>
  <li><a href="#no-new-windows">Checkpoint 10.1</a> - Until user agents allow
    users to turn off spawned windows, do not cause pop-ups or other windows
    to appear and do not change the current window without informing the
  user</li>
  <li><a href="#unassociated-labels">Checkpoint 10.2</a> - Until user agents
    support explicit associations between labels and form controls, for all
    form controls with implicitly associated labels, ensure that the label is
    properly positioned</li>
  <li><a href="#linear-tables">Checkpoint 10.3</a> - Until user agents
    (including assistive technologies) render side-by-side text correctly,
    provide a linear text alternative (on the current page or some other) for
    all tables that lay out text in parallel, word-wrapped columns</li>
  <li><a href="#place-holders">Checkpoint 10.4</a> - Until user agents handle
    empty controls correctly, include default, place-holding characters in
    edit boxes and text areas</li>
  <li><a href="#divide-links">Checkpoint 10.5</a> - Until user agents
    (including assistive technologies) render adjacent links distinctly,
    include non-link, printable characters (surrounded by spaces) between
    adjacent links</li>
</ul>
<hr>

<h3><a name="no-new-windows">Checkpoint 10.1</a> - Until user agents allow
users to turn off spawned windows, do not cause pop-ups or other windows to
appear and do not change the current window without informing the user</h3>

<h4><a name="valid-targets">Technique 10.1.1</a> [priority 1] Check
<code>A</code> and <code>AREA</code> elements for valid "<code>target</code>"
attributes</h4>

<h5><a name="q328">Open issues for this technique:</a></h5>
<ul>
  <li>How do we handle the "until user agents" clause?</li>
  <li>Is it enough for the document to inform the user that the link will open
    in a new window or must we completely avoid new windows?</li>
</ul>

<h5><a name="q329">Evaluation:</a></h5>
<ul>
  <li>Elements:
    <ul>
      <li><code>A</code></li>
      <li><code>AREA</code></li>
    </ul>
  </li>
  <li>Requirements:
    <ul>
      <li>Should not have "<code>target</code>" attributes of
        "<code>_blank</code>" or "<code>_new</code>".</li>
    </ul>
  </li>
</ul>

<h5><a name="q330">Suggested message:</a></h5>
<ul>
  <li>This anchor element [anchor text] will open a new window that can
    disorient some users.</li>
</ul>

<h5><a name="q331">Suggested repair:</a></h5>
<ul>
  <li>Allow the user to
    <ul>
      <li>remove the "<code>target</code>" attribute or</li>
      <li>use an existing window as the target</li>
    </ul>
  </li>
</ul>

<h5><a name="q332">Test Files and Discussion Files:</a></h5>
<ul>
  <li><a href="http://www.w3.org/WAI/ER/IG/ert/test101A.htm">Test file - link
    targets.</a></li>
</ul>

<h4><a name="verify-no-new-windows">Technique 10.1.2 [priority 1] Verify that
scripts do not spawn new windows.</a></h4>

<h5>Open issues for this technique:</h5>
<ul>
  <li>Do all <code>APPLET</code> elements trigger this technique?</li>
  <li>Are there other embedded elements or scripting languages that ought to
    trigger this technique?</li>
</ul>

<h5><a name="q334">Evaluation:</a></h5>
<ul>
  <li>Elements:
    <ul>
      <li><code>SCRIPT</code></li>
      <li><code>APPLET</code></li>
    </ul>
  </li>
  <li>Requirement: <code>SCRIPT</code> must not contain code of
    <code>window.open()</code></li>
</ul>

<h5><a name="q335">Suggested message:</a></h5>
<ul>
  <li>This script will open a new window that can be disorienting for some
    users.</li>
</ul>

<h5><a name="q336">Suggested repair:</a></h5>
<ul>
  <li>Allow the user to remove the scripting code that opens a new
  window.</li>
</ul>
<hr title="Separator from Checkpoint 10.1">

<h3><a name="unassociated-labels">Checkpoint 10.2</a> - Until user agents
support explicit associations between labels and form controls, for all form
controls with implicitly associated labels, ensure that the label is properly
positioned</h3>

<h4><a name="label-positions">Technique 10.2.1 [priority 2] Verify that
<code>LABEL</code> elements are properly positioned.</a></h4>

<p>Refer also to checkpoint 12.4</p>

<h5><a name="q339">Discussion Status:</a></h5>
<ul>
  <li>Create a separate technique for <code>LEGEND</code> and
    <code>LABEL</code>? [<a
    href="http://lists.w3.org/Archives/Public/w3c-wai-er-ig/2000Jan/0132.html">Michael
    Cooper - 28 January 2000</a>]</li>
</ul>

<h5><a name="q340">Evaluation:</a></h5>
<ul>
  <li>Elements:
    <ul>
      <li><code>INPUT</code></li>
      <li><code>SELECT</code></li>
      <li><code>TEXTAREA</code></li>
    </ul>
  </li>
  <li>Requirement: Text labels must be positioned as the first text
    immediately before or after the form control.</li>
</ul>

<h5><a name="q341">Suggested message:</a></h5>
<ul>
  <li>Labels for form controls should be positioned close to their
    corresponding form controls. This control [control type] does not have a
    closely positioned label.</li>
</ul>

<h5><a name="q342">Suggested repair:</a></h5>
<ul>
  <li>Allow the user to reposition labels associated with form controls as
    follows:
    <ul>
      <li>Labels for radio buttons and checkboxes should appear after the
        radio button or checkbox. For example: [checkbox] oranges, [checkbox]
        apples.</li>
      <li>Labels for text fields appear before the text field. For example:
        last name [text area].</li>
      <li>Labels for groups of any form control should appear before the
        group. For example: choose a city [radio button] Boston [radio button]
        Madison.</li>
    </ul>
  </li>
</ul>
<hr title="Separator from Checkpoint 10.2">

<h3><a name="linear-tables">Checkpoint 10.3</a> - Until user agents (including
assistive technologies) render side-by-side text correctly, provide a linear
text alternative (on the current page or some other) for all tables that lay
out text in parallel, word-wrapped columns</h3>

<h4><a name="linearized-table-exists">Technique 10.3.1 [priority 3] Verify
that a linearized version of tables used for layout is provided.</a></h4>

<h5><a name="q345">Evaluation:</a></h5>
<ul>
  <li>Element: <code>TABLE</code></li>
  <li>Requirement: A linear version of the table is provided</li>
</ul>

<h5><a name="q346">Suggested message:</a></h5>
<ul>
  <li>Please consult the definition of linearized table. This checkpoint
    benefits people with user agents (such as some screen readers) that are
    unable to handle blocks of text presented side-by-side; the checkpoint
    should not discourage content developers from using tables to represent
    tabular information.</li>
</ul>

<h5><a name="q347">Suggested repair:</a></h5>
<ul>
  <li>If it has been determined that the table is used for layout (see
    Technique 5.1.1) then create a linear version of the table by: [@@insert
    heuristics from table linearizer - basically replace <code>TABLE</code>
    markup with text structural markup]. The author will then need to check
    that it is readable.</li>
  <li>If it has been determined that the table is used for data (see Technique
    5.1.1) then create a linear version of the table by: [@@table linearizer
    heuristics? basically, for each cell repeat the column and row headers
    associated with it]. The author will then need to check that it is
    readable.</li>
</ul>

<h5><a name="q348">Test Files and Discussion Files:</a></h5>
<ul>
  <li>Table linearizer(@@link)</li>
  <li>Trace "HelpDB" (@@link)</li>
  <li>other examples?</li>
</ul>
<hr title="Separator from Checkpoint 10.3">

<h3><a name="place-holders">Checkpoint 10.4</a> - Until user agents handle
empty controls correctly, include default, place-holding characters in edit
boxes and text areas</h3>

<h4><a name="default-values">Technique 10.4.1 [priority 3] Check for valid
default values of<code> INPUT, TEXTAREA</code>, and <code>SELECT</code>
elements.</a></h4>

<h5><a name="q351">Evaluation:</a></h5>
<ul>
  <li>Elements:
    <ul>
      <li><code>INPUT type="text | checkbox | radio"</code></li>
      <li><code>TEXTAREA</code></li>
      <li><code>OPTION</code></li>
    </ul>
  </li>
  <li>Requirements
    <ul>
      <li><code>INPUT</code> elements that have a type of <code>"text",
        "checkbox" or "radio"</code> must have at least one word of text in
        their "<code>value</code>" attribute.</li>
      <li>Between the <code>TEXTAREA</code> start and <code>TEXTAREA</code>
        end elements must be at least one word of text.</li>
      <li>One <code>OPTION</code> in each group contained by
        <code>SELECT</code> elements must have a "<code>selected</code>"
        attribute.</li>
    </ul>
  </li>
</ul>

<h5><a name="q352">Suggested message:</a></h5>
<ul>
  <li><code>INPUT</code> element missing value: This form control is missing
    placeholder text.</li>
  <li><code>TEXTAREA</code> missing text: This <code>TEXTAREA</code> is
    missing placeholder text.</li>
  <li><code>OPTION</code> not selected: At least one <code>OPTION</code> must
    be selected within this group.</li>
</ul>

<h5><a name="q353">Suggested repair:</a></h5>
<ul>
  <li><code>INPUT</code> element missing value: Allow user to enter
    placeholder text.</li>
  <li><code>TEXTAREA</code> missing text: Allow user to enter text.</li>
  <li><code>OPTION</code> not selected: Display all options and allow user to
    select one as "selected".</li>
</ul>
<hr title="Separator from Checkpoint 10.4">

<h3><a name="divide-links">Checkpoint 10.5</a> - Until user agents (including
assistive technologies) render adjacent links distinctly, include non-link,
printable characters (surrounded by spaces) between adjacent links</h3>

<h4><a name="chars-between-A">Technique 10.5.1 [priority 3] Check for
non-whitespace characters between consecutive <code>A
</code>elements.</a></h4>

<h5><a name="q356">Evaluation:</a></h5>
<ul>
  <li>Element: <code>A</code> end element.</li>
  <li>Requirement: <code>A</code> sections within the same line of text must
    be separated by a sequence of "whitespace, non-whitespace,
  whitespace".</li>
  <li>Whitespace is a space, tab, CR, or &amp;nbsp;</li>
  <li>Non-whitespace is any text character.</li>
</ul>

<h5><a name="q357">Suggested message:</a></h5>
<ul>
  <li>These sequential links do not have separating characters: [sequential
    links].</li>
</ul>

<h5><a name="q358">Suggested repair:</a></h5>
<ul>
  <li>Allow user to insert " | " characters between sequential links. Allow
    user to choose another character other than "|" for separator.</li>
</ul>
<hr title="Separator from Checkpoint 10.5">

<h2><a name="use-w3c">Guideline 11</a>. Use W3C technologies and
guidelines</h2>
<ul>
  <li><a href="#latest-w3c-specs">Checkpoint 11.1</a> - Use W3C technologies
    when they are available and appropriate for a task and use the latest
    versions when supported</li>
  <li><a href="#avoid-deprecated">Checkpoint 11.2</a> - Avoid deprecated
    features of W3C technologies</li>
  <li><a href="#content-preferences">Checkpoint 11.3</a> - Provide information
    so that users may receive documents according to their preferences</li>
  <li><a href="#alt-pages">Checkpoint 11.4</a> - If, after best efforts, you
    cannot create an accessible page, provide a link to an alternative page
    that uses W3C technologies, is accessible, has equivalent information (or
    functionality), and is updated as often as the inaccessible (original)
    page</li>
</ul>
<hr>

<h3><a name="latest-w3c-specs">Checkpoint 11.1</a> - Use W3C technologies when
they are available and appropriate for a task and use the latest versions when
supported</h3>

<h4><a name="verify-w3c">Technique 11.1.1 [priority 2] Verify that W3C
technologies are used, where possible and appropriate.</a></h4>

<h5>Open issues for this technique:</h5>
<ul>
  <li>Many of these W3C formats are not widely supported yet. Therefore, how
    do we deal with this in the meantime? Present the info and let the author
    decide?</li>
</ul>

<h5><a name="q362">Evaluation:</a></h5>
<ul>
  <li>Element: ?@@</li>
  <li>Requirements:
    <ul>
      <li>Check for uses of non-W3C technologies such as: PDF, Flash, GIF
        images, JPG images, proprietary HTML elements (@@other major
      ones??).</li>
      <li>@@link See 1.1.1 for images used for mathematical equations.</li>
      <li>Note. I left out JavaScript because there is not a W3C equivalent
        technology yet.</li>
    </ul>
  </li>
</ul>

<h5><a name="q363">Suggested message:</a></h5>
<ul>
  <li>Non-W3C technology used: W3C technologies have been reviewed for
    accessibility issues throughout the design phase and have accessibility
    built-in. Many non-W3C formats require specific applications (often called
    plug-ins) that are inaccessible or do not work well with assistive
    technologies. Using W3C technologies will tend to make pages more
    accessible to more people using a wider variety of hardware and software.
    If inaccessible technologies (proprietary or not) must be used, equivalent
    accessible pages must be provided.</li>
</ul>

<h5><a name="q364">Suggested repair:</a></h5>
<ul>
  <li>Suggest that where appropriate, the author:
    <ul>
      <li>convert quicktime movies (others?) into SMIL presentations.</li>
      <li>convert GIF and JPG images with text to text with style sheets.</li>
      <li>convert Flash animations to a combination of valid HTML, SMIL, and
        PNG or SVG.</li>
      <li>convert images of math equations to MathML.</li>
    </ul>
  </li>
  <li>Use a text-only page generator (such as Adobe's PDFtoText) to create an
    equivalent accessible page.</li>
</ul>
<hr title="Separator from Checkpoint 11.1">

<h3><a name="avoid-deprecated">Checkpoint 11.2</a> - Avoid deprecated features
of W3C technologies</h3>

<h4><a name="check-deprecated">Technique 11.2.1 [priority 2] Check for
deprecated features of W3C technologies.</a></h4>

<h5><a name="q367">Evaluation:</a></h5>
<ul>
  <li>Elements: <code>APPLET | BASEFONT | CENTER | DIR | FONT | ISINDEX | MENU
    | S | STRIKE</code>, and <code>U</code>. (Refer to the <a
    href="http://www.w3.org/TR/html401/appendix/changes.html#idx-deprecated">list
    of deprecated elements in the HTML 4.01 specification</a>.)</li>
  <li>Requirements:
    <ul>
      <li>Should not be used.</li>
      <li>See checkpoint 3.2 for more information on public text
      identifiers.</li>
    </ul>
  </li>
</ul>

<h5><a name="q368">Suggested message:</a></h5>
<ul>
  <li>This HTML element [deprecated element] is now deprecated and should not
    be used. Use this element instead: [replacement element].</li>
</ul>

<h5><a name="q369">Suggested repair:</a></h5>
<ul>
  <li>Allow the user to replace <code>FONT</code> with <code>CSS</code>.</li>
  <li>Allow the user to replace <code>IMG</code> and <code>APPLET</code> with
    <code>OBJECT</code>.</li>
</ul>
<hr title="Separator from Checkpoint 11.2">

<h3><a name="content-preferences">Checkpoint 11.3</a> - Provide information so
that users may receive documents according to their preferences</h3>

<h4><a name="server-by-user-pref">Technique 11.3.1 [priority 3] Check that
documents are served per user preferences.</a></h4>

<h5><a name="q372">Evaluation:</a></h5>
<ul>
  <li>Element: ?@@</li>
  <li>Requirement: ?@@</li>
</ul>

<h5><a name="q374">Suggested repair:</a></h5>
<ul>
  <li>Prompt user to specify language of document in <a
    href="#primary-lang">technique 4.3.1</a>.</li>
  <li>Use CC/PP or XML/XSLT or other transformations on the server or gateway
    to configure a page for various user preferences and device profiles.</li>
  <li>Serve style sheets based on user preferences - use the media types.</li>
  <li>Work with your server system administrator to provide content
    negotiation.</li>
  <li>Use browser sniffing on the client to request documents on the
  server.</li>
  <li>Use cookies to remember user preferences between sessions and server
    documents per those preferences.</li>
  <li>Link to other versions of the document (other formats and
  languages).</li>
  <li>If not possible to use content negotiation, indicate content type or
    language through markup (e.g., in HTML use "<code>type</code>" and
    "<code>hreflang</code>").</li>
</ul>
<hr title="Separator from Checkpoint 11.3">

<h3><a name="alt-pages">Checkpoint 11.4</a> - If, after best efforts, you
cannot create an accessible page, provide a link to an alternative page that
uses W3C technologies, is accessible, has equivalent information (or
functionality), and is updated as often as the inaccessible (original)
page</h3>

<h4><a name="track-conformance">Technique 11.4.1 [priority 1] Verify that the
page has passed all checkpoints of the desired conformance level.</a></h4>

<h5><a name="q377">Evaluation:</a></h5>
<ul>
  <li>Elements: All elements specified in this document.</li>
  <li>Requirements: Check the document for compliance to the WCAG guidelines
    according to the level specified by the user.</li>
</ul>

<h5><a name="q378">Suggested message:</a></h5>
<ul>
  <li>This document does not conform to the WCAG guidelines. If you are unable
    to make the necessary repairs to this document then please create another
    equivalent page that is accessible and link to it from this document.</li>
</ul>

<h5><a name="q379">Suggested repair:</a></h5>
<ul>
  <li>Allow user to insert a link in the document to another more accessible
    page.</li>
  <li>Dynamically generated alternative pages [references@@].</li>
  <li>Tools to generate alternative pages [references@@].</li>
</ul>
<hr title="Separator from Checkpoint 11.4">

<h2><a name="complex-elements">Guideline 12</a>. Provide context and
orientation information</h2>
<ul>
  <li><a href="#frame-names">Checkpoint 12.1</a> - Title each frame to
    facilitate frame identification and navigation</li>
  <li><a href="#frame-longdesc">Checkpoint 12.2</a> - Describe the purpose of
    frames and how frames relate to each other if it is not obvious by frame
    titles alone</li>
  <li><a href="#group-information">Checkpoint 12.3</a> - Divide large blocks
    of information into more manageable groups where natural and
  appropriate</li>
  <li><a href="#associate-labels">Checkpoint 12.4</a> - Associate labels
    explicitly with their controls</li>
</ul>
<hr>

<h3><a name="frame-names">Checkpoint 12.1</a> - Title each frame to facilitate
frame identification and navigation</h3>

<h4><a name="frame-titles">Technique 12.1.1</a> [priority 1] Check
<code>FRAME</code> elements for valid "<code>title</code>" attributes</h4>

<h5><a name="q383">Evaluation:</a></h5>
<ul>
  <li>Element: <code>FRAME</code></li>
  <li>Requirement: Must have valid "<code>title</code>" attribute .</li>
</ul>

<p>Valid "<code>title</code>" attribute:</p>
<ul>
  <li>Not allowed - NULL value ("")</li>
  <li>Not allowed - spaces (" ")</li>
  <li>Suspicious - <a href="#AppendixH">placeholder title text</a></li>
</ul>

<h5><a name="q384">Suggested message:</a></h5>
<ul>
  <li>Missing title for this frame: [frame file name].</li>
</ul>

<h5><a name="q385">Suggested repair:</a></h5>
<ul>
  <li>Display the frame content and allow user to enter a new title for the
    frame.</li>
</ul>

<h5><a name="q386">Test Files and Discussion Files:</a></h5>
<ul>
  <li><a href="http://www.w3.org/WAI/ER/IG/ert/test121A.htm">Test file - frame
    titles.</a></li>
</ul>
<hr title="Separator from Checkpoint 12.1">

<h3><a name="frame-longdesc">Checkpoint 12.2</a> - Describe the purpose of
frames and how frames relate to each other if it is not obvious by frame
titles alone</h3>

<p>@@ covered by 1.1.8?</p>

<p>@@Suggest that if the <code>FRAME "title"</code> does not describe the
frame that a "<code>longdesc</code>" is needed?</p>
<hr title="Separator from Checkpoint 12.2">

<h3><a name="group-information">Checkpoint 12.3</a> - Divide large blocks of
information into more manageable groups where natural and appropriate</h3>

<p>@@Any suggestions??</p>
<hr title="Separator from Checkpoint 12.3">

<h3><a name="associate-labels">Checkpoint 12.4</a> - Associate labels
explicitly with their controls</h3>

<h4><a name="label-for">Technique 12.4.1 [priority 2] Check <code>LABEL</code>
elements for valid "<code>for</code>" attribute values.</a></h4>

<h5><a name="q391">Evaluation:</a></h5>
<ul>
  <li>Elements: <code>INPUT</code> and <code>LABEL</code></li>
  <li>Requirements:
    <ul>
      <li><code>INPUT</code> elements must have a valid "<code>id</code>"
        attribute.</li>
      <li><code>LABEL</code> elements must have a valid "<code>for</code>"
        attribute that matches the ID of one of the <code>INPUT</code>
        elements in the document.</li>
    </ul>
  </li>
</ul>

<h5><a name="q392">Suggested message:</a></h5>
<ul>
  <li>This form control is not explicitly labeled: [form control].</li>
  <li>This label is not explicitly associated with a form control:
  [label].</li>
</ul>

<h5><a name="q393">Suggested repair:</a></h5>
<ul>
  <li>Allow the user to set the "<code>id</code>" attribute for each
    <code>INPUT</code> element in the document.</li>
  <li>Allow the user to set the "<code>for</code>" attribute of each
    <code>LABEL</code> element so it matches an <code>INPUT</code>
  element.</li>
</ul>
<hr title="Separator from Checkpoint 12.4">

<h2><a name="facilitate-navigation">Guideline 13</a>. Provide clear navigation
mechanisms</h2>
<ul>
  <li><a href="#meaningful-links">Checkpoint 13.1</a> - Clearly identify the
    target of each link</li>
  <li><a href="#use-metadata">Checkpoint 13.2</a> - Provide metadata to add
    semantic information to pages and sites</li>
  <li><a href="#site-description">Checkpoint 13.3</a> - Provide information
    about the general layout of a site</li>
  <li><a href="#clear-nav-mechanism">Checkpoint 13.4</a> - Use navigation
    mechanisms in a consistent manner</li>
  <li><a href="#nav-bar">Checkpoint 13.5</a> - Provide navigation bars to
    highlight and give access to the navigation mechanism</li>
  <li><a href="#group-links">Checkpoint 13.6</a> - Group related links,
    identify the group (for user agents), and, until user agents do so,
    provide a way to bypass the group</li>
  <li><a href="#searches">Checkpoint 13.7</a> - If search functions are
    provided, enable different types of searches for different skill levels
    and preferences</li>
  <li><a href="#front-loading">Checkpoint 13.8</a> - Place distinguishing
    information at the beginning of headings, paragraphs, lists, etc</li>
  <li><a href="#bundled-version">Checkpoint 13.9</a> - Provide information
    about document collections</li>
  <li><a href="#skip-over-ascii">Checkpoint 13.10</a> - Provide a means to
    skip over multi-line ASCII art</li>
</ul>
<hr>

<h3><a name="meaningful-links">Checkpoint 13.1</a> - Clearly identify the
target of each link</h3>

<h4><a name="clear-link-target">Technique 13.1.1 [priority 2] Verify that the
target of each link is clearly identified.</a></h4>

<h5><a name="q397">Evaluation:</a></h5>
<ul>
  <li>Element: <code>A</code></li>
  <li>Requirements:
    <ul>
      <li>Names must be unique for each target.</li>
      <li>Must be meaningful</li>
      <li>Should be terse</li>
    </ul>
  </li>
</ul>

<p>Suspicious anchor names:</p>
<ul>
  <li>click here</li>
  <li>more</li>
  <li>follow this</li>
  <li>greater than 60 characters</li>
</ul>

<h5><a name="q398">Suggested message:</a></h5>
<ul>
  <li>If non-meaningful text found: This link text may not be meaningful when
    read on its own: [link text].</li>
  <li>If lengthy text found: This link text is quite long and should be
    shortened: [link text].</li>
</ul>

<h5><a name="q399">Suggested repair:</a></h5>
<ul>
  <li>Allow user to change the link text and surrounding text.</li>
  <li>Retrieve the <code>TITLE</code> of the target page and suggest that as
    link text.</li>
  <li>If the author is trying to make a Level Triple A site, Ask the author to
    provide supplemental information about the link in the
    "<code>title</code>" attribute.</li>
</ul>

<h5><a name="q400">Related resources</a></h5>

<p>Harper, S., Stevens, R., and Goble, C. (1999). Towel: Real World Mobility
on the Web. In Vanderdonckt, J. and Puerta, A., eds.: Computer-Aided Design of
User Interfaces II. Dordrecht, Netherlands: Kluwer Academic Publishers.</p>
<hr title="Separator from Checkpoint 13.1">

<h3><a name="use-metadata">Checkpoint 13.2</a> - Provide metadata to add
semantic information to pages and sites</h3>

<h4><a name="check-for-meta-data">Technique 13.2.1 [priority 2] Check for
<code>META, ADDRESS, TITLE</code> and <code>LINK</code> elements.</a></h4>

<h5><a name="q403">Evaluation:</a></h5>
<ul>
  <li>Elements:
    <ul>
      <li><code>META</code></li>
      <li><code>ADDRESS</code></li>
      <li><code>TITLE</code></li>
      <li><code>LINK</code></li>
    </ul>
  </li>
  <li>Requirements: Must have at least one of these elements in the
  document.</li>
</ul>

<h5><a name="q404">Suggested message:</a></h5>
<ul>
  <li>This document does not contain any META information.</li>
</ul>

<h5><a name="q405">Suggested repair:</a></h5>
<ul>
  <li>If no <code>META, ADDRESS, TITLE</code> or <code>LINK</code> elements
    are found, request information from the author to be stored as meta
    information. Examples of content to prompt for:
    <ul>
      <li>title of the page (required for frames, see checkpoint 12.1),</li>
      <li>type of content,</li>
      <li>descriptions of the content of the page,</li>
      <li>conformance claims,</li>
      <li>author information,</li>
      <li>next page in a series (e.g., <code>LINK rel="next"</code>).</li>
    </ul>
  </li>
  <li>If a <code>LINK</code> element is found, check if it is used for style
    sheets. If it is, then proceed as if no <code>LINK</code> element were
    found.</li>
  <li>If a <code>META</code> element is found, check if it is used to create a
    redirect. If it is, then proceed as if no <code>META</code> element were
    found (refer also to checkpoints 7.4 and 7.5).</li>
</ul>

<h4><a name="check-rdf">Technique 13.2.2 [priority 2] Check for use of
RDF.</a></h4>

<p>@@Similar to 13.2.1, yet might be best in own technique??</p>
<hr title="Separator from Checkpoint 13.2">

<h3><a name="site-description">Checkpoint 13.3</a> - Provide information about
the general layout of a site</h3>

<p>@@Machine checkable? Generate user notification?</p>
<hr title="Separator from Checkpoint 13.3">

<h3><a name="clear-nav-mechanism">Checkpoint 13.4</a> - Use navigation
mechanisms in a consistent manner</h3>

<p>@@Machine checkable? Generate user notification?</p>
<hr title="Separator from Checkpoint 13.4">

<h3><a name="nav-bar">Checkpoint 13.5</a> - Provide navigation bars to
highlight and give access to the navigation mechanism</h3>

<p>@@Machine checkable? Generate user notification?</p>
<hr title="Separator from Checkpoint 13.5">

<h3><a name="group-links">Checkpoint 13.6</a> - Group related links, identify
the group (for user agents), and, until user agents do so, provide a way to
bypass the group</h3>

<h4><a name="check-for-link-groups">Technique 13.6.1 [Priority 3] Verify if
links should be grouped.</a></h4>

<h5>Open issues for this technique:</h5>
<ul>
  <li>WCAG question: can we suggest that links be grouped by <code>DIV or
    SPAN</code>?</li>
  <li>WCAG question: is the use of <code>MAP</code> to group links completely
    agreed upon?</li>
</ul>

<h5><a name="q413">Discussion status:</a></h5>

<p>This suggests another technique that is not widely supported by user
agents.</p>

<h5><a name="q414">Evaluation:</a></h5>
<ul>
  <li>Element: Several <code>A</code> elements all in one row or column of
    table and/or separated only by
    <ul>
      <li>spaces,</li>
      <li>bullets,</li>
    </ul>
    <ul>
      <li><code>BR</code> elements,</li>
      <li>or a few characters such as "] [" or " | " or</li>
    </ul>
  </li>
  <li>Requirement: links should be grouped by <code>SPAN,DIV</code> or
    <code>MAP</code> elements.</li>
</ul>

<h5><a name="q415">Suggested message:</a></h5>
<ul>
  <li>Groups of links should be grouped with a structural element.</li>
</ul>

<h5><a name="q416">Suggested repair:</a></h5>
<ul>
  <li>Ask the user if an identified list of links should be grouped.</li>
  <li>If the user wants to group the links, use one of the following
    techniques
    <ul>
      <li>a <code>MAP</code> element</li>
      <li><code>SPAN</code> or <code>DIV</code> with appropriate
        "<code>title</code>"</li>
    </ul>
  </li>
  <li>Suggest that the user provide a link to bypass the group or that they
    move the group to the bottom of the page or that they use a high
    "<code>tabindex</code>" attribute value.</li>
</ul>
<hr title="Separator from Checkpoint 13.6">

<h3><a name="searches">Checkpoint 13.7</a> - If search functions are provided,
enable different types of searches for different skill levels and
preferences</h3>

<h4><a name="search-variety">Technique 13.7.1 [priority 3] Verify that search
functions enable a variety of skill levels and preferences.</a></h4>

<h5><a name="q419">Evaluation:</a></h5>
<ul>
  <li>Element: <code>FORM</code></li>
  <li>Requirement: Check if a <code>FORM</code> is used to submit a
  search.</li>
</ul>

<h5><a name="q420">Suggested message:</a></h5>
<ul>
  <li>When providing search functionality, content developers should offer
    search mechanisms that satisfy varying skill levels and preferences. Most
    search facilities require the user to enter keywords for search terms.
    Users with spelling disabilities and users unfamiliar with the language of
    your site will have a difficult time finding what they need if the search
    requires perfect spelling. Search engines might include a spell checker,
    offer "best guess" alternatives, query-by-example searches, similarity
    searches, etc.</li>
</ul>
<hr title="Separator from Checkpoint 13.7">

<h3><a name="front-loading">Checkpoint 13.8</a> - Place distinguishing
information at the beginning of headings, paragraphs, lists, etc</h3>

<p>@@Machine checkable? Generate user notification?</p>
<hr title="Separator from Checkpoint 13.8">

<h3><a name="bundled-version">Checkpoint 13.9</a> - Provide information about
document collections</h3>

<h4><a name="doc-collections">Technique 13.9.1 [priority 3] Verify that
information about document collections is provided.</a></h4>

<h5><a name="q424">Open issues for this technique:</a></h5>
<ul>
  <li>Is there a way to use RDF to describe document collections?</li>
</ul>

<h5><a name="q425">Evaluation:</a></h5>
<ul>
  <li>Elements: @@? <code>LINK, A</code></li>
  <li>Requirement: If the page is part of a collection, such as a slide show,
    or a chapter in a book, the previous and next pages ought to be marked as
    such.</li>
</ul>

<h5><a name="q426">Suggested message:</a></h5>
<ul>
  <li>Bundled documents can facilitate reading off-line.</li>
</ul>

<h5><a name="q427">Suggested repair:</a></h5>
<ul>
  <li>In HTML/XHTML specify document collections with the <code>LINK</code>
    element and the "<code>rel</code>" and "<code>rev</code>" attributes.</li>
  <li>Suggest that that the author create a collection by building an archive
    (e.g., with zip, tar and gzip, stuffit, etc.) of the multiple pages.</li>
</ul>
<hr title="Separator from Checkpoint 13.9">

<h3><a name="skip-over-ascii">Checkpoint 13.10</a> - Provide a means to skip
over multi-line ASCII art</h3>

<h4><a name="skip-ascii-art">Technique 13.10.1 [priority 3] Verify that one
can skip over multi-line ASCII art.</a></h4>

<h5><a name="q430">Open issues for this technique:</a></h5>
<ul>
  <li>See 1.1.13 for algorithm to find ASCII art</li>
</ul>

<h5><a name="q431">Evaluation:</a></h5>
<ul>
  <li>Elements: <code>PRE</code> and <code>XMP</code></li>
  <li>Requirements: A link must be provided to skip over ASCII art.</li>
</ul>

<h5><a name="q432">Example of message to be displayed:</a></h5>
<ul>
  <li>A link must be provided to skip over this character based (ASCII art)
    artwork: [display artwork]</li>
</ul>

<h5><a name="q433">Suggested repair:</a></h5>
<ul>
  <li>Allow user to insert a link in the document that skips over the ASCII
    art.</li>
  <li>Set title of link to "Skip Over ASCII Art" so it can be detected in
    future.</li>
</ul>
<hr title="Separator from Checkpoint 13.10">

<h2><a name="facilitate-comprehension">Guideline 14</a>. Ensure that documents
are clear and simple</h2>
<ul>
  <li><a href="#comprehension">Checkpoint 14.1</a> - Use the clearest and
    simplest language appropriate for a site's content</li>
  <li><a href="#icons">Checkpoint 14.2</a> - Supplement text with graphic or
    auditory presentations where they will facilitate comprehension of the
    page</li>
  <li><a href="#navigation">Checkpoint 14.3</a> - Create a style of
    presentation that is consistent across pages</li>
</ul>
<hr>

<h3><a name="comprehension">Checkpoint 14.1</a> - Use the clearest and
simplest language appropriate for a site's content</h3>

<p>@@Check document using fog index? Generate user notification?</p>
<hr title="Separator from Checkpoint 14.1">

<h3><a name="icons">Checkpoint 14.2</a> - Supplement text with graphic or
auditory presentations where they will facilitate comprehension of the
page</h3>

<p>@@Machine checkable?  Generate user notification?</p>
<hr title="Separator from Checkpoint 14.2">

<h3><a name="navigation">Checkpoint 14.3</a> - Create a style of presentation
that is consistent across pages</h3>

<h4><a name="consistent-style">Technique 14.3.1 [priority 3] Verify that a
consistent style of presentation is used across pages.</a></h4>

<h5><a name="q439">Open issues for this technique:</a></h5>
<ul>
  <li>@@This requires looking at pages throughout the site. Need two levels of
    checking: page vs site?</li>
</ul>

<h5><a name="q440">Evaluation:</a></h5>
<ul>
  <li>Elements:<code> STYLE</code> and <code>LINK</code></li>
  <li>Requirements:
    <ul>
      <li>The properties of <code>STYLE</code> elements should be consistent
        between pages.</li>
      <li>The names of external style sheets (referenced with
        <code>LINK</code> elements) should be consistent between pages.</li>
      <li>This should be verified by the author. There are good reasons to use
        different styles between pages.</li>
    </ul>
  </li>
</ul>

<h5><a name="q441">Suggested message:</a></h5>
<ul>
  <li>Consistent page layout and recognizable graphics benefit all users. In
    particular, they help people with cognitive disabilities or who have
    difficulty reading.</li>
</ul>

<h5><a name="q442">Suggested repair:</a></h5>
<ul>
  <li>If style properties vary between pages, or various external style sheets
    are used, suggest the author consolidate style properties into external
    style sheets and use consistently.</li>
</ul>
<hr title="Separator from Checkpoint 14.3">

<h3><a name="DocumentRating" id="DocumentRating">Document Rating</a></h3>

<p>After evaluating a document, an evaluation and/or repair tool should
provide the user with a document rating. The rating is based on conformance to
the <a href="http://www.w3.org/TR/WAI-WEBCONTENT/#Conformance">W3C Web Content
Accessibility Guidelines</a> and will be:</p>
<ul>
  <li><strong>Level "A"</strong>: all Priority 1 checkpoints are
  satisfied;</li>
  <li><strong>Level "Double-A"</strong>: all Priority 1 and 2 checkpoints are
    satisfied;</li>
  <li><strong>Level "Triple-A"</strong>: all Priority 1, 2, and 3 checkpoints
    are satisfied;</li>
</ul>

<p>Some checkpoints can not be checked by a software program and will require
user evaluation. The user must be informed of the items that they must
check.</p>

<p>Refer to the <a href="http://www.w3.org/WAI/ER/IG/rating/">Rating Algorithm
for Evaluation of Web Pages</a> by Len Kasday.</p>
<hr title="Separator from Document Rating">

<h2><a name="AppendixA" id="AppendixA">Appendix A</a> - Placeholder text</h2>
<ul>
  <li>an image file suffix (see Appendix B)</li>
  <li>the single word "Image", "Photo"</li>
  <li>the word "images"  (e.g. as in "turn on images").</li>
</ul>
<hr title="Separator from Appendix A">

<h2><a name="AppendixB" id="AppendixB">Appendix B</a> - Image File
Suffixes</h2>
<ul>
  <li>.jpg</li>
  <li>.gif</li>
  <li>.png</li>
</ul>
<hr title="Separator from Appendix B">

<h2><a name="AppendixC" id="AppendixC">Appendix C</a> - Placeholder OBJECT
text equivalent</h2>
<ul>
  <li>{object text goes here}</li>
</ul>
<hr title="Separator from Appendix C">

<h2><a name="AppendixD" id="AppendixD">Appendix D</a> - Sound File
Suffixes</h2>
<ul>
  <li>.wav</li>
  <li>.au</li>
  <li>.snd</li>
  <li>.dwd</li>
  <li>.iff</li>
  <li>.svx</li>
  <li>.sam</li>
  <li>.smp</li>
  <li>.vce</li>
  <li>.voc</li>
  <li>.pcm</li>
  <li>.aif</li>
</ul>
<hr title="Separator from Appendix D">

<h2><a name="AppendixE" id="AppendixE">Appendix E</a> - Placeholder
<code>NOSCRIPT</code> text</h2>
<ul>
  <li>{NOSCRIPT text goes here}</li>
</ul>
<hr title="Separator from Appendix E">

<h2><a name="AppendixF" id="AppendixF">Appendix F</a> - Placeholder
<code>TABLE "summary"</code> text</h2>
<ul>
  <li>Summary</li>
  <li>Table</li>
  <li>Table Summary</li>
</ul>
<hr title="Separator from Appendix F">

<h2><a name="AppendixG" id="AppendixG">Appendix G</a> - Placeholder table
header "<code>abbr</code>" text</h2>
<ul>
  <li>@@</li>
</ul>
<hr title="Separator from Appendix G">

<h2><a name="AppendixH" id="AppendixH">Appendix H</a> - Placeholder
<code>FRAME "title"</code> text</h2>
<ul>
  <li>@@</li>
</ul>
<hr title="Separator from Appendix H">

<h2><a name="AppendixI" id="AppendixI">Appendix I</a> - Applet Executable
Suffix</h2>
<ul>
  <li>.class</li>
  <li>.java</li>
  <li>.jar</li>
  <li>.zip</li>
</ul>
<hr title="Separator from Appendix I">

<h2><a name="AppendixJ" id="AppendixJ">Appendix J</a> - Bullet
Identification</h2>

<p>An image will be identified as a bullet if it has the following
characteristics:</p>
<ul>
  <li>@@</li>
</ul>

<p><a href="http://www.w3.org/WAI/ER/IG/ert/Bullet.htm">Identifying Bullets
page</a></p>
<hr title="Separator from Appendix J">

<h2><a name="AppendixK" id="AppendixK">Appendix K</a> - Horizontal Rule
Identification</h2>

<p>An image will be identified as a horizontal rule if it has the following
characteristics:</p>
<ul>
  <li>@@</li>
</ul>

<p><a href="http://www.w3.org/WAI/ER/IG/ert/Hr.htm">Identifying HRs
page</a></p>
<hr title="Separator from Appendix J">

<h2><a name="AppendixL" id="AppendixL">Appendix L</a> - Links To Associated
Sites</h2>
<ul>
  <li><a href="http://www.cast.org/bobby/">Bobby</a> - Accessibility evaluator
    tool</li>
  <li><a href="http://www.delorie.com/web/lynxview.html">Lynx Viewer</a> -
    Displays a text-only view of web pages</li>
  <li><a href="http://aprompt.snow.utoronto.ca/">A-Prompt</a> - Accessibility
    evaluator and repair tool</li>
</ul>
<hr title="Separator from Appendix K">

<h2><a name="q456">Glossary</a></h2>

<p>@@link to WCAG and ATAG glossaries?</p>
<dl>
  <dt>Programmatic object</dt>
    <dd>An object that is embedded in a document with the SCRIPT or
      <code>APPLET</code> elements, and sometimes with the OBJECT or EMBED
      elements. @@need to clarify the definition and then use it.</dd>
</dl>
<hr>
<a href="http://www.w3.org/WAI/WCAG1AA-Conformance" title="Explanation of
Level Double-A Conformance"> <img height="31" width="88" border="0"
src="http://www.w3.org/WAI/wcag1AA" alt="Level Double-A conformance icon,     
     W3C-WAI Web Content Accessibility Guidelines 1.0"></a> <a
href="http://validator.w3.org/"><img border="0"
src="http://validator.w3.org/images/vh40" alt="Valid HTML 4.0!" height="31"
width="88"></a> <a
href="http://jigsaw.w3.org/css-validator/validator.html.en"><img height="31"
width="88" border="0" src="http://jigsaw.w3.org/css-validator/images/vcss.gif"
alt="Valid CSS!"></a>

<div class="navbar">
<hr class="navbar" title="Navigation area separator">
[<a accesskey="c" href="#TOC">contents</a>]  </div>
</body>
</html>