Module 4: Accessible Design Practices

Why Typography Matters:
Typography directly impacts whether users can comfortably read and understand content. Poor font choices, tiny sizes, or bad spacing can make text inaccessible for users with visual impairments, dyslexia, or cognitive processing disorders.

Typography Accessibility Guidelines:

Font Size:

• • Use a minimum of 16px for body text (about 12pt in documents).

  • Increase size for headings, mobile users, or when designing for older adults.
    
    

Font Style:

• • Avoid decorative or cursive fonts.

  • Stick to simple, clean fonts that are easy to distinguish.
    
    

Font Family:

• • Choose sans-serif fonts like Arial, Verdana, Open Sans, or Tahoma.

  • Serif fonts (like Times New Roman) can be harder to read, especially at smaller sizes.
    
    

Line Spacing (Leading):

• • Use at least 1.5x line height for body text to prevent crowding.

  • Increase paragraph spacing to separate ideas clearly.
    
    

Additional Tips:

• • Avoid all caps for long sentences (harder to scan).

  • Limit italicized text and underlining (which can confuse screen readers).
    
    

Impact on Visual Impairments:
Accessible typography helps users with low vision, dyslexia, or cognitive disabilities quickly process information without fatigue or confusion.

Importance of Color Contrast:
Color contrast between text and background is crucial for users with low vision, color blindness, or light sensitivity. Low contrast makes reading difficult or impossible.

Color Contrast Guidelines (WCAG 2.1 Standards):

• Text should have a contrast ratio of at least 4.5:1 against its background.

• Large text (over 18px or 14px bold) can have slightly lower contrast (3:1).
  
  

Best Practices for Using Color:

• Don't rely on color alone to convey meaning (e.g., "errors shown in red").

• Use symbols, labels, or textures alongside colors.

• Use tools like the WebAIM Contrast Checker to verify your color choices.

• Choose color schemes that are friendly for users with color vision deficiencies.

Example: Avoid red-green combinations (common color blindness issue).

Addressing Color Blindness:

• Use patterns, icons, or labels in charts and graphs.

• Combine color differences with text or shape changes.

What is Information Architecture?
It’s how content is organized, structured, and labeled to make it easy to navigate.

Best Practices:

Use Heading Levels Properly:

• • H1 for page titles

  • H2 for major sections

  • H3 for subsections
    
    

Create Logical Groupings:

• • Group related content under headings or in bulleted/numbered lists.
    
    

Keep Menus Simple:

• • Avoid overwhelming users with too many choices.
    
    

Chunk Information:

• • Break large text blocks into smaller sections with headings.
    
    

Why It Matters:
Good structure helps users using screen readers, people with cognitive disabilities, and all users who need to skim for information.

Why Plain Language is Important:
Clear writing ensures everyone—including users with cognitive disabilities, English language learners, and busy professionals—can quickly understand the content.

Plain Language Guidelines:

• Use short sentences and paragraphs (preferably under 20 words per sentence).

• Prefer common, familiar words over technical jargon.

Example: Say "use" instead of "utilize".

Use active voice whenever possible.

Example: "The student completed the assignment," not "The assignment was completed by the student."

• Provide context before details.

• Use bullets or numbered lists for clarity.

• Summarize complex ideas before diving into deeper explanation.