Google mobile test for websites Test here

1 Alt tags

All sites should have alt tags on images

In the image box where it says 'Alternative Text', type, your organisation name followed by image description i.e

'Name of Parish Council Clerks Councillors page image'

 2 Writing clearly for screen readers

  • do not hyperlink a word i.e See Planning write See Planning Click Here
  • if it is not obvious that it relates to the Parish Council, be obvious, don't write minutes click here, write name of Parish Council minutes date click here
  • Similarly all forms should be really clear i.e Name of Parish Council Application form for vacancy of whatever click here pdf

3 Using alt text for links as above the link should be clear and stand alone so as above 

See Planning Click Here - the alt text which appears when the link is moused over or read by a reader should say, this link is for more information and the planning page

To do alt text highlight your text and click link select advanced and advisory title, write what you widsh to say that the link does in here.

  • Be careful of abbreviations - including organisations, write in full in brackets if unsure how a reader will say it.

4 Add a site map

5 Uploading Documents

  • Ensure that the title of the pdf you upload has a title that can be read by a reader and that title makes sense i.e minutes Nov 2019

This well be read out as:- Nov 2019.pdf

5 Pdf's and Screen readers

I downloaded a screen reader and our PC sites work well, including PDF's. I downloaded screen reader and on most pdf's it read well, though there was a slight delay. some pdf's I tested did not read at all so I would suggest that all clerks download a screereader and test their recent pdf's.

When creating pdf's please see govenment guidelines. We can't really help with that BUT there is no requirement to fix PDF's from prior to Sept 18.


 ---------------- Accessibility Statement ---------- 

This website is run by xxxxxxxxxxxxxxxxxxxx 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.

For more information please go to 

Most older PDF documents are not fully accessible to screen reader software

Changing text size and colour

All modern web browsers allow you to change colours and font sizes. We’ve tried to create a site which doesn’t get in the way when you change these settings.

For advice on changing settings, check out the BBC’s accessibility pages click here.

How we run our site

Mobile and tablet friendly

Whatever device and browser you use, our site should be simple to use. If something doesn't look right, please let us know.

Plain English

We try to write in plain English and avoid council jargon. If something doesn't make sense, please let us know.

Headings and page structure

Our site uses simple heading structures to make it easier to navigate, especially if you use a screen reader or other assistive device.

Web standards

We try our best to comply with current web standards (CSS and HTML) and accessibility guidelines. Please make sure you are using the latest version of your preferred web browser - our site is designed to get the best out of modern web standards and technologies.

What to do if you cannot access parts of this website

If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille:

If you have any problems using the site, we’d really like to know. We’ll try and sort it out quickly and offer you advice.

You can email us at xxxxxxxxxxxxxxxxxxxx

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: xxxxxxxxxxxxxxxx

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

Yealand Redmayne 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. Yealand Redmayne Parish Council is partially compliant as it meets most requirements of the WCAG 2.1 AA standard.

PDFs and other documents

Many of our older PDFs and Word documents do not meet accessibility standards - for example, they may not be structured so they’re accessible to a screen reader. This does not meet WCAG 2.1 success criterion 4.1.2.

Some of our PDFs and Word documents are essential to providing our services. For example, we have PDFs with information on how users can access our services, and forms published as Word documents. By September 2020, we plan to either fix these or replace them with accessible HTML pages.

The accessibility regulations do not require us to fix PDFs or other documents published before 23 September 2018 if they’re not essential to providing our services. For example, we do not plan to fix some older pdf's.

Any new PDFs or Word documents we publish will meet accessibility standards.