Accessibility statement for Legal Aid Management System (LAMS)
This page explains how accessible the nidirect legal aid management system (LAMS) is and what is being done to improve accessibility.
This statement applies to the LAMS extranet based application accessible via the www.nidirect.gov.uk website. This service is part of the wider nidirect website. There’s a separate accessibility statement for the main nidirect website.
This extranet application is run by the Department of Justice. It is designed to be used by solicitors and barristers who are making and managing Legal Aid applications and cases on behalf of their clients. The text should be clear and simple to understand by legal professionals. When accessing the extranet application through the web browser, you should be able to:
- zoom in up to 300 per cent without problems
- navigate most of the app using just a keyboard
- navigate most of the app using speech recognition software
- use most of the app using a screen reader (including the most recent versions of JAWS, NVDA and Voice Over)
How accessible this extranet application is
Parts of this extranet application are not fully accessible. For example:
- some images and icons do not have alternative text
- some pages include missing landmark tags
- some pages have fields that has autocomplete turned to off, as the Legal Aid process requires that specific fields need to updated in real time
- some pages and elements have poor colour contrast
- on the customer portal on one page when increased to 200per cent zoom level, the requests table is cut off slightly on the right-hand side
- some tables do not display well on a screen width of 320px, and the content displays over each other
- some pages have not the required level of contrast ratio of at least 3.1.
Feedback and contact information
If you need information in a different format contact us by calling the nidirect Contact Centre who handle calls on behalf of the Legal Services Agency on 028 90408888 and advise us of:
- the web address (URL) of the content
- your name and email address
- the format you need, for example, audio CD, braille, BSL or large print, accessible PDF
Reporting accessibility problems
We are always looking to improve the accessibility of this extranet application. If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact us on 028 90408888 and we will investigate the issue.
The Equality Commission for Northern Ireland (ECNI) is responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (the ‘accessibility regulations’) in Northern Ireland. If you’re not happy with how we respond to your complaint, contact the Equality Commission for Northern Ireland (ECNI).
Technical information about this extranet application accessibility
nidirect is committed to making its website and applications accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
The nidirect Legal Aid Management System (LAMS) does not meet WCAG 2.0 A or AA as a whole.
This extranet application is not compliant with the Web Content Accessibility Guidelines version 2.1 AA standard. The ‘non-compliances are listed below.
The content that is not accessible is outlined below with details of:
- the accessibility problem(s) and
- where it fails the success criteria
We are currently working towards developing a timeline of when we plan to fix these issues and this will be updated when available.
Level A - 1.1.1 Non-text content. There are many examples in the customer and employee portal where images and icons do not have alternative text.
Level A - 1.3.1 Info and relationships. Across the customer and employee portal common areas of concern include missing or landmark tags used by screen reader users to navigate through the content, missing elements used to group content together and also using incorrect heading styles
Level AA -1.3.5 Identify input purpose (added in WCAG 2.1). Some of these fields have autocomplete turned to ‘off’.
Level A - 1.4.1 Use of Colour. All links use both colour and underlining to indicate that they are links. They do not rely solely on colour.
Level AA - 1.4.3 Contrast (minimum). There are many cases throughout the customer and employee portal where the colour contrast between the text and the background is not high enough, making it difficult for some users to read
Level AA - 1.4.4 Resize text. When increased to 200 per cent zoom level, the requests table is cut off slightly on the right-hand side.
Level AA - 1.4.10 Reflow. When the screen is reduced in size, the table showing the requests displays scroll bars both horizontally and vertically.
Level AA - 1.4.11 Non-text contrast (added in WCAG 2.1). The dropdown list to select a business has an outline colour of #999999. Against the white background, this is not of high enough contrast. It has a contrast ratio of 2.84:1. The required ratio is 3:1.
Level A - 2.1.1 Keyboard. In general, most of the pages can be accessed via keyboard and in the correct order. For each page in the system, check that the user can access each element via keyboard and that when tabbing through, the user can tab through in the correct order.
Level A - 2.4.1 Bypass blocks. On the employee portal, there is no skip link on any of the pages that on activation will allow users to skip to the main content of the page. They will have to tab through all the navigation before reaching the main content. This skip link should be the first element focusable on a page and should skip repeated content.
Level A - 2.4.4 Link purpose (in context). Each <a> element must contain text or an img with an alt attribute.
Level AA - 2.4.6 Headings and labels. The <h2> heading is empty. Headings should not be empty.
Level AA - 2.4.7 Focus visible. There are some pages that do not have the current keyboard focus.
Level A - 3.3.2 Labels or instructions. There are currently no aria tags such as aria-required for those that use screen readers. Therefore the users will be informed in the label that the field is required, but the input itself could benefit with aria-required tags.
Level A - 4.1.1 Parsing. There are multiple elements on some pages with the same ID. However, whilst these elements seem to be visually hidden, it is important not to use duplicate IDs as this may confuse those users who use screen readers.
Level A - 4.1.2 Name, role, value. Each <a> element must contain text or an img with an alt attribute.
Level AA (Added in WCAG 2.1) 4.1.3 Status messages. Across the pages audited, the error messages do not contain aria live tags. It is recommended to use these tags to assist those who use screen readers.
Content that’s not within the scope of the accessibility regulations
As an extranet application we are required to comply with the web accessibility regulations for content published after 23 September 2019.
Some of our content is exempt from the accessibility regulations:
- pre-recorded audio and video content that was published before September 2020
- third party content that’s under someone else’s control. In the context of LAMS this includes supporting information uploaded onto LAMS by suppliers and
- content on the extranet published before 23 September 2019
PDFs and other documents
Many documents are non-accessible in a number of ways including missing text alternatives and missing document structure.
The accessibility regulations do not require us to fix PDFs or other documents published before 23 September 2018 if they’re not essential to providing our services.
Any new PDFs or other documents we publish will meet the required accessibility standards.
How we tested this extranet application
This extranet application was and is currently being tested for compliance with the Web Content Accessibility Guidelines 2.1 level A and level AA, and these tests have been carried out externally and independently of the Department of Justice.
We used the Website Accessibility Conformance Evaluation Methodology (WCAG-EM) approach to deciding on a sample of pages to test.
What we’re doing to improve accessibility
We are currently working towards developing a timeline of when we plan to fix these issues and this will be made available once completed.
This statement was prepared on 22 September 2020. It was last updated on 6 October 2020.