VibeLinker All articles
Tools & Platforms

Testing the Doorway: An Accessibility MOT for Your UK Community Platform

VibeLinker
Testing the Doorway: An Accessibility MOT for Your UK Community Platform

Photo: B722N, CC BY-SA 4.0, via Wikimedia Commons

Think of accessibility as the doorway to your community rather than the paperwork behind it. A doorway that only some people can get through is not a policy failure first — it is a room that stays half empty. That framing matters, because it changes the question from does this satisfy the Equality Act to who is currently standing outside looking in.

Below is a practical audit you can run yourself in an afternoon, without a consultant, aimed at the kind of digital spaces UK community groups actually use: forums, Discord and Slack servers, Facebook groups, WhatsApp communities, newsletters and the little websites that hold them together.

Run the five-minute scan first

The Web Content Accessibility Guidelines are long, but four of their principles do most of the work. Your platform should be perceivable, operable, understandable and robust. In plain terms:

The most useful single check is keyboard-only. Unplug the mouse, load your platform, and try to reach every important control using Tab, Enter and Escape. If you get stuck, or lose track of where the focus is, so will a lot of your members.

Captions are not a bonus feature

Anything with audio should have a text equivalent. That means captions for live sessions and transcripts for recordings — and transcripts are the more useful of the two, because they can be searched, skimmed and read on a train with no headphones.

Auto-captioning has improved enormously, but it still mangles names, acronyms and regional accents. Budget ten minutes to skim and correct it. If you are running hybrid meetings, check that the room microphone picks up the people in the actual room, not just whoever is nearest a laptop.

Remember too that captions serve people with tinnitus, people in noisy kitchens, people whose first language is not English, and anyone watching on mute at work. The overlap between accessibility and ordinary convenience is enormous.

Write like a human, not a policy document

Plain English is the cheapest accessibility upgrade available. Aim for short sentences, active voice, and the front-loading of the important bit. Cut jargon where a normal word exists. If you must use acronyms, expand them the first time.

A few habits worth adopting across your community:

Screen readers, colour and the things people forget

Check contrast ratios. Body text against background needs to reach the WCAG AA threshold, and thin grey-on-white text is the single most common failure found in community newsletters. Never use colour alone to convey meaning — the red-for-urgent convention means nothing to someone who cannot distinguish it.

Then listen to your own space. Turn on VoiceOver on an iPhone or TalkBack on Android and browse your group for five minutes. Narrating navigation is where most platforms fall apart: icon-only buttons announced as unlabelled, cookie banners that trap focus, forms without proper field labels. If your platform is a third-party app, this is worth raising with the vendor. If it is a group you run inside a platform, your lever is the content you post — accessible headings, alt text, and no images of text.

Low bandwidth and older devices

Not everyone is on fibre. Some members are tethering, some are on pay-as-you-go data, some are using a six-year-old handset borrowed from a relative. A page that loads three megabytes of video before anything readable appears is effectively a locked door.

Practical moves: compress images before upload, avoid autoplay of anything, keep essential documents in lightweight formats rather than heavy scans, and make sure the group works as plain text. A WhatsApp community with a text-first welcome pack reaches more people than an interactive dashboard ever will.

The Equality Act bit, briefly

The Equality Act 2010 requires service providers to make reasonable adjustments for disabled people, and that principle has been applied to digital services. Nobody is going to fine a village newsletter for missing alt text, but the underlying expectation is real and reasonable: if a member tells you a space does not work for them, you respond and adapt. In practice, the strongest compliance step is also the simplest one — build a visible way for people to tell you what is getting in their way, and answer it.

Your audit sheet

Work through this and note the gaps rather than scoring them:

That last point is the one people skip, and it is the one that matters most. Testing with real people who use assistive technology will surface things no checklist predicts. Pay them for their time if you can.

Accessibility is not a gate you pass once. Platforms update, members join, formats change. But treat it as the ongoing act of widening a doorway and the community gains something at every step — more people in the room, fewer good conversations missed, and a space that links people up rather than quietly filtering them out.

All Articles

Related Articles

Bricks, Bandwidth and Belonging: Making Hybrid Community Spaces Work in 2026

Bricks, Bandwidth and Belonging: Making Hybrid Community Spaces Work in 2026

Seven Homegrown Tools Putting the 'Local' Back Into Local Life (2026 Field Guide)

Seven Homegrown Tools Putting the 'Local' Back Into Local Life (2026 Field Guide)

The 11pm Group Chat Tax: Why UK Volunteer Moderators Keep Logging Off for Good

The 11pm Group Chat Tax: Why UK Volunteer Moderators Keep Logging Off for Good