Accessibility change log template

Compliance is proven through auditable history. This template records every change against the WCAG success criteria it touches, the person responsible, verification notes, and regression risk. Keep it alongside your DPIA, sprint notes, and release packs.

Back to WCAG service overview Download CSV template

Working table structure

Copy these columns into your tracking tool (Linear, Jira, Notion, spreadsheet). We keep column names human-readable so stakeholders understand the evidence instantly.

Date	Change summary	WCAG success criteria	Owner	Status	Verification evidence	Regression risk	Notes
2024-09-12	Homepage hero contrast adjusted	1.4.3 Contrast (Minimum)	S. Malik	Verified	axe scan + manual NVDA check	Low	Updated Tailwind tokens + design lib snapshot
2024-09-30	Navigation order restructured for keyboard	2.1.1 Keyboard; 2.4.3 Focus Order	E. Brady	In review	Video walkthrough + tab order script	Medium	Pending mobile VoiceOver confirmation

CSV starter

Import this comma-separated template into spreadsheets or data warehouses.

"Date","Change summary","WCAG success criteria","Owner","Status","Verification evidence","Regression risk","Notes"
"2024-09-12","Homepage hero contrast adjusted","1.4.3 Contrast (Minimum)","S. Malik","Verified","axe scan + manual NVDA check","Low","Updated Tailwind tokens + design lib snapshot"
"2024-09-30","Navigation order restructured for keyboard","2.1.1 Keyboard; 2.4.3 Focus Order","E. Brady","In review","Video walkthrough + tab order script","Medium","Pending mobile VoiceOver confirmation"

Markdown table

Drop this into docs, Git repositories, or retrospectives for quick sharing.

| Date | Change summary | WCAG success criteria | Owner | Status | Verification evidence | Regression risk | Notes |
| --- | --- | --- | --- | --- | --- | --- | --- |
| 2024-09-12 | Homepage hero contrast adjusted | 1.4.3 Contrast (Minimum) | S. Malik | Verified | axe scan + manual NVDA check | Low | Updated Tailwind tokens + design lib snapshot |
| 2024-09-30 | Navigation order restructured for keyboard | 2.1.1 Keyboard; 2.4.3 Focus Order | E. Brady | In review | Video walkthrough + tab order script | Medium | Pending mobile VoiceOver confirmation |

How we keep the log truthful

Pair every entry with evidence. Screenshots, screen recordings, and audit reports are stored alongside the log so the entry stands up to audit.
Reference success criteria explicitly. Never rely on shorthand ("contrast fix"). Name the WCAG clause so discussions stay objective.
Track regression risk. Accessibility can slip during redesigns. Our log flags risk so regression tests get budgeted.
Share the log. We publish ours to stakeholders weekly — aligning with the Breath Technology principle that marketing statements must match delivery actions.

Need deeper help? Request an accessibility audit and we will walk your team through adopting this workflow.