Enter this page in the NHS service manual, which says:

Creating a new PDF document is a last resort and you should avoid it unless there is a specific user need for it. You should always provide an HTML version too.

Not only can you use this page to bolster your no-PDFs argument, it also includes examples of when you might really need to use a PDF and, if so, how to do it in the best possible way.

The Inclusive Design Guide can be applied to digital design as well as to the design of services, the built environment and physical products. It can be applied to processes like workshops, meetings, conferences, and even our daily interactions with one another. It can be used by anyone.

By the way, I found this via an excellent collection of accessible design resources put together by Chris Nasrawi.

It does a few things, but the most important is it remembers more than one thing you copied, including images and any formatting if you want it.

Here is the blurb:

If copy and paste is a part of your workflow, Pastebot is an indispensable tool to improve your productivity. Quickly recall clippings that you have copied before and apply powerful text filters to format before pasting. Queue up multiple clippings to paste in sequence. Pastebot is always running and only a keyboard shortcut away to command copy & paste.

And if you do not use a Mac, Zapier has a list of what it reckons to be the 5 best clipboard managers, which covers various platforms.

Here's a good introduction to alt text on GOV.UK.

In time, I will no doubt link to specific resources and add the most relevant stuff to our very own Clear Language Bookmarks. But don't wait for me to find the most golden of nuggets – get stuck in and start exploring.

The Co-op team do lots of great work and this piece by lead content designer, Helen Lawson, includes some fine examples. It covers the principles that help funeral directors write and work with content.

This paragraph resonated with me:

We reduce the chances of misinterpretation by being very deliberate with the language we choose. For example, we say “he died” not “he passed away” because euphemisms can be misunderstood – especially when English is not someone’s first language. Defined by Collins Dictionary as “a polite expression used to refer to things which people may find upsetting to talk about”, euphemisms about death do not soften the blow but they can lead to confusion.

I have spent the last 18 months working on content where I have needed to tackle this exact challenge. How can we write clearly and directly, while also showing empathy, understanding, even warmth? It is not easy. Often, I have felt like there were no right words available to me at all.

Luckily, I have been working alongside a team of other experienced content designers. We've had the most success when we have worked openly and improved content based on insights from user research. In practice, that means making changes to language and tone in response to feedback from the audience. And by sharing with and learning from each other.

Sometimes, that work has led to a change in terminology – a simple update to the style guide. But there have also been fundamental shifts in how the entire organisation talks and writes about the service and its users. It has had a material effect on both internal culture and the user experience.

Of course, this is how you should approach all projects. Listen to your audience. Write or make a thing. Test it and be willing to change. But I'd argue it is even more important to have these conversations and work iteratively when the content you're working on has potential to cause harm or traumatise.

You may already know about WAVE, which is one of many free tools that helps you check the accessibility of a website or single web page.

WAVE^® is a suite of evaluation tools that helps authors make their web content more accessible to individuals with disabilities. WAVE can identify many accessibility and Web Content Accessibility Guideline (WCAG) errors, but also facilitates human evaluation of web content.

The second clause in that last sentence is some way from being written in clear language, but it is important.

WAVE is fantastic at automatically picking up errors in your website. But you – dear human – must be the one to look for and identify accessibility issues more generally, and especially with your content.

Watch the 11-minute explainer video to get a good introduction to WAVE. Then head to the home page, enter a web address and poke around to see how it works hands on.

As I was preparing the requirements for an accessible web video player, there was some confusion around subtitles, closed captions, audio descriptions and transcripts. In this post, I use interactive examples to show the difference. I also provide related success criteria from the Web Content Accessibility Guidelines (WCAG).

I'm sure there will have been times where I have previously talked about subtitles when what I really meant was closed captions. Maybe for you too?

If you create videos of any kind, this is the sort of stuff you should know. And of course, video-making tools are now so much better at helping you create and add subtitles, captions and transcripts. There isn't much of an excuse to not make your video content accessible.

For example, I use the excellent Descript to make podcasts. Add an audio or video file to your project and the app will auto-generate a transcript for you. The transcript is never perfect, but it gives you a fantastic start by doing the bulk of the work for you. A few tweaks and it's ready to go.

Designing for older adults isn’t about simplifying everything or creating a “senior version” of your digital experience. It’s about designing with respect, complexity, and care — just like you would for any other audience.

That's the gist of it, but Kelly also includes a range of research-backed personas to help you think about how different people might approach your content. Basically, it's 2026 and we are quite some way past the notion of the 'silver surfer'.

I can recommend this short talk on the writing process by Scott Kubie, which sets out four stages for each 'assignment'.

It's all great, but I want to particularly second the idea of creating an outline before you get started. That could be a few bullet points, draft headings or even a sentence that describes what will go where.

Things might change when you get into the meat of things, but that's okay. Everything changes. Change is good. Life is change.

Scott has a personal website absolutely full of content-related resources that you should also visit and explore.

Allow me to share a tip of my own. It sounds silly, but there is one style guide of mine that got used the most. I knew it would make a huge impact if everyone embraced it, but there was low digital maturity in the team. So I printed hard copies out and put them on everyone's desks.

It worked because they could see it right there in front of them and watch each other use it as a reference document. Within a few months, they were adding new stuff to the guide themselves and gradually we all moved to the digital version, which was collectively kept up to date. Win!