Find the guide for your task.

Match each image alternative to its purpose, use captions for context, and hand off complex or interactive imagery for technical review.

Organize meaningful images with distinct alternatives, then have developers make gallery, carousel, and lightbox interactions usable by keyboard and assistive technology.

Put dates, times, locations, registration, and changes in HTML. Use flyers as supporting content, never as the only source of event information.

Use headings as an outline and write scannable copy so visitors can navigate sections, understand the page, and find the next action.

Give links purposeful labels, identify downloads honestly, and send unusual link behavior or document questions for technical review before publishing.

Use tables for related data, with captions and real headers. Keep structures simple and request technical help for complex or very large tables.

Ask only for needed information, label controls visibly, explain requirements, and provide errors people can find and correct before resubmitting.

Use Word styles, meaningful alt text, simple tables, and the right checker to create reports, forms, meeting documents, and design standards that people can navigate.

Create a tagged PDF from a structured source, then verify its reading order, links, forms, and text with automated and human checks.

Turn a structured source into an interactive PDF form with labeled fields, predictable keyboard order, clear instructions, and a tested alternative path.

Triage a legacy PDF, locate its source, repair OCR, tags, reading order, links, and fields, then document human verification and remaining risks.

Make Excel data and PowerPoint slides navigable with real headers, meaningful labels, alt text, logical order, and checks that follow the reader’s task.

Publish safety clips, meeting recordings, galleries, and podcasts with accurate captions, applicable transcripts, audio description, and a player people can operate.

Evaluate embeds, forms, portals, and vendor widgets as part of the user journey, with an equivalent path and monitoring when providers change.

Organize reports, forms, standards, meeting packets, galleries, and media with descriptive metadata, form IDs, revisions, useful links, accessible formats, and accountable maintenance routines.

A repeatable path from a draft to a checked live page, with a record of what changed and who reviewed it.

Define who prepares content, who checks it, who fixes barriers and who can make policy decisions.

Review new content, retest technical changes and keep evidence that makes the next review easier.

Capture the problem, help the person complete their task and keep the issue open until the fix is checked.

A first review for editors, plus the tests that need a trained reviewer. Check the whole task, not just how the page looks.

What the standard means, what changed in 2.2 and what this publishing guide can and cannot establish.