Skip to main contentAccessibility Statement

Accessibility essentials

Work in progress

This content design guide is constantly being updated and improved. 

Got something you would like to see included? Email [email protected].

How to make your content usable for everyone and meet legal accessibility requirements

We need to make sure all content can be understood and used by everyone.

Web accessibility is a legal requirement for all public sector bodies. To maintain our website accessibility, we work to WCAG 2.2 AA standard.

Think accessibility first

Always ask yourself: who might not be able to use your content? Then fix it.

For example, if you:

  • upload a PDF document, make sure you have checked it is accessible
  • upload an image, include alt text
  • embed a video, it must have subtitles for people who cannot hear the audio content

How to make your content accessible

Documents

We should always try to avoid uploading PDFs to the website. Webpage content is easier to read, especially on mobile devices.

Documents should only be considered when the content is extremely long and all of it is needed (such as the school admissions prospectuses).

Follow this guide to make your document accessible:

Use plain language

Avoid jargon, acronyms and complex terms.

Explain technical terms if they must be used.

Find out more about writing for the web.

Headings, structure and navigation

Use bulleted or numbered lists where appropriate.

Break up long blocks of text with subheadings.

Ensure headings follow a clear hierarchy:

  • the page title is pre-set as H1
  • use H2 for headings
  • use H3 for sub-headings

If there are things people need to know before they are taken to a form, tell them clearly before the form link. You can see an example of this on the Pay a parking Penalty Charge Notice (PCN) page.

Links

See guidance on links.

Forms

Label all form fields clearly.

Include instructions before the field, not after.

Use error messages that explain what went wrong and how to fix it.

Tables

Use tables only for data, not for layout.

Add headers and ensure tables make sense when read top to bottom, left to right.

Avoid using merged cells.

Images

When using different colours in images, always check they meet colour contrast requirements using the WebAIM contrast checker.

Add alt text to images, explaining what the image contains in as few words as possible.

Try to avoid using images with text in them.

Language and translation

Not everyone will read your content direct from your page in English.

Using clear and concise language will make it easier for:

  • translation tools to translate your content accurately
  • search engines and AI large language models to provide accurate summaries

Animations and flashing content

Avoid flashing content or autoplaying video/audio.

Provide a way to pause or stop motion.

Testing accessibility

We monitor the West Northamptonshire Council website using a product called Silktide, which checks for accessibility issues.

Silktide also provides a monthly accessibility index of UK council websites

Check West Northamptonshire's current Silktide Index score.

Help with accessibility

For advice and support on accessibility, please email [email protected].

Last updated 23 July 2025