Knowledge (XXG):Manual of Style/Accessibility

2540: 4116:(for "horizontal list") are available to improve accessibility and semantic meaningfulness. This feature makes use of the correct HTML markup for each list item, rather than including bullet characters which, for example, are read out (e.g., "dot cat dot dog dot horse dot...") by the assistive software used by people who are blind. The templates differ only in the wiki-markup used to create the list. Note that when text is being passed to these (or any other) templates, the vertical bar character ( 2740: 5169:. Closed captions are meant to be viewed instead of subtitles. Closed captions provide a text version of all important information provided through the sound. It can include dialogue, sounds (natural and artificial), the setting and background, the actions and expressions of people and animals, text or graphics. Off-Knowledge (XXG) guides should be consulted for how to create closed captions. 1672:; although lower resolutions will tend to stretch paragraphs vertically, moving images apart in that direction, be careful not to add images or other floating content on both sides of the screen simultaneously. Large tables and images can also create problems; sometimes horizontal scrolling is unavoidable, but consider restructuring wide tables to extend vertically rather than horizontally. 3005: 2309: 2283: 2239: 2214: 2167: 2141: 59: 4342: 3385: 3193: 3144: 3098: 3057: 2886: 2859: 2832: 4295: 3358: 3306: 2982: 2959: 2936: 2913: 134: 2265: 2127: 1245:

only—a single blank line may be added beneath each heading, but not more than one; more than one blank line beneath a section heading will cause extra space to be visible on the rendered page. Consideration should also be given to how a single blank white line beneath section headings may appear on a

2819:

Likewise, do not switch between initial list marker types (colons, asterisks or hash signs) in one list. When indenting in reply to a post that starts with any mix of colons and asterisks and sometimes hash signs, it is necessary to copy whatever series of those characters was used above, and append

1171:

A standardized structure of articles improves accessibility, because it enables users to expect contents to be in a specific part of the page. For example, if a blind user is searching for disambiguation links and doesn't find any at the top of the page, they will know that there aren't any and they

5424:

To accommodate these considerations, test any potentially disruptive changes with JavaScript or CSS disabled. In Firefox or Chrome, this can be done easily with the Web Developer extension; JavaScript can be disabled in other browsers in the "Options" screen. Be particularly careful with inline CSS

4667:

Like the caption, these help present the information in a logical structure to visitors. The headers help screen readers render header information about data cells. For example, header information is spoken prior to the cell data, or header information is provided on request. Because the row header

5412:

in ways we cannot predict as well as accessed directly via older browsers. At the same time, it is recognized that it is impossible to provide the same quality of appearance to such users without unnecessarily avoiding features that would benefit users with more capable browsers. As such, features

1715:

do not indicate presentational text attributes (bold, italic, underline, monospace, strikethrough) or even semantic text attributes (emphasis, importance, text deletion), so struck-out text is read normally along with any other text. (Editors using screen readers who participate in Knowledge (XXG)

1629:

the section they belong to; do not place the image at the end of the previous section. (Depending on platform, "stacking" of several images alongside a relatively small amount of text may cause a particular image to be pushed down to a later section. However, this is not an accessibility issue, as

2365:, which provide language-specific functionality to editors, such as the ability to easily display several transliterations with one template. Not every language has its own template, but using one may be helpful to streamline wikitext, instead of cluttering paragraphs with instances of 2629:

Several other tools exist on the web, but check if they are up-to-date before using them. Several tools are based on WCAG 1.0's algorithm, while the reference is now WCAG 2.0's algorithm. If the tool doesn't specifically mention that it is based on WCAG 2.0, assume that it is

1768:

for all text in a non-Latin writing system where the non-Latin character is important in the original context such as names, places, things etc. This functionality is available in templates that signify non-Latin-script languages and can also be found in templates such as

1478:

cannot be used because of lower-level headings elsewhere in the article, then using bold for the sub-sub-sub headings causes the least annoyance for screen reader users. Using a pseudo heading at all means you have exhausted all other options. It is meant as a rarity.

5254:

relating to a sport team might use a yellow and red color scheme, to tie in with the colors of the team livery. In this case, dark red links on light yellow provide enough color contrast, and thus would be accessible, while white on yellow or black on red would not.

1902:

of the original font size and not as an absolute size in pixels or point size. Relative sizes increase accessibility for visually impaired users by allowing them to set a large(r) default font size in their browser settings. Absolute sizes deny users such ability.

3593:

The second approach, for when the material is meant to be a single comment (or other list item, e.g. in article text) is to use new-paragraph markup on the same output line (see previous section for advanced techniques in this, to include complex content blocks):

3583:

The first is to add a blank line with the same number of colons on it as those preceding the text above and below the blank line. This is appropriate when two editors are making comments immediately after each other at the same indentation level. For instance:

4744:

Avoid using tables for visual positioning of non-tabular content. Data tables provide extra information and navigation methods that can be confusing when the content lacks logical row and column relationships. Instead, use semantically appropriate elements or

5242:. Members of the accessibility project have ensured that the default style is accessible. If some template or specific color scheme deviates from the standard, its authors should make sure that it meets accessibility requirements such as providing enough 5005:

Avoid referring in text to images as being on the left or right. Image placement may be different for viewers of the mobile site, and is meaningless to people having pages read to them by assistive software. Instead, use captions to identify images.

1030: 1759:

and it is not safe to assume how any given character in these ranges will be pronounced. If they are not recognized by the screen reader or speech synthesizer, they may be pronounced as a question mark or omitted entirely from the speech output.

1811:

The sequence of characters must be sufficient to convey semantic aspects of the text (and, preferably, other similar forms of content); reliance on custom "special symbols" distinguishable only by CSS properties or wiki markup is not acceptable.

2739: 3150:

In both cases, this must be done on a single code line. However, you can optionally use the trick of wrapping a code line break in an HTML comment (which suppresses it as an output line break), to separate paragraphs better in code view:

3559:). The result is that assistive technology, such as screen readers, will announce a description list that does not exist, which is confusing for any visitor unused to Knowledge (XXG)'s broken markup. This is not ideal for accessibility, 5413:

that would cause content to be hidden or corrupted when CSS or JavaScript is unavailable must not be used. However, consideration for users without CSS or JavaScript should extend mainly to making sure that their reading experience is

5219:

is more carefully tested to ensure accessibility (e.g. sufficient color contrast) and compatibility with a wide range of browsers. Moreover, it allows users with very specific needs to change the color schemes in their own style sheet

197: 2816:, which will announce multiple lists when only one was intended, and therefore may mislead or confuse users of these programs. Such improper formatting can also more than triple the length of time it takes them to read the list. 5000: 1723:

is normally ignored by screen readers, its rare use in articles (e.g., to show changes in a textual analysis) will cause accessibility problems and outright confusion if it is the only indication used. This applies to both the

4440:

tags in adjacent cells to emulate a visual row that isn't reflected in the HTML table structure. This is a problem for users of screen readers which read tables cell by cell, HTML row by HTML row, not visual row by visual row.

1020: 1007: 6183: 2604: 4951: 2666:

Additional tools can be used to help produce graphical charts and color schemes for maps and the like. These tools are not accurate means to review contrast accessibility, but they can be helpful for specific tasks.

5031:), and not in the heading itself nor at the end of the previous section. This ensures that screen readers will read, and the mobile site will display, the image (and its textual alternative) in the correct section. 3837:

line breaks, which should not be used—see above. They differ only in the wiki-markup used to create the list. Note that because these are templates, the text of each list item cannot contain the vertical bar symbol

1246:

small screen for a particular article, as many editors use mobile devices to edit, and having a single blank line beneath the heading may actually detract from the readability for these editors, for some articles.

1458:) and try to avoid using bold markup. Screen readers and other assistive technology can only use headings that have heading markup for navigation. If you want to reduce the size of the table of contents (TOC), use 2108:

