Council Site Check

Accessibility statement for a parish council website (with template)

Updated 15 November 2026. Sources checked 15 November 2026.

Every public sector website, including parish and town council websites, must publish an accessibility statement and keep it under regular review. For the AGAR, the Practitioners’ Guide treats the statement as the minimum a council needs for the website part of Assertion 10.

What the statement must include

Regulation 8 of the 2018 regulations says the statement must be in an accessible format, published on the website, and must include:

  1. which parts of the content aren’t accessible, and why;
  2. where appropriate, the accessible alternatives you offer;
  3. a way to tell you about accessibility problems and to ask for content that’s exempt (a contact form or route);
  4. a link to the enforcement procedure (in England, the Equality Advisory and Support Service, then the EHRC).

The guide adds that the statement should give the reasons for not meeting the requirements, how to get alternative copies of documents that aren’t accessible, and a point of contact.

How often to review it

The regulations say “regular review” without a fixed period. The internal audit checklist in the guide (test O) asks auditors to check that the website’s accessibility has been tested at least once a year and that the statement has been updated as needed, so a yearly review, with the date shown in the statement, is the practical minimum.

The standard

GOV.UK guidance now refers to WCAG 2.2 AA, and so does the Practitioners’ Guide. If fixing something would be a disproportionate burden, you must carry out an assessment and say so in the statement. Lack of time or knowledge doesn’t count.

Template

This is adapted from the GOV.UK sample statement (Open Government Licence v3.0). Replace everything in square brackets, and only claim what you have actually tested.

Accessibility statement for [council name]

This accessibility statement applies to [website address], run by [council name].

We want as many people as possible to be able to use this website. For example, you should be able to change colours, contrast levels and fonts, zoom in up to 400% without the text spilling off the screen, and navigate most of the website using a keyboard or speech recognition software.

How accessible this website is
We know some parts of this website are not fully accessible:
- [for example: some older PDF documents are not fully accessible to screen reader software]
- [list each known problem]

Feedback and contact information
If you need information on this website in a different format, such as accessible PDF, large print or audio, contact the clerk at [council email] or [phone]. We’ll consider your request and get back to you in [number] days.

Reporting accessibility problems with this website
If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact the clerk at [council email].

Enforcement procedure
The Equality and Human Rights Commission (EHRC) is responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (the ‘accessibility regulations’). If you’re not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).

Technical information about this website’s accessibility
[Council name] is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

Compliance status
This website is [fully / partially / not] compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, due to [the non-compliances / the exemptions] listed below.

Non-accessible content
[List each problem, the WCAG success criterion it fails and when you plan to fix it. If you are claiming disproportionate burden, say so and why.]

Content that’s not within the scope of the accessibility regulations
[For example: PDFs published before 23 September 2018 that aren’t needed to use our services.]

Preparation of this accessibility statement
This statement was prepared on [date]. It was last reviewed on [date].
This website was last tested on [date] against the WCAG 2.2 AA standard. The test was carried out by [who].

Link the statement from every page, usually in the footer, and record the review at a council meeting so you have evidence for the internal auditor.

Sources

Independent automated check. Not an audit and not legal advice.