九色视频

In this page:

1. Titles and Headings
2. Readability
3. Tables
4. Links
5. Color
6. Alternative Text
7. Multimedia

---

1. Titles and Headings

Are they unique and descriptive? Do they provide a hierarchical structure?

Headings and Titles are style elements that may be applied to sections of text to provide structural information about the content. It is like creating an outline for your document or web page. They will be invaluable for people using screen readers, while also assisting your sighted users and boosting your Search Engine Optimization (SEO).

Titles

• Web page and document titles should be unique and descriptive.
• They will appear in the browser/Acrobat tab and search results.

Headings

• Use headings for structure; don’t use headings for design.
• Use the styles panel to apply heading tags. (For web, use Heading Styles to modify design without changing the Heading tag.)
• Use only one H1 (Heading Level 1) per webpage or document. (Note: on web, H1 is generated automatically from the page title or Custom Heading field.)
• Use in hierarchical order: H1 (main topic), H2 (subtopics of H1), H3 (subtopics of H2), H4 (subtopics of H3), H5 (subtopics of H4), H6 (subtopics of H5).
• Avoid skipping heading levels.
• By using headings & styles, you can also quickly add a table of contents, which is a valuable navigation tool for everyone.

Guidance: Headings & Document Outline

---

2. Readability

Is the language clear, and does the layout reduce cognitive load?

• Use plain language.
• Avoid jargon and figures of speech.
• Define acronyms on first use.
• Keep paragraphs short and use lists where possible to support scanning and understanding.
• Left-align all paragraph text: avoid centered and justified text. Centered text is difficult to track when new lines don’t start in the same place. Never use “Full Justify” alignment: it creates uneven “rivers of white space” that make reading significantly harder for users with dyslexia or cognitive disabilities.

Fonts and text spacing:

• Use standard, sans-serif fonts鈥攕uch as Arial or Verdana鈥攖hat will be available on all devices.
• Avoid fonts difficult to read fonts, such as serif, cursive, and ornate ones.
• Line height (line spacing): at least 1.5 times the font size.
• Font size: at least 12 pixels (or 11pt) for body text.
• Spacing following paragraphs: at least 2 times the font size.
• Letter spacing (tracking): at least 0.12 times the font size.
• Word spacing: at least 0.16 times the font size.

Guidance: Typography & Readability

---

3. Tables

Use tables for column-delineated data that has multiple rows. Don’t use tables for simple lists or for a grid to organize text.

• Avoid Tables for Layout: Never use a table to 鈥渓ook鈥� like columns or rows. Only use tables for actual data. Layout tables confuse screen readers by announcing 鈥淐olumn 1, Row 1鈥� for standard paragraph text.
• Always define header rows. A screen reader needs to know which cell is the “label” for the data below it. When a screen reader user is in the middle of a large table, they can’t see the top row. An accessible table will repeat the header name as they move (e.g., “Price: $20,” “Price: $35”) so they don’t lose context.
• Keep the structure simple. Screen readers move through tables linearly (left-to-right, top-to-bottom).
  • Avoid merged or split cells: “Rowspan” and “Colspan” (merging two cells into one) break the mental map for a screen reader. If you have to merge cells, your table might be too complex.
  • One table per topic: If a table is becoming a “mega-table” with multiple sub-headers or numerous empty cells, break it into two separate, simpler tables. (Example: separate multi-day conference schedules into one table per day.)
• No empty cells for “spacing”. Don’t leave cells blank: If a data point is missing, type “N/A” or “None.” An empty cell can make a screen reader user think the table has ended prematurely or that there is an error in the content.
• Provide a caption or summary. Most editors allow you to add a “Table Caption.” This acts like a title that is read first, allowing the user to decide if they want to skip the table or listen to the data. (Example: “Table 1: 2024 Staff Training Schedule.”)

Guidance: Accessible Tables

---

4. Links

Are links easy to find in the text? Are they descriptive of where the link goes or what may happen if clicked?

• Convey clear and accurate information about the destination. Write clear, unique link text so that the user knows where the link is going.
• Visually stand out from the surrounding text. Make sure links are distinct links are distinct from other text, using both color and underline or bold, and make sure the color contrast is compliant. (Our website styles links like this for editors automatically.)
• Be understandable out of context. Link text should make sense outside of context, screen reader users may pull up a list of just links on the page. 鈥淐lick Here鈥� or 鈥淩ead more鈥� is not allowed because users won’t know what they’re clicking into.

Guidance: Writing Helpful Links

---

5. Color

Does the text have enough contrast, and is color NOT the only way of conveying meaning?

Color Contrast

• Choose a text color that provides a high level of contrast against the background.
• The standard for web accessibility is a ratio between the two colors of 4.5:1.
• Avoid light text on a light background or dark text on dark background.
• Use the to test your colors.

Color for Meaning

• Avoid using color as the only indicator for conveying meaning or information.
• Use bold (<strong>) or italics (<em>) for emphasis rather than color, which may get confused for links.
• Use an additional element to convey information, such as icons, shape differences, or text labels.

Guidance: Color Contrast & Meaning

---

6. Images & Alternative Text

Determine if the information must be displayed as an image:

• Images should convey photographic or visual elements that paint a general picture better than words can convey.
• Images should not contain large amounts of text, or important textual details, that are better shared as textual content or tables.
• Images with text should use large, easily scannable text that is readable on both large and small screens, such as cell phones that shrink images.

If the information is best presented as an image:

Do all meaningful images have a descriptive text alternative?

• Alt text is read by screen reader software, and displays on the page if the image fails to load.
• Alt text should not just describe the image, but provide context on how the image relates to the page content.
• Alt text in linked images should describe where users will be taken when they select the image.
• Decorative Images, without information and used only for decoration, add null (“”) alt text or mark as decorative (role="presentation" alt="").
• Keep it simple, helpful & descriptive.

Guidance: Write Helpful Alt Text

---

7. Multimedia

Do audio and video multimedia have appropriate alternatives?

Transcripts

Provide transcripts for audio-only media, like podcasts or audio interviews.

Captions

Provide accurate captions for video.

Descriptive Audio

Provide descriptive audio in video or add an audio description track.

Guidance: Video Captions & Audio Transcripts