Skip to content
St George's and City have merged. Find out more.

The current standard for accessibility is Web Content Accessibility Guidelines (WCAG) 2.1. These guidelines outline the requirements for optimising websites for people with disabilities.

The guidance on this page provides a very basic blueprint for writing accessibly on the website.

Writing your content in plain English will also help you meet accessibility requirements. Read our guidance for writing for the web.

Tips for writing accessible content

View all Close all
Meaningful links

Your link text should describe the content being linked to. This allows people using screen readers to understand where links will take them.

You should always:

Read the Gov.uk guidance for creating links for examples and more information.

Alternative text (alt text)

Alt text provides a description of an image on a website. All images added to the website need to contain alt text.

You should also make sure that your alt text is informative – provide a useful description of the image or its function, don’t just write “a group of students”.

Here are some good examples of informative alt text.

 

 

Vaccine being placed in fridge

Alt text: A person placing a vaccine into a refridgerator in a lab.

An etching of St George's at Hyde Park Corner by Toms, c,1740.

Alt text: An etching of the front of St George's at Hyde Park Corner, Central London.

Learn how to add alt text on our image guide.

Avoid images containing text

You should always avoid using images that contain text. These images are not accessible to people using screen readers.

If it is unavoidable, provide as much detail as possible in your alt text for the image.

Write captions and transcripts

All videos on the site should include captions and a transcript. Make sure you include descriptions of any audio important to understanding the content.

For audio content, you will need to provide a transcript.

Keep your headings in order

Headings are essential for people using screen readers. They allow them to navigate websites quickly and easily.

Your headings should always follow the level order, H2 through H6.

These heading levels need to properly nested. As a general rule, H2 headings will indicate major sections of your page. A H3 heading will then create a new section under that H2. A H4 then marks a new section under the H3 heading and so on.

See Subheadings and page structure for more on how to structure your page using headings.

Avoid PDFs exported from Word

As a general rule, PDFs exported from Word will not meet accessibility requirements. The document first has to be optimised for accessibility in Word before you export it as a PDF.

Avoid this by putting the content on to a webpage instead.  Speak to our Design Team for support with making your documents accessible (email graphics@sgul.ac.uk).

Resources

WCAG have published their own guide: Tips for Getting Starting Writing for the Web Accessibility. The guide covers the basic considerations for starting to write accessibly for the web.

 

Find a profileSearch by A-Z