Accessibility statement for Computer Assisted Mapping E-commerce Online 2 (CAMEO 2)
This page explains how accessible the nidirect Computer Assisted Mapping E-commerce Online 2 (CAMEO 2) is and what is being done to improve accessibility.
This service is part of the wider nidirect website. There’s a separate accessibility statement for the main nidirect website.
This page only contains information about the nidirect Computer Assisted Mapping E-Commerce Online 2 (CAMEO 2).
This statement applies to the CAMEO 2 services web based application which is accessible via the www.nidirect.gov.uk website.
This application is run by the Department of Finance. It's designed to be used by as many people as possible. The text should be clear and simple to understand. When accessing the application through the web browser, you should be able to:
- zoom in up to 300 per cent without problems
- navigate most of the application using just a keyboard
- navigate most of the application using speech recognition software
- use most of the application using a screen reader (including the most recent versions of JAWS, NVDA and Voice Over)
How accessible is this web application
Parts of this web application are not fully accessible. For example:
- provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language
- create content that can be presented in different ways for example simpler layout without losing information or structure
- ensuring the colour contrast is high enough between the text colour and the background colour to make it easier to read
- provide users enough time to read and use content
- provide ways to help users navigate, find content and determine where they are
Feedback and contact information
If you need information in a different format contact us by either:
- calling the NI Direct Contact Centre which handle calls on our behalf on 0300 200 7802
- email: DOF.Enquiries@finance-ni.gov.uk
and advise the following:
- 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 application. If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact us on 0300 200 7802 or by email at DOF.Enquiries@finance-ni.gov.uk 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 web apps accessibility
nidirect is committed to making its website and apps accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
The NI Direct CAMEO 2 service does not meet WCAG 2.1 A or AA as a whole.
Non-compliance with the accessibility regulations
The content that is not accessible is outlined below with details of:
- the accessibility problem(s)
- 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. All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for the following situations: Controls Input, Time Based Media, Test, Sensory CAPTCHA and Decoration, Formatting, Invisible.
Level A - 1.3.1 Info and relationships. All pages make use of ARIA landmarks, but are missing landmark tags. Landmark tags are used by screen reader users to navigate through the content more easily.
Level AA - 1.3.5 Identify input purpose (added in WCAG 2. Within the customer portal, when collecting information about the user and the input field serves a purpose identified in https://www.w3.org/TR/WCAG21/#inputpurposes, then the autocomplete attribute should be used with appropriate tokens listed, so that assistive technology can programmatically determine the purpose of a form input1).
Level AA - 1.4.3 Contrast (minimum). A colour contrast for normal text of 4.5:1, and large text at 3:1, is required to provide enough contrast between text and its background so that it can be read by people with moderately low vision or visual impairments such as colour blindness.
Level AA - 1.4.4 Resize text. When text is zoomed to 200 per cent, the search select drop down loses its content, however this can be perceived when clicking on the dropdown itself. It is recommended to measure elements height and padding in relative rem or em units rather than pixels, so they respond to the user’s text size.
Level AA - 1.4.10 Reflow. With the customer portal it is noted that the right-hand side section (with an empty box for an assumed map) is removed from the page on a smaller breakpoint. If this is intended for smaller device users to not access this content, then this is no issue. However, consider if this could be displayed for mobile users, and design accordingly.
Level AA - 1.4.11 Non-text contrast (added in WCAG 2.1). A colour contrast for non-text elements such as user interface components, and graphical objects, of 3:1 is required to provide enough contrast between an element and its background so that it can be perceived by people with moderately low vision.
Level AA - 1.4.12 Text spacing (added in WCAG 2.1). When the required text spacing properties are applied, which some users will use to provide a more perceivable reading experience, the out of stock warning message is hidden behind the right-hand side box and some content is lost. Make sure that when the text spacing properties are applied, the warning message is not hidden.
Level A - 2.2.1 Timing adjustable. Within the customer portal there is no warning of a timeout occurring, and the user does not have an opportunity to extend this timeout or adjust it. They are logged out of the system without warning. Whilst their basket is retained, it is important to allow users to extend their time limit to provide more time for users with vision, dexterity or cognitive limitations.
Level A - 2.4.1 Bypass block. A mechanism is available to bypass blocks of content that are repeated on multiple Web pages.
Level A - 2.4.2 Page titled. The web page to have a descriptive and informative page title.
Level A - 2.4.3 Focus order. If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability.
Level A - 2.4.4 Link purpose (in context). The username is inserted into the top navigation using pseudo content through CSS. For users who need to turn off stylesheets in order to view content, assistive technology may not be able to access this information. Whilst the username is not necessary for function, and the drop-down menu associated will appear next to the empty link, it is important to never inject content with CSS across the service.
Level AA - 2.4.7 Focus visible. Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible.
Level A - 3.3.1 Error identification. If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text.
Level A - 3.3.2 Labels or instructions. Labels or instructions are provided when content requires user input.
Level AA - 3.3.3 Error suggestion. If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content.
Level AA - 3.3.4 Error prevention (legal, financial, data). Within the customer portal the checkout user journey, which ultimately will cause a financial commitment to the user, has multiple opportunities for users to check their data, including a summary screen of the user’s entered values. However, due to the fields not providing help text or error indication for screen reader users, there is concern that assistive technology users may struggle to check their data and in general struggle to complete the form. However, due to the summary screen which provides an overview of information, this user journey partially passes.
Level A - 4.1.1 Parsing. In content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features.
Level A 4.1.2 - Name, role, value. For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies.
Level AA (Added in WCAG 2.1) 4.1.3 Status messages. In content implemented using markup languages, status messages can be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus.
Content that’s not within the scope of the accessibility regulations
As a web application published before 23 September 2018, we are required to comply with the web accessibility regulations from 23 September 2020.
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 web application
This web 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.
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 October 2020. It was last updated on 27 October 2020.