Skip to Content

Iain Broome

Sheffield, UK

Freelance content designer and founder of Clear Language Club.

61 posts

Posts by Iain Broome

Using clear and effective headings Link post

I'm always slightly fascinated by the way different organisations in different sectors present their style guidelines. Here is Imperial College London on writing good headings and I can't see much I disagree with.

It includes the following statistic and link:

According to a WebAIM survey of 1,539 people in January 2024, 71.6% of screen reader users navigate pages using headings.

Make as note of that, as it might come in handy for future discussions with your senior leadership team or design colleagues.

The basics of plain language Link post

More good stuff on plain language basics in the Australian government's style guide:

There are 4 basic elements of plain writing. If you consider these elements, you’ll be well on the way to writing in plain language. They are: structure, word choice, active voice, short sentences.

I really like the last section that explains why plain language benefits everyone. Always worth reminding yourself. And anyone who'll listen.

Designing for people with anxiety Link post

This is a great post about designing for people with anxiety by Demelza Feltham on the Tetra Logical blog.

A lot of the ideas (or considerations) here are rooted in principles of good design and writing in clear language. But it's really useful to see how they translate to anxiety specifically.

These considerations focus on reducing cognitive load, lowering stress, and creating experiences that feel calmer and clearer for everyone. It’s not a complete list, but it highlights the areas that make the biggest difference to a calmer, more supportive user experience.

As someone who mostly works on government services these days, the section on transparency hit home:

It’s important to explain why certain information is being requested. If someone in real life asked for your date of birth or your pronouns without context, both personal details that aren’t automatically assumed, you might feel cautious or hesitant. Forms work the same way. Offering a brief explanation reduces worry, builds trust, and reassures people that their information is being requested for a clear, legitimate purpose.

This is in the context of creating a form, but I think it applies to any content where you are asking the user for something.

It's about being honest and clear, but you are also building trust. If a user thinks your website, service or organisation is being straight with them, that reduces the potential for anxiety.

There is another word I'd throw into the mix: acknowledgment. By explaining why you need a piece of information, you are showing empathy and understanding. You acknowledge that your request might cause anxiety, but providing reassurance that there is a reason for the ask.

You can follow a selection of links to other resources at the end of Feltham's blog post, including these designing for anxiety posters from the UK Home Office.