We want everyone who visits our website to be able to access the full range of services available, regardless of their skill or technology.
The current version of this website was launched in 2016, but some individual elements of it may not have been updated since then.
How accessible the site is
We know some parts of this website aren’t fully accessible. We have an action plan and are working to put this right.
What to do if you have problems or queries
If you have any accessibility problems or feedback, please email us at email@example.com
If you need to contact us about any other issues, please use our contact us page.
The Equality and Human Rights Commission (EHRC) is responsible for enforcing the accessibility regulations. If you’re not happy with how we respond, please contact the Equality Advisory and Support Service (EASS).
Technical information about this website’s accessibility
Horden Parish Council is committed to making its website accessible, in accordance with The Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
Under the Equality Act 2010 we must ensure we do not unlawfully discriminate in our service delivery and make reasonable adjustments for people with disabilities where necessary. We are constantly working to improve the accessibility and usability of our site.
This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances listed below.
Non compliance with the accessibility regulations
- headings: some headings don’t cascade inside some features on some web pages
- link text: some pages contain the same or limited link text going to different pages, some link text referring to the same page requires consistency
- text: while the website has been developed using plain English there is a need to ensure consistency across the site including use of consistent and accessible dates and times and remove characters that are difficult to be read
- images: some images have duplicate alternative text or have no alternative text
- tables: generated table code is not HTML5 compliant
- PDF’s : we need to check that pdf’s we use now are accessible and convert pdf’s to text where possible.
We intend to resolve these issues by July 2020 in order that we are fully compliant by September 2020.
- Documents that are supplied to us by other organisations will not be edited to make them accessible
Content that’s not within the scope of the accessibility regulations
- PDFs and documents: many of our older PDF documents don’t meet accessibility standards and may not be marked up so they’re accessible to a screen reader. The accessibility regulations don’t require us to fix PDFs or other documents published before 23 September 2018 if they’re not essential to providing our services. Where PDFs were published prior to that date we make a statement to that effect at the bottom of each page where such PDF’s are located.
How we test the site
We re-assess a website or system for accessibility whenever it undergoes a major modification.
Most page content is checked every time it is updated.
We will keep this accessibility statement under review and will amend it when necessary to ensure our commitment to bringing our website in line with the appropriate legislation.