Accessibility statement for eCase

This accessibility statement applies to the main eCase service. Note that eCase provides other services, for example when sending documents to people or publishing FOI disclosures - these other services have their own accessibility statements.

Using this service

We want as many people as possible to be able to use this service, and have a firm belief that disabilities should not affect an individual's ability to do their job. For eCase, that means you should be able to:

• change colours, contrast levels and fonts
• zoom in up to 300% without the text spilling off the screen
• get from the start of the service to the end using just a keyboard
• get from the start of the service to the end using speech recognition software
• listen to the service using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)

We have also made the text in the service as simple as possible to understand.

AbilityNet has advice on making your device easier to use if you have a disability.

How accessible this service is

We know some parts of this service are not fully accessible:

• some rich text editors aren't labelled correctly
• users of VoiceOver on iOS may find their focus becoming trapped on the collapsing sections of the Response screen
• user generated content, such as files added to cases, may not follow best accessibility practices. We recommend contacting the original author if you need them in a different format. For example large print, audio recording or braille.

If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact: support@ecase.co.uk.

How we are making the service accessible

To help us make eCase accessible we are taking the following steps:

• accessibility testing is part of our quality assurance process
• we have accessibility evangelists within Fivium whose aim is to raise awareness and empathy within our team
• we have internal guidelines for best practice which all developers must read and understand
• we run accessibility workshops with our software developers to increase awareness of best practice

To make sure eCase works in real-life and not just “in the lab”, we have run multiple one-to-one testing sessions with actual users of eCase who have disabilities or use assistive technologies. Testing with people who understand what tasks eCase is meant to perform and observing them as they use it provides us with deep insights into real-world scenarios.

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

Technical information about this service’s accessibility

We are committed to making this service accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

This service is partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, due to the non-compliances listed below

Non-accessible content

The content listed below is non-accessible for the following reasons.

Rich text editors, where you can format text as bold or insert tables, are not properly associated with their labels and do not effectively show focus to users. This means users of accessibility tools may not see which form input is currently selected or understand what they are required to enter. This does not meet WCAG 2.2 success criteria 3.3.2 (Labels or Instructions) and 2.4.7 (Focus Visible). We have written a new version of the rich text editor which corrects this issue - this is in the process of being updated everywhere on eCase.

The collapsing sections on the Response screen may not function optimally with iOS VoiceOver. Specifically, the focus may become trapped on the section title, requiring users of VoiceOver to either perform rapid multiple swipes or use the two-finger swipe down gesture to navigate and read the entire page effectively.

Searchable dropdowns fail some automated accessibility tests, but in practice we have found they are usable with assistive technology.

Preparation of this accessibility statement

This statement was prepared on 21 November 2024.

This service has been tested by Zoonou. This test was carried out on 24 April 2024.