3.2 Format columns When TAB characters are 1194.21(a); and page structure used to visually separate text 1194.21(c); to present a and make it appear like 1194.31(a); proper reading columns, the reading order is 1194.31(b); order to assistive garbled for screen reader 1194.31(f) technologies (do users. Programmatic column not rely on tables, formatting will maintain the TAB characters, correct reading order. Also, etc.). 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. 4 Document Structure 4.1 Use The use of styles and/or 1194.21(a); , page 45 programmatically other programming allows 1194.21(d); , page 50 discoverable keyboard-only and assistive 1194.22(o); headings to technology users to navigate 1194.31(a); logically structure content. Applying bigger 1194.31(b); content, and avoid fonts, bold, underline, italic 1194.31(f) the skipping of etc. does not heading levels. programmatically set text as a heading. Skipped heading levels may lead screen reader users to believe there is missing information in the document. 5 Paragraphs 5.1 Use paragraph Excess carriage returns are 1194.31(b) , page 56 spacing settings spoken by screen readers, instead of carriage interfering with normal returns when reading. additional line spacing is needed between paragraphs. 6 Color Contrast
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
Word2007E_AccessibilityGuidance.docx