This statement applies to content published on the https://govfundingpublic.nics.gov.uk website.
This website is run by the Department for Communities. It is designed to be used by as many people as possible. The text should be clear and simple to understand. For example you should be able to:
- zoom in up to 300% without problems
- navigate most of the website using just a keyboard
- navigate most of the website using speech recognition software
- use most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)
How accessible this website is
Parts of this website are not fully accessible. For example:
- some pages and elements have poor colour contrast
- some images do not have good alternative text
- some elements of pages would be difficult for keyboard or assistive technology to read
- deprecated HTML attributes are present, for example the align, width and height attributes in tables
How to request content in an accessible format
If you need information in a different format contact us by using the feedback form and tell us:
- 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 with this website
We’re always looking to improve the accessibility of this website. If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact us by using the feedback form and our Communications & Engagement Unit 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 are not happy with how we respond to your complaint, contact the Equality Commission for Northern Ireland (ECNI).
Technical information about this website’s accessibility
The Department for Communities is committed to making its websites accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
This website is not 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.
Non-compliance with the accessibility regulations
A basic audit check was completed on the website, using a range of tools. Examples of non-accessible content are outlined below, with details of:
- the accessibility problem(s)
- where it fails the success criteria, and
- when we plan to fix it
The website was not developed by the Department for Communities and was inherited for support purposes after the NICS departmental restructuring in November 2016.
There is a lack of technical documentation.
Our IT team currently has a lack of available resources and skills in web accessibility.
The web application is old and is deemed out of support.
Examples of content that does not meet WCAG 2.1 design principles:
Principle 1 (Perceivable) - Information and user interface components must be presentable to users in ways they can perceive.
There are multiple images used within the website that do not have the alt attribute. Without alternative text, the function of an image button is not made available to screen reader users or when images are disabled or unavailable.
After searching for an organisation, results are displayed within a table. The header and the footer display text which fall outside the allowed contrast ratio. The contrast between the colour of text and its background for the element makes it difficult to read the text and not easily distinguishable. The contrast between the colour of text and its background element should be in the ratio of 4.5:1 for standard text, or 3:1 for larger text.
Principle 3 (Understandable) - Information and the operation of user interface must be understandable
The language attribute on all pages within the website has not been set. When the language is not set, screen readers and other assistive technologies have no way of being sure of the correct way to accessibly present the contents. Each page should declare the natural language for the page so that the content will be pronounced properly by text-to-speech software.
Principle 4 (Robust) - Content must be robust enough that it can be interpreted by a wide variety of user agents, including assistive technologies.
There are several examples where a deprecated HTML attribute has been used. Attributes such as valign, cellspacing, cellpadding and width are now deemed obsolete. A stylesheet should be used instead. The continued use of deprecated tags may result in content being displayed incorrectly, which could make the application unusable in future releases of common web browsers.
When we plan to do to fix the issues
A full web accessibility audit is to be conducted by 30 November 2020. When the extent of the accessibility issues are reviewed, a plan of action will be produced and a statement update published.
Content that’s not within the scope of the accessibility regulations
As a website published before 23 September 2018, we are required to comply with the web accessibility regulations from 23 September 2020.
However, some of our content is exempt from the accessibility regulations:
- pre-recorded audio and video published before 23 September 2020
- heritage collections
- PDFs or other documents published before 23 September 2018 - unless required for the use of a service, for example a form
- third party content that is not within our control, for example, embedded video players like Vimeo or YouTube, and embedded Google Maps.
If you have any problems using this website, tell us using the feedback form and our Communications & Engagement Unit will investigate the issue and/or provide you with the information you need in an alternative format.
How we tested this website
A basic audit test was carried out internally for this website for compliance with the Web Content Accessibility Guidelines 2.1 level A and level AA.
We used the Website Accessibility Conformance Evaluation Methodology (WCAG-EM) approach to deciding on a sample of pages to test.
Ranges of tools were:
- Code Sniffer
The results of tests can be requested by using the feedback form.
What we’re doing to improve accessibility
We plan to conduct a full web accessibility audit by 30 November 2020 to identify all of the accessibility issues, followed by a course of action to either plan remediation work or to replace the website in order to meet the accessibility regulations. This statement will be updated once the results of the full audit have been reviewed.
This statement was prepared on 22 September 2020. It was last updated on 22 September 2020.