Accessibility statement for staywell.rochdale.gov.uk

Website Accessibility

This accessibility statement applies to www.staywell.rochdale.gov.uk
This website is run by Rochdale Borough Council. We want as many people as possible to be able to use this website. For example, this means you should be able to:

• Understand the page name as our web pages have page titles that clearly describe their topic or purpose.
• Use the website easier as we have a logical navigation order.
• Use the content page structure as it's presented and maintained in a meaningful sequence.

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:

• Some users may not be able to use text alternatives, to change text into other forms, such as large print, braille, speech, symbols or simpler language.
• Some users may not be able to access content in different ways (for example, simpler layout) without losing information or structure.
• Some users may not be able to navigate every page using a keyboard.
• Some users may not be able to navigate the content of the webpage quickly and easily.
• Some users may not be able to determine the purpose of each link.
• Some users may not be able to operate functionality through various inputs beyond keyboard.
• Some users may face difficulty when using a screen reader or keyboard.
• Some users may face difficulty when navigating our forms.
• Some users may experience loss of content or functionality when resizing text.
• Some users may not be able to use media alternative for text.
• Some users may experience loss of information or functionality when navigating the webpage.
• Some users may not be able to distinguish content from its background.
• Some users may find it hard to distinguish what each element of the webpage is about.
• Some users may not find the content readable and understandable.
• Some users may not be able to turn off changes of context.
• Some users may not be provided with content-sensitive help.

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:

• Email: adult.care@rochdale.gov.uk
• Phone 0300 303 8886 (Monday - Friday 8.30am - 4.45pm)
• Write to: Adult Care, Floor 3, Number One Riverside, Smith Street, Rochdale OL16 1XU

When contacting us please tell us:

1. The web address (URL) of the content.
2. Your name and email address.
3. The format you need, for example, audio CD, braille or large print.

We'll consider your request and respond to you within 7 working days.
If you cannot view the map on our ‘contact us' page, call or email us Portal Home (rochdale.gov.uk) for directions.

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, please

• Email: adult.care@rochdale.gov.uk
• Phone 0300 030 8886 (Monday - Friday 8.30am - 4.45pm)
• Write to: Adult Care, Floor 3 Number One Riverside, Smith Street, Rochdale, OL16 1XU

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 deaf, hearing impaired or have a speech impediment.
If you contact us before your visit we can arrange a British Sign Language (BSL) interpreter.

Call or email us for more information on this service.

Technical information about this website's accessibility

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

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

We are currently undertaking an internal review to update all the pages and information held on our website and aim for this project to be complete in 2022. As part of this project, we expect to resolve issues detailed below and reassess in 2022.
The content listed below is non-accessible for the following reasons.

Non-compliance with the accessibility regulations

Success criterion 1.1.1 (Text Alternatives)

• Missing alternative text on graphics and symbols. This fails WCAG 2.1 success criterion 1.1.1 (Non-text Content).
• There are two email addresses with the same link text that link to different addresses. This fails WCAG 2.1 success criterion 1.1.1 (Non-text Content).

Success criterion 1.3.1 (Adaptable)

• Some content (including content that is motion automated) may be difficult to operate for screen reader and keyboard users. Not all buttons and links have focus visible styles. Some links and form content automatically initiates a change of context which isn't communicated to screen reader users. This fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships).
• Information and structure is not always conveyed with native, appropriate or semantic HTML elements. This fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships).
• Information that is portrayed by variations in presentation of text are not always conveyed using text. This fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships).
• Depreciated HTML tags are used to make text bold. This fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships).
• The heading structure is incorrect on a number of pages. This fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships).

Success criterion 1.3.3 (Adaptable)

• Information that is portrayed by variations in presentation of text are not always conveyed using text. This fails WCAG 2.1 success criterion 1.3.3 (Sensory Characteristics).

Success criterion 1.4.4 (Distinguishable)

• Depreciated HTML tags are used to make text bold. This fails WCAG 2.1 success criterion 1.4.4 (Resize Text).

Success criterion 1.4.5 (Distinguishable)

