This accessibility statement applies to the Salford City Council’s Citizen Portal website.
We want as many people as possible to be able to use this website. For example, that means you should be able to:
We’ve also made the portal text as simple as possible to understand.
AbilityNet has advice on making your device easier to use if you have a disability.
We know some parts of this website are not fully accessible:
If you find any problems not listed on this page or think we’re not meeting accessibility requirements, please email webmaster@salford.gov.uk
It would be helpful if your email contained the following:
If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille email webmaster@salford.gov.uk
We’ll consider your request and get back to you in 10 working days.
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).
If you’d like to phone us please see our how to phone us page.
To visit us in person see our how to find us page for our office locations.
Capita One (as a part of Capita Business Services Limited) and Salford City Council are 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.2 AA standard, due to the non-compliances listed below.
The content listed below is non-accessible for the following reasons.
Appearance
Some colour contrasts do not provide the ratio required meaning that some people with visual impairments may not be able to see the all the text clearly, or the edge of some form fields with sufficient clarity. This fails WCAG 2.2 success criterion 1.4.3 (AA) Contrast (Minimum) and 1.4.11 (AA) Non-text Contrast.
A few elements do not allow the user to easily change the colours, fonts, text appearance, or spacing via their browser. This fails WCAG 2.2 success criterion 1.4.4 (AA) Resize Text and 1.4.12 (AA) Text Spacing.
We plan to ensure all colour contrasts are compliant by April 2025, and when we add new functionality will ensure it meets accessibility standards.
Navigating and accessing information
Some status messages are not reported to screen readers. This fails WCAG 2.2 success criterion 4.1.3 (AA) Status Messages.
A few pieces of placeholder text, such as the example eligibility code placeholder, are not fully visible without mouseover when the text is resized in the browser to 200%. This fails WCAG 2.2 success criterion 2.1.1 (A) Keyboard, 1.4.4 (AA) Resize Text.
Some pages have a flow that is yet to be optimised for current user needs or have inconsistently rendered controls or control placement. This fails WCAG 2.2 success criterion 2.4.3 (A) Focus Order, 3.2.3 (AA) Consistent Navigation, 3.2.4 (AA) Consistent Identification, 1.3.1 (A) Info and Relationships, 1.3.2 (A) Meaningful Sequence.
We plan to improve the flow and improve the experience for assistive technology users to be compliant by December 2024, and if new pages are added will ensure the flow is logical and optimised for user needs, with all controls correctly programmed.
Consistency
There are some interactive elements that are displayed slightly differently in different areas of the website, such as some text input controls which are positioned either below the corresponding label, or adjacent to the corresponding label. This fails WCAG 2.2 success criterion, 3.2.4 (AA) Consistent Identification.
We plan to improve the consistency to be compliant by December 2024.
Errors
There are a couple of ways in which errors are detected and shown to the user, not all of which have suggestions for correction. This fails WCAG 2.2 success criterion 3.3.1 (A) Error Identification, 3.3.3 (AA) Error Suggestion.
We plan to improve the error handling to be compliant by April 2025.
Responsive Design and Mobile
There are some places where horizontal scrolling is required or content is misaligned on some smaller browser windows, mobile screens and orientations. This fails WCAG 2.2 success criterion 1.4.10 (AA) Reflow.
We plan to make the mobile experience compliant by December 2024.
We have not identified anything that qualifies as disproportionate burden as of yet.
The accessibility regulations (legislation.gov.uk) don’t require us to fix PDFs or other documents published before 23 September 2018 if they’re not essential to providing our services.
Live video streams do not have captions. This fails WCAG 2.1 success criterion 1.2.4 (captions - live).
We do not plan to add captions to live video streams because live video is exempt from meeting the accessibility regulations.
Online maps, for example our interactive maps.
We plan to improve the accessibility of this website with ongoing releases throughout the year. We are committing to improve the accessibility of this website in various ways including rectifying issues with colour contrast and status messaging, fixing robustness issues, and addressing inconsistencies by December 2024.
This statement was prepared on 27 August 2020. It was last reviewed on 15 May 2024.
This website was last tested on 27 August 2020. The test was carried out internally by Capita One.
We tested all core pages within the website as these contain all control types and elements used throughout; subsequently only pages which have been updated will be tested for accessibility.