Creating Accessible Content

Content Creation

If you create, edit, upload, publish or distribute content, you must ensure it’s accessible before posting or distributing communications and Web pages, LMS items, documents (PDF/Word/Slides/etc.), images and charts, audio/video, forms/surveys, announcements/emails, and social posts from official accounts.

Use the following baseline practices to help ensure your web content, documents, media, and forms are accessible to all users.

  • Use proper headings.
  • Write clear, concise, plain language; avoid jargon.
  • Alt text for informative images; alt="" for decorative.
  • Meaningful links (“Apply for housing,” not “click here”).
  • Ensure color contrast; don’t use color alone for meaning.
  • Use lists and tables correctly (headers, no layout tables, no merged cells, add description).
  • For documents: use built-in styles, tag PDFs, set reading order.
  • For media: add captions; provide transcripts for audio; include audio description when visual info is essential.
  • For forms: keep labels clear; provide instructions and error help.
     

Web development

If you design, build, or maintain websites or web apps, you must ship code that is accessible by default, keyboard operable, screen-reader compatible, and usable at zoom/reflow before release.

Use the following baseline practices to help ensure your pages, components, and apps are accessible to all users.

  • Use semantic HTML first; add ARIA only when necessary.
  • Ensure full keyboard access, logical focus order, and a visible focus indicator.
  • Provide skip links, unique page titles, clear headings/landmarks.
  • Meet color contrast (text and UI); don’t use color alone for meaning.
  • Forms: explicit labels, instructions, error messages, and programmatic associations; announce async updates.
  • Images and icons: informative images have meaningful alt; decorative use alt=""; label icon-only controls.
  • Media: captions for video; transcripts for audio; audio description when visuals convey essential info.
  • Custom widgets: expose correct name/role/value; manage focus; support arrow keys where appropriate.
  • Responsive/reflow: content works at 200%+ zoom without loss; no horizontal scroll for text.
  • Tables: use headers/scope for data tables; avoid layout tables.
  • Performance and timing: avoid timeouts that hinder assistive tech; provide controls for moving/auto-updating content.
     

Need help, support or guidance?

Need Help?

Request support from our Accessibility Compliance Specialist.

Barriers

We strive to make our content accessible to everyone. If you’re experiencing issues, please let us know.

Accommodations

Request alternate format or disability-related accommodations.