Alt Text at Four O'Clock: Wiring Accessibility Into the Social Scheduling Queue

It is four o'clock on a Friday. Seven posts are queued for the weekend, the image files have arrived from an agency, and the person scheduling them has roughly twenty minutes before the school run. This is the moment at which most social media accessibility is won or lost — not in the brand guidelines, and certainly not in a design review that happened three weeks ago.

Accessibility guidance tends to be written for people who build things. Social teams need guidance for people who ship things, under time pressure, using tools they did not choose. A half-day audit is enough to find the gaps and, more importantly, to change the defaults so the gaps stop reappearing.

The legal backdrop, kept deliberately brief

The Equality Act 2010 requires service providers and employers to make reasonable adjustments for disabled people, and the Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018 impose specific duties on public sector organisations. Neither is a social media regulation as such, and neither will be satisfied by an alt-text field alone. The practical reading for a UK team is straightforward: accessible posts are the reasonable default, inaccessible ones need a justification, and a documented process is much easier to defend than good intentions. Treat this as quality assurance rather than a compliance programme.

Structuring the half-day

Four blocks of roughly an hour each, with a working lunch in the middle, is enough for a team of two to five people:

Time	Block	Output
09:00	Contrast and template audit	A list of branded templates that fail and need redesign
10:15	Platform settings and alt text	A per-platform field guide, saved as a team document
11:30	Captions and video	A caption style decision: burned-in, auto, or both
13:00	Workflow and ownership	Named writer, named checker, tool-level checks

Block one: does the branded template survive a phone screen?

Open each recurring template — quote cards, event banners, carousel frames — and test the text against the background at the size it will actually appear. WCAG 2.2 asks for a contrast ratio of at least 4.5:1 for body text and 3:1 for large text; a free contrast checker will give you the number in seconds. The usual failures are predictable: thin white type over a photograph, pale grey captions on a pastel brand colour, and text placed across a busy part of an image that shifts with each crop.

Fix the templates rather than the individual posts. If a colour pairing fails, it will fail every week until someone changes the master file, and the scheduler will not be the person who does it.

Block two: alt text, platform by platform

The alt text field exists on most major platforms now, and its character limit varies by network and changes from time to time — check the current limit rather than trusting a number in a blog post. What does not change is the technique. Describe what the image conveys in the context of the post, front-load the important detail, and skip phrases such as 'image of' because screen readers announce the medium already. If the image is decorative, leave the field empty rather than inventing filler.

Watch for the platforms that auto-generate descriptions. They are better than nothing and worse than almost any human description: they will identify a dog but not that the dog is wearing the company's branded collar at a fundraising event. Keep automatic alt text switched on as a fallback, and always overwrite it.

On LinkedIn and Facebook, alt text attaches to the image at upload; if the image is swapped later, the description does not travel with it. Build the habit of checking that the two still match before the post goes live.

Block three: captions are not just for silent viewing

Auto-captions have improved considerably and still mishear brand names, regional accents, technical vocabulary and anything said over music. For video, decide on a single house standard and apply it consistently. Burned-in captions are the safest choice for short-form social, where many viewers watch muted and the platform's own toggles are inconsistent. For YouTube and for any video embedded on the website, a proper caption file gives viewers control over size and contrast.

Whichever you choose, check the result on a phone with the sound off before scheduling. A caption that covers the speaker's mouth or disappears behind the platform's interface is not accessibility; it is decoration.

Block four: emoji, hashtags and link text

Screen readers announce emoji by name, so a row of five celebratory symbols becomes five spoken words in the middle of a sentence. Use them sparingly, keep them out of the opening line of a post, and never use them as bullet points.

Hashtags should be written in CamelCase — #DigitalWorkflows rather than #digitalworkflows — because screen readers use the capitalisation to find the word boundaries. Keep the number of hashtags modest and put them where they interrupt least.

Link text matters more than most social teams realise. 'Click here' tells a screen reader user nothing when links are read out of context, and shortened links are worse. Where the platform allows, write the destination into the sentence: 'the full report is on our website'. Also avoid putting essential information only inside an image; if the date and venue appear on the graphic, repeat them in the post copy.

Who writes it, and who checks it

The realistic answer is that the person scheduling the post writes the alt text, because they are the only person who knows what the post is trying to say. The check should be a second pair of eyes at the approval stage — a ninety-second read against a short checklist, not a formal review. Record the responsibility in whatever brief template the team already uses, so it survives the departure of the person who cares most about it.

Building the check into the tool

Most scheduling platforms — Buffer, Hootsuite, Sprout Social, Later and the native schedulers — have an alt text field and a preview. Add the accessibility check to the approval step inside that tool rather than in a separate spreadsheet; anything that lives outside the queue will be skipped the first busy week.

A workable fixture list for each post: alt text written and matched to the final image; captions checked with sound off; contrast passed on the template; hashtags in CamelCase; link text readable. Post the list beside the desk, in the team channel, and in the scheduling tool's notes field.

What to expect by the end of the quarter

The audit will not make every post perfect, and it should not slow the queue — the aim is ninety seconds of additional care per post, absorbed into the approval step that already exists. What it will do is move accessibility from a topic someone raises in a meeting to a property of the default workflow. That is the difference between a team that cares about accessibility and a team whose posts are accessible.