By default, English Knowledge (XXG) articles state explicitly to the browser that they are written wholly in English. Text in a language other than English should be tagged as such, typically with a template like

1139: 6506: 709: 4947:

that acts as a substitute for the image for blind readers, search-spiders, and other non-visual users. If additional alt text is added, it should be succinct or refer the reader to the caption or adjacent text.

5016:

Detailed image descriptions, where not appropriate for an article, should be placed on the image's description page, with a note saying that activating the image link will lead to a more detailed description.

3287:

Be aware that not every fancy template can be used in this manner (e.g. some decorative quotation templates are table-based, and the MediaWiki parser will not handle such markup as being inside a list item).

2661:

enables you to pick colors on the page, and review their contrast thoroughly. However, be sure to only use the up-to-date "luminosity" algorithm, and not the "color brightness/difference", which is outdated.

3713:

but will be read by a screen reader as: "List of 2 items: (bullet) White rose, (bullet) Yellow rose, list end. List of 1 items: (bullet) Pink rose, list end. List of 1 items: (bullet) Red rose, list end."

2639:

with colors being marked towards level AA conformance. It is used for all user-interface elements across products and in the main Wikimedia themes, desktop and mobile. However, it does not consider linked

1013: 3547:). The visual effect in most Web browsers is to indent the line. This is used, for example, to indicate replies in a threaded discussion on talk pages. However, this markup alone is missing the required 2572:

