Skip to main content

Free guides to the law for parish, town and community councils

Guides for: England

We remember this choice with one cookie on this device, and use it for nothing else. Forget my choice

Does a parish council website need an accessibility statement?

England and Wales. Last checked against the source on .

Yes: a council with a website must publish an accessibility statement on it, in an accessible format, written to the government's model statement, and keep it under regular review. The website itself must meet the accessibility rules, with some exceptions; the statement says how far it does and what is not accessible and why, and links to a contact form for reporting a problem or asking for content that the rules let the council leave inaccessible. The regulations do not name parish, town or community councils, but they cover local authorities, and this page treats these councils as covered.

Applies to: Every parish, town and community council in England and Wales that has a website. The regulations make no exception for a small council or a small website.

The rules cover the websites of public sector bodies, which include "regional or local authorities". The regulations do not define that phrase. The Local Government Act 1972 counts parish and community councils as local authorities, though only for that Act (section 270). This page assumes that the regulations cover them too.

A council with its own mobile app must cover the app as well, in the same statement or a separate one. For the app, the statement must be in an accessible format, on the council's website or with the information people see when they download the app, and give the app's version and date.

What the statement must say

The regulations say the statement must include:

The regulation asks for "a contact form". It does not say whether an email address alone is enough, so the safe course is a form on the website.

What the website is measured against

The regulations require a council to make its website "perceivable, operable, understandable and robust", apart from the content they leave out and anything that would be a disproportionate burden (both below). A website is assumed to meet that requirement as far as it meets the Web Content Accessibility Guidelines (WCAG), published by the World Wide Web Consortium, at their Levels A and AA. Documents on the website, such as PDFs and Word files, are covered as well as its pages, apart from the older ones listed below.

Following the model

The statement must be "in accordance with the model accessibility statement". The government publishes the model on GOV.UK as the Model accessibility statement. It contains wording that must be used, with gaps in square brackets for the council to fill in. Its sections are:

GOV.UK also has a sample accessibility statement for a fictional public sector website, with sample wording and guidance. The sample is guidance; the model is what the regulations require the statement to follow.

Content the rules leave out

The rules do not apply to some content. Where content of these kinds is not accessible, the statement lists it as outside the scope of the regulations. Those a council is most likely to have are:

The other exclusions, for some copies of items in heritage collections and for older content on intranets and extranets (websites open only to a closed group, such as councillors), are in regulation 4.

Disproportionate burden

A council does not have to meet the requirement where doing so would impose a disproportionate burden on it. To rely on that, it must first assess how far meeting the requirement would be a burden. It must take account of all the relevant circumstances, including its size, resources and nature. It must also weigh the estimated costs and benefits for the council against the estimated benefits for disabled people, bearing in mind how often and for how long the website is used.

If it decides that meeting the requirement would be a disproportionate burden, it must explain in the statement which parts of the requirement it could not meet. Where appropriate, it must also provide accessible alternatives to documents it holds that are not available on its website.

Where it goes and how people find it

The statement must be in an accessible format and published on the council's website. The model's notes say a link to it should be easy to find on the home page, or on every page, and prominent, for example in the header or footer.

The duty is the council's own: the regulations put these duties on public sector bodies, not on the companies that build or host their websites.

Keeping it up to date

The regulations require the statement to be kept "under regular review", and set no interval. The model's notes recommend checking regularly, and at least once a year, that what the statement says is still accurate. They also recommend evaluating the website again, and updating the statement, after a substantial revision of the website. The statement gives the date it was last reviewed.

When someone reports a problem or asks for content

A person who thinks the website does not meet the requirement may tell the council. A person may also ask for content in an accessible format where it has been left out under the exclusions above, or because of a disproportionate burden. The council must respond within a reasonable time. If it does not, or the person is not satisfied with the response, they may complain to the Equality and Human Rights Commission, the enforcement body for councils in England and Wales.

If the council does not comply

What this page does not cover

Source

The official website shows the 2018 Regulations as revised, with no outstanding changes. Their last changes, on 3 June 2025, passed the Minister for the Cabinet Office's functions under them to the Secretary of State. It shows section 21 of the 2010 Act and section 270 of the 1972 Act as revised, each with changes not yet in force elsewhere in its Act; the one listed against section 270 itself does not affect the meaning of local authority. GOV.UK shows the model as last updated on 30 September 2024.

Last checked against the source on 14 November 2026.