782:
think that's important even if some some of our visually impaired readers have been blind since birth. I am not visually impaired and I don't use screen readers. The reason I am writing is to ask for suggestions of things to avoid when writing alt text. Things that bother you in alt text that you wish the writers would not do. That way I could better understand things from the perspective of a person who uses alt text. By the way, I've also started to use AI image generators to see how well my descriptions can duplicate the image. It's an interesting experiment and the results suggest that a picture requires far far more than a thousands words to describe as is commonly said. Nevertheless, most of the time the descriptions are reasonable approximations.
350:
318:
1768:(thank the forces that be) doesn't display the name of each typeface in that typeface. But some people, when they create or see a list of countries, they feel the impulse to prefix each name with the country's flag, as though every mention of a country merits another reminder to the reader of what that country's flag looks like. This situation is the same. It's an encyclopedia, not a font catalog or sports journal or score sheet. Identify typefaces, countries, routes, teams, etc., by name, without decoration. And not only do the color embellishments serve no useful purpose but, as you note, they break accessibility.
478:
460:
1116:
388:
329:
544:
520:
287:
422:
256:
336:
1209:. That is to say, line breaks are acceptable when they actually represent semantic breaks in content, perhaps roughly equivalent to a paragraph break. They should neither be used to create the appearance of lists nor to manually wrap a single block of text, but beyond that there are actually plenty of plausible applications. Infobox templates themselves actually use them a lot under the hood.
328:
335:
853:. I'm thinking though that it would likely be more straightforward to just always have the alt text be something like "archiving icon". I've searched through pages that make use of the "alt" parameter. It's rarely used and when it is used, it is usually "Icon of a filing cabinet". I've listed several examples of its usage below.
1536:
The operative sentence uses the word "blinking" in a manner I find to be a bit vague: I would intuit some distinction many people would perceive between "blinking", merely "looping", and "ongoing" animated content in terms of its potential to interfere with their ability to focus or comfortably read?
1517:
Moving content can also be a severe distraction for some people. Certain groups, particularly those with attention deficit disorders, find blinking content distracting, making it difficult for them to concentrate on other parts of the Web page. Five seconds was chosen because it is long enough to get
781:
Dear visually impaired readers of
Knowledge. I sometimes add alt text to images to aid accessibility. I aim to be as succinct as possible while also being as correct as possible. The latter goal tends to make the descriptions lengthier but I try to keep them under 250 words. I mention color because I
1664:
uses white text on a orange background extensively. Orange text or backgrounds are particularly problematic because white on orange fails WCAG 2.x contrast test, but some people find orange on black harder to read. The logo doesn't need to meet contrast, but text does. The best practice would likely
1278:
Line breaks are for visual appearance only, and so semantically they are equivalent to whitespace. Appropriate semantic markup should be used as applicable. Line breaks should be used sparingly. As browser widths change or other elements are added to the page, the page will automatically be laid out
729:
the max-height vertical scroller can be a bit of a problem for screenreader users on mobile phones, as having a vertical scroller within a vertical scroller can be confusing for discovery, but as long as there are no controls inside the vertical scroller, that too seems unlikely to cause a problem. —
1653:
I notice a lot of issues on
Knowledge where text has contrast issues because someone has duplicated team or transit route colors. Do we want to specifically mention that using team and transit colors for text is not exempt from meeting contrast requirements, and that accessibility takes precedence
1580:
It doesn't only say blinking, it also says moving or scrolling. The area of concern is "The intent of this
Success Criterion is to avoid distracting users during their interaction with a Web page." Long form animations need to be done via a pauseable video rather than by an uncontrollable animated
728:
All sticky headings use pure CSS. For screenreader users it should be just fine because of that. If anything, it's more likely to be a problem for people with partial blindness or for older users etc, as the position of the element changes, which might be confusing to some. I can also imagine that
1696:
The color #FFFFFF (white) on #4EC3E0 (light blue) has a contrast of 2.05:1, which fails for text at all sizes. This issue is complicated that the icon is supplied by the government of Mexico City, but the license permits modification, such as making the "1" black instead of white (changing
1189:
I have seen this sort of visual break in many articles that I have edited, especially less cared ones, but how should it be handled? is it COMPLETELY discouraged it, even for use cases where there is legitemately no factor other than aesthetics or what to do instead?
993:
If the template allows the image to be chosen on the page where it's used, an editor can choose an image that is not public domain or available under an equivalent license. All creative commons images need to link to the page with their attribution information.
1562:
As I understood it at the time that the HTML BLINK element was first deprecated, it's because certain blink rates can trigger seizures. I've never heard of a looped animation doing that, unless the animation is essentially two images displayed alternately.
713:
They generally work fine here. The only exception is JAWS under Chrome, but I think that's a JAWS issue and not a problem with the tables per se ... the combination of JAWS and Chrome is having problems with all sorts of tables at the moment.
1745:
for an example. (Some ice hockey editors don't like how it looks, while others do, but the consensus has held.) I feel this approach is a reasonable tradeoff between visual design goals, and should be considered for other similar scenarios.
1605:
Moving content can also be a severe distraction for some people. Certain groups, particularly those with attention deficit disorders, find blinking content distracting, making it difficult for them to concentrate on other parts of the Web
1760:
I don't see the point of it. It's a digression. I mean, I guess the people doing it think it adds a coolness factor, but this isn't TikTok. We aren't here to be cool, and we're here to be informative, and coolness is a distraction from
1490:
From what I understand, and I'm woefully underread in the literature so this is partially anecdotal so forgive me, there is a significant distinction in accessibility between short animations that loop and long animations.
1248:
It's incomplete at the moment, and I like the idea that others would link such things rather than me if they find it useful so that only useful things get linked, so if you think it would help others then go for it!
875:
1599:
Content that moves or auto-updates can be a barrier to anyone who has trouble reading stationary text quickly as well as anyone who has trouble tracking moving objects. It can also cause problems for screen
1513:
Content that moves or auto-updates can be a barrier to anyone who has trouble reading stationary text quickly as well as anyone who has trouble tracking moving objects. It can also cause problems for screen
1071:
Typically, though, there would already be a text heading or description conveying the same information. In that case, having alt text on the decorative image that replicates the text is superfluous.
1537:
Later, "blinking" is defined as "content that causes a distraction problem", which is unfortunately a bit circular for our purposes. If blinking is coterminous with moving, why isn't moving used?
1343:
I would put it on the doc page as well. If there's not a maintenance category for templates with accessibility issues, maybe it should be created and populated! I would personally appreciate that.
804:
Thanks very much for this. As a totally blind person from birth, I can't think of anything to add but I find it hard to evaluate alt text because I don't know what I'm missing; see my comments in
1319:
template has major issues with contrast. But if I place the template at the top of the template itself, it will appear on dozens of pages, which would be disruptive. I wound up placing it on the
1186:
template into the HTML line break, as this was not being used for a list but as a visual break for the default size, separating the series title from the year in a table, for visual harmony.
1717:
1337:
89:
1648:
1294:
489:, a group of editors promoting better access for disabled or otherwise disadvantaged users. For more information, such as what you can do to help, see the main project page.
573:
247:
700:
175:
1741:
Many years ago, the ice hockey WikiProject moved to using colour borders instead of colour backgrounds in order to improve accessibility (including legibility). See
1612:
The first point is about moving content in general, and doesn't really apply to our conversation about looping GIFs in particular. The second specifically discusses
805:
643:
762:
This seems out of date; it works just fine on my phone or when I try the mobile preview on my computer. I'll remove it for now but let me know if anyone objects.
652:
243:
239:
235:
231:
227:
223:
219:
215:
211:
207:
203:
199:
195:
191:
187:
183:
179:
1132:
1085:
If the image in a template like this needs to be linked for attribution, it'd be better if there was alt text on the image (despite its slight redundancy).
850:
659:) were not a problem. You said: "it doesn't affect totally blind screen reader users." Those were a particular set of scrolling tables discussed here:
1459:
441:
669:
I want to know if this is also true for the scrolling tables (from a different template) in this version of a list article with 3 scrolling tables:
771:
1419:
Rather than risking getting into an edit war, I am moving the matter here to attempt to gain consensus on wording before proposing a final edit.
1106:
979:
Purely decorative images should have no link and no alt text according to accessibility experts since ever. What's the concern with that option?
1777:
1143:
555:, a collaborative effort to improve Knowledge's help documentation for readers and contributors. If you would like to participate, please visit
849:
has a little filing cabinet icon, but this can be changed to anything. An alt parameter and link parameter were added after this edit request:
1636:
1590:
1485:
1409:
1363:
959:
1747:
1280:
1155:
1072:
1755:
1736:
1395:
1377:
817:
723:
412:
683:
1792:
1575:
1269:
1243:
1229:
1670:
The color #FFFFFF (white) on #F15C22 (orange) has a contrast of 3.33:1, which fails for text smaller than 18.66px bold or 24px not bold.
1557:
1386:
Thank you! I've moved it to the template documentation as well as added it to a related template. That's what I will do moving forward.
1234:
oh, that's actually a great essay! if you think it is appropriate please link it on the section, that's exactly what I was looking for.
746:
1288:
1080:
791:
663:
124:
1094:
974:
624:
1066:
1465:
Suffice it to say, this does require conversation as almost no one operates based on this understanding, even if it's well-founded.
606:
27:
1005:
988:
758:
Note that mobile versions of the website do not support collapsing, so any collapsible content will automatically be uncollapsed.
74:
1320:
1199:
435:
673:
1807:
1802:
614:
323:
130:
832:
parameters for selectable images, but what about a template where the image should be purely decorative? Should it have an
255:
1137:
1022:
to an empty string can be a problem. If use of the image requires attribution (this includes, but is not limited to, the
937:
883:
485:
465:
1428:
Looping GIFs are permitted as long as they stop looping such that the total animation time is 5.0 seconds or less. So:
1368:
Place it in the template, either in the documentation, or if it doesn't, then at the bottom between the noinclude tags.
1688:
823:
1681:
1403:
1313:
430:
1724:
1173:
1050:
to an empty string does not, of itself, violate any policies so is much less of an issue. But if Graham87 suggests
1036:
Except for public-domain images, it must always be possible for the reader to reach the image-description page, so
767:
34:
1797:
901:
600:
70:
17:
1518:
a user's attention, but not so long that a user cannot wait out the distraction if necessary to use the page.
349:
317:
119:
1705:
in the SVG code). But it might be simpler and less distracting to use actual text rather than an SVG image.
1030:
licenses), we must be able to reach the file description page so that the attribution may be seen. Indeed,
674:
https://en.wikipedia.org/search/?title=List_of_countries_by_firearm-related_death_rate&oldid=1232941127
445:
of
Knowledge's policy and guideline documents is available, offering valuable insights and recommendations.
397:
298:
1742:
1279:
differently by browsers, and manual overrides can work against this process producing a pleasing result.
1206:
763:
742:
560:
110:
365:(MoS) guidelines by addressing inconsistencies, refining language, and integrating guidance effectively.
170:
1764:
When we have a list of the names of fruits, we don't precede each one by an icon depicting the fruit.
155:
929:
401:
362:
357:
1713:
1586:
1455:
1391:
1333:
656:
405:
270:
1120:
1108:
828:
How should a template handle alt text on an icon, if the icon can be changed? Some templates need
752:
361:, a collaborative effort focused on enhancing clarity, consistency, and cohesiveness across the
1326:
It would be good to clarify this in the text as to where it would best be placed in templates.
776:
556:
551:
525:
400:
procedure and is given additional attention, as it closely associated to the
English Knowledge
148:
1492:
1424:
Technique G152: Setting animated gif images to stop blinking after n cycles (within 5 seconds)
1309:
template at the top of articles with contrast issues. What about templates. For example, the
1018:
parameters are unrelated; the value of one does not affect the meaning of the other. Setting
787:
696:
304:
1773:
1303:
477:
459:
1687:
themes colors by route and mode. Several of the routes use insufficient contrast, such as
1595:
I'm just trying to fully understand what SC 2.2.2 says and why. Most concretely, it says:
8:
1709:
1661:
1582:
1571:
1451:
1387:
1329:
1239:
1195:
1128:
1062:
100:
1723:
These colors have always been horrible, and not only for accessibility reasons. Look at
1423:
1628:
1549:
1477:
1355:
1261:
1221:
1090:
1001:
970:
955:
919:
893:
813:
719:
140:
115:
1765:
911:
839:
I'm asking about general best practices but will link examples that brought this up.
96:
1751:
1732:
1373:
1284:
1160:
1076:
948:
Useful parameter or simpler to use standardized alt text regardless of icon image?
843:
799:
783:
708:
690:
442:
guidance on how to contribute to the development and revision of
Knowledge policies
1031:
876:
Knowledge talk:WikiProject
Computing/Computer Programming task force/Archive Index
1769:
1448:
Hope that makes it clear (which I believe the current page wording does not do).
1416:
with the comment "This is confusing to me: are looping GIFs simply not allowed?"
738:
33:"WT:COLOR" and "WT:COLOUR" redirect here. For WikiProject Color's talk page, see
1564:
1235:
1191:
1161:
1151:
1124:
1055:
984:
266:
1786:
1618:
1539:
1467:
1413:
1345:
1251:
1211:
1086:
966:
809:
715:
648:
568:
387:
1180:
1728:
1369:
995:
949:
543:
519:
653:
Talk:COVID-19 pandemic deaths/Archive 1#Scrolling versus expanded tables
271:
730:
563:
and see a list of open tasks. To browse help related resources see the
26:"WT:ACCESS" redirects here. For the related wikiproject talk page, see
1691:, which has white on light blue, which violates contrast at all sizes.
1147:
980:
564:
851:
Template talk:Archives/Archive 1#Accessibility improvement for image
684:
Help:Table/Advanced#Table with sticky header in simple scroll window
429:
For information on
Knowledge's approach to the establishment of new
1027:
421:
268:
1144:
Knowledge talk:Manual of Style § Mobile skin and block quotations
965:
Yeah making the alt text "Archiving icon" sounds sensible to me.
664:
Help:Table/Advanced#Advanced scrolling tables with sticky headers
1205:
Not to hock my own slogan, but essentially as I understand it,
272:
1023:
836:
parameter, or should it use the same alt text consistently?
59:
Please place new discussions at the bottom of the talk page.
1649:
Do we need to call out team and transit colors under color?
1295:
Where to place accessibility templates on problem templates
1438:
A 2 or 2.5 second long animated GIF could only loop twice
1616:, which is the distinction I'm currently unclear about.
1444:
Endlessly looping animated GIFs are not permitted at all
1168:
are there any acceptable uses for the HTML line break
1410:
Animations: Clarified 5 seconds as total playing time
644:
Accessibility of scrolling tables. Different template
605:
This page does not require a rating on the project's
679:
This method for scrolling tables is discussed here:
655:, that the scrolling tables in the related article (
65:
1441:A 3 second long animated GIF could not loop at all
1435:A 1.5 second long animated GIF could loop 3 times
1784:
1727:, the hyperlink in title is completely hidden.
1432:A 1 second long animated GIF could loop 5 times
415:carefully and exercise caution when editing.
1321:Transport in Mexico City template talk page
572:
1299:The section on color suggests placing the
1119:You are invited to join the discussion at
1146:. Please feel free to participate there.
297:does not require a rating on Knowledge's
355:This page falls within the scope of the
28:Knowledge talk:WikiProject Accessibility
14:
1785:
579:and a volunteer will visit you there.
549:This page is within the scope of the
411:Contributors are urged to review the
371:Knowledge:WikiProject Manual of Style
1665:be to abandon the orange background.
1502:
880:File:Replacement filing cabinet.svg
408:. Both areas are subjects of debate.
374:Template:WikiProject Manual of Style
286:
284:
280:
52:
39:
1142:Page watchers may be interested in
938:File:Replacement filing cabinet.svg
884:File:Replacement filing cabinet.svg
495:Knowledge:WikiProject Accessibility
303:It is of interest to the following
73:for discussing improvements to the
23:
1793:WikiProject Accessibility articles
498:Template:WikiProject Accessibility
420:
386:
24:
1819:
483:This page is within the scope of
1725:Template:Geelong Football League
1138:Mobile skin and block quotations
1114:
651:. You noted in this discussion,
542:
518:
476:
458:
348:
334:
327:
316:
285:
254:
90:Click here to start a new topic.
35:Knowledge talk:WikiProject Color
1054:, I would go with that 100%. --
824:Alt text for icons in templates
588:Template:Knowledge Help Project
1778:17:13, 28 September 2024 (UTC)
1756:16:22, 28 September 2024 (UTC)
1737:21:32, 27 September 2024 (UTC)
1718:21:24, 27 September 2024 (UTC)
1637:10:04, 27 September 2024 (UTC)
1591:09:57, 27 September 2024 (UTC)
1576:08:20, 27 September 2024 (UTC)
1558:07:22, 27 September 2024 (UTC)
1486:07:13, 27 September 2024 (UTC)
1460:07:11, 27 September 2024 (UTC)
1404:Looping GIFs and accessibility
1396:07:21, 27 September 2024 (UTC)
1378:08:31, 26 September 2024 (UTC)
1364:07:04, 26 September 2024 (UTC)
1338:06:14, 26 September 2024 (UTC)
1289:18:40, 19 September 2024 (UTC)
1270:12:56, 19 September 2024 (UTC)
1244:12:49, 19 September 2024 (UTC)
1230:12:24, 19 September 2024 (UTC)
1200:12:21, 19 September 2024 (UTC)
1121:WP:HD § Accessibility question
1109:WP:HD § Accessibility question
902:File:Oregon DEM relief map.gif
575:ask for help on your talk page
18:Knowledge talk:Manual of Style
13:
1:
1156:04:07, 7 September 2024 (UTC)
1095:09:10, 8 September 2024 (UTC)
1081:15:43, 7 September 2024 (UTC)
1067:09:16, 7 September 2024 (UTC)
1006:04:33, 7 September 2024 (UTC)
989:04:10, 7 September 2024 (UTC)
87:Put new text under old text.
75:Manual of Style/Accessibility
1808:Knowledge Help Project pages
1803:Mid-importance Help articles
924:License plate reading "JCT"
619:This page has been rated as
7:
1743:Template:Montreal Canadiens
1493:SC 2.2.2: Pause, Stop, Hide
1133:07:40, 28 August 2024 (UTC)
975:04:04, 24 August 2024 (UTC)
960:20:51, 23 August 2024 (UTC)
818:15:30, 13 August 2024 (UTC)
792:10:21, 13 August 2024 (UTC)
95:New to Knowledge? Welcome!
10:
1824:
625:project's importance scale
396:This page falls under the
138:
32:
25:
1629:
1550:
1478:
1356:
1262:
1222:
1169:
1040:should be used only with
942:Icon of a filing cabinet
934:Icon of a filing cabinet
930:User talk:XAM2175/2023/06
888:Icon of a filing cabinet
869:
866:
863:
860:
772:19:13, 27 July 2024 (UTC)
618:
604:
559:, where you can join the
537:
486:WikiProject Accessibility
471:
428:
394:
358:Knowledge:Manual of Style
343:
311:
125:Be welcoming to newcomers
46:Skip to table of contents
1682:Transport in Mexico City
1654:over non-logo branding?
1323:at the top of my topic.
1314:Transport in Mexico City
747:08:15, 8 July 2024 (UTC)
724:14:32, 6 July 2024 (UTC)
701:14:22, 6 July 2024 (UTC)
657:COVID-19 pandemic deaths
377:Manual of Style articles
45:
431:policies and guidelines
764:Closed Limelike Curves
585:Knowledge:Help Project
552:Knowledge Help Project
501:Accessibility articles
425:
391:
120:avoid personal attacks
1798:B-Class Help articles
1174:a recent edit of mine
424:
406:article titles policy
390:
248:Auto-archiving period
906:Small map of Oregon
753:Collapsing on mobile
1662:Geelong West Giants
1052:|alt=Archiving icon
857:
777:Alt text for images
1422:WCAG 2.1 provides
1176:, I substituted a
920:File:Jct plate.svg
894:User talk:Jsayre64
856:
426:
413:awareness criteria
398:contentious topics
392:
299:content assessment
131:dispute resolution
92:
60:
1766:List of typefaces
1531:
1530:
1207:break means pause
946:
945:
912:Template talk:Jct
639:
638:
635:
634:
631:
630:
513:
512:
509:
508:
453:
452:
449:
448:
279:
278:
111:Assume good faith
88:
64:
63:
58:
51:
50:
1815:
1704:
1700:
1686:
1680:
1674:Transit example
1635:
1633:
1627:
1623:
1614:blinking content
1607:
1601:
1567:
1556:
1554:
1548:
1544:
1503:
1484:
1482:
1476:
1472:
1412:was reverted by
1362:
1360:
1354:
1350:
1318:
1312:
1308:
1302:
1268:
1266:
1260:
1256:
1228:
1226:
1220:
1216:
1185:
1179:
1171:
1118:
1117:
1058:
1053:
1049:
1043:
1039:
1021:
1017:
1013:
998:
952:
858:
855:
848:
842:
835:
831:
803:
734:
712:
593:
592:
589:
586:
583:
578:
557:the project page
546:
539:
538:
533:
530:
522:
515:
514:
503:
502:
499:
496:
493:
480:
473:
472:
462:
455:
454:
439:. Additionally,
379:
378:
375:
372:
369:
352:
345:
344:
339:
338:
337:
332:
331:
330:
320:
313:
312:
290:
289:
288:
281:
273:
259:
258:
249:
158:
156:WT:ACCESSIBILITY
151:
66:
53:
40:
1823:
1822:
1818:
1817:
1816:
1814:
1813:
1812:
1783:
1782:
1702:
1698:
1689:Cablebús line 1
1684:
1678:
1651:
1625:
1619:
1617:
1604:
1598:
1565:
1546:
1540:
1538:
1474:
1468:
1466:
1406:
1352:
1346:
1344:
1316:
1310:
1306:
1300:
1297:
1258:
1252:
1250:
1218:
1212:
1210:
1183:
1177:
1166:
1140:
1115:
1112:
1056:
1051:
1047:
1041:
1037:
1019:
1015:
1011:
996:
950:
846:
840:
833:
829:
826:
806:this discussion
797:
779:
755:
732:
706:
646:
590:
587:
584:
581:
580:
531:
528:
500:
497:
494:
491:
490:
402:Manual of Style
376:
373:
370:
368:Manual of Style
367:
366:
363:Manual of Style
333:
326:
324:Manual of Style
275:
274:
269:
246:
164:
163:
162:
161:
154:
147:
143:
136:
106:
38:
31:
22:
21:
20:
12:
11:
5:
1821:
1811:
1810:
1805:
1800:
1795:
1781:
1780:
1762:
1758:
1739:
1710:Thisisnotatest
1707:
1706:
1703:fill="#000000"
1699:fill="#FFFFFF"
1693:
1692:
1672:
1671:
1667:
1666:
1650:
1647:
1646:
1645:
1644:
1643:
1642:
1641:
1640:
1639:
1615:
1610:
1609:
1608:
1602:
1583:Thisisnotatest
1578:
1529:
1528:
1525:
1524:
1523:
1522:
1521:
1519:
1515:
1507:
1501:
1500:
1499:
1498:
1496:
1452:Thisisnotatest
1446:
1445:
1442:
1439:
1436:
1433:
1405:
1402:
1401:
1400:
1399:
1398:
1388:Thisisnotatest
1381:
1380:
1366:
1330:Thisisnotatest
1296:
1293:
1292:
1291:
1276:
1275:
1274:
1273:
1272:
1165:
1159:
1139:
1136:
1111:
1107:Discussion at
1105:
1104:
1103:
1102:
1101:
1100:
1099:
1098:
1097:
1008:
977:
944:
943:
940:
935:
932:
926:
925:
922:
917:
914:
908:
907:
904:
899:
896:
890:
889:
886:
881:
878:
872:
871:
868:
865:
862:
825:
822:
821:
820:
778:
775:
760:
759:
754:
751:
750:
749:
726:
687:
686:
677:
676:
667:
666:
645:
642:
637:
636:
633:
632:
629:
628:
621:Mid-importance
617:
611:
610:
603:
597:
596:
594:
582:Knowledge Help
569:Help Directory
547:
535:
534:
532:Mid‑importance
526:Knowledge Help
523:
511:
510:
507:
506:
504:
481:
469:
468:
463:
451:
450:
447:
446:
427:
417:
416:
410:
393:
383:
382:
380:
353:
341:
340:
321:
309:
308:
302:
291:
277:
276:
267:
265:
264:
261:
260:
166:
165:
160:
159:
152:
144:
139:
137:
135:
134:
127:
122:
113:
107:
105:
104:
93:
84:
83:
80:
79:
78:
62:
61:
56:
49:
48:
43:
15:
9:
6:
4:
3:
2:
1820:
1809:
1806:
1804:
1801:
1799:
1796:
1794:
1791:
1790:
1788:
1779:
1775:
1771:
1767:
1763:
1759:
1757:
1753:
1749:
1744:
1740:
1738:
1734:
1730:
1726:
1722:
1721:
1720:
1719:
1715:
1711:
1695:
1694:
1690:
1683:
1677:
1676:
1675:
1669:
1668:
1663:
1660:
1659:
1658:
1657:Team example
1655:
1638:
1634:
1632:
1624:
1622:
1613:
1611:
1603:
1597:
1596:
1594:
1593:
1592:
1588:
1584:
1579:
1577:
1573:
1569:
1561:
1560:
1559:
1555:
1553:
1545:
1543:
1535:
1534:
1533:
1532:
1526:
1520:
1516:
1512:
1511:
1510:
1509:
1508:
1505:
1504:
1497:
1494:
1489:
1488:
1487:
1483:
1481:
1473:
1471:
1464:
1463:
1462:
1461:
1457:
1453:
1449:
1443:
1440:
1437:
1434:
1431:
1430:
1429:
1426:
1425:
1420:
1417:
1415:
1411:
1397:
1393:
1389:
1385:
1384:
1383:
1382:
1379:
1375:
1371:
1367:
1365:
1361:
1359:
1351:
1349:
1342:
1341:
1340:
1339:
1335:
1331:
1327:
1324:
1322:
1315:
1305:
1290:
1286:
1282:
1277:
1271:
1267:
1265:
1257:
1255:
1247:
1246:
1245:
1241:
1237:
1233:
1232:
1231:
1227:
1225:
1217:
1215:
1208:
1204:
1203:
1202:
1201:
1197:
1193:
1187:
1182:
1175:
1163:
1158:
1157:
1153:
1149:
1145:
1135:
1134:
1130:
1126:
1122:
1110:
1096:
1092:
1088:
1084:
1083:
1082:
1078:
1074:
1070:
1069:
1068:
1064:
1060:
1045:
1033:
1029:
1025:
1009:
1007:
1003:
999:
992:
991:
990:
986:
982:
978:
976:
972:
968:
964:
963:
962:
961:
957:
953:
941:
939:
936:
933:
931:
928:
927:
923:
921:
918:
915:
913:
910:
909:
905:
903:
900:
897:
895:
892:
891:
887:
885:
882:
879:
877:
874:
873:
859:
854:
852:
845:
837:
819:
815:
811:
807:
801:
796:
795:
794:
793:
789:
785:
774:
773:
769:
765:
757:
756:
748:
744:
740:
736:
727:
725:
721:
717:
710:
705:
704:
703:
702:
698:
694:
693:
685:
682:
681:
680:
675:
672:
671:
670:
665:
662:
661:
660:
658:
654:
650:
641:
626:
622:
616:
613:
612:
608:
607:quality scale
602:
599:
598:
595:
591:Help articles
577:
576:
570:
566:
562:
558:
554:
553:
548:
545:
541:
540:
536:
527:
524:
521:
517:
516:
505:
492:Accessibility
488:
487:
482:
479:
475:
474:
470:
467:
466:Accessibility
464:
461:
457:
456:
444:
443:
438:
437:
432:
423:
419:
418:
414:
409:
407:
403:
399:
389:
385:
384:
381:
364:
360:
359:
354:
351:
347:
346:
342:
325:
322:
319:
315:
314:
310:
306:
300:
296:
292:
283:
282:
263:
262:
257:
253:
245:
241:
237:
233:
229:
225:
221:
217:
213:
209:
205:
201:
197:
193:
189:
185:
181:
177:
174:
172:
168:
167:
157:
153:
150:
146:
145:
142:
132:
128:
126:
123:
121:
117:
114:
112:
109:
108:
102:
98:
97:Learn to edit
94:
91:
86:
85:
82:
81:
76:
72:
68:
67:
57:
55:
54:
47:
44:
42:
41:
36:
29:
19:
1708:
1673:
1656:
1652:
1630:
1620:
1551:
1541:
1479:
1469:
1450:
1447:
1427:
1421:
1418:
1407:
1357:
1347:
1328:
1325:
1298:
1263:
1253:
1223:
1213:
1188:
1170:<br/: -->
1167:
1141:
1113:
1035:
947:
870:Description
838:
827:
780:
761:
691:
688:
678:
668:
647:
640:
620:
574:
550:
484:
440:
434:
395:
356:
305:WikiProjects
295:project page
294:
251:
169:
69:This is the
1304:Overcolored
1032:WP:EIS#Link
800:Jason Quinn
784:Jason Quinn
709:Timeshifter
692:Timeshifter
436:WP:PROPOSAL
433:, refer to
1787:Categories
1770:Largoplazo
561:discussion
404:, and the
1125:Marchjuly
864:Alt text
565:Help Menu
149:WT:ACCESS
141:Shortcuts
133:if needed
116:Be polite
71:talk page
1621:Remsense
1600:readers.
1542:Remsense
1514:readers.
1470:Remsense
1414:Remsense
1408:My edit
1348:Remsense
1254:Remsense
1214:Remsense
1087:Graham87
1046:Setting
1028:CC BY-SA
967:Graham87
810:Graham87
743:contribs
716:Graham87
649:Graham87
171:Archives
101:get help
1162:WP:NOBR
1044:images.
898:Oregon
844:Archive
623:on the
529:B‑class
252:90 days
1748:isaacl
1729:Gonnym
1568:rose64
1370:Gonnym
1281:isaacl
1073:isaacl
1059:rose64
1042:|thumb
1038:|link=
1034:says:
1020:|link=
1016:|link=
867:Image
301:scale.
1761:that.
1606:page.
1581:GIF.
1236:Juwan
1192:Juwan
1172:? on
1164:notes
1123:. --
1048:|alt=
1024:CC BY
1012:|alt=
861:Page
834:|alt=
830:|alt=
571:. Or
293:This
176:Index
129:Seek
77:page.
16:<
1774:talk
1752:talk
1733:talk
1714:talk
1587:talk
1572:talk
1570:🌹 (
1495:says
1456:talk
1392:talk
1374:talk
1334:talk
1285:talk
1240:talk
1196:talk
1152:talk
1148:Izno
1129:talk
1091:talk
1077:talk
1063:talk
1061:🌹 (
1026:and
1014:and
1010:The
1002:talk
985:talk
981:Izno
971:talk
956:talk
916:Jct
814:talk
788:talk
768:talk
739:talk
720:talk
697:talk
118:and
1701:to
1566:Red
1181:ubl
1057:Red
997:Rjj
951:Rjj
615:Mid
567:or
1789::
1776:)
1754:)
1735:)
1716:)
1685:}}
1679:{{
1626:‥
1589:)
1574:)
1563:--
1547:‥
1527:”
1506:“
1475:‥
1458:)
1394:)
1376:)
1353:‥
1336:)
1317:}}
1311:{{
1307:}}
1301:{{
1287:)
1259:‥
1242:)
1219:‥
1198:)
1184:}}
1178:{{
1154:)
1131:)
1093:)
1079:)
1065:)
1004:)
987:)
973:)
958:)
847:}}
841:{{
816:)
808:.
790:)
770:)
745:)
741:•
735:DJ
731:Th
722:)
699:)
689:--
250::
244:17
242:,
240:16
238:,
236:15
234:,
232:14
230:,
228:13
226:,
224:12
222:,
220:11
218:,
216:10
214:,
210:,
206:,
202:,
198:,
194:,
190:,
186:,
182:,
178:,
99:;
1772:(
1750:(
1731:(
1712:(
1631:论
1585:(
1552:论
1480:论
1454:(
1390:(
1372:(
1358:论
1332:(
1283:(
1264:论
1238:(
1224:论
1194:(
1150:(
1127:(
1089:(
1075:(
1000:(
983:(
969:(
954:(
812:(
802::
798:@
786:(
766:(
737:(
733:e
718:(
711::
707:@
695:(
627:.
609:.
601:B
307::
212:9
208:8
204:7
200:6
196:5
192:4
188:3
184:2
180:1
173::
103:.
37:.
30:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.