Sign In
Skip Navigation LinksHome > Site Terms and Conditions > Website Accessibility

​Website Accessibility​​

 1. Using this website

This website is run by Redcar & Cleveland Borough Council. We want as many people as possible to be able to use this website. For example, that means you should be able to:

  • Zoom in up to 200% 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) 
  • View the website using any device eg Mobile phone, Tablet, Desktop computer
  • View any videos that we add to this website, ensuring they are accessible to all with audio or written alternatives available where required
  • View and understand content where we use colour. We will ensure that colours used have a sufficient colour contrast

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

Please note this website may not function correctly if you are using an older browser ie Internet Explorer. It is recommended if you are using Internet Explorer that you instead use Google Chrome or Microsoft Edge.


2. How accessible is this website?

A recent audit of the website undertaken by the Government Digital Service (GDS) outlined a number of accessibility issues with the Redcar & Cleveland Borough Council website (these issues are outlined in section 9). We are currently working with our development partner to address the technical issues that have resulted in some elements of the site not meeting accessibility standards. Further to this, we are continually working through content on the site address accessibility issues raised in relation non-technical elements such as alt-text for images, video, and hyperlinks.


3. What to do if you can't access parts of this website

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

 

4. Reporting accessibility problems with this website

We're always looking to improve the accessibility of this website. If you find any problems that aren't listed on this page or think we're not meeting accessibility requirements, contact the Digital team by emailing the issue to communications@redcar-cleveland.gov.uk


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


6. Technical information about this website's accessibility

Redcar & Cleveland Borough Council is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances listed under section two of this page.

We have identified that some accessibility issues relate the structural design of the website and the limitations of the product used to develop it. To this end, Redcar & Cleveland Borough Council are investing the development of new public facing website. The aim of this website is to create a simpler, more welcoming user experience that has accessibility at its' core. Further to this, we are working with our development partner to ensure that the design and build of the new website meets accessibility standards and remains flexible enough to ensure that all required changes can take place quickly and easily.


7. Content that's not within the scope of the accessibility regulations

PDFs and other documents

Many of our older 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 doesn't meet WCAG 2.1 success criterion 4.1.2 (name, role value). 

The accessibility regulations don't require us to fix PDFs or other documents published before September 2018 if they're not essential to providing our services. For example, we don't plan to fix old issues of the 'This Is' resident's magazine or older PDF documents.

We are working with colleagues to improve the accessibility of PDF documents with a view to ensuring that all documentation published to the Redcar & Cleveland Borough Council website meets accessibility standards.


8. How we test this website

This website is tested every 90 days. The tests are carried out by the Redcar & Cleveland Borough Council Web Team using the Google Lighthouse developer tool. Required changes that are discovered as a result of these tests will be implemented within three months.

 

9. Known Issues

We are aware of some issues on the Redcar & Cleveland Borough Council website that impact the overall accessibility of the site. The issues outlined below have been identified alongside a predicted timeframe for resolution. The information below​ will be updated to reflect the newest information relating to the identification and resolution of accessibility issues.

Issue DescriptionWhere the issue was found

WCAG 2.1.1 Keyboard.

 

Users should be able to use a keyboard to access all content and functionality of a web page. This means the page can be used by people with no vision as well as people who use alternative keyboards or input devices that act as a keyboard.

All web pages:

There is no way to fully expand the 'Rate this page' sidebar via ke​yboard RESOLVED 20 July 2021
All pages with the 'Contact' sidebar:

The "Live chat" function cannot be accessed via keyboard. RESOLVED 30 July 2021​

WCAG 1.4.4. Resize Text.

 

Visual text, including text-based controls can be scaled so that they can be read directly by users with visual impairments without using assistive technology such as a screen magnifier.

 

Text must be able to be resized up to 200 percent without loss of content or function.



All web pages:

At 200% zoom the "Rate this page" sidebar is pushed to the bottom and you can only read the word "page". RESOLVED 20 July 2021
Council Tax Payment page:

At 200% zoom some of the menu items along the left hand side are cut off. Target resolution date: 31/08/21
Council Tax Valuation Bands:

At 2​00% zoom the right hand side content overlaps the main content. Target resolution date: 31/08/21

WCAG 1.4.10 Reflow

 

