Best Practices

Digital Accessibility (ADA)

Build accessibility into copy, visuals, documents, email, presentations, and social content from the beginning.

01

Understand ADA Title II

ADA Title II covers state and local governments, including public colleges and universities. The Department of Justice’s web and mobile app accessibility rule uses WCAG 2.1 Level AA as its technical standard. Read the official Title II guidance.

  • Title II is especially relevant to NASPA members working at public institutions. NASPA is a membership association, not a state or local government.
  • Use these accessibility practices across marketing materials, including websites, documents, email, presentations, and social media.
  • For an institution’s legal obligations, deadlines, and exceptions, consult its accessibility or legal team and current Department of Justice guidance.

This page provides practical design guidance, not legal advice or a determination of which ADA provisions apply to a particular organization. Good color contrast alone does not establish ADA or WCAG compliance.

Visual example

Know the difference

ReferenceWhat it covers
ADA Title IIState and local government services, including public institutions.
Title II web ruleWCAG 2.1 Level AA for covered web content and mobile apps.
WCAG 2.2Additional accessibility guidance used in this portal.
This pagePractical marketing and design checks, not legal certification.

02

Choose readable brand color combinations

A brand color is not automatically readable on every background. Check the text color against the exact background where it will appear.

  • Standard text needs at least 4.5:1 contrast. Large text needs at least 3:1.
  • Large text means at least 24px at regular weight or about 18.7px in bold (18pt regular or 14pt bold). If unsure, use the 4.5:1 standard.
  • White text works on NASPA Blue, NASPA Green, and Navy. Navy text works on White, Mint, and Emerald. Emerald text works on Navy.
  • White on Emerald fails both text thresholds. Use Navy text on Emerald, and Navy with White text for primary buttons. Keep Cyan, Emerald, and Mint out of text on White; on light backgrounds, Emerald is a decorative accent, not a meaningful icon or the only cue for a control or state.

The poor-contrast samples are intentional examples of what to avoid. Their labels, hex values, results, and suggested alternatives appear separately in readable text.

Visual example

Brand color contrast: good and poor examples

Good contrast

Navy on White

#043352 / #FFFFFF

13.12:1 · Passes AA for standard and large text

Use for body copy on light backgrounds.

White on NASPA Blue

#FFFFFF / #0E6BB1

5.59:1 · Passes AA for standard and large text

Use for text on a NASPA Blue field.

White on NASPA Green

#FFFFFF / #007960

5.38:1 · Passes AA for standard and large text

Use for text on a NASPA Green field.

White on Navy

#FFFFFF / #043352

13.12:1 · Passes AA for standard and large text

Use for primary buttons, with NASPA Blue on hover.

Navy on Mint

#043352 / #BAF5DC

10.74:1 · Passes AA for standard and large text

Use for text on a Mint field.

Navy on Emerald

#043352 / #34B879

5.17:1 · Passes AA for standard and large text

Use for text in an Emerald callout or accent field.

Emerald on Navy

#34B879 / #043352

5.17:1 · Passes AA for standard and large text

Use for accent text or icons on Navy, with a clear text label.

Poor contrast: avoid for text

White on Emerald

#FFFFFF / #34B879

2.54:1 · Fails AA for standard and large text

Use Navy text on Emerald, or Navy with White text for a primary button.

Cyan on White

#00B3F0 / #FFFFFF

2.41:1 · Fails AA for standard and large text

Use NASPA Blue or Navy for text on White.

Mint on White

#BAF5DC / #FFFFFF

1.22:1 · Fails AA for standard and large text

Use Navy text on Mint instead.

NASPA Blue on Navy

#0E6BB1 / #043352

2.35:1 · Fails AA for standard and large text

Use White text on Navy instead.

Ratios use the exact hex values shown on solid, opaque backgrounds. These are text-contrast checks, not a full accessibility assessment. Recheck gradients, photos, transparency, and the final output.

03

Make the visual understandable

A strong design stays readable across screens, zoom levels, and different ways of perceiving content.

  • Use at least 4.5:1 contrast for standard text and 3:1 for large text.
  • Check at least 3:1 contrast against adjacent colors for meaningful graphics and the visual information needed to identify interface controls or states. Make keyboard focus clearly visible.
  • Do not use color, position, or shape as the only way to communicate meaning; add labels, patterns, or text.
  • Keep essential text large enough for the final output and away from crop zones.
  • Write concise alternative text for informative images, charts, and graphics; mark decorative images accordingly.

Visual example

Contrast and meaning

Do

  • Text label + color
  • Strong foreground contrast
  • Useful image description

Avoid

  • Color-only status
  • Text over busy imagery
  • Filename as alt text

04

Create useful structure

Structure helps everyone scan content and gives assistive technology a meaningful reading order.

  • Use a logical heading sequence and real list formatting.
  • Use descriptive links that explain the destination or action.
  • Give tables clear headers and avoid using a table only to control layout.
  • Caption video, provide transcripts for audio, and describe essential visuals in the spoken content.

Visual example

Accessible reading path

  1. 1Page title
  2. 2Section heading
  3. 3Short paragraphs
  4. 4Descriptive action
  5. 5Supporting details

05

Test before publishing

Automated checkers are useful, but they cannot determine whether the content is understandable or the alternative text is meaningful.

  • Run the accessibility checker in the authoring tool.
  • Review reading order, keyboard access, zoom, captions, links, and document properties.
  • Inspect the final exported file, not only the editable source.
  • Ask a person to review high-impact or complex material when possible.

Visual example

Five-minute check

  • Contrast
  • Headings
  • Alt text
  • Links
  • Captions
  • Reading order
  • Final file

References and influences

These external resources informed the draft’s structure and practices. They do not replace NASPA policy or MarComm approval.

U.S. Department of Justice

ADA Title II: web and mobile app accessibility

Official guidance on the Title II rule for state and local governments, including public colleges and universities, and its WCAG 2.1 Level AA standard.

W3C Web Accessibility Initiative

Web Content Accessibility Guidelines (WCAG) 2.2

The current W3C accessibility standard for perceivable, operable, understandable, and robust digital content.

W3C Web Accessibility Initiative

How to Meet WCAG 2.2

A filterable quick reference for WCAG requirements, techniques, and common content decisions.

W3C Web Accessibility Initiative

Understanding text contrast

Minimum text contrast ratios, the definition of large text, and how contrast is measured.

W3C Web Accessibility Initiative

Images tutorial

A practical framework for deciding when an image needs a text alternative and what that alternative should communicate.

W3C Web Accessibility Initiative

Understanding non-text contrast

Guidance for contrast in controls, icons, charts, focus indicators, and other meaningful graphics.

U.S. Section 508

Create accessible social media content

Practical federal guidance for accessible images, video, links, hashtags, and platform content.

Canva

Create accessible PDFs with Canva

Canva guidance for contrast, alternative text, headings, reading order, and accessible PDF export.

Microsoft

Make PowerPoint presentations accessible

Accessibility guidance for slide structure, reading order, images, links, and media.

Salesforce Trailhead

Email design and accessibility tips

Marketing Cloud guidance for accessible, clear, responsive, and on-brand email design.

Last updated