- Home (UK)
Accessibility on serco.com
We want everyone who visits the Serco.com website to feel welcome and find the experience rewarding.
What are we doing?
To help us make the Serco.com website a positive place for everyone, we are using the Web Content Accessibility Guidelines (WCAG) 2.1. These guidelines explain how to make web content more accessible for people with disabilities, and user friendly for everyone.
The guidelines have three levels of accessibility (A, AA and AAA). We’ve chosen Level AA as the target for the Serco.com website.
How are we doing?
We're working hard to achieve our goal of Level AA accessibility, and realise there are some areas that still need improving.
We completed a technical compliance review in May 2020 and have since made some significant technical compliance changes on our website which will greatly improve accessibility, in addition we have now added the Reciteme assistive toolbar on all our pages.
We run a weekly scan of the website against the WCAG 2.1 standards using Powermapper Site Sort and continue to work on any identified issues.
This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the following the non-compliances listed below which are being fixed.
- Ensure that text and background colors have enough contrast. WCAG 2.1 AA 1.4.3 Section 508 (2017) AA 1.4.3
- Form field labels should be unique on a page, or be close to text providing context. WCAG 2.1 AA 2.4.6 Section 508 (2017) AA 2.4.6
- Headings should not be empty. WCAG 2.1 AA G130 Section 508 (2017) AA G130
- Radio buttons with very generic labels need to be enclosed in a fieldset with a legend explaining the label. WCAG 2.1 AA 2.4.6 Section 508 (2017) AA 2.4.6
- The CSS outline or border style on this element makes it difficult or impossible to see the dotted link focus outline. WCAG 2.1 AA F78 Section 508 (2017) AA F78
In addition we have one exemption where a name is being identified as a language, this only impacts 2 pages.
- Phrases in a different language should be in a span or div with a lang attribute. WCAG 2.1 AA 3.1.2 Section 508 (2017) AA 3.1.2
What we’re doing to improve accessibility
We are tackling some of the key WCAG 2.1 A standard items that have been identified specifically around PDFs so they are tagged to be accessible to screen readers making sure document titles are included in the properties, changing general text where no surrounding text explains the link purpose.
This work is being carried out throughout 2021.
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 firstname.lastname@example.org.
This accessibility statement was updated on 16th January 2021. The site was last tested on 16th January 2021 in-house using Powermapper Site Sort.