WCAG 2.2 AA for Parish Councils – An Introduction

What is web accessibility?

Web accessibility means making sure your website can be used by everyone, including people who:

  • Have poor eyesight or are blind

  • Are deaf or hard of hearing

  • Have learning difficulties or cognitive conditions

  • Have mobility issues and cannot use a mouse

  • Use assistive technology such as screen readers or voice control

In simple terms: an accessible website works for all residents, not just some of them.

Why accessibility matters for parish councils

As a parish council, your website is often the main way residents get information, such as:

  • Agendas and minutes

  • Contact details

  • Consultations

  • Policies and forms

If your website is not accessible, some residents may be excluded from local democracy.

Accessibility is important because:

1. It is the law

Public sector websites in the UK must meet accessibility rules under the
Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018.

These rules are based on WCAG 2.2 Level AA.

2. It helps real people

Accessible websites are easier for:

  • Older residents

  • People using mobile phones or tablets

  • People with slow internet connections

  • Anyone who finds websites confusing

3. It reduces complaints and risk

An inaccessible website can lead to:

  • Complaints from residents

  • Involvement from the Equality and Human Rights Commission

  • Extra work later to fix problems

Doing it right from the start saves time.

What is WCAG 2.2 AA?

WCAG stands for Web Content Accessibility Guidelines.

Version 2.2 AA is the current standard most UK public bodies are expected to meet.

It is based on four simple principles. Your website should be:

  • Perceivable – people can see or hear the content

  • Operable – people can use it with a keyboard or other tools

  • Understandable – content is clear and simple

  • Robust – works with assistive technology

You do not need to know technical details to apply most of this.

What the clerk needs to know

As the clerk, you are usually responsible for:

  • Adding new pages

  • Uploading agendas, minutes and policies

  • Updating contact details and news

This means most accessibility issues come from everyday content, not technical code.

The good news:

You can make a big difference just by how you write and upload content.

Next steps

To learn what to actually do in practice, read:

These two guides explain the practical steps in simple language.