Seven Checks Before Launch: A 2026 Accessibility Sprint for UK Campaigns

Campaign deadlines have a way of compressing testing into the final afternoon. That is precisely when accessibility issues slip through: a form that cannot be completed by keyboard, a video without captions, or a PDF that fails on a mobile screen. A pre-campaign accessibility check does not need to become a full audit. It should be a short, evidence-based routine that reduces risk before traffic arrives.

Why run a check before launch?

Accessibility problems are harder and more expensive to fix after launch, when content has been shared, links have been promoted and users have already met a barrier. For UK organisations, accessibility is also a legal and reputational concern. The Equality Act 2010 applies to many service providers and employers; public sector bodies have additional duties under the Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018. WCAG 2.2 AA is a practical benchmark for many teams, even where it is not a strict legal requirement.

The seven checks below are prioritised for campaign pages, service landing pages and event registration forms. They are not a substitute for a full audit, but they catch common issues quickly.

1. Keyboard navigation

Put the mouse aside and use the Tab key through the page. Check that focus is visible, the order is logical, skip links work and no component traps keyboard focus. Open any modal dialog and confirm it can be closed without a mouse. Test the main call to action and the full registration form.

Quick win: restore visible focus styles if they have been removed by a design system. A clear outline is not a cosmetic detail; it is how many people know where they are on the page.

2. Contrast and visual clarity

Check text against its background, including buttons, links, placeholder text and error messages. Normal text should generally meet a 4.5:1 contrast ratio; large text and non-text interface components should generally meet 3:1. Do not rely on colour alone to communicate meaning.

Quick win: replace low-contrast placeholder text with visible labels and stronger supporting text. Placeholder-only instructions are a frequent failure point on campaign forms.

3. Alt text with a purpose

Every meaningful image needs alternative text that conveys its function in context. Decorative images should have empty alt attributes so they are ignored by assistive technology. Complex charts or infographics need a short alt text plus an adjacent description.

Quick win: review the campaign hero image, logos, icons and social cards. Avoid alt text that begins with “image of”; describe what matters to the user instead.

4. Form labels and error messages

Registration and donation forms are common barriers. Each field needs a visible, programmatically associated label. Error messages should identify the field, explain the problem and suggest a fix. Group related fields, such as address lines, and avoid asking for information that is not needed.

Quick win: test the form by submitting it with missing or invalid information. If the error is only shown in colour, or only at the top of the page without a link to the field, fix that before launch.

5. Captions and transcripts

Campaign videos, social clips and audio need captions or transcripts. Captions should be accurate, synchronised and readable. Avoid autoplaying media with sound, and provide controls for anything that moves or updates automatically.

Quick win: check the campaign video on a mobile device with the sound off. If the message depends entirely on audio, captions are not optional.

6. Downloadable PDFs

PDF-only content is a frequent accessibility barrier. Provide an HTML version wherever possible. If a PDF is necessary, check that it has a logical reading order, meaningful headings, alt text for images and selectable text. Event packs, reports and campaign toolkits deserve particular attention.

Quick win: replace a PDF-only registration pack with a short HTML summary and keep the PDF as a supplementary download. This helps mobile users and assistive technology users alike.

7. Accessibility statement and contact route

An accessibility statement should explain how accessible the service is, note known limitations and provide a contact route for users who encounter problems. Public sector bodies have specific duties here, but the practice is useful for any UK organisation. Check that the statement is current, linked in the footer and includes a realistic response time.

Quick win: add a named contact or team inbox and review the statement before each major campaign. An out-of-date statement undermines trust.

When to bring in specialist support

Bring in specialist support when the campaign involves a complex form, a third-party booking widget, a new design system, a public sector compliance requirement or a significant legal or reputational risk. Specialist testing with disabled users can add valuable insight, particularly for services that will be used repeatedly.

Specialist support should complement the basics, not replace them. Fixing keyboard access, contrast, labels and captions first makes any specialist review more productive.

A simple launch routine

Assign an owner, run the seven checks on desktop and mobile, record issues in one place and fix blockers before launch. Note any known limitations in the accessibility statement. Then repeat the routine for the next campaign, rather than reinventing it under deadline pressure. A short accessibility sprint is a practical way to enable more users to take part from day one.