Ensure that color is not the only method used to communicate important information. Especially, do not use colored text or background unless its status is also indicated using another method, such as an

584: 574: 4698: 4450: 1898:

Reduced or enlarged font sizes should be used sparingly, and are usually done with automated page elements such as headings, table headers, and standardized templates. Size changes are specified as a

1068: 989: 2707:, a "free color blindness simulator for Windows, Mac and Linux". It lets you view whatever is on your screen as it would be seen by someone with one of three types of color-blindness or in greyscale. 944: 6753: 6346: 954: 6668: 1736:, usually visually rendered as underlined), as well as templates that use them. Do not use strikethrough to object to content you think is inappropriate or incorrect. Instead, comment it out with 6359: 1058: 3682:

list will be ended before the line break, and another HTML list will be opened after the line break. This effectively breaks what is seen as one list into several smaller lists for those using

4996: 1132: 4414:

for more information on the special syntax used for tables. Do not solely use formatting, either from CSS or hard-coded styles, to create semantic meaning (e.g., changing background color).

5527:

The general font size for infoboxes and navboxes is 88% of the page's default. The general font size for reference sections is 90% of the page's default. Additional values can be found at

4977:. Where possible, any charts or diagrams should have a text equivalent or should be well-described so that users who are unable to see the image can gain some understanding of the concept. 3628: 3348: 634: 2533: 7000: 6282: 810: 719: 649: 520: 775: 699: 644: 599: 4780:

prefixes. Make sure the content's reading order is correct. Visual effects, such as centering or bold typeface, can be achieved with style sheets or semantic elements. For example:

1125: 1073: 736: 629: 624: 7220: 5225: 1106: 604: 224: 3199:

This technique can be used for various forms of block-inclusion within a list item (because list items are technically block elements, which can contain other block elements):

6499: 2346: 2103: 1078: 639: 589: 569: 1716:

policy and deletion debates are advised to turn on notifications about text attributes when doing so, as struck text is very common in Knowledge (XXG)-internal discussions.)

6926: 5465: 855: 669: 614: 609: 594: 579: 44: 1840:

Do not use techniques that require interaction to provide information, such as tooltips or any other "hover" text. Abbreviations are exempt from these requirements, so the

5862: 5639: 1025: 6339: 1063: 564: 492: 242: 2532:

This section is about the use of colors in articles (though the advice on contrast ratios is applicable more generally). For the civility essay dealing with colors, see

1238:) and so on. (Level 1 is the auto-generated page title.) Do not skip parts of the sequence, such as selecting levels for emphasis; this is not the purpose of headings. 2647:

shows the results for 14 hues of finding the darkest or lightest backgrounds that are AAA-compliant against black text, white text, linked text and visited linked text.

2644: 192: 5723:"F84: Failure of Success Criterion 2.4.9 due to using a non-specific link such as 'click here' or 'more' without a mechanism to change the link text to specific text" 1040: 704: 662: 557: 379: 4999:). Articles with many images may time out on mobile versions of Knowledge (XXG). Ideally, a page should have no more than 100 images (regardless of how small). See 6069: 687: 537: 175: 91: 5515: 6959: 2396:

templates, which italicize text using the Latin alphabet by default. If text should not be italicized, such as with the names of places or people, the parameter

1967: 1961: 754: 674: 327: 292: 259: 6683: 6332: 726: 714: 544: 406: 362: 2136:

is merely italicized, and has not specified that it is French-language text. Most screen readers attempting to handle this will sound ridiculous or confusing.

7159: 5348: 2095: 1868: 1706: 442: 431: 349: 279: 274: 254: 204: 949: 771: 619: 374: 229: 6693: 6435: 5454: 970: 515: 510: 264: 249: 4668:

and column header may be spoken before the data in each cell when navigating in table mode, it is necessary for the column headers and row headers to

1804: 1793:

Symbols that cause problems for screen readers may already have templates created to produce an image and alt text. An example is the dagger template

6974: 6760: 6629: 5232:. The problem is that when the default site-wide classes are overridden, it makes it far more difficult for an individual to choose their own theme. 5215:

In general, styles for tables and other block-level elements should be set using CSS classes, not with inline style attributes. The site-wide CSS in

4970:

using the built-in image syntax. The caption should concisely describe the meaning of the image and the essential information it is trying to convey.

1180: 339: 5409: 3564: 6179: 5172:

A text version of the video would also be needed for the blind, but as of November 2012 there is no convenient way to provide alt text for videos.

5061: 5048: 5042: 4925: 2015: 984: 731: 487: 482: 209: 4060: 3617: 3293: 883: 761: 477: 472: 418: 2278:– By default, it is expected for Japanese text to be written using the native writing system, whose rules may treat some characters differently. 1943:

within those elements. In no case should the resulting font size of any text drop below 85% of the page's default font size. Note that the HTML

5100: 7057: 5490: 5247: 4426: 4246: 4097: 4004: 3026:

This injection of a bullet unnecessarily adds to list complexity and makes people more likely to use the wrong indentation levels in replies.

1907: 935: 870: 865: 694: 214: 187: 30: 6254: 6122: 6087: 2746: 6947: 4967: 4963: 888: 299: 269: 6430: 6098: 5235:

It also creates a greater degree of professionalism by ensuring a consistent appearance between articles and conformance to a style guide.

2749:

Contrast ratios of web safe colours vs black (top row) and white (bottom) or vice versa, with contours at 3 (red), 4.5 (green) and 7 (blue)