• Depreciated HTML tags are used to make text bold. This fails WCAG 2.1 success criterion 1.4.5 (Images of Text).

Success criterion 1.4.9 (Distinguishable)

• Depreciated HTML tags are used to make text bold. This fails WCAG 2.1 success criterion 1.4.9 Images of Text (No Exception).

Success criterion 1.4.10 (Distinguishable)

• Content doesn't reflow or response well on smaller screens or with zoomed displays. This fails WCAG 2.1 success criterion 1.4.10 (Reflow).

Success criterion 1.4.11 (Distinguishable)

• Some focus visible styles (e.g. on green buttons) do not provide enough contrast from default states or background colours and may be difficult to locate. This fails WCAG 2.1 success criterion 1.4.11 (Non-Text Contrast).

Success criterion 2.1.1 (Keyboard Accessible)

• Some parts of our forms (tick boxes, list boxes and combination boxes) are difficult to operate with a keyboard when using a screen reader. This fails WCAG 2.1 success criterion 2.1.1 (Keyboard).
• When using the enter key to operate form elements, e.g. list boxes, required field validation messages will display before you submit your data. This fails WCAG 2.1 success criterion 2.1.1 (Keyboard).
• Some content (including content that is motion automated) may be difficult to operate for screen reader and keyboard users. Not all buttons and links have focus visible styles. Some links and form content automatically initiates a change of context which isn't communicated to screen reader users. This fails WCAG 2.1 success criterion 2.1.1 (Keyboard).
• The ‘onclick' event handler isn't device independent. This fails WCAG 2.1 success criterion 2.1.1 (Keyboard).

Success criterion 2.1.2 (Keyboard Accessible)

• Some parts of our forms (tick boxes, list boxes and combination boxes) are difficult to operate with a keyboard when using a screen reader. This fails WCAG 2.1 success criterion 2.1.2 (No Keyboard Trap).
• Some content (including content that is motion automated) may be difficult to operate for screen reader and keyboard users. Not all buttons and links have focus visible styles. Some links and form content automatically initiates a change of context which isn't communicated to screen reader users. This fails WCAG 2.1 success criterion 2.1.2 (No Keyboard Trap).

Success criterion 2.1.3 (Keyboard Accessible)

• Some parts of our forms (tick boxes, list boxes and combination boxes) are difficult to operate with a keyboard when using a screen reader. This fails WCAG 2.1 success criterion 2.1.3 (No Exception).

Success criterion 2.3.3 (Seizures and Physical Reactions)

• Some parts of our forms use motion animation which is triggered by interaction. The motion animation cannot be disabled. This fails WCAG 2.1 success criterion 2.3.3 (Animation from Interactions).

Success criterion 2.4.1 (Navigable)

• Repeated blocks on content including navigation links, heading graphics and footer links may prevent a user reaching the main content of a web page quickly and easily. This fails WCAG 2.1 success criterion 2.4.1 (Bypass Blocks).

Success criteria 2.4.4 (Navigable)

• There are two email addresses with the same link text that link to different addresses. This fails WCAG 2.1 success criteria 2.4.4 Link Purpose (In Context).

Success criterion 2.4.6 (Navigable)

• Not all web page elements include a heading or label to describe the topic or purpose. This fails WCAG 2.1 success criterion 2.4.6 (Headings and Labels).
• The purpose of each link cannot always be determined from the link text alone. This fails WCAG 2.1 success criterion 2.4.6 (Headings and Labels).
• There are empty heading tags on some pages. This fails WCAG 2.1 success criterion 2.4.6 (Headings and Labels).

Success criterion 2.4.7 (Navigable)

• Some content (including content that is motion automated) may be difficult to operate for screen reader and keyboard users. Not all buttons and links have focus visible styles. Some links and form content automatically initiates a change of context which isn't communicated to screen reader users. This fails WCAG 2.1 success criterion 2.4.7 (Focus Visible).

Success criterion 2.4.9 (Navigable)

