WCAG 2.1 AA for annual report PDFs: a practical checklist
A working checklist for accessibility tagging in annual report PDFs, written for in-house comms teams who need to sign off without guessing.
Most annual report PDFs that claim WCAG 2.1 AA conformance fall over on three things: incorrect reading order, missing table headers, and decorative graphics tagged as content. The fix is process, not a final-week clean-up.
Tagging that actually passes
- Document language set to en-AU at file level, not page level.
- Reading order matches the visual order on every spread, including pull quotes and call-outs.
- Headings tagged H1 through H6 in a logical hierarchy. No skipping levels for visual weight.
- Tables use TH cells with scope attributes for row and column headers. Merged cells are avoided.
- Decorative imagery marked as artifact. Charts get a short alt text plus a long description in the body or appendix.
Color and contrast
Body text needs 4.5:1 against its background. Large display text and bold subheads can run at 3:1. Brand colours that fail need a swap, not a workaround. We test every palette against WCAG ratios before we lock the design system, not after.
Charts and infographics
Charts are the most-failed component in accessibility audits. Each chart needs a short title, a one-sentence summary in the alt text, and either a data table in the document or a linked appendix. Color must not be the only way to read a series. Pair color with shape, label, or pattern.
Conformance statement
Every accessible report we lodge ships with a one-page signed conformance statement listing the standard (WCAG 2.1 Level AA), the testing tools used, the screen readers tested, and any known limitations. Auditors and procurement teams will ask for it.
Quick answers
Is WCAG 2.1 AA still the right target, or should we plan for 2.2?
AA at version 2.1 is the current Australian Government and most state procurement minimum. WCAG 2.2 adds nine criteria and is becoming standard for new procurement. We design to 2.2 by default and document conformance against 2.1 AA for compliance.
Do we need a separate accessible PDF and a print PDF?
Usually no. The same source file can output both, provided the design system is built with tagging in mind from week one. Retrofitting a print-first PDF for accessibility costs roughly the same as designing it accessible from scratch.