What this playbook covers and when to run it
The playbook covers everything a marketing team publishes: landing pages and forms, the website's marketing pages, emails, social posts and video, in-app messages, dashboards shared with colleagues and clients, and the support routes customers use when something does not work. It runs from finding the barriers that exist today to keeping new ones out. It does not teach the guidelines, colour contrast, alternative text writing, captions, form labelling or email structure; the guide to accessibility as conversion work explains what the Web Content Accessibility Guidelines ask in brief and where barriers sit along a journey, and each phase below hands off to the guide that owns its method.
Run it when accessibility fixes keep arriving as complaints rather than checks; when each channel has its own idea of what "accessible" means; when templates, brand colours or generated captions have never been checked; or when a redesign, a new template or a new channel is about to multiply whatever barriers exist now. Run it also before a large content programme, because barriers built into a template are copied into every page made from it.
Like the other playbooks in the playbooks library, it is a starting shape. A small team may run it with one owner and a short list of checks folded into existing routines; a larger one spreads the checks across content, design, development and service. It works alongside the creative production playbook, which carries assets from brief to release, and the SEO content operations playbook, which publishes and refreshes pages; this playbook adds the accessibility checks to both rather than running a separate line of work.
Roles and responsibilities
- Accessibility owner. Owns the programme: the standards, the barrier log, the schedule of spot checks and journey tests, the training and the yearly refresh. Decides the order of fixes with each channel owner. Does not carry out every check.
- Brand and design lead. Owns the accessible identity: approved colour pairs, type sizes, motion and the Brand VoiceThe consistent personality a brand expresses in its words across channels, with tone adjusting to the situation and the audience., and the templates built from them. Signs off new templates before they are used.
- Content editors and social managers. Write to the standards, fill the alternative text and caption fields and run the channel's checks before anything is published.
- Web and email developers. Build forms, pages and email templates that pass the checks, fix barriers in code and confirm each fix with the check that found it.
- Video and creative producers. Supply captions, transcripts and text alternatives with every asset, and review any generated versions before release.
- Customer service lead. Owns the route for customers to report a barrier, makes sure they get help another way while it is fixed, and passes every report to the barrier log.
A RACI matrix is a useful way to write these roles down per channel, because the commonest failure is a check everyone assumes someone else did. In a small team one person may hold several roles; the checks still need a named owner in each channel, or they slip on busy weeks.
Cadence, inputs and outputs
The rhythm below is a suggested starting point. Adjust it to how much the team publishes, how many channels it uses and how often templates change; it is not a standard or a legal requirement.
| Cadence | Owner | Inputs | Outputs |
|---|---|---|---|
| Per asset | Channel owner, producer | The brief, the template, the channel's checks | An asset that passed the checks before publishing, or a recorded exception |
| Monthly | Accessibility owner, channel owners | A sample of live pages, emails, posts and videos | Spot-check findings logged; repeated failures traced to a template or a step |
| Quarterly | Accessibility owner, developers | The key journeys, the barrier log | Journeys completed with the keyboard and a screen reader; barriers ranked and assigned |
| Annually | Accessibility owner, brand lead | The year's log, template changes, new channels | Standards, templates and training refreshed; the programme's next priorities |
| On report | Customer service lead, accessibility owner | A barrier reported by a customer | A reply and another route for the customer; the barrier logged, fixed and confirmed |
Each cadence feeds the next. Spot checks show which channel step keeps failing; the quarterly journey tests find the barriers spot checks miss; customer reports show which barriers matter most to the people affected; and the yearly refresh turns all three into changes to templates and training, so fewer barriers reach the next round of checks.
The playbook in phases
Find the barriers that exist now
Start with the journeys that matter most, from the first screen to the confirmation, and check them with the methods the accessibility guide sets out: the keyboard alone, a screen reader on a desktop and a phone, zoom and reflow, a phone held in one hand and an automated scan as a first pass only. The landing page audit scores accessibility against the WCAG success criteria as a guide to what to check, not as a legal opinion, and a Usability TestA research session in which a person attempts a realistic task on a site, app or prototype while an observer notes where they struggle. run as the usability testing guide describes, with participants who use assistive technology, finds what no checklist anticipates. Rank each barrier by where it stops people: on the conversion path first, then in content. The first pass becomes the barrier log every later phase reads and updates.
Build accessibility into the identity and templates
Decide colour, type and voice once so every asset inherits them. The guide to designing an accessible brand identity sets the approved colour pairs, colour that never carries meaning alone, legible type and logos, rules for motion, imagery and sound, and an accessible voice; the brand guidelines template records them. Then build the templates that carry most of the work: forms with labels, instructions and errors as the forms guide lists them, and email templates with real headings, alternative text and a sensible reading order, as the newsletter design and copy guide covers. A template with caption and alternative text fields that cannot be skipped makes every later check quicker.
Write it into briefs and standards
Accessibility belongs in the standards everyone writes to, not in a separate document nobody reads. The content governance guide puts accessibility beside style and accuracy in the editorial standards: headings in order, descriptive link text, alternative text for informative images, captions and transcripts. The writing for the web guide shows how several of the guidelines' success criteria are met or failed by the writer alone, and the guide to headings and content structure covers the structure screen reader users move through. Add a line to every brief that the work must be usable with a keyboard and a screen reader, so it is designed in rather than added afterwards.
Check before publishing in each channel
Build the same few checks into each channel's own publishing step rather than adding a separate review. For web pages, the web page publishing SOP includes a live check that the page is readable with keyboard navigation, and the landing page checklist carries the checks every new page should pass. For social, the guide to accessible social media posts covers alternative text, captions, text in images, motion and links, and the social post publishing checklist is the gate. For email, the comparison of plain-text and HTML email sets out what each format asks of accessibility, and the email campaign QA checklist is run before every send. In-app messages follow the accessible design section of the guide to designing in-app messages, and dashboards follow the accessibility and colour section of the dashboard design guide.
Review generated text and media
Alternative text, captions and transcripts drafted by a tool are drafts. The guide to AI for alt text, captions and transcripts explains why: a model can describe what is visible and transcribe speech at scale, but it cannot reliably supply purpose, names, exact figures or the judgement about what matters, and the people who rely on the text are the least able to notice when it is wrong. It sets review rules and a workflow by asset type. A person reviews every generated alternative before it goes out, and the creative approval SOP includes an accessibility check before release, which is where a missing caption or an unreviewed description is caught.
Support customers who meet a barrier
However good the checks, some customers will meet a barrier. Give them a clear route to report it and another way to get what they came for while it is fixed. The support channels guide sets out accessibility and inclusive support: chat widgets and contact forms that work with a keyboard and a screen reader, and more than one route to a person, including a written channel and a spoken one. The guide to supporting customers in vulnerable circumstances covers how agents adapt the process and record a need with the customer's agreement. Every report goes to the barrier log with what was reported, what help was offered and who will fix it, and the customer hears back when it is fixed.
Audit, fix and report
Barriers are fixed, not tested. The guide to conversion work without A/B tests lists an accessibility barrier among the changes that should simply ship: ship it, verify it, log it. After each fix, repeat the check that found the barrier. The approvals and compliance reviews guide makes accessibility part of the approval matrix by risk, with new pages, email templates and interactive content reviewed against the accessibility standard the organisation has adopted, and keeps an audit trail. Each quarter the accessibility owner reports what was found, what was fixed and what remains, and each year the standards, templates and training are refreshed from the log.
Who owns which check in which channel
The programme works only if every channel has a named owner for its check and a gate where the check happens. The table is a starting map; adjust the owners to the team's structure, but keep one owner per row.
| Channel | Checks that matter most | Owner of the check | Where the check happens | Guide |
|---|---|---|---|---|
| Landing pages and forms | Keyboard alone, screen reader, labels and errors in text, zoom | Web developer, page builder | Publishing and landing page checks | Accessibility as conversion work |
| Website content | Headings in order, link text, alternative text, plain language | Content editor | Web page publishing SOP | Writing for the web |
| Headings, alternative text, reading order, plain-text part | Email developer, campaign owner | Email campaign QA | Newsletter design and copy | |
| Social posts | Alternative text, captions, text in images, motion, links | Social manager | Social post publishing checks | Accessible social posts |
| Video and creative | Captions, transcripts, contrast, reviewed generated text | Producer | Creative approval | Alt text, captions and transcripts |
| Brand and templates | Approved colour pairs, type sizes, required text fields | Brand and design lead | New template sign-off | Accessible brand identity |
| Support routes | Keyboard and screen reader use, more than one route to a person | Customer service lead | Quarterly journey tests | Support channels |
Two rules keep the map honest. A check that has no gate is a hope, so every row names the step where it happens. And a failure found in a spot check is traced back to the row that should have caught it, so the fix goes into the template or the step as well as the asset. The academy capstone on a social programme governance plan for a swimwear brand practises setting accessibility standards and checks for every channel, beside an evidence plan, incident readiness and programme audits, in one year's calendar.
An adult education college makes its marketing accessible
Yelvisk College, an invented adult education college, starts the programme after a learner writes in to say she could not finish the course enquiry form. The accessibility owner checks the enquiry journey with the keyboard alone and with a screen reader and logs 6 barriers: the course picker cannot be reached by keyboard, errors show only as a red outline and the confirmation is silent to a screen reader, among others. A review of the last 20 social videos finds none with captions. The form is fixed without waiting for a test, and the keyboard check is repeated before it goes live. Captions and an alternative text check are added to the social publishing step and the creative approval step, and a template field for alternative text is made required. Each month the owner spot-checks 5 pages, 3 emails and 5 posts; the first spot check finds 2 posts with generated captions that misspelled course names, so a review step is added for generated captions. Over the year, 2 barriers are reported by learners through the enquiry line; each learner is helped to enrol by phone the same week, and both barriers are fixed and logged. At the yearly refresh the brand colour pairs are narrowed and the training is updated with the log's most common failures.
Measuring the playbook
The programme works when fewer barriers reach customers and those that do are fixed quickly. Operating signals show whether the rhythm is holding: whether every channel's publishing step includes its checks, whether the monthly spot checks and quarterly journey tests run and are recorded, whether every customer report is logged and answered, and whether each fix is confirmed with the check that found the barrier.
Outcome signals show whether the programme is changing how work is made: barriers found in spot checks that trace back to a template or step, and whether that number falls once the template is fixed; barriers reported by customers, which should come to light less often for problems the checks already cover; and the time from a report to a confirmed fix. Watch the step rates on key journeys too, such as a form's Form Abandonment RateThe share of people who start filling in a form, by entering a first field, but leave without submitting it., without expecting them to prove anything on their own; as the accessibility guide notes, a fix is justified by the barrier, not by the number.
Common mistakes
- Fixing pages but not templates. A barrier fixed on one page returns on the next one made from the same template. Trace every repeated failure to its template or step.
- Relying on an automated scan. A scan finds what a machine can see. The keyboard and screen reader checks, and people who use assistive technology, find the rest.
- Testing whether to remove a barrier. An A/B test keeps the barrier in place for half the visitors and cannot answer the question. Fix it, then test between accessible alternatives if needed.
- Trusting generated captions and alternative text. A tool's draft is not a reviewed alternative. A person checks every one before it goes out.
- One channel only. A website that passes while emails, social posts and videos do not is not accessible marketing. Give every channel a check and an owner.
- No route for customers. A customer who meets a barrier and cannot report it simply leaves. Offer a route, another way to get help, and a reply when it is fixed.
- Treating a tool or overlay as the fix. No tool makes content accessible on its own. The standards, templates and checks in this playbook do the work.