• The purpose of each link cannot always be determined from the link text alone. This fails WCAG 2.1 success criterion 2.4.9 Link Purpose (Link Only).
• There are two email addresses with the same link text that link to different addresses. This fails WCAG 2.1 success criterion 2.4.9 Link Purpose (Link Only).

Success criterion 2.4.10 (Navigable)

• Not all web page elements include a heading or label to describe the topic or purpose. This fails WCAG 2.1 success criterion 2.4.10 (Section Headings).
• The heading structure is incorrect on a number of pages. This fails WCAG 2.1 success criterion 2.4.10 (Section Headings).

Success criterion 2.5.3 (Input Modalities)

• The label elements on forms do not always identify the control. This fails WCAG 2.1 success criterion 2.5.3 (Label in Name).
• Missing alternative text on graphics and symbols. This fails WCAG 2.1 success criterion 2.5.3 (Label in Name).

Success criterion 2.5.5 (Input Modalities)

• Some of our links or ‘buttons' are small targets and can be difficult to click or touch. This fails WCAG 2.1 success criterion 2.5.5 (Target Size).

Success criterion 3.1.4 (Readable)

• Some words are presented using abbreviations only. This fails WCAG 2.1 success criterion 3.1.4 (Abbreviations).

Success criterion 3.1.5 (Readable)

• Some technical words relating to Adult Social Care are used which may require a more advanced reading ability. This fails WCAG 2.1 success criterion 3.1.5 (Reading Level).

Success criterion 3.2.1 (Predictable)

• Some content (including content that is motion automated) may be difficult to operate for screen reader and keyboard users. Not all buttons and links have focus visible styles. Some links and form content automatically initiates a change of context which isn't communicated to screen reader users. This fails WCAG 2.1 success criterion 3.2.1 (On Focus).

Success criteria 3.2.5 (Predictable)

• Navigation through the website sometimes automatically launches new windows. This fails WCAG 2.1 success criterion 3.2.5 (Change on Request).

Success criterion 3.3.1 (Input Assistance)

• Form validation and error messages are not read out by some screen readers. This fails WCAG 2.1 success criterion 3.3.1 (Error Identification).

Success criterion 3.3.5 (Input Assistance)

• Where a form field requires a specific format or text no further instructions or explanations are provided. This fails WCAG 2.1 success criterion 3.3.5 (Help).
• The link to further information when a user requires further information (e.g. Help link) does not provide specific or relevant information to that webpage or item. This fails WCAG 2.1 success criterion 3.3.5 (Help).

Success criterion 4.1.1 (Compatible)

• Depreciated HTML tags are used to make text bold. This fails WCAG 2.1 success criterion 4.1.1 (Parsing).

Success criterion 4.1.2 (Compatible)

• Depreciated HTML tags are used to make text bold. This fails WCAG 2.1 success criterion 4.1.2 (Name, Role, Value).

Success criterion 4.1.2 (Compatible)

• Some parts of our forms (such as checkboxes, list boxes and combination boxes) are difficult or impossible to use with some screen readers and voice command software. This fails WCAG 2.1 success criterion 4.1.2 (Name, Role, Value).

Disproportionate burden

We've assessed the cost of fixing the following issues. We believe that doing so now would be a disproportionate burden within the meaning of the accessibility regulations.

• There are no issues that are currently being listed as being assessed as a disproportionate burden within the meaning of the accessibility regulations. 

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

The following types of content do not need to be fixed on the website because they are exempt from the accessibility regulations.
PDFs and other documents - some of our PDFs and Word documents are essential to providing our services. For example, we have PDFs with information from external agencies. We plan to either fix these or link to the pdf on the host website.
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.

What we're doing to improve accessibility

We aim to provide all information as web pages where possible. Sometimes we provide information in other formats such as PDF (Portable Document Format) and Word documents. 

Preparation of this accessibility statement

This statement was prepared on 15 September 2020. It was last reviewed on 18 August 2021.
This website was last tested in August 2021. The test was carried out by Sitemorse.
Future testing and audits will include user testing – asking users with accessibility needs to test the website, and learning from their feedback. We intend to test the accessibility features of the website through user sessions, with customers.