Accessibility Statement

Website Accessibility Statement

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 2009 and some individual elements of it may not have been updated since then.

How accessible is the website

We know that this website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard but some parts of this website are not fully accessible. We have an action plan and are working to put this right. Many of our older PDFs and Word documents may not meet accessibility standards - for example, they may not be structured 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. Any new PDFs or Word documents we publish will meet accessibility standards.

What to do if you have problems or queries about accessing parts of this website

If you have any accessibility problems or feedback, please email clerk@fulfordpc.org.uk

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 theEquality Advisory and Support Service (EASS).

Technical information about this website’s accessibility

Fulford Parish Council is committed to making its website accessible, in accordance withThe Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

Under theEquality Act 2010we 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 theWeb Content Accessibility Guidelines version 2.1AA standard, due to the non-compliances listed below.

Non-compliance with the accessibility regulations

· Image with no alt attribute - Image with no alt attribute. The image does not have an 'alt' attribute (alt=""). It’s important all images have the attribute for alternative text regardless of whether an alternative text is added.

· Image link is missing alternative text - Image with no alt attribute - It’s important all images have the alternative text attribute regardless of whether alternative text is

· Input field has no description - Input fields need a description associated with the field so users of assistive technologies know what the field is for.

· Text area has no description - Text areas need a description associated with the area so users of assistive technology know what the area is for

· Select box has no description - Drop-down menu (select boxes or role=”listbo”) need descriptions so assistive technology users know what they’re for.

· Webpage has multiple title elements or no title element - Webpages need a single title. The first thing a screen reader encounters when a page loads is the ‘title’ attribute text.

· Webpage title is missing text - Webpages need a title describing the topic. The webpage ‘title’ is added in the page ‘head’. The first thing a screen reader encounters on a loaded page is the ‘title’ text.

· Heading is missing text - This means an empty heading occurs. The tag for the heading is present, but there is no text in the tag.

· Alternative text for the image is a file name - The alternative text for an image must reflect the purpose of the image and not contain the image file name.

· Element ID is not unique - The ID used for an element on the page is also used for another element on the page. IDs must be unique

· Form control label is missing text - The form element has a label, but the text has not been added (label is empty). Add the text for the form element within the label-tag or WAI-ARIA ‘aria-labelledby’ attribute that is already present.

· Use of automatic redirect after a time delay - Do not use media redirect with a time limit. Instead use one of the recommended techniques.

· Language of page has not been set - The webpage is missing a definition of the natural language. Provide a ‘lang’ attribute for HTML documents or an xml:lang attribute for xhtml documents to indicate the natural language of the page.

· WAI-ARIA image is missing alternative text - The WAI-ARIA image, created with role=”img”, does not havean accessible name. If the image is informative or functional , use either the WAI-ARIA attribute ‘aria-label’ or ‘aria-labelledby’ to create an alternative text for the image. If the image is purely decorative, use the WAI-ARIA attribute role=”presentation” instead of role=”img” for the image. This will cause assistive technologies to ignore the image.

Content outside the scope of the accessibility regulations

· PDFs/documents (pre-September 2018):

· pre-recorded audio and videopublished before 23 September 2020

· live audio and video

· interactive mapsunless they provide core information

· content that’s under someone else’s control that we haven’t paid for or developed how we test the site

How we test the site

This website was last tested for Web Content Accessibility Guidelines version 2.1 AA standard compliance on 14th September 2020 by Fulford Parish Council using SiteImprove.

We tested our main website platform, available at www.fulfordparishcouncil.org.uk

Website Accessibility Action Plan

Investigate options for website provision and budget for a new, fully Web Content Accessibility Guidelines version 2.1 AA standard compliant website to be created and launched before April 2022.

PRE SEPTEMBER 2020 TESTING Accessibility Statement

This site conforms to the web standards defined by the W3C and complies with the UK Disability Discrimination Act of 1995. Content is served as semantically structured xHTML. Presentation information and dynamic functionality is separated from content using externally referenced Cascading Style Sheets and Javascript files. Because of this, one may view the site:

  • with Javascript or Stylesheets disabled,
  • using a wide range a devices, such as mobile phones, hand-held computers and screen-readers
  • using a computer of any age and specification that can run a standards-compliant browser (such as Firefox).

and it will remain accessible and understandable.

Adjusting the text size

To adjust the text size on this website:

  1. Click 'View' in the menu at the top of this window.
  2. Move the cursor to 'Text Size' in the drop-down menu.
  3. Select a new text size from the options that appear.

Help us improve...

If you have any problems using this website we would like to hear from you. Please contact the website designers with your feedback.