Accessibility statement for Knowsley Council

This accessibility statement applies to the Knowsley Council website and microsites including:

  • https://www.knowsley.gov.uk/
  • All Mendix pages e.g. https://knowsleytransaction.mendixcloud.com/index.html
  • https://onlineregistrar.knowsley.gov.uk/eregistrar.knowsley
  • https://planapp.knowsley.gov.uk/online-applications/
  • https://knowsleyclaims.teamnetsol.com/
  • https://parentportal.knowsley.gov.uk/web/portal/pages/home
  • https://secured.knowsley.gov.uk/
  • https://www.knowsley.gov.uk/onlinechat.html
  • https://ip.e-paycapita.com/AIP/itemSelectionPage.do?link=showItemSelectionPage&siteId=63&languageCode=EN&source=AIP
  • https://secured.knowsley.gov.uk/myneighbourhood
  • https://my.knowsley.gov.uk/CustomerPortal/(S(ffzicjbfqnyngk5dkeejk4p4))/Content/BusinessPortal/BusinessPortal.aspx
  • https://my.knowsley.gov.uk/CustomerPortal/(S(33dmck0i3so02pe11p5hv5tb))/Content/Home/Login.aspx
  • http://archives.knowsley.gov.uk/
  • https://fostering.knowsley.gov.uk/
  • http://www.prescotthi.org.uk/
  • https://www.prescotmuseum.org.uk/
  • https://www.knowsleyinfo.co.uk/
  • http://knowsleynews.co.uk/
  • https://www.discoverknowsley.co.uk/
  • http://knowsleycareleavers.co.uk
  • https://www.knowsleyflowershow.com
  • http://www.knowsleyhwb.org.uk
  • https://knowsleyknowledge.org.uk
  • https://www.knowsleyscp.org.uk
  • https://www.shakespearenorthplayhouse.co.uk
  • https://www.investknowsley.co.uk
  • https://www.knowsleybettertogether.co.uk
  • https://www.knowsleybusinessawards.com
  • https://www.knowsleysocialworkacademy.co.uk

These websites are run by Knowsley Council. We want as many people as possible to be able to use our websites. 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)

AbilityNet has advice on making your device easier to use if you have a disability.

How accessible this website is

Overall our website is quite accessible and our customers should be able to use the site without too much difficulty. We are aware of some issues that may affect the accessibility of some parts of the website:  

  • forms do not provide descriptive error messaging
  • most older PDF documents are not fully accessible to screen reader software
  • it is not always clear which page element has focus
  • some pages do not reflow when you change the size of the browser window or magnification level
  • some buttons and form fields are not announced in a useful way by the screen reader

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:

We’ll consider your request and get back to you in 3 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.

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

Contacting us by phone or visiting us in person

We provide a text relay service for people who are D/deaf, hearing impaired or have a speech impediment.
Our offices have audio induction loops, or if you contact us before your visit we can arrange a British Sign Language (BSL) interpreter.
Find out how to contact us

Technical information about this website’s accessibility

Knowsley 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-compliance with the accessibility regulations

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

Page design

Colour contrast is insufficient in places making it hard from some people to read content or perceive graphics on our website. This fails WCAG success criteria 1.4.3 (Contrast (Minimum)) and 1.4.11 (Non-text contrast).

Text spacing cannot be increased in some places on the site, which may be an issue for users who need to manipulate how the text is displayed. This fails WCAG success criterion 1.4.12 (Text Spacing)

Some older images on our microsites do not have alternative text which means screen readers cannot communicate what the image is to users. This fails WCAG success criterion 1.1.1 (Non-text Content).

Page structure

Heading elements are not always used correctly, which can make it difficult for some users to discern the structure of the webpage. This fails WCAG success criterion 1.3.1 (Info and relationships).

Our website has no ARIA page landmarks, which can make it difficult for some users to discern the structure of the webpage. This fails WCAG success criterion 1.3.1 (Info and relationships).

Some of the portal pages on our website do not reflow when at high browser magnification, which means people with visual impairments may be unable to access some content. This fails WCAG success criterion 1.4.10 (Reflow).

Our web pages are currently missing a lang attribute so some screen reader users may have issues using our site. This fails WCAG success criterion 3.1.1 (Language of page)

Navigation, links and buttons

