Knowledge (XXG) talk:Manual of Style/Accessibility/Archive 4

121:" key to move to the end of the table, and to move to the TOC from the lead section, I press "H" to move to the next heading (as the TOC is a level 2 heading). My problem with navboxes is that there's no way to reliably get out of them by jumping past HTML elements. I usually use the "n" key (move to the next non-linked text block), but that usually gets me to the wrong place. Otherwise, it helps if navboxes are either at the end of an article or close to another HTML element (a heading, a table, etc). Here's a 35: 761:

and columns need captions, and there needs to be a uniform number of rows and columns. How I imagine it is a row containing something like "first quarter-final | Roger Federer v. David Nalbandian | 6-2, 6-1, 6-4|Roger Federer" with column headings of "match title | players | score | winner", where vertical bars separate the elements in my examples. Note that there is no problem with large tables if they're needed:

1325:(May 2007 archived diff). I won't attempt to summarize it all (though I do apologize to Andy for my tone and goodfaith in some of the comments there), but there are numerous pros and cons to both displaying or not-displaying animations directly within articles. And numerous editors/admins supporting each position, hence no consensus for a change seems to have been reached there. 1010:

It's not the case that screen readers do a bad job of reading such things; they read what they're given, and if we give them garbage, that's what they'll read. Why should talk pages be any less accessible to people who cannot see, than article pages? In fact, I see that the use of colon characters to

965:

says, which is "Do not leave blank lines between items in a bulleted or numbered list unless there is a reason to do so, since this causes the Wiki software to interpret each list item as an individual list." -- except perhaps adding that it causes screen readers to announce each item as belonging to

402:

The problem is many articles have all three: an infobox (with an image), followed by a separate image, followed by yet another navbox. We used to have them in that order. I no longer know what matters; would need to hear from Graham, but I'll be traveling and will probably lose track of this. And

221:

No, not the ones I've checked through. It seems that hitting "z" to go to the next division gets me out of the navbox most of the time, and if not, hitting "n" to get to the next non-link text will also work. I didn't think of moving to the next division to get out of navboxes before ... I'll keep it

190:

I can get close to the end of it with one keystroke. Moving to the first non-linked text moves me to the last item which happens to be a self-link for "suicide note", and moving to the next div tag moves me to the text "This box:", which is close enough to the end of the navbox. I can't move past the

1302:

Tagging would be a good idea ... complex animations make JAWS unresponsive. I have images turned off in my web browser to save bandwidth, but I realise that isn't an option for everyone using shared computers. I always thought that only still images were displayed on the Main Page with a link to the

1283:

I'd have no objection to tagging moving images as moving and letting users set a preference that they only want to see the first frames of animation; that might have value to people sensitive in one way or another, and it would also help people who prefer to avoid animation because of bandwidth. (I

1070:

element is nothing but a font-styling tag and has no semantic function at all. I just checked the current version of the W3C HTML specs, and for some reason it has not been deprecated according to the Index of Elements, but this is surely either a typographical error or other oversight, as all other

995:

P.S. But let's make it clear we're talking about article-space. On talk pages, it's common for people to leave a blank line between someone else's bullet point and their bullet point to enhance readability. If screen readers do a bad job reading this, then we should complain to the people who make

847:

They're not much of a problem, because as discussed above, they're easily skippable. They would e even easier to skip past if they were part of the infobox table. However the fact that they're collapsed by default makes them fairly easy to skip past with the arrow keys in screen readers that support

760:

The current ordering is the best way because it's how people would expect to find the results. The way they are displayed, however, is hideous for accessibility. Maybe it'd be better to have one table for the quarter-finals, another table for the semi-finals and so on. Either that or the table rows

300:

To make sure I follow. Vertical navboxes are now are OK after the infobox in the lead (although still preferred at the bottom of the article)? And if a vertical navbox is placed within another section, does it still need to be at the bottom of the section? Also, on updating this, the text is also

1410:

A lot of people browse Knowledge (XXG) on cellphones and PDAs these days. Some browse on Kindle, which has gray-scale only, no color. I imagine some people like to listen to articles from Knowledge (XXG) while they're driving. People who use small screens and screen readers would agree with the

420:

I don't thinkthis is as big a deal as spelling errors, broken tables, or things like that. I'd slighgtly prefer the image being before the navbox because a well-written image description will give important information for the article and I think the image is more important than a navbox. But this

387:

However, since the infobox is actually part of the article, then (per other comments on general principles on this page) we should probably not have first some article (infobox) — then some not-article (navbox) — and then go back for the rest of the article. But I'm (a) open to other arrangements

241:

Placing a vertical navbox at the end of the lead is a layout problem. It looks a bit strange to have the navbox start at the top of the table of contents instead of at the top of the page (when there are no other images and no other infoboxes present), and a long navbox (longer than the table of

383:

Sandy, I'd rather have your questions now, no matter how many, than a mess later. My intention was to put navboxes after infoboxes, because when both are present, the infobox is more important by far -- being, as it were, an actual part of the article instead of merely part of the navigation

957:

This is presumably just fine if you know exactly what a line-break is and believe that invisible HTML list tags are important. However, "no more than one line-break" may be misinterpreted as "no more than one blank line" by some readers, and the relevance of HTML list tags is non-obvious.

191:

navbox with the table navigation keys because it seems to be a one-column table which JAWS considers to be a layout table, and by default, JAWS does not count those. As for Suruena's question, I use infoboxes to get a piece of information quickly, but otherwise I just skip past them.

870:

We state here a requirement that unordered lists (those beginning with a bullet instead of a number) not have blank lines between them. There are good reasons for this that have absolutely nothing to do with access for disabled readers, and it's mentioned in other guidelines.

1547:

doesn't render well with JAWS. The images with no captions sound like "link graphic Compass_rose_pale.svg/50px-Compass_rose_pale.svg", the links for viewing, discussing, and editing the template get in the way, and it's hard to tell what direction you're reading about.

1411:

main thrust of this page, which seems to me to be, put things where people are expecting them to be, to aid navigation. Should we mention that the issues on this page have wide applicability? I think some people think of this page as having more limited scope. - Dan

646:... those tables are very hard for me to read, and I can only make some sense out of them because I know a bit about tennis and the fact that a set usually has six games. At the very least they need to have column and row headers. Am I right in my reading that 670:

Yes, you are correct. It seems to me that it might be better to flip the chart so the winners in the final round would appear/be read first? Of course, that would be counterintuitive for the average English reader who is used to reading left to right...

1568:

is the most accessible, but the table would be easier to use with row and column titles. When I navigate from east to southeast, I also hear the "southwest" part because JAWS thinks that's the title of the row. Speaking of directional templates, the

1268:

could cause problems for people with some photo-sensitive conditions like epilepsy - I don't have that, but I find them distracting. My preference would be to use a static version, and link to the moving image, with a caution in the link in place.

1161:

also sometimes depend heavily on the semantics of HTML elements not being violated. (I doubt that hCard in particular makes any use of these specific elements, but that's beside the point; who knows how many microformats their are or will be?)

820:

Are these an accessibility problem? Can they be improved by providing an anchor and/or skip link in the box, or by including it within the infobox table? Or is there a problem simply with having navigation near the beginning of an article?

696:

I'd expect the quarter-finals to be listed first in a chart like that. It's best to have them in chronological order. It's sort of interesting to find out if any of the top contenders were eliminated, or if there were any surprises.

1189:, etc. (other than for purposes of actual quotations, of course), since "scare-quoting" them is simply redundant; the markup itself already sets them apart as non-regular segment of the running prose. I.e., write "use <code: --> 115:

uses quick navigation keys that can jump to the next HTML element of a specific type, get out of the current HTML element or go to the next different HTML element. Other modern Windows screen readers, including the free

1153:(or rather one has a meaning and the other does not), and it is likely that some screen readers and other software (XML applications, and such) are already distinguishing between them, and have for some time. Inline 272:

Thanks for your response. Since it doesn't actually matter for accessibility, and it does matter for visual layout, then I'll change the guideline to list them after the infoboxes instead of after the lead's text.

242:

contents) can interfere with the text of the next section. If it really didn't cause any more trouble for you than the typical infobox, then I'd rather put the navboxes at the top of a section instead of the end.

342: 1125:, etc.). This should probably be undone by the developers, as there are often good semantic reasons to use these elements, especially in technical articles and in template documentation. Something for 539:) I can't think of any others right now, but I come across exactly that a lot. When the infofox isn't so long, or when there isn't an infobox, the horizontal nav works in the lead. The problem at 1521:). It is proposed that these two should be merged into the above. To my mind, the latter looks the most accessible, in that it includes compass-directions as text, and linearises properly. 207:

