Knowledge

talk:Manual of Style/Accessibility - Knowledge

Source 📝

789:
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.
357: 325: 485: 467: 1123: 395: 336: 551: 527: 294: 429: 263: 343: 1216:. 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. 335: 342: 860:. 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. 788:
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
1285:
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
736:
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. —
735:
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
1196:
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?
1000:
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.
720:
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.
1255:
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!
882: 1078:
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.
811:
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
1193:
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.
96: 23: 496:, 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. 580: 254: 707: 182: 812: 650: 769:
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.
659: 250: 246: 242: 238: 234: 230: 226: 222: 218: 214: 210: 206: 202: 198: 194: 190: 186: 1139: 1092:
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).
857: 666:) 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: 448: 676:
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:
778: 1113: 986:
Purely decorative images should have no link and no alt text according to accessibility experts since ever. What's the concern with that option?
1150: 562:, a collaborative effort to improve Knowledge's help documentation for readers and contributors. If you would like to participate, please visit 856:
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:
966: 1287: 1162: 1079: 824: 730: 419: 690: 1310: 1276: 1250: 1236: 1241:
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.
753: 1295: 1087: 798: 670: 131: 1101: 981: 631: 1073: 613: 34: 1012: 995: 765:
Note that mobile versions of the website do not support collapsing, so any collapsible content will automatically be uncollapsed.
81: 1206: 442: 680: 1325: 1320: 621: 330: 137: 839:
parameters for selectable images, but what about a template where the image should be purely decorative? Should it have an
262: 1144: 1029:
to an empty string can be a problem. If use of the image requires attribution (this includes, but is not limited to, the
944: 890: 492: 472: 830: 437: 1180: 1057:
to an empty string does not, of itself, violate any policies so is much less of an issue. But if Graham87 suggests
1043:
Except for public-domain images, it must always be possible for the reader to reach the image-description page, so
774: 41: 1315: 908: 607: 77: 17: 356: 324: 126: 1037:
licenses), we must be able to reach the file description page so that the attribution may be seen. Indeed,
681:
https://en.wikipedia.org/search/?title=List_of_countries_by_firearm-related_death_rate&oldid=1232941127
452:
of Knowledge's policy and guideline documents is available, offering valuable insights and recommendations.
404: 305: 1286:
differently by browsers, and manual overrides can work against this process producing a pleasing result.
1213: 770: 749: 567: 117: 372:(MoS) guidelines by addressing inconsistencies, refining language, and integrating guidance effectively. 177: 162: 936: 408: 369: 364: 663: 412: 277: 1127: 1115: 835:
How should a template handle alt text on an icon, if the icon can be changed? Some templates need
759: 368:, a collaborative effort focused on enhancing clarity, consistency, and cohesiveness across the 783: 563: 558: 532: 407:
procedure and is given additional attention, as it closely associated to the English Knowledge
155: 1025:
parameters are unrelated; the value of one does not affect the meaning of the other. Setting
794: 703: 311: 484: 466: 8: 1246: 1202: 1135: 1069: 107: 1268: 1228: 1097: 1008: 977: 962: 926: 900: 820: 726: 147: 122: 918: 846:
I'm asking about general best practices but will link examples that brought this up.
103: 1291: 1167: 1083: 955:
Useful parameter or simpler to use standardized alt text regardless of icon image?
850: 806: 790: 715: 697: 449:
guidance on how to contribute to the development and revision of Knowledge policies
1038: 883:
Knowledge talk:WikiProject Computing/Computer Programming task force/Archive Index
745: 40:"WT:COLOR" and "WT:COLOUR" redirect here. For WikiProject Color's talk page, see 1242: 1198: 1168: 1158: 1131: 1062: 991: 273: 1304: 1258: 1218: 1093: 973: 816: 722: 655: 575: 394: 1187: 1002: 956: 550: 526: 660:
Talk:COVID-19 pandemic deaths/Archive 1#Scrolling versus expanded tables
278: 737: 570:
and see a list of open tasks. To browse help related resources see the
33:"WT:ACCESS" redirects here. For the related wikiproject talk page, see 1154: 987: 571: 858:
Template talk:Archives/Archive 1#Accessibility improvement for image
691:
Help:Table/Advanced#Table with sticky header in simple scroll window
436:
For information on Knowledge's approach to the establishment of new
1034: 428: 275: 1151:
Knowledge talk:Manual of Style § Mobile skin and block quotations
972:
Yeah making the alt text "Archiving icon" sounds sensible to me.
671:
Help:Table/Advanced#Advanced scrolling tables with sticky headers
1212:
Not to hock my own slogan, but essentially as I understand it,
279: 1030: 843:
parameter, or should it use the same alt text consistently?
66:
Please place new discussions at the bottom of the talk page.
1175:
are there any acceptable uses for the HTML line break
651:
Accessibility of scrolling tables. Different template
612:
This page does not require a rating on the project's
686:
This method for scrolling tables is discussed here:
662:, that the scrolling tables in the related article ( 72: 1302: 24:Knowledge talk:Manual of Style (accessibility) 422:carefully and exercise caution when editing. 579: 1126:You are invited to join the discussion at 1153:. Please feel free to participate there. 304:does not require a rating on Knowledge's 362:This page falls within the scope of the 35:Knowledge talk:WikiProject Accessibility 14: 1303: 586:and a volunteer will visit you there. 556:This page is within the scope of the 418:Contributors are urged to review the 378:Knowledge:WikiProject Manual of Style 887:File:Replacement filing cabinet.svg 415:. Both areas are subjects of debate. 381:Template:WikiProject Manual of Style 293: 291: 287: 59: 46: 1149:Page watchers may be interested in 945:File:Replacement filing cabinet.svg 891:File:Replacement filing cabinet.svg 502:Knowledge:WikiProject Accessibility 310:It is of interest to the following 80:for discussing improvements to the 30: 1311:WikiProject Accessibility articles 505:Template:WikiProject Accessibility 427: 393: 31: 1337: 490:This page is within the scope of 1145:Mobile skin and block quotations 1121: 658:. You noted in this discussion, 549: 525: 483: 465: 355: 341: 334: 323: 292: 261: 97:Click here to start a new topic. 42:Knowledge talk:WikiProject Color 1176: 1061:, I would go with that 100%. -- 831:Alt text for icons in templates 595:Template:Knowledge Help Project 1296:18:40, 19 September 2024 (UTC) 1277:12:56, 19 September 2024 (UTC) 1251:12:49, 19 September 2024 (UTC) 1237:12:24, 19 September 2024 (UTC) 1207:12:21, 19 September 2024 (UTC) 1128:WP:HD § Accessibility question 1116:WP:HD § Accessibility question 909:File:Oregon DEM relief map.gif 582:ask for help on your talk page 18:Knowledge talk:Manual of Style 13: 1: 1163:04:07, 7 September 2024 (UTC) 1102:09:10, 8 September 2024 (UTC) 1088:15:43, 7 September 2024 (UTC) 1074:09:16, 7 September 2024 (UTC) 1013:04:33, 7 September 2024 (UTC) 996:04:10, 7 September 2024 (UTC) 94:Put new text under old text. 82:Manual of Style/Accessibility 1326:Knowledge Help Project pages 1321:Mid-importance Help articles 931:License plate reading "JCT" 626:This page has been rated as 7: 1140:07:40, 28 August 2024 (UTC) 982:04:04, 24 August 2024 (UTC) 967:20:51, 23 August 2024 (UTC) 825:15:30, 13 August 2024 (UTC) 799:10:21, 13 August 2024 (UTC) 102:New to Knowledge? Welcome! 10: 1342: 632:project's importance scale 403:This page falls under the 145: 39: 32: 1269: 1229: 1047:should be used only with 949:Icon of a filing cabinet 941:Icon of a filing cabinet 937:User talk:XAM2175/2023/06 895:Icon of a filing cabinet 876: 873: 870: 867: 779:19:13, 27 July 2024 (UTC) 625: 611: 566:, where you can join the 544: 493:WikiProject Accessibility 478: 435: 401: 365:Knowledge:Manual of Style 350: 318: 132:Be welcoming to newcomers 53:Skip to table of contents 754:08:15, 8 July 2024 (UTC) 731:14:32, 6 July 2024 (UTC) 708:14:22, 6 July 2024 (UTC) 664:COVID-19 pandemic deaths 384:Manual of Style articles 52: 438:policies and guidelines 771:Closed Limelike Curves 592:Knowledge:Help Project 559:Knowledge Help Project 508:Accessibility articles 432: 398: 127:avoid personal attacks 1316:B-Class Help articles 1181:a recent edit of mine 431: 413:article titles policy 397: 255:Auto-archiving period 913:Small map of Oregon 760:Collapsing on mobile 1059:|alt=Archiving icon 864: 784:Alt text for images 1183:, I substituted a 927:File:Jct plate.svg 901:User talk:Jsayre64 863: 433: 420:awareness criteria 405:contentious topics 399: 306:content assessment 138:dispute resolution 99: 67: 1214:break means pause 953: 952: 919:Template talk:Jct 646: 645: 642: 641: 638: 637: 520: 519: 516: 515: 460: 459: 456: 455: 286: 285: 118:Assume good faith 95: 71: 70: 65: 58: 57: 22:(Redirected from 1333: 1275: 1273: 1267: 1263: 1235: 1233: 1227: 1223: 1192: 1186: 1178: 1125: 1124: 1065: 1060: 1056: 1050: 1046: 1028: 1024: 1020: 1005: 959: 865: 862: 855: 849: 842: 838: 810: 741: 719: 600: 599: 596: 593: 590: 585: 564:the project page 553: 546: 545: 540: 537: 529: 522: 521: 510: 509: 506: 503: 500: 487: 480: 479: 469: 462: 461: 446:. Additionally, 386: 385: 382: 379: 376: 359: 352: 351: 346: 345: 344: 339: 338: 337: 327: 320: 319: 297: 296: 295: 288: 280: 266: 265: 256: 165: 163:WT:ACCESSIBILITY 158: 73: 60: 47: 27: 1341: 1340: 1336: 1335: 1334: 1332: 1331: 1330: 1301: 1300: 1265: 1259: 1257: 1225: 1219: 1217: 1190: 1184: 1173: 1147: 1122: 1119: 1063: 1058: 1054: 1048: 1044: 1026: 1022: 1018: 1003: 957: 853: 847: 840: 836: 833: 813:this discussion 804: 786: 762: 739: 713: 653: 597: 594: 591: 588: 587: 538: 535: 507: 504: 501: 498: 497: 409:Manual of Style 383: 380: 377: 375:Manual of Style 374: 373: 370:Manual of Style 340: 333: 331:Manual of Style 282: 281: 276: 253: 171: 170: 169: 168: 161: 154: 150: 143: 113: 45: 38: 29: 28: 21: 20: 12: 11: 5: 1339: 1329: 1328: 1323: 1318: 1313: 1299: 1298: 1283: 1282: 1281: 1280: 1279: 1172: 1166: 1146: 1143: 1118: 1114:Discussion at 1112: 1111: 1110: 1109: 1108: 1107: 1106: 1105: 1104: 1015: 984: 951: 950: 947: 942: 939: 933: 932: 929: 924: 921: 915: 914: 911: 906: 903: 897: 896: 893: 888: 885: 879: 878: 875: 872: 869: 832: 829: 828: 827: 785: 782: 767: 766: 761: 758: 757: 756: 733: 694: 693: 684: 683: 674: 673: 652: 649: 644: 643: 640: 639: 636: 635: 628:Mid-importance 624: 618: 617: 610: 604: 603: 601: 589:Knowledge Help 576:Help Directory 554: 542: 541: 539:Mid‑importance 533:Knowledge Help 530: 518: 517: 514: 513: 511: 488: 476: 475: 470: 458: 457: 454: 453: 434: 424: 423: 417: 400: 390: 389: 387: 360: 348: 347: 328: 316: 315: 309: 298: 284: 283: 274: 272: 271: 268: 267: 173: 172: 167: 166: 159: 151: 146: 144: 142: 141: 134: 129: 120: 114: 112: 111: 100: 91: 90: 87: 86: 85: 69: 68: 63: 56: 55: 50: 15: 9: 6: 4: 3: 2: 1338: 1327: 1324: 1322: 1319: 1317: 1314: 1312: 1309: 1308: 1306: 1297: 1293: 1289: 1284: 1278: 1274: 1272: 1264: 1262: 1254: 1253: 1252: 1248: 1244: 1240: 1239: 1238: 1234: 1232: 1224: 1222: 1215: 1211: 1210: 1209: 1208: 1204: 1200: 1194: 1189: 1182: 1170: 1165: 1164: 1160: 1156: 1152: 1142: 1141: 1137: 1133: 1129: 1117: 1103: 1099: 1095: 1091: 1090: 1089: 1085: 1081: 1077: 1076: 1075: 1071: 1067: 1052: 1040: 1036: 1032: 1016: 1014: 1010: 1006: 999: 998: 997: 993: 989: 985: 983: 979: 975: 971: 970: 969: 968: 964: 960: 948: 946: 943: 940: 938: 935: 934: 930: 928: 925: 922: 920: 917: 916: 912: 910: 907: 904: 902: 899: 898: 894: 892: 889: 886: 884: 881: 880: 866: 861: 859: 852: 844: 826: 822: 818: 814: 808: 803: 802: 801: 800: 796: 792: 781: 780: 776: 772: 764: 763: 755: 751: 747: 743: 734: 732: 728: 724: 717: 712: 711: 710: 709: 705: 701: 700: 692: 689: 688: 687: 682: 679: 678: 677: 672: 669: 668: 667: 665: 661: 657: 648: 633: 629: 623: 620: 619: 615: 614:quality scale 609: 606: 605: 602: 598:Help articles 584: 583: 577: 573: 569: 565: 561: 560: 555: 552: 548: 547: 543: 534: 531: 528: 524: 523: 512: 499:Accessibility 495: 494: 489: 486: 482: 481: 477: 474: 473:Accessibility 471: 468: 464: 463: 451: 450: 445: 444: 439: 430: 426: 425: 421: 416: 414: 410: 406: 396: 392: 391: 388: 371: 367: 366: 361: 358: 354: 353: 349: 332: 329: 326: 322: 321: 317: 313: 307: 303: 299: 290: 289: 270: 269: 264: 260: 252: 248: 244: 240: 236: 232: 228: 224: 220: 216: 212: 208: 204: 200: 196: 192: 188: 184: 181: 179: 175: 174: 164: 160: 157: 153: 152: 149: 139: 135: 133: 130: 128: 124: 121: 119: 116: 115: 109: 105: 104:Learn to edit 101: 98: 93: 92: 89: 88: 83: 79: 75: 74: 64: 62: 61: 54: 51: 49: 48: 43: 36: 25: 19: 1270: 1260: 1230: 1220: 1195: 1177:<br/: --> 1174: 1148: 1120: 1042: 954: 877:Description 845: 834: 787: 768: 698: 695: 685: 675: 654: 647: 627: 581: 557: 491: 447: 441: 402: 363: 312:WikiProjects 302:project page 301: 258: 176: 76:This is the 1039:WP:EIS#Link 807:Jason Quinn 791:Jason Quinn 716:Timeshifter 699:Timeshifter 443:WP:PROPOSAL 440:, refer to 1305:Categories 568:discussion 411:, and the 1132:Marchjuly 871:Alt text 572:Help Menu 156:WT:ACCESS 148:Shortcuts 140:if needed 123:Be polite 78:talk page 1261:Remsense 1221:Remsense 1094:Graham87 1053:Setting 1035:CC BY-SA 974:Graham87 817:Graham87 750:contribs 723:Graham87 656:Graham87 178:Archives 108:get help 1169:WP:NOBR 1051:images. 905:Oregon 851:Archive 630:on the 536:B‑class 259:90 days 1288:isaacl 1080:isaacl 1066:rose64 1049:|thumb 1045:|link= 1041:says: 1027:|link= 1023:|link= 874:Image 308:scale. 1243:Juwan 1199:Juwan 1179:? on 1171:notes 1130:. -- 1055:|alt= 1031:CC BY 1019:|alt= 868:Page 841:|alt= 837:|alt= 578:. Or 300:This 183:Index 136:Seek 84:page. 16:< 1292:talk 1247:talk 1203:talk 1159:talk 1155:Izno 1136:talk 1098:talk 1084:talk 1070:talk 1068:🌹 ( 1033:and 1021:and 1017:The 1009:talk 992:talk 988:Izno 978:talk 963:talk 923:Jct 821:talk 795:talk 775:talk 746:talk 727:talk 704:talk 125:and 1188:ubl 1064:Red 1004:Rjj 958:Rjj 622:Mid 574:or 1307:: 1294:) 1266:‥ 1249:) 1226:‥ 1205:) 1191:}} 1185:{{ 1161:) 1138:) 1100:) 1086:) 1072:) 1011:) 994:) 980:) 965:) 854:}} 848:{{ 823:) 815:. 797:) 777:) 752:) 748:• 742:DJ 738:Th 729:) 706:) 696:-- 257:: 251:17 249:, 247:16 245:, 243:15 241:, 239:14 237:, 235:13 233:, 231:12 229:, 227:11 225:, 223:10 221:, 217:, 213:, 209:, 205:, 201:, 197:, 193:, 189:, 185:, 106:; 1290:( 1271:论 1245:( 1231:论 1201:( 1157:( 1134:( 1096:( 1082:( 1007:( 990:( 976:( 961:( 819:( 809:: 805:@ 793:( 773:( 744:( 740:e 725:( 718:: 714:@ 702:( 634:. 616:. 608:B 314:: 219:9 215:8 211:7 207:6 203:5 199:4 195:3 191:2 187:1 180:: 110:. 44:. 37:. 26:)

Index

Knowledge talk:Manual of Style
Knowledge talk:Manual of Style (accessibility)
Knowledge talk:WikiProject Accessibility
Knowledge talk:WikiProject Color
Skip to table of contents
talk page
Manual of Style/Accessibility
Click here to start a new topic.
Learn to edit
get help
Assume good faith
Be polite
avoid personal attacks
Be welcoming to newcomers
dispute resolution
Shortcuts
WT:ACCESS
WT:ACCESSIBILITY
Archives
Index
1
2
3
4
5
6
7
8
9
10

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