2596: 1160: 6979: 6356: 5485: 2099: 765: 219: 67: 3555:(description/definition) pertains. As can be seen by inspecting the code sent to the browser, this results in broken HTML (i.e. it fails 5126: 3886: 2459:

characters as icons; use an icon with alt text instead. For example, a character like "→" cannot be reproduced into useful text by some

7225: 6969: 6964: 5034: 5009: 4981: 4418: 2555: 1915: 1669: 1620: 1224: 1176: 467: 452: 447: 344: 334: 314: 5317: 3364:

Definitely do not attempt to use a colon to match the indentation level, since (as mentioned above) it produces three separate lists:

6984: 6921: 6425: 5495: 5165:

for the hearing impaired. As of November 2012 this is not possible, but this feature could be easily added and has been requested in

5057: 4955: 4937: 4048: 4040: 4027: 3624: 3297: 2791: 1455: 501: 413: 369: 309: 6210: 2539: 6698: 6658: 6599: 6516: 6444: 6420: 4407:

Screen readers and other web browsing tools make use of specific table tags to help users navigate the data contained within them.

845: 457: 2585:

users or readers accessing Knowledge (XXG) through a printout or device without a color screen will not receive that information.

6594: 5251: 5229: 5136:

produce more than three flashes in any one-second period. Content that flashes more than that limit is known to cause seizures.

4694:

if a row header spans a group of rows, adjusting the span count as needed. Headers can now be associated to corresponding cells.

4220: 3978: 1911: 4756:

When using a table to position non-tabular content, help screen readers identify it as a layout table, not a data table. Set a

3833:

are available, to improve accessibility and semantic meaningfulness by marking up what is clearly a list rather than including

919: 7189: 7010: 6688: 6663: 6609: 3577:– especially in article content. This is interpreted by the software as marking the end of a list and the start of a new one. 2607:

for recommended colors. For other usage, here is a selection of tools that can be used to check that the contrast is correct:

2551: 1101: 850: 40: 36: 5181: 5180:

Subtitles for speech, lyrics, dialogue, etc. can easily be added to audio files. The method is similar to that of the video:

5155: 7052: 6828: 6775: 6748: 6678: 6653: 2526: 462: 384: 3678:

The problem with blank lines in the middle of a list is that, if list items are separated by more than one line break, the

3556: 7174: 6624: 6619: 6589: 6494: 6450: 6378: 5460: 4992: 4985: 4933: 4422: 4047:

markup, and the list numbering will reset after the line break. The list-breakage problem of blank lines also applies to

2712:

If an article overuses colors, and you don't know how to fix it yourself, you can ask for help from other editors. Place

304: 79: 7136: 6314: 6126: 6077: 5448: 5396:

Knowledge (XXG) articles should be accessible to readers using browsers and devices that have limited or no support for

4285:, and worse. The semicolon line is a one-item description list, with no description content, followed by a second list. 6942: 6823: 6743: 6526: 6521: 5442: 5390: 5378: 5347:

element to indicate something like an example link that isn't really clickable, but underlining is otherwise generally

5243: 5125:

This requires that GIFs with animations longer than five seconds be converted to video (to learn how, see the tutorial

5053: 4929: 3504: 2787: 2651: 2091: 151: 71: 17: 6073: 5263: 4995:

because screen size and browser formatting may affect accessibility for some readers due to fragmented image display (

7005: 6911: 6866: 6818: 6813: 6531: 6489: 6455: 5629: 4072: 3503:(a universal template, with the same name on all Wikimedia sites); these indent with various whitespace characters. 1745: 820: 815: 805: 2812:

will interpret the blank line as the end of one list and start a new one. Excessive double line breaks also disrupt

1163:

2.1, on which the following suggestions are based. Pages adhering to them are easier for everyone to read and edit.

5020: 1906:

Avoid using smaller font sizes within page elements that already use a smaller font size, such as most text within

1155:

is the goal of making web pages easier to navigate and read. While this is primarily intended to assist those with

6899: 6484: 6415: 5470: 3247:

Imagine a world in which every single person on the planet is given free access to the sum of all human knowledge.

2800:(a list made with a leading semicolon or colon, which is also how most talk-page discussions are formatted) or an 2796:

Do not separate list items by leaving empty lines or tabular column breaks between them. This includes items in a

6158: 6041: 6011: 5981: 5951: 5921: 5830: 5799: 5760: 5730: 5700: 5669: 5607: 2600: 6894: 6614: 6604: 6371: 6228: 5145: 2685:

provides a set of nine colors that work for color-blind users and with black text labels (among other palettes).

2326:

Without specifying a script, IETF tags assume the most common script used to write a given language. Therefore,

800: 159: 3827: 3759: 2376: 2338: 2317: 1773: 1668:, or to readers using monitors with a low resolution. On desktop, this is sometimes an issue in articles with 6765: 3478: 2821: 7131: 5405: 5221: 3587:: I completely agree. —User:Example : : I'm unconvinced. Is there a better source available? –User:Example2 2471: 2467: 7198: 7064: 6703: 6579: 6511: 6479: 6440: 5475: 3395:

to guarantee grouping. This is most useful for including block elements, such as formatted code, in lists:

1096: 860: 835: 830: 6546: 5401: 3492: 7069: 6770: 6673: 6584: 6574: 3664:

For bulleted vertical lists, do not separate items by leaving blank lines between them. Instead, use the

893: 87: 48: 6247: 6088:"Closed Captioning Standards and Protocol for Canadian English Language Television Programming Services" 4772:

elements inside the table, or inside any nested tables. In wiki table markup, this means do not use the

3876: 3679: 3523: 3486: 2726: 1852:

element) may be used to indicate the long form of an abbreviation (including an acronym or initialism).

7081: 7076: 6569: 5360: 5193: 5078: 4907: 4727: 4390: 4079: 3789: 3780:

if the list could be better rendered horizontally (inline) as described in the following two sections.

3720: 3647: 3460: 3035: 2765: 2486: 2053: 1874: 1816: 1681: 1647: 1602: 1428: 1192: 840: 101: 6392: 5600:"F26: Failure of Success Criterion 1.3.3 due to using a graphical symbol alone to convey information" 5528: 5437: 5216: 2716: 1971: 741: 6916: 6906: 5852: 5028: 3580:

If space is needed, there are two approaches, which will have different results for screen readers:

2693: 825: 5332:}} templates to change font size, rather than setting it explicitly with CSS style attributes like 3515: 3392: 3052:

Normal MediaWiki list markup is unfortunately incompatible with normal MediaWiki paragraph markup.

2432: 2190:– This is similar to the above, but uses a template specifically designed for French-language text. 1111: 912: 1664:

Knowledge (XXG) articles should be accessible to readers using devices with small screens such as

6720: 6102: 6065: 5892: 5480: 5118:

Not exceed a duration of five seconds (which results in making it a purely decorative element) or

4657:

A caption is a table's title, describing its nature. Data tables should always include a caption.

3817: 3751: 2162:, which is italicized by default and will allow screen readers to select a French-language voice. 1665: 1472: 1462: 6298: 5382: 3675:. (A blank line before the start of a list, or after the end of the list, causes no problems.) 3590:

This will tell the screen reader that this is two list items (the blank one will be ignored).

1175:

Standardization is already a habit on Knowledge (XXG), thus the guidelines to follow are simply

165: 5166: 7141: 6260: 6251: 6207: 4103: 3767: 3567:, but is currently commonly used, despite the problems it causes for users of screen readers. 2673:(previously Color Scheme Designer) helps to choose a good set of colors for a graphical chart. 2561: 2518: 2118: 2085: 1997: 1934: 1152: 6324: 6241: 5578:

structure is the same; only the terminology has changed between HTML specification versions.

5558: 4121: 3540: 2797: 2418: 2360: 2352: 2175: 161: 6033: 4410:

Use the correct wikitable pipe syntax to take advantage of all the features available. See

2697: 2595:

or visually impaired. Ensure the contrast of the text with its background reaches at least

7121: 5321: 5162: 2592: 2522: 2474:

helps the partially sighted to locate more easily the link target on the destination page.

2328: 2182: 1765: 5027:

Images should be inside the section to which they are related (after the heading and any

2623: 2568:

Articles (and other pages) that use color should keep accessibility in mind, as follows:

1797: 6004:"Guideline 2.3 Seizures: Do not design content in a way that is known to cause seizures" 5914:"H63: Using the scope attribute to associate header cells and data cells in data tables" 5428:

In 2016, around 7% of visitors to Knowledge (XXG) did not request JavaScript resources.

4281:

Improper use of a semicolon to bold a "fake heading" before a list (figure 1) creates a

3600:

To display a mathematical formula or expression on its own line, it is recommended that

2201:

allows speech synthesizers to select a voice capable of correctly reading out the text.

5884: 5329: 5325: 4276: 4111: 3775: 2805: 2578: 2021: 1926: 1855:

Do not insert line breaks within a sentence, since this makes it harder to edit with a

905: 142:

Knowledge (XXG) pages should be easy to navigate and read for people with disabilities.

5944:"G152: Setting animated gif images to stop blinking after n cycles (within 5 seconds)" 3312:

Do not use line breaks to simulate paragraphs, because they have different semantics:

2703:

A very simple open-source tool that can be helpful for choosing contrasting colors is

7214: 6790: 5543: 5303: 5283: 4944: 3872:

etc.). If this becomes too much of a hassle, you may be able to use the variant with

3683: 3560: 3342: 2813: 2460: 2387: 2368: 2291: 2273: 2247: 2222: 2149: 2112: 1991: 1856: 1843: 1720: 1712: 1242: 163: 7098: 2682: 2543:

A pair of screenshots showing the effects of red/green color-blindness on legibility

5338: 5311: 5288: 4956:

WP:Manual of Style/Icons § Remember accessibility for people with visual impairment

4411: 3498: 3495:

to indent the material. For single lines, a variety of templates exist, including

2426: 2410: 1994:

or may be unreasonably difficult for readers with impaired vision to decipher. Use

1986: 1980: 1975: 1787: 1756: 7126: 3981:

and the like, or any suitable container, such lists may be styled with the class "

2636: 1483:

Examples of acceptable and incorrect use of pseudo-headings and description lists

78:

It is a generally accepted standard that editors should attempt to follow, though

5753:"Markup Validation Service: Check the markup (HTML, XHTML, ...) of Web documents" 5425:

effects, which are not supported by several browsers, media, and XHTML versions.

4223:

and the like, or any suitable container, such lists may be styled with the class

3104:

