Website Accessibility

Decorative images have been given descriptive alternative attributes, resulting in unnecessary information being announced to users of screen readers. This fails WCAG 2.1 success criterion 1.1.1 - Non-Text Content. 

We plan to resolve this by August 2024.

Adjacent image links and text which links to the same location are not combined on the ‘Jobs’ webpage. This may result in the text being announced twice by screen readers. This fails WCAG 2.1 success criterion 1.1.1 - Non-Text Content.

We plan to resolve this by August 2024.

Buttons do not have an accessible name. Across many pages, the website search and mobile hamburger menu button do not contain an accessible name. This can affect users of screen readers. This fails WCAG 2.1 success criterion 1.1.1 - Non-text Content. 

We plan to resolve this by August 2024.

Form input fields lack an associated text label or descriptive title. Across many pages several of the form inputs provide labels which are blank. This can affect users of screen readers. This fails WCAG 2.1 success criterion 1.1.1 - Non-text Content. 

We plan to resolve this by August 2024.

Embedded multimedia is not identified by accessible text. On the ‘Care home details page’ embedded multimedia elements lack accessible text. This affects users of screen readers. This fails WCAG 2.1 success criterion 1.1.1 – Non-text Content.

We plan to resolve this by August 2024.

Pre-recorded video lacks transcript or audio description. Videos do not provide a text description or media alternative. This can affect user’s with visual impairments. This fails WCAG 2.1 success criterion 1.2.3 - Audio Description or Media Alternative (Pre-Recorded).

We plan to resolve this by August 2024.

Unable to interact with all user interface components using a keyboard only. Across both ‘Care home details page’ and 'Respite care home’ select components cannot focused using the keyboard. This can affect users with motor impairments. This fails WCAG 2.1 success criterion 2.1.1 - Keyboard. 

We plan to resolve this by August 2024.

Duplicate ‘Skip to Main Content’ buttons are present. The first skip to main button is non-functional. However, the second ‘Skip to Main Content’ button is functional. This can affect users who rely on screen readers. This fails WCAG 2.1 success criterion 2.4.1 - Bypass Blocks

We plan to resolve this by August 2024.

Page regions are not identified with ARIA landmarks. Certain content is not contained within ARIA landmarks. Unique to the ‘Respite care home’ webpage a contentinfo landmark is also incorrectly nested. This can affect users who rely on assistive technologies. This fails WCAG 2.1 success criterion 1.3.1 - Info and Relationships.

We plan to resolve this by August 2024.

The tab order of many pages is not logical. The user must tab through the entire header menu, including all menu dropdowns. Additionally, the focus order is not logical within the large menu dropdowns. The user is also focused on the expanded search field after the 'Make enquiry' button. All pages also contain a 'Leave a message'/'Chat with us' widget that when selected moves the users focus top of the content in the focus order. Hidden content is also focused and select elements are focused twice on the 'Care Home Listing Page', 'Care Home Detail Page', 'Respite care home', 'Help and advice' and 'Contact Us' pages. This can affect users who navigate using a keyboard. This fails WCAG 2.1 success criterion 2.4.3 - Focus Order.

We plan to resolve this by August 2024.

A visible tab focus indicator is absent for select components on the ‘Care Home Detail Page’. The carousel and the play icon on the carousel video do not have a visible focus indicator. This can affect users who navigate using a keyboard. This fails WCAG 2.1 success criterion 2.4.7 - Focus Visible

We plan to resolve this by August 2024.

Copy has insufficient contrast against its background. Across all page’s text does not have sufficient contrast which could affect users with low vision, users who are colour blind or other visual impairments being able to navigate the site. This fails WCAG 2.1 success criterion 1.4.3 - Contrast (Minimum).

We plan to resolve this by August 2024.

There is insufficient contrast between the visual boundaries of user interface components and the background. This means some users may find it difficult to view and recognise form fields easily. This fails WCAG 2.1 success criterion 1.4.11 - Non-Text Contrast.

We plan to resolve this by August 2024.

There is insufficient contrast for user interface components that are in a focus or selected state. This means some users may find it difficult to view and recognise form fields easily. This fails WCAG 2.1 success criterion - 1.4.11 Non-Text Contrast.

We plan to resolve this by August 2024.

There is a lack of contrast within graphical objects. The map icon and graphical information images do not have sufficient colour contrast. This means visually impaired users may not be able to recognise the icon. This fails WCAG 2.1 success criterion - 1.4.11 Non-Text Contrast.

We plan to resolve this by August 2024.

The navigation is not consistent on the ‘Jobs’ webpage. The webpage contains a different navigational header menu which is inconsistent when compared across the website. This means visually impaired users may become disorientated. This fails WCAG 2.1 success criterion 3.2.3 - Consistent Navigation.

We plan to resolve this by August 2024.

Rendering issues are present when zooming text only to 200% using browser zoom controls. This may affect users with visual impairments. This fails WCAG 2.1 success criterion 1.4.4 - Resize Text.

We plan to resolve this by August 2024.