All the navboxes I found today (well, yesterday) are fundamentally tables. Can you give me an example of a page that you can't get past (or at least very close to the end of) the navbox?

98: 1375:

Or, Tell us if you ever see an article that is already using the static-link method! (I've never seen one.) Perhaps the policy should rather be changed to reflect actual practices/usage...

683: 578:

By complete coincidence I saw the bit where it says navboxes in the lead and came to question it here. I've never come across this. Sandy, are there any current FAs where it can be seen?

90: 85: 73: 68: 63: 1036:

Sounds good. I didn't realise that separating lists was mentioned in the Manual of Style when I wrote that section, but it needs to be mentioned in the accessibility guidelines as well.

516:

used in the lead? I've never encountered it, and I have looked at some thousands of articles. (Many of which, I admit, display properly standardized navboxes created by Arcadian.)

1284:

don't keep up with image issues; maybe this is possible already?) Tagging would be much preferable to discarding; animations are very important in sci/tech articles. - Dan

1361:

It helps quite a lot. I didn't know that policy prefers static images with links to animations in most cases; I'll mention that in my reviews when it comes up. - Dan

1061:

Someone or other seems to be confused about the meanings of some HTML entities. To give examples of source code snippets (like wiki markup, template code, etc.), use

21: 1225:; and you're right, so I'll try not to do so again. But microformats do not make use of HTML elements, other than generically, with a few specific exceptions ( 1386:, for example, are immensely informative/educational, and I'd be sorry to see them get removed by one level - where many readers will never discover them. -- 708: 462:

OK, so the preferred (not required) order is images before navboxes, and navboxes are now before the text, not after. I've updated this page as well as

1426:

Agreed. The more accessible a page is to "the disabled" (™), the more accessible it is to everyone, not least the people you list - and search engines.

929:

Yes, by default, JAWS and other screen readers signal the beginning and end of each list with "list of x items" and "list end". Therefore the lists in

1213: 1334:

Inline animations should be used sparingly; a static image with a link to the animation is preferred unless the animation has a very small file size.

1579:

shows the suburbs or towns surrounding a certain place, but it's hard to tell the directions of the towns with a screen reader. An example is at

952:

Do not separate list items by more than one line-break. If list items are separated by more than one line break, the HTML list tags will be ended

618: 625: 1340: 589: 1631: 1020: 1134:

That fact that most browsers (we cannot be certain that it is all of them, since I doubt anyone, including me, has possibly ever used

1344: 1573: 766: 1074:

A lot of other semantic (or "logical" as someone wrote in the guideline page – where'd that come from?) elements get confused with

388:

and (b) no longer certain that it makes sense to have infoboxes listed separately from navboxes at all. I invite other opinions.

51: 17: 595: 1347:

might be preferable(?), but it'd be good to have accessibility experts in on the discussion wherever it is. Hope that helps. --

1261: 874:

But is this actually an issue of accessibility? Does a screen reader signal the beginning of a list? For example, does this:

643: 256:

No it doesn't really matter where navboxes are placed. The trick for mooving past them I found isn't intuitive, but it works.

140: 1149:

as monospaced, non-proportional text, at the same size and otherwise styled identically, is irrelevant. They have different

1011:

indent discussions like this one actually generates definition list mark-up. I wonder if that's a good habit to perpetuate?

384:

infrastructure -- and should appear at the top of the article (instead of much further down the page or in a later section).

1611:

2.1 Ensure that all information conveyed with color is also available without color, for example from context or markup. -

1329: 1195:

to provide a reason for applying this template" would be severely wrong unless the single-quotes were part of the actual

1580: 1541: 1469: 1634: 1594: 1529: 1487: 1452: 1434: 1420: 1395: 1370: 1356: 1314: 1293: 1277: 1249: 1047: 1023: 1005: 990: 975: 944: 922: 907: 859: 780: 737: 665: 636: 599: 573: 555: 525: 482: 432: 415: 397: 378: 361: 338: 321: 282: 267: 251: 233: 216: 202: 177: 155: 144: 654:

in straight sets 6-2, 6-4, 6-1, in the first quarter-final? I'm not even going to try to read the rest of the table.

1619: 824:

We're currently discussing refurbishing a body of navigation templates for tanks and armoured fighting vehicles at

42: 1378:

Personally, I strongly support including the majority of animations directly within the article. The animation at

421:

shouldn't be a hard and fast rule ... if it looks better for the image to be below the navbox, then put it there.

543:

was that, because of the long infobox, moving the horizontal navbox to after the text left a huge white space.

583: 535:

article raised earlier in this discussion (the nominator has now moved that to the bottom, but lots of editors

117: 1618:

We should therefore discourage the use of colour (or shading-pattern) alone to convey information, as seen in

950:

Thanks, Graham. Then we should definitely keep this. However, the current text is not IMO ideal. It says,

1627: 1526: 1484: 1431: 1274: 1246: 1016: 734: 633: 128: 1562: 1511: 971: 903: 569: 551: 521: 478: 411: 393: 374: 357: 317: 278: 247: 212: 173: 825: 806: 346: 327:

Also, WhatamIdoing, I'm going to be traveling, so if this changes, if you don't mind, please make sure

1165:

If for some reason monospaced type is needed but it is not code, it is really more appropriate to use

1265: 898:

If there's no actual difference for disabled users, this should not be mentioned in this guideline.

814: 112: 802: 111:

I can't find a good place to fit this reply, so I've created a new section for it. My screen reader

1552: 1497: 579: 366:

eeek, a third question. WhatamIdoing, you put navboxes *before* images; are you sure about that?

1612: 467: 403:

I can't think of a sample off the top of my head, but I've seen all three crammed into one lead.

306: 122: 1623: 1589: 1522: 1480: 1427: 1391: 1352: 1309: 1270: 1242: 1097:

Presently, MediaWiki (or at least Knowledge (XXG)'s installation of it) actually does not accept

1042: 1012: 939: 854: 775: 730: 703: 660: 629: 427: 262: 228: 197: 136: 1443:

And a large number of people over 40 have a larger default font size on their computers. - Dan

672: 1476: 967: 899: 565: 544: 517: 471: 404: 389: 367: 350: 310: 274: 243: 208: 169: 463: 302: 1448: 1416: 1366: 1289: 1205: 1001: 986: 918: 837: 810: 651: 1126: 962: 809:

placed under the infobox of articles, for a long time. They are often used singly, as in

510: 332: 151:

And what about infoboxes? Do you usally skip them, or are a good summary of the article? —

1091: 164:

I think we're trying to solve a non-existent problem. Graham, could you take a look at

1196: 1585: 1387: 1348: 1305: 1168: 1038: 935: 850: 771: 699: 656: 647: 423: 258: 224: 193: 132: 1558:

reads OK linearly but it is still hard to figure out what direction everything is.

1193:' to provide a reason for applying this template" (and note that "use <code: --> 1154: 165: 152: 1260:

I'm no expert, but I think that moving images like a recent "picture of the day":

1117:, which we should ignore as being no different from deprecated obsolete junk like 1444: 1412: 1362: 1285: 997: 982: 914: 834: 762: 50:

If you wish to start a new discussion or revive an old one, please do so on the

1518: 1504: 1383: 328: 1071:

purely-presentational markup has been deprecated in favor of CSS since 1998.

120:, use a similar scheme. In JAWS, to get out of infoboxes, I press the ": --> 628:

which contain tables which seem to me to be very inaccessible. Thank you.

1475:

render in assistive browsers? Could it be improved? (For an example, see

1323:

Knowledge (XXG):Village pump (proposals)/Archive#Avoid movement in pages

1191:

to provide a reason for applying this template", not "use '<code: -->

1182:

version, just to better keep the content and the presentation separate.

560:

Ah, I see. So it's not so much that it's a horizontal navbox as it's a

540: 532: 1379: 1336:" (Though I haven't seen any articles that actually use this idea...) 1138:

browser in existence, and I'm a professional web developer) display

238:

So it shouldn't actually matter where the navboxes are placed then?

1158: 1613:

http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-color-convey

813:, and sometimes in multiples, for example, there are three in 29: 168:

and tell me whether you can skip the first template there?

123:

full list of JAWS keystrokes including Internet keystrokes

107:

How I navigate pages with JAWS and my thoughts on navboxes

470:; if anything changes, please sync those pages as well. 1094:). These all have distinguishable semantic purposes. 1322: 930: 536: 1330:

Knowledge (XXG):Image use policy#Displayed image size

848:

these hide/show buttons (and most modern ones do). .

828:, and I'd like to incorporate input from here. 961:Could we rephrase this to something like what 8: 1321:Notes: This was last discussed at length at 1477:Bergman, Edmonton#Surrounding_Neighborhoods 1233:) and none do or are likely to make use of 1185:PS: We should not use quotation marks with 506:Can you give me an example of a horizontal 1332:, which has stated since late 2005 that " 1341:Knowledge (XXG):Village pump (technical) 1303:animation, but that might have changed. 1241:other than as interchangeable elements. 763:this list of Sydney weather observations 729:to display them as the are at present. 48:Do not edit the contents of this page. 1345:Knowledge (XXG) talk:Image use policy 626:Category:Tournament bracket templates 7: 1264:and especially flashing images like 18:Knowledge (XXG) talk:Manual of Style 1620:List of Oasis band members#Timeline 1603:Use of colour to convey information 1328:The relevant policy section is at 28: 1199:required in the source code!). 1262:Image:Tablet press animation.gif 885:get read differently from this: 341:) knows so he can add it to the 33: 981:Agreed with all of that. - Dan 931:this version of Antonio Vivaldi 681: 674: 1519:Marylebone#Location in Context 797:Military history campaignboxes 673: 644:2005 U.S. Open - Men's Singles 1: 1635:21:48, 2 September 2008 (UTC) 1595:01:18, 2 September 2008 (UTC) 1530:19:12, 1 September 2008 (UTC) 1488:19:01, 1 September 2008 (UTC) 1461:Template: Geographic Location 1453:13:58, 1 September 2008 (UTC) 1435:08:22, 1 September 2008 (UTC) 1421:02:41, 1 September 2008 (UTC) 1396:03:51, 6 September 2008 (UTC) 1371:03:54, 2 September 2008 (UTC) 1357:19:48, 1 September 2008 (UTC) 1315:03:06, 1 September 2008 (UTC) 1294:02:24, 1 September 2008 (UTC) 1278:00:54, 1 September 2008 (UTC) 1250:00:28, 1 September 2008 (UTC) 1221:I've been guilty of misusing 1048:14:05, 1 September 2008 (UTC) 1024:11:41, 6 September 2008 (UTC) 1006:14:04, 1 September 2008 (UTC) 991:13:30, 1 September 2008 (UTC) 976:06:22, 1 September 2008 (UTC) 945:02:33, 1 September 2008 (UTC) 923:02:25, 1 September 2008 (UTC) 725:"best" in what way? It's not 619:16TeamBracket-Compact-Tennis5 1632:Andy Mabbett's contributions 1581:Nollamara, Western Australia 1021:Andy Mabbett's contributions 966:a separate, one-item list? 803:Military History Wikiproject 610:Tournament bracket templates 447:Update, navboxes before text 1216:23:25, 31 August 2008 (UTC) 908:22:47, 31 August 2008 (UTC) 860:01:49, 29 August 2008 (UTC) 826:WT:AFV#Navigation templates 781:03:47, 30 August 2008 (UTC) 738:08:17, 29 August 2008 (UTC) 709:05:50, 29 August 2008 (UTC) 684:03:10, 29 August 2008 (UTC) 666:03:09, 28 August 2008 (UTC) 637:19:30, 27 August 2008 (UTC) 600:06:44, 26 August 2008 (UTC) 574:00:41, 26 August 2008 (UTC) 556:22:53, 25 August 2008 (UTC) 526:22:48, 25 August 2008 (UTC) 483:13:11, 30 August 2008 (UTC) 433:10:27, 30 August 2008 (UTC) 416:04:59, 30 August 2008 (UTC) 398:04:53, 30 August 2008 (UTC) 379:03:09, 30 August 2008 (UTC) 362:03:07, 30 August 2008 (UTC) 322:03:05, 30 August 2008 (UTC) 283:02:58, 30 August 2008 (UTC) 268:00:49, 27 August 2008 (UTC) 252:19:56, 26 August 2008 (UTC) 234:11:16, 26 August 2008 (UTC) 217:06:31, 26 August 2008 (UTC) 203:06:09, 26 August 2008 (UTC) 178:21:44, 25 August 2008 (UTC) 156:14:51, 25 August 2008 (UTC) 145:14:38, 25 August 2008 (UTC) 1650: 996:the screen readers. - Dan 805:has been using navigation 769:is completely accessible. 1505:Chelmsford#Nearest places 1574:Infobox Australian Place 118:NonVisual Desktop Access 1382:, or the three used in 1176:text here</span: --> 1129:. I have ], actually. 1616: 1194:'reason='<code: --> 1015:(User:Pigsonthewing); 343:August monthly updates 1626:(aka Pigsonthewing); 1609: 1214:_is_not_<code: --> 1078:, as well, including 767:Bureau of Meteorology 624:and other members of 46:of past discussions. 1628:Talk to Andy Mabbett 1527:Talk to Andy Mabbett 1485:Talk to Andy Mabbett 1432:Talk to Andy Mabbett 1275:Talk to Andy Mabbett 1247:Talk to Andy Mabbett 1192:reason=<code: --> 1190:reason=<code: --> 1057:is not <code: --> 1017:Talk to Andy Mabbett 815:Operation Barbarossa 735:Talk to Andy Mabbett 634:Talk to Andy Mabbett 537:do what he had done. 1542:Geographic Location 1470:Geographic Location 1339:Discussing this at 841:2008-08-28 15:38 z 1178:) instead of the 1064:...</code: --> 1056:Note: <tt: --> 866:Relevance (lists) 842: 594: 588: 147: 131:comment added by 104: 103: 58: 57: 52:current talk page 1641: 1592: 1578: 1572: 1567: 1561: 1557: 1551: 1546: 1540: 1516: 1510: 1502: 1496: 1474: 1468: 1312: 1266:Image:Strobe.gif 1240: 1236: 1232: 1228: 1224: 1208: 1188: 1181: 1177: 1173:(a template for 1172: 1145: 1141: 1130: 1124: 1120: 1116: 1112: 1108: 1104: 1100: 1089: 1085: 1081: 1077: 1069: 1065: 1045: 942: 933:sound horrible. 857: 840: 811:Battle of Moscow 778: 706: 682: 679: 678: 663: 652:David Nalbandian 623: 617: 592: 586: 548: 515: 509: 475: 430: 408: 371: 354: 314: 265: 231: 200: 126: 82: 60: 59: 37: 36: 30: 1649: 1648: 1644: 1643: 1642: 1640: 1639: 1638: 1607:WCAG 1.0 says: 1605: 1590: 1576: 1570: 1565: 1559: 1555: 1549: 1544: 1538: 1514: 1508: 1500: 1494: 1472: 1466: 1463: 1408: 1310: 1258: 1238: 1234: 1230: 1226: 1222: 1204: 1186: 1179: 1174: 1166: 1143: 1139: 1131: 1122: 1118: 1114: 1110: 1106: 1102: 1098: 1087: 1083: 1079: 1075: 1067: 1062: 1059: 1043: 940: 868: 855: 799: 776: 704: 661: 621: 615: 612: 546: 513: 507: 501: 473: 449: 428: 406: 369: 352: 312: 263: 229: 198: 109: 78: 34: 26: 25: 24: 12: 11: 5: 1647: 1645: 1604: 1601: 1600: 1599: 1598: 1597: 1533: 1532: 1462: 1459: 1458: 1457: 1456: 1455: 1438: 1437: 1407: 1404: 1403: 1402: 1401: 1400: 1399: 1398: 1376: 1337: 1326: 1319: 1318: 1317: 1297: 1296: 1257: 1254: 1253: 1252: 1197:literal string 1058: 1054: 1053: 1052: 1051: 1050: 1031: 1030: 1029: 1028: 1027: 1026: 948: 947: 926: 925: 896: 895: 891: 890: 883: 882: 879: 867: 864: 863: 862: 798: 795: 794: 793: 792: 791: 790: 789: 788: 787: 786: 785: 784: 783: 747: 746: 745: 744: 743: 742: 741: 740: 716: 715: 714: 713: 712: 711: 689: 688: 687: 686: 611: 608: 607: 606: 605: 604: 603: 602: 580:Matthewedwards 500: 497: 496: 495: 494: 493: 492: 491: 490: 489: 488: 487: 486: 485: 448: 445: 444: 443: 442: 441: 440: 439: 438: 437: 436: 435: 385: 298: 297: 296: 295: 294: 293: 292: 291: 290: 289: 288: 287: 286: 285: 270: 239: 183: 182: 181: 180: 159: 158: 108: 105: 102: 101: 96: 93: 88: 83: 76: 71: 66: 56: 55: 38: 27: 15: 14: 13: 10: 9: 6: 4: 3: 2: 1646: 1637: 1636: 1633: 1629: 1625: 1621: 1615: 1614: 1608: 1602: 1596: 1593: 1588: 1587: 1582: 1575: 1564: 1563:Compass-table 1554: 1543: 1537: 1536: 1535: 1534: 1531: 1528: 1524: 1520: 1513: 1512:Compass-table 1506: 1499: 1492: 1491: 1490: 1489: 1486: 1482: 1478: 1471: 1460: 1454: 1450: 1446: 1442: 1441: 1440: 1439: 1436: 1433: 1429: 1425: 1424: 1423: 1422: 1418: 1414: 1405: 1397: 1393: 1389: 1385: 1381: 1380:Engine#Modern 1377: 1374: 1373: 1372: 1368: 1364: 1360: 1359: 1358: 1354: 1350: 1346: 1342: 1338: 1335: 1331: 1327: 1324: 1320: 1316: 1313: 1308: 1307: 1301: 1300: 1299: 1298: 1295: 1291: 1287: 1282: 1281: 1280: 1279: 1276: 1272: 1267: 1263: 1256:Moving images 1255: 1251: 1248: 1244: 1220: 1219: 1218: 1217: 1212: 1209: 1207: 1200: 1198: 1187:<code: --> 1183: 1175:<span: --> 1170: 1163: 1160: 1156: 1152: 1148: 1140:<code: --> 1137: 1132: 1128: 1119:<font: --> 1107:<code: --> 1103:<samp: --> 1095: 1093: 1092:documentation 1084:<samp: --> 1076:<code: --> 1072: 1063:<code: --> 1055: 1049: 1046: 1041: 1040: 1035: 1034: 1033: 1032: 1025: 1022: 1018: 1014: 1009: 1008: 1007: 1003: 999: 994: 993: 992: 988: 984: 980: 979: 978: 977: 973: 969: 964: 959: 955: 953: 946: 943: 938: 937: 932: 928: 927: 924: 920: 916: 913:Agree. - Dan 912: 911: 910: 909: 905: 901: 893: 892: 888: 887: 886: 880: 877: 876: 875: 872: 865: 861: 858: 853: 852: 846: 845: 844: 843: 839: 836: 829: 827: 822: 818: 816: 812: 808: 807:campaignboxes 804: 796: 782: 779: 774: 773: 768: 764: 759: 758: 757: 756: 755: 754: 753: 752: 751: 750: 749: 748: 739: 736: 732: 728: 724: 723: 722: 721: 720: 719: 718: 717: 710: 707: 702: 701: 695: 694: 693: 692: 691: 690: 685: 680: 677: 669: 668: 667: 664: 659: 658: 653: 649: 648:Roger Federer 645: 641: 640: 639: 638: 635: 631: 627: 620: 609: 601: 597: 591: 585: 581: 577: 576: 575: 571: 567: 563: 559: 558: 557: 553: 549: 542: 538: 534: 530: 529: 528: 527: 523: 519: 512: 504: 498: 484: 480: 476: 469: 465: 461: 460: 459: 458: 457: 456: 455: 454: 453: 452: 451: 450: 446: 434: 431: 426: 425: 419: 418: 417: 413: 409: 401: 400: 399: 395: 391: 386: 382: 381: 380: 376: 372: 365: 364: 363: 359: 355: 348: 344: 340: 337: 334: 330: 326: 325: 324: 323: 319: 315: 308: 304: 284: 280: 276: 271: 269: 266: 261: 260: 255: 254: 253: 249: 245: 240: 237: 236: 235: 232: 227: 226: 220: 219: 218: 214: 210: 206: 205: 204: 201: 196: 195: 189: 188: 187: 186: 185: 184: 179: 175: 171: 167: 163: 162: 161: 160: 157: 154: 150: 149: 148: 146: 142: 138: 134: 130: 124: 119: 114: 106: 100: 97: 94: 92: 89: 87: 84: 81: 77: 75: 72: 70: 67: 65: 62: 61: 53: 49: 45: 44: 39: 32: 31: 23: 22:Accessibility 19: 1624:Andy Mabbett 1617: 1610: 1606: 1584: 1523:Andy Mabbett 1481:Andy Mabbett 1464: 1449:send/receive 1428:Andy Mabbett 1417:send/receive 1409: 1367:send/receive 1333: 1304: 1290:send/receive 1271:Andy Mabbett 1259: 1243:Andy Mabbett 1210: 1203: 1201: 1184: 1171:|text here}} 1164: 1155:microformats 1150: 1146: 1135: 1133: 1111:<var: --> 1099:<kbd: --> 1096: 1088:<var: --> 1080:<kbd: --> 1073: 1060: 1037: 1013:Andy Mabbett 1002:send/receive 987:send/receive 968:WhatamIdoing 960: 956: 951: 949: 934: 919:send/receive 900:WhatamIdoing 897: 884: 873: 869: 849: 832: 830: 823: 819: 800: 770: 731:Andy Mabbett 726: 698: 675: 655: 630:Andy Mabbett 613: 566:WhatamIdoing 561: 518:WhatamIdoing 505: 502: 422: 390:WhatamIdoing 335: 309:, I think. 299: 275:WhatamIdoing 257: 244:WhatamIdoing 223: 209:WhatamIdoing 192: 170:WhatamIdoing 166:Suicide note 110: 79: 47: 41: 1206:SMcCandlish 1180:<tt: --> 1144:<tt: --> 1115:<tt: --> 1068:<tt: --> 894:Second item 881:Second item 676:L'Aquatique 614:Please see 347:WP:SIGNPOST 127:—Preceding 40:This is an 1553:GeoCompass 1498:GeoCompass 1384:Horse gait 1123:<b: --> 889:First item 878:First item 727:accessible 99:Archive 10 1517:(used on 1503:(used on 1493:See also 1465:How does 765:from the 564:navbox. 468:WP:LAYOUT 307:WP:LAYOUT 222:in mind. 91:Archive 6 86:Archive 5 80:Archive 4 74:Archive 3 69:Archive 2 64:Archive 1 1388:Quiddity 1349:Quiddity 1151:meanings 1147:visually 831:Thanks. 642:Like at 590:contribs 503:Sandy, 499:Sidebars 345:for the 339:contribs 141:contribs 133:Graham87 129:unsigned 20:‎ | 1507:); and 1343:and/or 1211:‹(-¿-)› 1105:, only 1066:. The 835:Michael 547:Georgia 541:AMX-30E 533:AMX-30E 474:Georgia 464:WP:LEAD 407:Georgia 370:Georgia 353:Georgia 313:Georgia 303:WP:LEAD 153:surueña 43:archive 1586:Graham 1445:Dank55 1413:Dank55 1363:Dank55 1306:Graham 1286:Dank55 1215:": --> 1127:WP:VPT 1039:Graham 998:Dank55 983:Dank55 963:WP:MOS 936:Graham 915:Dank55 851:Graham 772:Graham 700:Graham 657:Graham 511:navbox 424:Graham 259:Graham 225:Graham 194:Graham 1406:Scope 1159:hCard 1157:like 1136:every 1113:(and 650:beat 596:email 545:Sandy 472:Sandy 405:Sandy 368:Sandy 351:Sandy 329:Tony1 311:Sandy 16:< 1392:talk 1353:talk 1235:CODE 1231:ABBR 1169:Mono 1142:and 1109:and 1086:and 972:talk 954:. 904:talk 801:The 584:talk 570:talk 562:tiny 552:Talk 531:The 522:talk 479:Talk 466:and 412:Talk 394:talk 375:Talk 358:Talk 333:talk 318:Talk 305:and 279:talk 248:talk 213:talk 174:talk 137:talk 113:JAWS 1479:). 1237:or 1101:or 349:. 301:at 1630:; 1622:. 1591:87 1583:. 1577:}} 1571:{{ 1566:}} 1560:{{ 1556:}} 1550:{{ 1545:}} 1539:{{ 1525:| 1515:}} 1509:{{ 1501:}} 1495:{{ 1483:| 1473:}} 1467:{{ 1451:) 1430:| 1419:) 1394:) 1369:) 1355:) 1311:87 1292:) 1273:| 1245:| 1239:TT 1229:, 1223:TT 1202:— 1167:{{ 1121:, 1082:, 1044:87 1019:; 1004:) 989:) 974:) 941:87 921:) 906:) 856:87 838:Z. 817:. 777:87 733:| 705:87 662:87 632:| 622:}} 616:{{ 598:) 572:) 554:) 524:) 514:}} 508:{{ 481:) 429:87 414:) 396:) 377:) 360:) 320:) 281:) 264:87 250:) 230:87 215:) 199:87 176:) 143:) 139:• 125:. 95:→ 1447:( 1415:( 1390:( 1365:( 1351:( 1288:( 1227:A 1090:( 1000:( 985:( 970:( 917:( 902:( 833:— 593:• 587:• 582:( 568:( 550:( 520:( 477:( 410:( 392:( 373:( 356:( 336:· 331:( 316:( 277:( 246:( 211:( 172:( 135:( 54:.

Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.