Accessibility statement

This accessibility statement applies to The Thread website.

This website is run by Renfrewshire 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:

  • images with redundant alternative text
  • pages with redundant links or links that do not make sense out of context
  • heading elements that are not consistent
  • redundant title text
  • access key on cookie preferences
  • no facility to skip to the main content when using a screenreader.

What to do if you cannot access parts of this website

We’re always looking for ways 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, please let us know.

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

  • web@renfrewshire.gov.uk
  • 0300 300 0330
  • Digital Experience Team
    Communications and Marketing
    Renfrewshire Council
    Renfrewshire House
    Cotton St
    Paisley
    PA1 1WB.

We’ll get back to you in five working days.

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

Technical information about this website’s accessibility

Renfrewshire 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-compliances and exemptions listed below.

Non-accessible content

The content listed below is non-accessible for the following reasons.

Redundant alternative text

There are instances of alternative text that is the same as nearby or adjacent text which is presented multiple times to screen readers or when images are unavailable. This fails 1.1.1 Non-text Content (Level A).

Redundant links

Adjacent links sometimes go to the same URL. When adjacent links go to the same location, this is repetitive for keyboard and screen reader users. This fails 2.4.4 Link Purpose (In Context) (Level A).

Suspicious link text

Some elements of our theme are fixed and we are unable to change the text within them. This means that link text may not be unique and so may not make sense out of context. This can be confusing for screen reader users. This fails 2.4.4 Link Purpose (In Context) (Level A).

Skipped heading level

On rare occasions, heading elements are fixed by the theme that we have used and cannot be changed. Headings provide document structure and help with keyboard navigation for users of assistive technology. These users may be confused or have problems navigating when heading levels are skipped. This fails 1.3.1 Info and Relationships (Level A).

Skip to main content

There is no facility to skip to the main content when using a screenreader. This means that navigation and main content elements are repeated across web pages. This fails 2.4.1 Bypass Blocks (Level A).

Access key

An access key is used on our cookie preference tool. This is fixed by the plug in that we use. An accesskey may conflict with user shortcut keys. This fails 2.4.1 Bypass Blocks (Level A)

This statement was prepared on 27 July 2020. It was last updated on 4 August 2020.