This can also be done with explicit HTML markup for paragraphs (note the closing

2253: 2228: 2181: 2155: 6843: 6310: 5342:. Of course there are natural exceptions; e.g., it may be beneficial to use the 5295: 5259: 3692:

the software partially suppresses line spaces and therefore it looks like this:

3341:

a paragraph, such as lines of a poem or of a block of source code. See also the

3066: 2801: 2615: 2401: 6150: 5943: 5792:"H39: Using caption elements to associate data table captions with data tables" 5238:

Regarding accessibility, deviations from standard conventions may be tolerated

2696:(local file analysis). There are also browser extensions for webpage analysis: 2689: 2658: 6263: 6180:

File:Browsers, Geography, and JavaScript Support on Knowledge (XXG) Portal.pdf

5974:"G4: Allowing the content to be paused and restarted from where it was paused" 5913: 5822: 5791: 5722: 5692: 5661: 5599: 5540:

Further details on this usage are available on the template documentation for

5397: 5151: 5096: 4127: 2445: 1949: 1940: 1156: 6304: 5973: 3222:

This is another paragraph within this item, and we're going to quote someone:

2404:, text using a non-Latin script should almost never be italicized or bolded. 2260:– Serbian can typically be written using either the Latin or Cyrillic script. 6151:"G158: Providing an alternative for time-based media for audio-only content" 5320:

as needed, to emphasize logical differences not just visual ones. Use the {{

3528:

generic alternative was created for such non-quote cases, so please use it.

2809: 2783: 2582: 2096:

Knowledge (XXG):Manual of Style/Text formatting § Non-English language terms

5282:

for purely typographic italicization and boldfacing, respectively, and use

2299: 6184:

File:Analysis of Knowledge (XXG) Portal Traffic and JavaScript Support.pdf

5662:"H58: Using language attributes to identify changes in the human language" 3520:) for visual indentation; they are only for directly quoted material. The 2605:

Knowledge (XXG):Manual of Style/Accessibility/CSS colors for text on white

2208:

specification, but also which script is being used to write the language:

1859:. A single line break may follow a sentence, which may help some editors. 5379:

Knowledge (XXG):Manual of Style § Scrolling lists and collapsible content

29:

This is a guide to editing pages for accessibility. For the project, see

6319: 6003: 3535:) at the start of a line marks that line in the MediaWiki parser as the 2610:

You can use a few online tools to check color contrasts, including: the

1962:

Knowledge (XXG):Manual of Style/Dates and numbers § Fractions and ratios

6114: 2456: 2205: 1752: 1625:

In the wikicode, floating elements (including images) should be placed

6086:

English-language Working Group on Closed Captioning Standards (2008).

5066:

markup. Doing so can break links to sections and cause other problems.

3951:{{unbulleted list | White rose | Yellow rose | Pink rose | Red rose }} 1454:

Do not make pseudo-headings by abusing semicolon markup (reserved for

4954:

for more information. For additional considerations about icons, see

2611: 2444:

Create good link descriptions, especially for external links (avoid "

6232: 4686:

This clearly identifies a cell as a header for a column or row. Use

3616:

Richer and more accessible alternative description-list markup, see

2603:). To use named CSS colors for text on a white background, refer to 6293: 6287: 2517:"WP:COLOR" redirects here. For technical help on using colors, see 5857: 5634: 5041:

This guideline includes alt text for LaTeX-formatted equations in

4943:

Images and icons that are not purely decorative should include an

4699:

Knowledge (XXG):Manual of Style/Accessibility/Data tables tutorial

4451:

Knowledge (XXG):Manual of Style/Accessibility/Data tables tutorial

4151:{{flatlist | * White rose * Red rose ** Pink rose * Yellow rose }} 3911:{{plainlist | * White rose * Yellow rose * Pink rose * Red rose }} 2965:

Leaving blank lines between list items is generally bad practice,

2538: 1779:; these templates also have other accessibility benefits (see the 1751:

Screen readers have widely varying support for characters outside

5224:, or their browser's style sheet). For example, a style sheet at 2204:

IETF language tags specify the language of text according to the

6229:"Dive into Accessibility: 30 Days to a More Accessible Web Site" 6201: 4059:

markup; that type of list can have line breaks in it if instead

2384:

It is usually unnecessary to specify italics in addition to the

1990:). This is because some precomposed fractions may not work with 6328: 6283:

Recommendations for mobile friendly articles on Wikimedia wikis

5693:"G91: Providing link text that describes the purpose of a link" 4984:

text between two images or, unless absolutely necessary, using

2679:

provides safe color schemes for maps and detailed explanations.

2599:(WCAG) 2.0's AA level, and AAA level when feasible (see WCAG's 5111: 3063:

To put multiple paragraphs in a list item, separate them with

2808:. Lists are meant to group elements that belong together, but 2588:

Links should clearly be identifiable as a link to our readers.

1540::at least one definition or at least one description list item 166: 128: 53: 6277: 2907:

It seems to fit the spirit of Knowledge (XXG). —User:Example

2880:

It seems to fit the spirit of Knowledge (XXG). —User:Example

2853:

It seems to fit the spirit of Knowledge (XXG). —User:Example

2788:

Knowledge (XXG):Manual of Style § Bulleted and numbered lists

5752: 5286:

templates or elements for more meaningful differences. The

4952:

WP:Manual of Style/Accessibility/Alternative text for images

4193:{{hlist | White rose | Red rose | Pink rose | Yellow rose }} 2919:

But don't switch type from bullet list to description list,

2676: 1241:

For purposes of readability for editors with poor vision—in

1223:

Headings should be descriptive and in a consistent order as

7029: 2704: 2550:

are most commonly found in Knowledge (XXG) articles within

2407:

Phonetic transcriptions or pronunciation guides should use

1869:

Knowledge (XXG):Manual of Style/Text formatting § Font size

3813:

For unbulleted lists running down the page, the templates

3665: 2534:

Knowledge (XXG):Don't edit war over the color of templates

4096:

For lists running across the page, and in single rows in

3329:

This is the same paragraph, with a line break before it.

2619: 2296:

specifies Japanese written with the Latin alphabet (e.g.

2197:: Among other uses, specifying the language of text with 2100:

Knowledge (XXG):Manual of Style/Linking § Interwiki links

1786:

Do not use possibly unpronounceable symbols such as ♥ (a

1250:

Examples of correct and incorrect use of nested headings

5823:"H51: Using table markup to present tabular information" 5226:

Knowledge (XXG):Style sheets for visually impaired users

5182::commons:Commons:Video § Subtitles and closed captioning 5156::commons:Commons:Video § Subtitles and closed captioning 5010:

WP:Manual of Style/Images § References from article text

2688:

There are some tools for simulating color-blind vision:

2670: 2121:, which specifies the language and script. For example: 1159:, it can be helpful to all readers. We aim to adhere to 5368: 5201: 5158:. Subtitles are meant for the transcription of speech. 5086: 4934:

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

4915: 4735: 4398: 4087: 3864:, though you can bypass this by naming the parameters ( 3804: 3797: 3735: 3728: 3655: 3468: 3043: 2773: 2591:

Some readers of Knowledge (XXG) are partially or fully

2508: 2501: 2494: 2117:(or one of its derivatives). This wraps the text in an 2104:

Category:Knowledge (XXG) multilingual support templates

2075: 2068: 2061: 1952:

or side comments; do not use it for stylistic changes.

1889: 1882: 1831: 1824: 1696: 1689: 1655: 1610: 1443: 1436: 1214: 1207: 1200: 1181:

Knowledge (XXG):Manual of Style/Lead section § Elements

116: 109: 5466:

Knowledge (XXG):Make technical articles understandable

5121:

Be equipped with control functions (stop, pause, play)

5049:

Knowledge (XXG):Manual of Style/Mathematics § Alt text

3483:

An accessible approach to indentation is the template

3270:

This is a closing paragraph within the same list item.

2892:

Suppressing the bullet on a reply is also acceptable,

2449: 45:

Knowledge (XXG):Make technical articles understandable

2824:

and start a new discussion (i.e., a new HTML list).

2560:

For technical assistance on how colors are used, see

6669:

Do not disrupt Knowledge (XXG) to illustrate a point

6034:"G69: Providing an alternative for time based media" 5292:

element should also be avoided in article text; use

5274:

to format text; it is preferable to use Wiki-markup

5266:. In particular, do not use the HTML style elements 3022: