Website Accessibility Statement

Accessibility statement for Littlehampton Town Council

This accessibility statement applies to www.littlehampton-tc.gov.uk. 

This website is run by Littlehampton Town Council. We want as many people as possible to be able to use this website. For example, that means you should be able to:
•    change colours, contrast levels and fonts
•    zoom in up to 300% without the text spilling off the screen
•    navigate most of the website using just a keyboard
•    navigate most of the website using speech recognition software
•    listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)

We’ve also made the website text as simple as possible to understand.
AbilityNet has advice on making your device easier to use if you have a disability.


How accessible this website is

We know some parts of this website are not fully accessible:
•    many of our documents aren’t fully accessible to screen readers
•    you cannot modify the line height or spacing of text
•    you cannot skip to the main content when using a screen reader
•    some of our images do not have alternative text


Feedback and contact information

If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille please contact us. We’ll consider your request and get back to you in 10 working days.


Reporting accessibility problems with this website

We’re always looking to improve the accessibility of this website. If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact us. If you wish to make a formal complaint, please complete our complaints form.


Enforcement procedure

If you have made a complaint and you’re not happy with our response contact the Equality Advisory and Support Service (EASS).

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’). 


Technical information about this website’s accessibility

Littlehampton Town Council 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 partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliance issues listed below.

 

Content that’s not within the scope of the regulations 

The content listed below is non-accessible as we are not required to:
•    make documents published before 23 September 2018 accessible, unless they are essential to access a service
•    make reproductions of heritage documents accessible
•    make online maps accessible
•    add transcripts to audio files at Level A/AA.

Non-accessible content

The content listed below is non-accessible for the following reasons:
Non-compliance with the accessibility regulations


1.    Issues with images

Some images do not have a text alternative, so people using a screen reader cannot access the information. This fails WCAG 2.1 success criterion 1.1.1 (non-text content).
We plan to add text alternatives for all images by October 2020. When we publish new content we’ll make sure our use of images meets accessibility standards. When we publish new content we’ll make sure any images we use meet accessibility standards.


2.    Issues with documents

Many of our PDFs and Word documents don’t meet accessibility standards – for example, they may not be structured so they’re accessible to a screen reader. This fails WCAG 2.1 success criterion 4.1.2 (Name, Role, Value).
•    Some of our resource documents, such as posters, are designed to be downloaded and printed, so these may not be fully accessible.
•    Some of the documents we link to are owned by third parties and may not be accessible.
Accessibility regulations don’t require us to fix PDFs or other documents that we own and published before 23 September 2018 unless they’re essential to providing our services. If you need information in another format, please contact us.
We are working to improve the structure of PDFs and Word documents published after May 2019 to make them more accessible through a screen reader. We are creating a roadmap which should be complete by December 2020. It will explain how we will make changes and provide timescales for when the documents will be fixed.


3.    Issues with contrast

We are aware that some of the text on the site needs more colour contrast. Contrast issues with text, links, buttons and form elements. This fails WCAG 2.1 success criterion 1.4.3 (Contrast - Minimum). We are working to improve this.


4.    Issues with Maps

We are aware that the embedded Google Maps are not accessible. We are working to improve this.

Disproportionate Burden


PDFs and Word documents

Accessibility Regulations require that PDFs and Word documents published after 23 September 2018 be fully accessible. Our documents are accessible but could be better structured for screen readers. 

We’ve assessed the cost of fixing the issues with PDFs and Word documents published prior to May 2019. We believe that doing so now would be a disproportionate burden within the meaning of the accessibility regulations. 


Content that’s not within the scope of the accessibility regulations

The content listed below is non-accessible as we are not required to:
•    make documents published before 23 September 2018 accessible, unless they are essential to access a service
•    make online maps accessible
Any new PDFs or Word documents we publish will meet accessibility standards.


What we’re doing to improve accessibility

We are creating a roadmap which should be complete by December 2020. It will explain how we will make changes and provide timescales for when the issues will be fixed.


Preparation of this accessibility statement

This statement was prepared on 22 September 2020. It was last reviewed on 14 September 2020.

This website was last tested on 14 September 2020. The test was carried out by our website developers, Webcurl, and ourselves.