Reflow or 'responsive web design' helps users with low vision who may need to enlarge text on a webpage and read it in a single column without scrolling in more than one direction. It also helps users who are viewing the page on a mobile device.

 

If a page does not support reflow it can appear smaller and more difficult to use or content may be cut off.

 

Navigation menus often collapse into fewer items or into a single menu button to take up less space. All content and functionality must still be fully available.

All web pages:

At 400% zoom and in mobile view the header is stopping the page from reflowing correctly. Additionally this means you can no longer properly read the full coronavirus banner at the top of the page as white text spills on to a white background. RESOLVED 20 July 2021
All pages with the 'Contact' sidebar:

At 400% zoom the "Contact" title overlaps slightly with main content. RESOLVED 20 July 2021
News page:

At 400% zoom the content in each of the news items overlap. RESOLVED 20 July 2021
Council Tax Payment page:

At 400% zoom the header, footer and form do not reflow properly. The menu items on the left hand side are partially cut off. Target resolution date: 31/08/21

In mobile view the page gets smaller to fit the screen rather than reflowing. Target resolution date: 31/08/21

Council Tax Valuation Bands page:

At 400% zoom and in mobile view the table does not support reflow. Target resolution: 31/08/21

WCAG 1.4.5 Images of Text.

 

Images of text cause problems for users who need to adjust how visual content like font size, spacing or colours are displayed. The image quality can reduce and become blurry when users increase page magnification.

 

Images of text should not be used unless text cannot be formatted to the same effect, for example logos or branding. Text may be used in images where the text is part of an image that contains a lot of other visual content like graphs or diagrams that give important information through more than just text.

Book a Coronavirus Test page:

The buttons for booking tests are images of text and the alternative text does not​ accurately describe what they are. RESOLVED 20 July 2021

Council Tax Valuation Bands page:

The "current Council Tax charges for 2020-2021" table is an image of text. RESOLVED 20 July 2021
Festival of Thrift page:

Details for the festival are within an image of text and the alternative text does not describe the same information. RESOLVED 20 July 2021

WCAG 1.4.3 Contrast (Minimum).

 

Poor colour contrast makes it difficult for someone with sight loss to see the content properly. If there is a big difference between the background and foreground colours it should be much easier to see the difference between them.

 

Pages with the standard header:

In the top coronavirus banner the link in blue against the red background does not meet the minimum requirement. RESOLVED 20 July 2021

The placeholder text in the Search bar. RESOLVED 20 July 2021
Council Tax Payment page:
Target resolution date: 31/08/21

The blue ​and white colour combination used across this page does not meet the requirement.
Covid-19 Local Outbreak Management Plan PDF:

On page 32 the black text on a dark green background in the table does not meet the required contrast ratio.


WCAG 2.4.4 Link Purpose (In Context) and WCAG 4.1.2 Name, Role, Value – Links must have discernible text.

 

All link names should be accessible by a screen reader and be descriptive enough to tell a user where that link will take them. Common issues include:

the inner link text not being visible

duplicate link la​bels

the link not being focusable

You should not modify the style of a link to suppress the change in style when a link is in focus as this removes the ability of sighted keyboard users to know where they are on the page.

All links should receive focus and link text should not be hidden as this will stop a screen reader from relaying the link information.

Pages with the standard header:

The "This is Redcar and Cleveland" link.
Pages with the standard footer:

The social media icons.
RESOLVED 20 July 2021

WCAG 1.3.1 Info and Relationships and WCAG 4.1.2 Name, Role, Value – Form elements must have labels.

 

Form labels help assistive technologies to understand what input is expected in a form field. Adding a label reduces confusion and enlarges the clickable area which helps users with limited motor control.

 

Labels should be used for inputs such as:

  • Text entry fields
  • Radio buttons
  • Checkboxes
  • Select menus

All standard web pages:

The radio buttons in the 'Rate this page' form. RESOLVED 20 July 2021

 

We are committed to continually trying to improve the level of accessiblity of this website. If you have any problems accessing this website please contact webadministrator@redcar-cleveland.gov.uk and we will do our best to help.

Contact

Redcar & Cleveland House,
Kirkleatham Street, Redcar,
Yorkshire TS10 1RT

you could call our Customer Services Team on 01642 774774 between 9am to 5pm Monday to Friday.

contactus@redcar-cleveland.gov.uk

Live Chat Software by Click4Assistance UK

Related Documents

Related Links