Content which appears on hover or focus cannot be dismissed. This can be observed within the header menu and on several tooltips. The user must tab away from the content for the additional information to disappear. This fails WCAG 2.1 success criterion 1.4.13 - Content on Hover or Focus.

We plan to resolve this by August 2024.

Content which appears on hover or focus is not hoverable. This can be observed on the 'Care Home Listing Page' and 'Care Home Detail Page' tooltips. This may affect users who rely on magnification. This fails WCAG 2.1 success criterion 1.4.13 - Content on Hover or Focus.

We plan to resolve this by August 2024.

An alternative audio track containing an audio description is not present for a pre-recorded video on both the ‘Care Home Listing Page’ and ‘Respite Care Home’ webpage. This fails WCAG 2.1 success criterion 1.2.5 - Audio Description (Pre-Recorded).

We plan to resolve this by August 2024.

Multiple instances of identical link text are present. Across the ‘Care Home Listing Page’, ‘Care Home Detail Page’, and the ‘New Listing’ webpage identical links are present which direct the user to different locations. This may affect users who rely on assistive technologies from easily identifying each links unique purpose. This fails WAG 2.1 success criterion 2.4.4 - Link Purpose (In Context).

We plan to resolve this by August 2024.

A correctly formed heading structure is not present to facilitate navigation across the site, with empty and skipped heading levels present. This fails WCAG 2.1 success criterion 2.4.1 - Bypass Blocks.

We plan to resolve this by August 2024.

On many pages, the headings do not describe the topic or purpose. Select pages have duplicate headings. This may affect users who rely on a correct heading structure to navigate. This fails WCAG 2.1 success criterion 2.4.6 - Headings and Labels.

We plan to resolve this by August 2024.

Text descriptions are not provided for some error fields on forms. This can be seen on the email address and phone fields, if the user inputs an incorrect input, there is no explanation as to why this is incorrect. Furthermore, on form inputs which do display an error, the message is only displayed for 10 seconds. This may affect users with cognitive disabilities. This fails WCAG 2.1 success criterion 3.3.1 - Error Identification.

We plan to resolve this by August 2024.

Required or specific format fields do not provide information in the associated label or title attribute to indicate the required/specific format. On several pages the user is asked to fill out fields ‘Email’ and ‘Phone’ which require a specific format. This information is not provided to the user within the elements label or title attribute. This may affect users with cognitive disabilities. This fails WCAG 2.1 success criterion 3.3.2 - Labels or Instructions.

We plan to resolve this by August 2024.

Error suggestions are not provided for input errors. Known suggestions are not provided for input fields ‘Email’ and ‘Phone’. This may affect users with cognitive disabilities. This fails WCAG 2.1 success criterion 3.3.3 - Error Suggestion.

We plan to resolve this by August 2024.

Frames cannot be bypassed on the ‘Care Home Detail Page’. The video iFrame has an inappropriate title of “Undefined”. This may affect screen reader users. This fails WCAG 2.1 success criterion 2.4.1 -Bypass Blocks.

We plan to resolve this by August 2024.

All pages contain HTML validation errors which may introduce issues for users who navigate using assistive technologies. This fails WCAG 2.1 success criterion 4.1.1 - Parsing.

We plan to resolve this by August 2024.

The autocomplete attribute is not present for form input fields. This means that users who need to fill out forms with repetitive detail will need to do so without the help of autocomplete. This fails WCAG 2.1 success criterion 1.3.5 - Identify Input Purpose. 

We plan to resolve this by August 2024.

Colour only has been used to convey information. This can be seen on the ‘Chat with us’/’Leave a message’ widget, upon submission blank fields are only highlighted red. This may affect users with visual impairments. This fails WCAG 2.1 success criterion 1.4.1 - Use of Colour.

We plan to resolve this by August 2024.

The In-text link ‘privacy statement’ lacks additional styling, meaning that a link is only distinguished by its colour and no additional styling, like underlining. This can be seen on all pages with the ‘Chat with us’/’Leave a message’ widget. This fails WCAG 2.1 success criterion 1.4.1 - Use of Colour.

We plan to resolve this by August 2024.

MacOS Safari is unable to interact with most webpage content. This may affect users who rely on the Safari web browser. This fails WCAG 2.1 success criterion 4.1.2 - Name, Role, Value. 

We plan to resolve this by August 2024.

The focus order on mobile environments is incorrect. Header content is not navigated from left to right; the tab order is illogical. This may affect users who rely on mobile environments. This fails WCAG 2.1 success criterion 2.4.3 - Focus Order.

We plan to resolve this by August 2024.

Multiple ARIA related errors are present. Many pages include the use of incorrect ARIA attributes and incorrectly hidden content using ARIA. This may affect users who navigate using assistive technologies. This fails WCAG 2.1 success criterion 4.1.2 - Name, Role, Value.

We plan to resolve this by August 2024.

Interactive controls are nested. Across both ‘Help and advice’ and ‘Contact us’ webpage, markup has been used incorrectly with interactive controls being nested. This may affect screen reader users. This fails WCAG 2.1 success criterion 4.1.2 - Name, Role, Value.

We plan to resolve this by August 2024.