This accessibility statement applies to the StREAM software installation at the University of Essex. This software is known at the University of Essex as LEAP and will be referred to as such for the remainder of this document.
The application is licensed to the University of Essex from Soultionpath Limited.
We want as many people as possible to be able to use this web application. Solutionpath are therefore in the process of developing an accessible view for the student population. This alternate view will be available to the University within the July 2021 v4.2.1 increment, but may not be deployed until Summer 2022.
In the interim, Solutionpath have also made the website text as simple as possible to understand. Although all text displayed is defined by individual institutions.
AbilityNet has advice on making your device easier to use if you have a disability.
How accessible is the LEAP?
We know that some parts of the application aren’t fully accessible:
• Data representations are dynamic and we can't include information tags
• Data representations are difficult to see for those that are colour blind
• Our LEAP pages are difficult to navigate using just a keyboard
• Users can’t skip to main content when you are using a screen reader
If you need information on this application in a different format like accessible PDF, large print, easy read, audio recording or braille:
Email – firstname.lastname@example.org
We’ll consider your request and get back to you in 10 working days.
Reporting accessibility problems with LEAP
We’re always looking to improve the accessibility of this application. If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact Student Progress: email@example.com
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 applications accessibility
The University of Essex is committed to making LEAP accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
This application is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances listed below.
The content listed below is non-accessible for the following reasons
- Some images don’t have a text alternative, so the information in them isn’t available to people using a screen reader. This doesn’t meet WCAG 2.1 success criterion 1.1.1 (non-text content). We plan to add text alternatives for all images by April 2021. When we publish new content we’ll make sure our use of images meets accessibility standards.
- Engagement charts are not displayed as alternative text, so the information in them isn’t available to people using a screen reader. This doesn’t meet WCAG 2.1 success criterion 1.1.1 (non-text content).
- Some visual representations rely on colour. This doesn’t meet WCAG 2.1 success criterion 1.4.1 (use of colour). We plan to provide text alternatives as well as additional light and dark themes by April 2021. When we publish new content we’ll make sure our use of colour meets accessibility standards.
- Some form controls are missing labels which makes it hard for assisted technologies to know how to refer to each label when presenting a form control. This fails WCAG 2.1 success criterion 1.1.1 (Non-Text Content), 1.3.1 (Info and Relationships), 2.4.6 (Headings and Labels) and 3.3.2 (Labels or Instructions). We plan to ensure all labels are connected to a form control by April 2021
- Resource chart data is displayed in an alternative text, however navigation to the data is not accessible. This fails WCAG 2.1 success criterion 2.1.1 (Keyboard). We plan to ensure all content is accessible using a keyboard to navigate by April 2021.
- On some of our pages the language has not been set. This makes it difficult for some assisted technologies to know how to pronounce words or know what language the website is in. This fails WCAG 2.1 success criterion 3.1.1 (Language of Page). We plan to ensure every web page has its language set by April 2021.
Other non-compliance information
Acknowledging that we supply to HEI’s whom have obligations as PUBLIC sector organisations. Solutionpath subjected the LEAP platform to detailed analysis by a third party (Ability.net) it was determined that to make the application screen reader accessible would require;
A significant recreation of core code and modification of the design as LEAP was designed present complex data in an intuitive way and therefore reliant on graphical representations. To meet the requirements would take significant time and resource to do so, and
- Reduce the functionality of the software (such as removing visualisations).
It was considered to be a ‘disproportionate burden’ to achieve complete application accessibility for LEAP and therefore developing a dedicated accessible student view that ensures content is accessible is the proposed solution. This will be continually assessed as the disproportionate burden now won’t necessarily be a disproportionate burden forever.
Current functionality considered disproportionate burden
There’s no way to skip the repeated content in the page header (for example, a ‘skip to main content’ option). This doesn’t meet WCAG 2.1 success criterion 2.4.1 (bypass blocks).
- It’s not always possible to change the device orientation from horizontal to vertical without making it more difficult to view the content. This doesn’t meet WCAG 2.1 success criterion 1.3.4 (orientation).
- It’s not possible for users to change text size without some of the content overlapping. This doesn’t meet WCAG 2.1 success criterion 1.4.4 (resize text).
- Some of our interactive forms are difficult to navigate using a keyboard. For example, because some form controls are missing a ‘label’ tag.
- Our forms are built and hosted through third party software and ‘skinned’ to look like our website. This doesn’t meet WCAG 2.1 success criterion 1.3.1 (information and relationships).
We’ve assessed the cost of fixing the issues with navigation and accessing information, and with interactive tools and transactions. We believe that doing so now would be a disproportionate burden within the meaning of the accessibility regulations.
Content that’s not within the scope of the accessibility regulations
PDF’s and Other Documents
Many of our older PDFs and Word documents don’t meet accessibility standards - for example, they may not be structured so they’re accessible to a screen reader. This doesn’t meet WCAG 2.1 success criterion 4.1.2 (name, role value).
Some of our PDFs and Word documents are essential to providing our services. For example, we have PDFs with information on how users can access our services, and forms published as Word documents.
The accessibility regulations 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 don’t have captions. This doesn’t meet WCAG 2.1 success criterion 1.2.4 (captions - live).
We don’t plan to add captions to live video streams because live video is exempt from meeting the accessibility regulations.
Preparation of this accessibility statement
This statement was prepared on the 21 October 2020. It was last reviewed on 21 October 2020.
This application was last tested in December of 2018. The test was carried out by AbilityNet who tested the LEAP platform. A copy of the report may be requested by contacting us on: firstname.lastname@example.org.
What we’re doing to improve accessibility
Solutionpath will be releasing an accessible view in our v4.2.1 release in July 2021, the University may not deploy this until Summer 2022.
Soutionpath will be creating a single page accessible view of critical information for Student users.
Proposed accessible enhancements are as per the below and will be tested with the client base.
- The single page view will essentially be accordions that can be expanded and collapsed to see different sections of information.
- We're striving to make the page AA WCAG 2.1 compliant. We'll be using a plugin for the design software we’re using to ensure the designs adhere to proper contrast ratios and sizes. Furthermore, a checklist has been sent to members of the project to ensure everyone knows what boxes we're hoping to tick in terms of compliance.
- For the engagement tab, we're only showing the daily engagement data, and we're planning on changing the 'Overall' tab to a table view with the cohort average and top 25% lines represented in the table as extra rows.
- We'll be making slight modifications to the engagement bubbles to make them easier to understand; this will likely just be renaming of some labels.
- We'll be removing all date pickers and replacing them with set ranges of a week, four weeks and ten weeks.
- We'll be adding a filter for 'open' and 'complete' for exemptions and interventions to make it easier to find what users are looking for.
- We'll be inserting a big table showing resource usage.
- The profile tab will remain as is.
- We'll be leaving the context-sensitive links in place, but these will be added to the wireframes.
- Attendance will keep a summary table, and we will be adding filters for modules.
- Assessments will get a slight redesign with the addition of the assessment name on the accordion, we're also changing the date to the submission date, and we'll be adding a filter for modules.
- We'll also be creating a light theme and a dark theme for all three types of colour blindness.