Accessibility Review Checklist
Ensure communications are inclusive and accessible to people with different abilities and disabilities.
Keep in mind The AI can only judge what you paste or describe: contrast, keyboard, screen reader and PDF checks need real testing, and the review is not a statement of legal compliance.
Version 1.2 · Updated 30 October 2026
What you'll get
The opening of a worked example. Anonymised and shortened; yours will follow your inputs.
Fictional example: Brackenfold Housing, a housing association, reviewing its new "Report a repair" web page before launch.
Ready for review
1. Details
Title: Report a repair. Format: web page with a form. Standard: WCAG 2.2 Level AA. Reviewed by: [Confirm: name and date]
2. Visual
| Check | Result | Evidence | Fix |
|---|---|---|---|
| Alt text | Fails | Three photos showing where to find the boiler serial number have no alt text | Proposal: "Front of a boiler with the serial number label circled, bottom right" |
| Colour as the only signal | Fails | "Emergency repairs: call us, do not use this form" is shown only in red | Add a heading with the word "Emergency" and a labelled warning icon |
| Contrast | Not checked | No colour values given | Check text and button colours with a contrast checker |
3. Text
| Check | Result | Evidence | Fix |
|---|---|---|---|
| Heading structure | Fails | Section titles are bold text with no heading markup | Mark each section title as an h2 |
| Key points first | Meets | The emergency phone number is in the first paragraph | None |
| Plain language | Partly | "Responsive repair" and "void property" are not explained | Proposal: "a repair you report to us" and "an empty home" |
Next step
The prompt ends with questions for you. Answer them with this, in the same chat.
Here are my answers to your questions: [YOUR ANSWERS] Revise the draft using them. Remove the [Assumed] and [Confirm] marks my answers resolve, keep the rest, and update the questions and checks.
Human review checklist
Go deeper
Variations
Video and audio
Use this when the content is a video, podcast or webinar recording.
The content is [VIDEO, PODCAST OR WEBINAR], about [LENGTH]. Here is what is in it, in order: [DIALOGUE OR SCRIPT, SPEAKERS, IMPORTANT SOUNDS, TEXT ON SCREEN, AND WHAT IS SHOWN THAT IS NOT SAID]. Instead of headings 2 to 8, cover audio and video in full: caption guidance with examples of sound descriptions, a draft audio description for each visual moment that carries meaning and is not spoken, and the headings a transcript should use. Write captions and descriptions only from what I have listed; where you cannot tell what is on screen or who is speaking, mark it [Confirm: …]. Then complete headings 9 and 10.Plain-language rewrite
Use this when the main problem is that the text is too hard to read.
After the review, rewrite the text in plain language for [WHO WILL READ IT]. Keep every fact, figure, date, condition and legal or safety wording exactly as it is; where simplifying could change the meaning, keep the original and mark it [Confirm: can this be simplified without changing the meaning]. Then add a table with the columns Original | Plain version | Why, for the ten biggest changes. Do not give a reading age or score unless I have given you one from a tool.Full example output
Example output
Anonymised and shortened. Real outputs will vary based on your inputs.
Fictional example: Brackenfold Housing, a housing association, reviewing its new “Report a repair” web page before launch.
Ready for review
1. Details
Title: Report a repair. Format: web page with a form. Standard: WCAG 2.2 Level AA. Reviewed by: [Confirm: name and date]
2. Visual
| Check | Result | Evidence | Fix |
|---|---|---|---|
| Alt text | Fails | Three photos showing where to find the boiler serial number have no alt text | Proposal: “Front of a boiler with the serial number label circled, bottom right” |
| Colour as the only signal | Fails | ”Emergency repairs: call us, do not use this form” is shown only in red | Add a heading with the word “Emergency” and a labelled warning icon |
| Contrast | Not checked | No colour values given | Check text and button colours with a contrast checker |
3. Text
| Check | Result | Evidence | Fix |
|---|---|---|---|
| Heading structure | Fails | Section titles are bold text with no heading markup | Mark each section title as an h2 |
| Key points first | Meets | The emergency phone number is in the first paragraph | None |
| Plain language | Partly | ”Responsive repair” and “void property” are not explained | Proposal: “a repair you report to us” and “an empty home” |
4. Audio and video: not applicable, no video on this page.
5. Documents
| Check | Result | Evidence | Fix |
|---|---|---|---|
| Meaningful link text | Fails | Two links read “Click here” | Proposal: “Read our repairs policy” and “See which repairs are your responsibility” |
6. Interactive
| Check | Result | Evidence | Fix |
|---|---|---|---|
| Form labels | Fails | Postcode and phone fields use placeholder text only | Add a visible label above each field |
| Keyboard use and visible focus | Not checked | Described only | Tab through the whole form and note where focus is lost or hidden |
| Clear errors | Partly | The error says “Invalid entry” without naming the field | Name the field and say how to fix it |
7. Inclusive language: no ableist terms or metaphors found in the text provided.
8. Formats and distribution: the page says repairs can also be reported by phone. [Confirm: whether a text relay number is offered]
9. Issues to fix
| Issue | Where | Severity | Fix | Effort |
|---|---|---|---|---|
| Emergency warning shown by colour alone | Top of page | Critical | Heading and labelled icon | [Confirm: web team estimate] |
| Form fields without labels | Form | Critical | Visible labels | [Confirm: web team estimate] |
| Photos without alt text | Step 2 | Major | Add alt text (proposals above) | [Confirm: web team estimate] |
| Bold text used in place of headings | Throughout | Major | h2 markup | [Confirm: web team estimate] |
| Vague link text and error message | Step 3, form | Minor | Rewrite (proposals above) | [Confirm: web team estimate] |
10. Sign-off
Not ready for publication. Fix before publication: every failure listed above. Can go out with a recorded workaround: none until contrast, keyboard use and screen reader behaviour have been tested. Before sign-off, record any remaining limitations and who accepted them.
The template
Accessibility review checklist
Content title: [Type and subject]
Format: [e.g., web page, PDF, email, video, document]
Reviewed by: [Name and date]
Applicable standard: [e.g., WCAG 2.2 Level AA, EN 301 549]
Visual accessibility
- Images have descriptive alt text: Each informative image has alt text that describes it meaningfully for people using screen readers. Alt text is concise and meaningful; a file name such as “image123.jpg” does not count. Decorative images have empty alt text.
- Colour is not the only way to convey information: If colour indicates importance (red=urgent, green=approved), there is also text or a symbol, so people who cannot tell the colours apart still get the meaning.
- Contrast meets standards: Text contrast ratio is at least 4.5:1 for normal text, 3:1 for large text (WCAG AA standard). Check using a contrast checker.
- Text is readable size: Body text is a comfortable size (check your organisation’s web standards for a minimum). Text can be resized up to 200% without loss of content or functionality.
- Typography supports readability: Font choice and spacing are readable. Avoid long passages in capitals, justified text, or very narrow columns. Choose a clear, well-spaced typeface.
- Charts, diagrams, graphs have data tables: Complex visual information is available as accessible alternatives (tables, lists, descriptions) for people who can’t process images.
- Icons are explained: Decorative icons don’t need explanation, but functional icons (such as warning, tick or arrow icons) are explained or have text alternatives.
Textual accessibility
- Language is clear and simple: Jargon is minimised or defined. Sentence structure is straightforward. Avoid unnecessarily complex vocabulary. For public-facing content, GOV.UK’s guidance is to write for a reading age of around nine.
- Important information is up front: Key points appear first (inverted pyramid style). People using screen readers may not read the entire document.
- Headings structure the content: Proper heading hierarchy (H1, H2, H3) is used consistently. Headings describe the section clearly. Screen readers rely on this structure.
- Acronyms are expanded: First use of acronym is spelled out (e.g., “Service Level Agreement (SLA)”). People new to the field shouldn’t need external knowledge.
- Lists are formatted as actual lists: Bullet points and numbered lists use real list markup, so screen readers announce them as lists.
- Important content is in text: Key information is in live text, with no image of text carrying it alone. Where an image of text cannot be avoided, give the same information in the surrounding text as well as in the alt text.
Audio and video accessibility
- Videos have captions/subtitles: Deaf and hard of hearing people can access. Captions include dialogue and relevant sounds ([door slams], [music playing], etc.).
- Audio has transcript: For podcasts, webinars, video content without video access. Transcript is readable text, properly formatted.
- Audio description provided: For videos with important visual information, audio description (separate audio track or descriptive captions) explains what’s happening.
- Automated captions reviewed: If using auto-captions, they’re checked for accuracy (auto-generated captions can miss technical terms, names, accents).
Document accessibility
- PDFs are tagged properly: Document uses proper structure tags and real text. Generated from an accessible source document; scanned pages need fixing first.
- Fonts are embedded: Fonts work across devices/readers. Avoid decorative fonts that may not display correctly.
- Links are meaningful: Link text describes the destination; avoid “click here” or “link”. Used with screen readers, link text needs context.
- Tables have headers: Data tables use proper header markup. Cells reference headers for context. Avoid nested tables.
Interactive and digital accessibility
- Forms are properly labelled: Each form field has visible, associated label. People can understand what each field requires.
- Forms are navigable by keyboard: Can fill in the form using only the keyboard (tab and enter keys). Focus indicator shows where you are in form, and is not hidden behind sticky headers, banners or pop-ups (new in WCAG 2.2).
- Buttons and links are easy to hit: Touch and click targets are at least 24 by 24 CSS pixels, or have enough space around them (new in WCAG 2.2).
- Error messages are clear: When form validation fails, user knows which field has an error and how to fix it. Errors are announced to screen readers.
- Links and buttons are clearly defined: No “dummy” links (href=”#”). Buttons and links are keyboard accessible.
- Moving/animated content can be paused: Flashing, auto-playing, or moving content doesn’t create seizure risk (nothing flashing more than 3 times per second). Content can be paused by user.
Inclusive language
- No ableist language: Language doesn’t use disability as insult or negative metaphor (e.g., “blind to the issue,” “lame idea,” “deaf to concerns”). Language is respectful and person-first or identity-first as appropriate.
- Neurodiversity acknowledged: References to neurodiversity (ADHD, autism, dyslexia) aren’t pathologising or stigmatising. Respectful terminology used.
- Diverse representation implied or shown: Language and examples don’t assume everyone has same abilities/background. Inclusive pronouns used (they/them where you do not know someone’s pronouns).
- Plain language used: Content is clear and understandable for people with cognitive differences, non-native speakers, or lower literacy levels.
Format and distribution accessibility
- Multiple formats available: Content is available in a format other than PDF, such as an HTML or text version, or large print where needed.
- Email accessible: Email doesn’t rely on images to convey meaning. Text wraps properly in all email clients. Links are meaningful (avoid “click here”).
- Web version responsive: On mobile devices, content is as accessible as on desktop. Text doesn’t require horizontal scrolling.
- Print accessible: If printed, content remains accessible.
Sign-off
- Content meets applicable accessibility standard ([Standard name])
- Accessibility issues resolved or documented with workaround
- Ready for publication/distribution
- Accessibility maintained in updates
When to use it
What it is
An accessibility review checklist is a systematic assessment of whether your communications can be used by people with disabilities or different abilities, including people with vision impairments, hearing loss, motor limitations, cognitive differences, or older age-related changes. It covers everything from alt text for images to captions for videos to plain language alternatives to jargon.
Accessibility is also a legal duty. In the UK, the Equality Act 2010 requires organisations to make reasonable adjustments so disabled people are not put at a disadvantage, and public sector bodies must meet the Public Sector Bodies Accessibility Regulations 2018 for their websites, apps and documents. The European Accessibility Act has applied to specified products and services in the EU since 28 June 2025, with its own requirements and standards. GOV.UK guidance says UK public sector websites and apps must meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. Check with your legal or digital team which rules cover your organisation and content. This template helps you meet that standard for everyday communications, and clear, simple communication benefits every audience.
When to use it
Use this template when:
- Creating communications for public or broad audiences
- Accessibility compliance is required (legal, regulatory, or organisational policy)
- Communications include images, videos, PDFs, or complex formats
- Content will be published digitally
- You want to ensure inclusive practice
- Reviewing for legal/compliance before approval
- Creating materials for diverse audiences
Use something else if:
- You need a full technical audit of a website or app. This template covers communications content; a site or product audit needs a specialist auditor and testing with assistive technology.
- You need a formal accessibility statement for a public sector website. That has its own required format.
- The content is a quick internal message in plain text. Apply the plain language and inclusive language sections only.
Inputs needed
Before starting, gather:
- The content to review (all formats: text, images, videos, documents)
- Accessibility standards that apply (WCAG 2.2 Level AA is the current common standard)
- Your organisation’s accessibility policy or commitment
- Information about your audience accessibility needs
- Any known accessibility requirements from stakeholders
- Distribution channels (web, email, print, social, etc.)
- What has already been tested, and with which tools (contrast checker, automated tool, keyboard or screen reader test)
Tips for success
Use automated tools for baseline checking.
Automated checkers such as WAVE and Lighthouse catch obvious issues (missing alt text, colour contrast problems, structural issues). They find only part of what goes wrong, so treat them as a starting point, then test with a screen reader such as NVDA (Windows) or VoiceOver (Mac and iPhone).
Test with actual assistive technology.
Automated checking misses real usability issues. If possible, test with screen readers, keyboard navigation, speech recognition. Real user testing is invaluable.
Plain language benefits everyone.
Accessibility is part of good communication. Clear, simple language helps people with cognitive differences, non-native speakers, people on mobile, and people reading quickly. It makes the communication better for everyone.
Make captions comprehensive.
Caption more than dialogue: describe important sounds, silences, and visual information. “[Door slams]” or “[phone ringing]” help deaf viewers understand what’s happening. Captions should be complete enough someone could understand without sound.
Don’t assume disabilities.
Not all people with vision loss are completely blind. Not all people with hearing loss prefer sign language. Ask your users about their needs, which vary from person to person.
Common pitfalls
Assuming accessibility is “add-on.”
Retrofitting accessibility onto finished content can be hard. Building it in from the start is easier. Don’t create content then try to make it accessible afterward.
Only checking alt text and captions.
Yes, those matter, but accessibility is broader. If your page structure is broken, captions won’t help. If your language is too complex, clear alt text won’t fix understanding. Check everything.
Using poor colour contrast thinking it looks better.
Light grey text on white can fail contrast checks. Good design includes sufficient contrast.
Forgetting about keyboard users.
Some users can’t use a mouse (due to motor limitations, tremors, or preference). Everything that works with a mouse should work with keyboard alone (tab, enter, arrow keys). Test your whole site with keyboard navigation.
Setting alt text to blank for decorative images, then forgetting which are decorative.
Some “decorative” images are actually informative. Think carefully. A photo of a product is informative. A spacer image is decorative. Err on the side of including information if you’re unsure.
Related templates
Approval Workflow Mapper
Map out sign-off processes for content approval workflows to ensure clear accountability and timelines.
Content Approval Tracker
Monitor the status of multiple content items moving through approval workflows in a centralised dashboard.
Tone & Style Checker
Verify communications maintain brand voice consistency and appropriate tone for audience and context.