On this page you'll find more information about:
Web accessibility is defined as the degree to which a website is useable by as many people as possible. Making a website accessible means that it is easier for anyone to find and use, increasing the effectiveness of the site and potential audience.1
User Vision research found that 73% of the people in the UK living with disabilities are unable to complete basic transactions on more than a quarter of the websites they visit.
We build our digital touchpoints so anyone can use them. This includes people with varied (and sometimes multiple) accessibility needs. Such as customers with:
- A visual impairment (for example low vision, blindness and colour blindness), using screen readers or magnifiers.
- A hearing impairment using captioning and transcriptions on videos.
- A cognitive impairment (for example autism and dyslexia), where colour display settings, plain language, and logical and organised layouts are key.
- A motor impairment using voice recognition software for hands-free interaction.
- It’s important to remember that some users will have multiple conditions and will use several pieces of accessibility software to access the site.
The Digital Operations Team use Level Access for monitoring the accessibility of our website. As at 8 March 2024, our score was 95%.
If you have any questions related to accessibility, please contact the Digital Optimisation Team.
Web content accessibility guidelines
The web content accessibility guidelines (WCAG) were created to provide a single web accessibility standard to be used internationally. You can find out more about the four underlying principles by expanding the accordions below.
There is more information about understanding the guidelines on the WCAG website.
Information and user interface (UI) components must be presented to users in ways they can perceive. This means that users must be able to understand the information being depicted.
What this means for us
Text alternatives: Provide text alternatives for any non-text content so that it can be changed into other formats people need, such as large print, braille, speech, symbols, or simpler language.
Time-based media: Examples of time-based media include items that move, make noise, or change without user input. To make the site accessible, we need to provide alternatives.
Adaptable: Create content that can be presented in different ways (for example a simpler layout or large print) or determined by a screen reader without losing any information or structure.
Distinguishable: Make it easier for users to see and hear content. This includes ensuring colour contrasts are accessible and audio is clear.
User interface components and navigation must be operable. The interface cannot require interaction that a user cannot perform.
What this means for us
Keyboard Accessible: Make all functionality available from a keyboard (for example no pointer devices such as mice are required to use the site).
Enough time: Provide users enough time to read and use content.
Seizures and physical reactions: Do not design content in a way that is known to cause seizures or physical reactions.
Navigable: Provide ways to help users navigate, find content, and determine where they are. This includes ensuring navigation is presented in an order that makes sense when read by screen readers.
Input modalities: Make it easier for users to operate functionality through various inputs beyond keyboard (for example using pointer devices such as mice and touch screens).
Information and the operation of a user interface must be understandable. Users must be able to understand the information as well as the operation of the user interface.
What this means for us
Readable: Make text content readable and understandable for all users, including those using assistive technology.
Predictable: Make web pages appear and operate in predictable ways – this helps those using accessibility technology to use and navigate around the site.
Input assistance: Help users avoid and correct mistakes.
Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies. As technologies and user agents evolve, the content should remain accessible.
What this means for us
Compatible: Maximise compatibility with current and future user agents, including assistive technologies.
Accessible documents
All of our resources and PDFs need to be maintained to ensure brand consistency and accessibility.
When creating assets with APS:
- Check the document for accessibility, adding relevant metadata to MOS
- Check that the document is consistent with our brand and tone of voice guidelines
- Check the document for time sensitive content
- The layout is clear and simple - people prefer to read shorter documents
APS add and check the accessibility information of PDFs as part of the ‘provide final asset’ action for new and amended PDFs. You must complete the MOS accessibility tab for all APS produced PDFs that will be available online via our website before you send the asset for final approval.
Documents are checked that they are meeting accessibility standards as part of the consumer duty checklist.
Uploading to AEM
When adding a PDF (asset) to the AEM DAM, you must provide a further set of metadata in the page properties within AEM.
All of our assets should follow our naming conventions as provided in the AEM DAM Training guide.
For more information, please see the DAM Upload Workflow training guide.
- Our accessibility policy
- Magnifying glass - This can be added to your browser
- Microsoft Word accessibility checker - This tool is a good resource documents. This is also available in PowerPoint or Excel.
- NVDA screen reader - This can be downloaded free of charge by anyone
- VoiceOver - This is a resource built into iOS devices
- Wave - Wave can spot check a webpage for accessibility. Please note that this is an automated test (for example, the quality of alternative text is not assessed) and manual checks should still be done.
1Accessibility for everyone, Laura Kalbag. 2017.
