2.2 Set the appropriate language for passages and phrases that use a language than the document default. Exceptions: proper names, technical terms, or foreign words that have become part of the vernacular. Screen readers pronounce words according to the language specified, so if a passage of text is in another language it will mispronounce the words in the passage. 1194.21(d); 1194.31(a); 1194.31(b) , page 17 3 Page Layout 3.1 Place images, data tables, charts, and other objects ‘inline’ with the document content (rather than ‘floating’). Where floating objects are unavoidable, ensure both the object and wrapped text around the object are part of the read order. Screen readers can only detect and properly read objects when they are placed 'inline'. Assistive technologies must present users with the correct reading order when text wrapping is used or content may be read in a confusing manner (line of text, followed by a table row, followed by a line of text, etc.). 1194.21(a); 1194.31(a); 1194.31(b); 1194.31(f) , page 65
3.2 Format columns and page structure to present a proper reading order to assistive technologies (do not rely on tables, TAB characters, etc.). When TAB characters are used to visually separate text and make it appear like columns, the reading order is garbled for screen reader users. Programmatic column formatting will maintain the correct reading order. Also, horizontal formatting of vertically arranged letters is difficult for low vision users to read, and since the text can be read one letter at a time, confusing for screen reader users. 1194.21(a); 1194.21(c); 1194.31(a); 1194.31(b); 1194.31(f) 4 Document Structure 4.1 Use programmatically discoverable headings to logically structure content, and avoid the skipping of heading levels. The use of styles and/or other programming allows keyboard-only and assistive technology users to navigate content. Applying bigger fonts, bold, underline, italic etc. does not programmatically set text as a heading. Skipped heading levels may lead screen reader users to believe there is missing information in the document. 1194.21(a); 1194.21(d); 1194.22(o); 1194.31(a); 1194.31(b); 1194.31(f) , page 45 , page 50 5 Paragraphs 5.1 Use paragraph spacing settings instead of carriage returns when additional line spacing is needed between paragraphs. Excess carriage returns are spoken by screen readers, interfering with normal reading. 1194.31(b) , page 56 6 Color Contrast
6.1 Use high color contrast (background to foreground contrast, watermark to foreground contrast, etc.). The color contrast ratio between the background and text should be at least 4.5:1. Users with low vision and color blindness may have difficulty reading documents that do not present sufficient contrast and color difference between background and foreground elements. 1194.31(b) , page 28 6.2 Text, images, and non-decorative graphics (bullets, dividers, etc.) must be visible when viewed in "High Contrast" mode. Users with low vision must be able to see the document content when it is displayed in “High Contrast” mode. 1194.21(g); 1194.31(b) , page 28 7 and Outlines 7.1 Programmatically identify bulleted, numbered, outline, and multi-level lists. Lists that are programmatically formatted allow users of assistive technology to easily navigate through and out of list content. 1194.21(a); 1194.21(d); 1194.31(a); 1194.31(b) , page 8 8 Data Tables 8.1 Use a summary or a caption when displaying data tables. Sighted users can quickly scan tables to understand their purpose, but many assistive technology users navigate with the keyboard. These users need a table summary or caption to describe the purpose of a table. 1194.22(a); 1194.31(a); 1194.31(b) Missing Alt Text (Table) 8.2 Identify column and row header cells programmatically. Sighted users can visually scan up and across a data table to find row and column headers. Correctly labeling rows and columns headers allows non-sighted users can make this association. 1194.22(g); 1194.22(h); 1194.31(a); 1194.31(b) , page 72
8.3 Ensure data cells are associated with the correct header cells. Complex tables may require additional header labeling to maintain the correct relationship for cells and headers. Merged cells can confuse the programmatic associations between data cells and their intended table headers. 1194.22(g); 1194.22(h); 1194.31(a); 1194.31(b) , page 14 9 Alternative and Descriptive Text 9.1 Provide alternative text or descriptions for non-decorative images, images within a link, form fields, and other interface elements. People who are blind or have low vision may need additional information presented as text so they can access information and control interface elements. Complex images may require detailed descriptions to convey important or useful information. For instance, provide a more detailed description for a chart demonstrating a growth trend. 1194.21(d); 1194.21(f); 1194.22(a); 1194.22(i); 1194.22(l); 1194.22(n); 1194.31(a); 1194.31(b) , page 86 9.2 When images depict text, the alternative text for the image should use the text in the image. When text is rendered as an image, decoration and styling usually do not convey additional information. Therefore, alternate text and descriptions should read the text depicted in the image. (Note: This is different from text within a larger image, diagram, or chart; see 2.1 and 2.7, which would also apply.) 1194.21(d); 1194.22(a); 1194.31(a); 1194.31(b) , page 86