There is currently no ability to bypass repeated blocks of navigation with a ‘skip to content’ link on most of our webpages. This fails WCAG success criterion 2.4.1 (Bypass blocks). On mobile, the focus order is not always logical through the main navigation, which can make it confusing for blind users navigating via screen reader and non-mouse users. This fails WCAG 2.1 success criterion 2.4.3 (Focus Order).

In some places on our website the keyboard focus is not visible. This makes it hard for keyboard users to identify which part of the site is active and fails WCAG 2.1 success criterion 2.4.7 (focus visible).

The cookie banner is currently not keyboard operable so will be inaccessible to non-mouse users. This fails WCAG success criterion 2.1.1 (Keyboard).

The purpose of links is not always clear from the text alone, which will affect screen reader users when they list links. This fails WCAG success criterion 2.4.4 (Link Purpose (In Context)).

Some of our buttons, for example our social media icons, are missing programmatic labels so will be announced in an unhelpful way by a screen reader. This fails WCAG success criterion 4.1.2 (Name, Role, Value).

Interactive forms

Some forms field are missing programmatic labels, or the labels are not associated with the interactive page element, so the labels are not announced in a useful way by a screen reader. This fails WCAG success criteria 4.1.2 (Name, Role, Value), 1.3.1 (Info and relationships) and 3.3.2 (Labels or Instructions)

The error messaging on our forms is generic and does not describe how to correct the error. This fails WCAG success criterion 3.3.3 (Error suggestion)

The error messaging on our forms is not announced by the screen reader so blind users will be unaware an error has occurred. This fails WCAG success criterion 4.1.3 (Status Message).

PDFs

Some of our PDFs do not comply with WCAG 2.1 to Level A and AA which may make them difficult for some of our users to access. For example:

  • They currently do use the correct heading structure, which makes it difficult for screen reader users to navigate the document. This fails WCAG success criterion 1.3.1 (Info & Relationships)
  • There are no bookmarks in the PDFs, which makes it difficult for screen reader users to discern the structure of the document. This fails WCAG success criterion 2.4.5 (Multiple Ways)
  • Some PDFs are missing document titles, which can make it difficult for screen reader users to quickly discern the contents of the document. This fails WCAG success criterion 2.4.2 (Headings and labels)

What we are doing about this:

We are currently working with third party suppliers to assess the feasibility of fixing the issues above and the potential timescales required in order to make the website more accessible.

Where possible we plan to fix the accessibility issues with our most frequently used PDF documents. For any new PDFs, we will ensure they are created in an accessible way. 

We are keeping accessibility guidelines in mind when making any changes to web content such as providing images with alternative text and using correct headings.

Disproportionate burden

We are not yet planning to address the issues below, as to do so currently represents a ‘disproportionate burden’, as defined by the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018. This is because, in some cases, we are reliant on third party suppliers to make these changes, and in others the cost of doing so would be prohibitive. 

Currently representing a disproportionate burden are the following issues:
Some of our interactive forms have accessibility issues. These include:

  • Some forms field are missing programmatic labels. This fails WCAG success criteria 4.1.2 (Name, Role, Value) and 1.3.1 (Info and relationships)
  • Help icons are not keyboard operable. This fails WCAG success criterion 2.1.1 (Keyboard)
  • Help icons are not hoverable. This fails WCAG success criterion 1.4.13 (Content on Hover of Focus)
  • The payment session times out without giving the user warning or the opportunity to extend it. This fails WCAG success criterion 2.2.1 (Timing Adjustable)
  • Error messaging is not descriptive. This fails WCAG success criterion 3.3.3 (Error suggestion)
  • Error messaging is not announced by the screen reader. This fails WCAG success criterion 4.1.3 (Status message)

Our forms are built and hosted through third party software and ‘skinned’ to look like our website.

We’ve assessed the cost of fixing the above issues with the interactive tools and believe that doing so now would be a disproportionate burden within the meaning of the accessibility regulations. This is because we do not have direct access to edit these forms and are reliant on the third party organisation to make the fixes.

We are due to be developing and launching a new website by 2023. Any new site would be built with WCAG 2.1AA guidelines in mind.

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

PDFs and other documents

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.

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

Preparation of this accessibility statement

This statement was prepared on 6 October 2020 It was last reviewed on 7 October 2020.

This website was last tested on 25 September 2020. This website was tested for compliance with the Web Content Accessibility Guidelines V2.1 level A and level AA, and the test was carried out by Web Usability Partnership Ltd.

We used the Website Accessibility Conformance Evaluation Methodology (WCAG-EM) approach to deciding on a sample of pages to test.