Create a Marketing Campaign Accessibility Exception and Remediation Log

Overview

A tracking method for recording accessibility issues found in campaign assets, assigning proportionate remediation, and verifying that fixes work in the published experience.

Record the barrier in context

An accessibility finding should describe what a person cannot do, perceive, or understand, and where the barrier occurs. Record the asset, channel, page or timestamp, affected interaction, test method, and evidence needed to reproduce it. Avoid vague entries such as 'accessibility failed' that leave the next person guessing.

Examples include missing alternative text, captions that omit meaningful speech, insufficient contrast, keyboard traps, unclear link names, and form errors that are not announced. Record the user impact and the task blocked, not just the technical rule that appears to be violated.

Prioritise by impact and exposure

Rank issues by how seriously they block the customer journey, how many assets are affected, and whether a practical workaround exists. A keyboard trap in a checkout flow usually deserves faster action than a minor issue in a rarely visited decorative element. Consider the severity of the task, not only the number of defects.

Use a consistent priority scale and explain the rationale. Do not downgrade an issue simply because the team has limited time. If an immediate fix is impossible, record an interim mitigation, owner, deadline, and escalation route. The log should make risk visible rather than convert it into an indefinite backlog.

Assign ownership and verify fixes

Give each issue one accountable owner, a target date, and a clear acceptance test. Design, content, engineering, media, and platform vendors may need different responsibilities. Specify whether the fix requires new copy, a layout change, caption correction, code adjustment, or replacement of a media asset.

After remediation, repeat the original test and check the live version. A ticket marked complete is not proof that a customer can now complete the task. Retest related templates and responsive states because a fix in one viewport may leave a barrier elsewhere.

Handle exceptions transparently

Some third-party tools or legacy assets may not be immediately replaceable. Document the reason, affected users, available alternative, decision-maker, and review date. An exception should be time-bounded and revisited, not used as a permanent substitute for accessible design.

Do not claim an asset is fully accessible solely because a vendor supplied a statement or an automated scanner reported no errors. Combine appropriate automated checks with manual keyboard, content, and assistive-technology testing based on the asset and risk.

Turn recurring issues into prevention

Review the log periodically for repeated defects across templates, agencies, and campaign types. Update creative briefs, component libraries, caption instructions, and release checklists to prevent recurrence. Track issue age and repeat rate, but interpret them alongside impact and remediation quality.

Share concise lessons with the people who create and approve assets. The best outcome is fewer barriers entering production, not simply a larger spreadsheet of issues that were found after launch.

Worked example

A campaign landing page has a button that cannot be reached by keyboard and a video with incomplete captions. The log records the exact page state, reproduction steps, user impact, owner, and target date. Engineering fixes the focus order, the content team corrects captions, and a reviewer retests both desktop and mobile. The release checklist is updated so the same components are tested on future campaign pages.

Implementation review

Use the applicable accessibility standard and qualified review for the asset, jurisdiction, and audience. Automated tools are useful for detecting some classes of defects but cannot establish full conformance on their own. Keep the remediation log linked to release evidence and revisit overdue high-impact issues.

Key takeaways

• Describe the user barrier and reproduction steps clearly.
• Prioritise by impact, assign an owner, and verify the live fix.
• Use repeated findings to improve templates and production checks.

Conclusion and next steps

Keep each finding tied to a reproducible barrier, a responsible owner, and a retest result. Review overdue high-impact issues with the release owner rather than allowing exceptions to remain invisible. Use the most frequent defect patterns to improve the components and briefs used by future campaigns.

References and further reading

• W3C — Web Content Accessibility Guidelines (WCAG) 2.2
• W3C WAI — Easy Checks
• W3C WAI — Making audio and video media accessible