Skip to main content
Checklist

Inline Diagrams Pre-Ship Checklist

By ยท Updated ยท 4 read

Overview

Before merging any new diagram to production, run through this checklist. Misses on any item degrade citation eligibility, accessibility, or visual quality. The checklist is short on purpose โ€” these are the load-bearing things.

Structure

- The diagram is inline SVG (or HTML/CSS), not an external image file

- The `<svg>` element has a `viewBox` attribute for scaling

- `width="100%"` and `height="auto"` set for responsive sizing

- Wrapped in `<figure>` with a `<figcaption>` describing what it shows

Accessibility

- `role="img"` on the `<svg>` element

- `aria-labelledby` attribute pointing at `<title>` and `<desc>` element IDs

- `<title>` element exists as a child of `<svg>`, contains a short one-sentence summary

- `<desc>` element exists as a child of `<svg>`, contains a longer description of what the diagram conveys

Schema

- ImageObject JSON-LD block added to page `<head>`

- Block includes `name`, `description`, `contentUrl` (with anchor pointing to the diagram)

- Validated via Google's Rich Results Test โ€” no errors

Visual

- Brand-palette colors only (cyan, mint, coral-sparingly, purple, white, body, muted) โ€” no other colors

- Text labels at 11-14px (smaller is unreadable on mobile)

- Stroke widths: 2px for lines, 4-8px for accent strokes (never hairlines)

- Tested at 320px viewport โ€” no label overlap, no horizontal scroll

Performance + animation

- SVG size under 10KB (if larger, evaluate whether it should be external)

- If animated: `@media (prefers-reduced-motion: no-preference)` wrapper around the animation

- Animations use `transform` and `opacity` only (not `top`, `left`, `width`, `height` โ€” those cause layout shifts)

Frequently asked questions

What if a diagram fails one of these checks โ€” can I still ship it?

Depends on which one. Schema and accessibility are non-negotiable (failing those means failing the broader content bar). Visual and performance items have more flexibility โ€” a diagram slightly over 10KB is fine if it's genuinely needed at that detail level. Use judgment, but don't skip the non-negotiables.

How often should I re-audit diagrams that are already live?

Quarterly is plenty. The brand palette doesn't change often, accessibility patterns are stable, schema requirements evolve slowly. The main thing to watch: new pages going live without diagrams (the deliverable bar in CLAUDE.md should catch this proactively, but spot-check periodically).

MG
Written by

Matt is the founder of RunOctopus. He built All Angles Creatures from zero to page-1 rankings in reptile feeder insects in under 60 days using exactly this method โ€” turning a hard, entrenched niche into RunOctopus's proof store for programmatic SEO and AI search citation.

Connect on LinkedIn →

See what Otto would build for your store

Free architecture preview. No card required. Five minutes.

Generate Preview →