Accessibility statement for NRW jobs (Kallidus Recruit)
This accessibility statement applies to the internal and external portal.
This website is run by Natural Resources Wales. We want as many people as possible to be able to use this website. For example, 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
- navigate most of the website using just a keyboard
- navigate most of the website using speech recognition software
- listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)
We’ve also made the website text as simple as possible to understand.
AbilityNet has advice on making your device easier to use if you have a disability.
You can:
- call us on 0300 065 3000 (Mon-Fri, 9am-5pm)
- email enquiries@naturalresourceswales.gov.uk
- write to us at:
Natural Resources Wales
Welsh Government Offices
Cathays Park
King Edward VII Avenue
Cardiff
CF10 3NQ
We’ll consider your request and get back to you in 5 working days.
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 website’s accessibility
Natural Resource Wales is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
Compliance status
This website is not compliant with the Web Content Accessibility Guidelines version 2.2 AA standard. The non-compliances are listed below.
Non-accessible content
The content listed below is non-accessible for the following reasons.
Non-compliance with the accessibility regulations
The ‘Yes or No’ control on the ‘Your Account - Job Alerts’ webpage lacks an associated text label or descriptive title. Without a label, no information is available to provide functionality or context about the form control to screen reader users. This fails WCAG 2.2 success criterion 1.1.1 - Non-text Content.
We plan to resolve this by: 31/3/2026
Variations in text are not marked using semantic markup. On the ‘Internal Opportunities’ webpage, an <h3> heading is implemented as a custom <div>. On the ‘Your Application’ webpage, the list within ‘Tell us what you bring to this role’ does not use <ul> and <li> markup. This fails WCAG 2.2 success criterion 1.3.1 - Info and Relationships.
We plan to resolve this by: 31/3/2026
The ‘Internal Opportunities’ webpage contains a table with an empty header cell. This fails WCAG 2.2 success criterion 1.3.1 - Info and Relationships.
We plan to resolve this by: 31/3/2026
ARIA landmarks are not used to identify all page content. This may result in content being overlooked by screen reader users. This fails WCAG 2.2 success criterion 1.3.1 - Info and Relationships.
We plan to resolve this by: 31/3/2026
Fieldset’s are implemented incorrectly on the ‘Your Account -Change Password’ and ‘Your Account- Job Alerts’ webpages, which may result in confusing announcements for screen reader users. This fails WCAG 2.2 success criterion 1.3.1 - Info and Relationships.
We plan to resolve this by: 31/3/2026
Buttons do not have accessible names. The mobile navigation menu button and the location button on the ‘Internal Opportunities’ webpage lack an accessible name. This fails WCAG 2.2 success criterion 1.3.1 - Info and Relationships.
We plan to resolve this by: 31/3/2026
The autocomplete attribute is set to ‘Off’ for the password, first name, last name, telephone, address, and email fields. As a result, these fields cannot be programmatically identified by assistive technologies. This fails WCAG 2.2 success criterion 1.3.5 - Identify Input Purpose.
We plan to resolve this by: Date 31/3/2026
Text does not meet sufficient contrast requirements against the page background. This fails WCAG 2.2 success criterion 1.4.3 - Contrast Minimum.
We plan to resolve this by: Date 31/3/2026
Two-dimensional scrolling is required to access page content when zooming the page to 400% with a browser width of 1280px. This fails WCAG 2.2 success criterion 1.4.10 - Reflow.
We plan to resolve this by: Date 31/3/2026
The visual focus indicator does not meet the required contrast ratio. This fails WCAG 2.2 success criterion 1.4.11 - Non-Text Contrast.
We plan to resolve this by: Date 31/3/2026
Interactive error messages are not accessible via keyboard alone. As a result, users who navigate the website solely using a keyboard may be unable to access the error message link functionality. This fails WCAG 2.2 success criterion 2.1.1 - Keyboard.
We plan to resolve this by: Date 31/3/2026
A correctly formed heading structure is not present on the ‘Your Account - Job Alerts’ webpage. A skipped <h2> heading level has been identified, which may disrupt navigation for screen reader users. This fails WCAG 2.2 success criterion 2.4.1 - Bypass Blocks.
We plan to resolve this by: Date 31/3/2026
The tab order on some pages is not logical. After an error is displayed, focus moves to the top of the webpage and then to the footer, which may confuse keyboard and screen reader users. This fails WCAG 2.2 success criterion 2.4.3 - Focus Order.
We plan to resolve this by: Date 31/3/2026
Multiple instances of identical link text are present, each directing the user to a different location. This fails WCAG 2.2 success criterion 2.4.4 - Link Purpose - In Context.
We plan to resolve this by: Date 31/3/2026
On the ‘Application Form’ page, all text area input fields have an accessible name of ‘Required’. This fails WCAG 2.2 success criterion 2.5.3 - Label in Name.
We plan to resolve this by: Date 31/3/2026
The page language has not been defined. As a result, screen reader users may not hear the correct pronunciation of certain words. This fails WCAG 2.2 success criterion 3.1.1 - Language.
We plan to resolve this by: Date 31/3/2026
Format requirements are not specified within field labels, which may cause confusion for screen reader users. This fails WCAG 2.2 success criterion 3.3.2 - Labels or Instructions.
We plan to resolve this by: Date 31/3/2026
The ‘Skip to main content’ functionality is visually hidden but focusable on both iOS and Android devices. Focusing on visually hidden content with a screen reader may be disorienting for users. This fails WCAG 2.2 success criterion 4.1.2 - Name, Role, Value.
We plan to resolve this by: Date 31/3/2026
While using TalkBack and VoiceOver (mobile screen readers), unexpected announcements occur. Select content is announced twice, job descriptions and roles include the announcement ‘Term’, and on VoiceOver, invalid announcements display a warning icon which, when focused, produces no announcement. This fails WCAG 2.2 success criterion 4.1.2 - Name, Role, Value.
We plan to resolve this by: Date 31/3/2026
Some uses of ARIA are not appropriate and may cause certain content to be announced incorrectly by screen readers. This fails WCAG 2.2 success criterion 4.1.2 - Name, Role, Value.
We plan to resolve this by: Date 31/3/2026
Not all content may be interactable whilst navigating using Dragon Naturally Speaking. This fails WCAG 2.2 success criterion 4.1.2 - Name, Role, Value.
We plan to resolve this by: Date 31/3/2026
Disproportionate burden
Dragon Naturally Speaking (speech recognition software) can only upload files when using the mouse grid feature. This issue is believed to be an ongoing issue with the Dragon Naturally Speaking software and further information can be found on the following link: https://github.com/alphagov/reported-bugs/issues/35.
As this is a third-party issue we are unable to fix this and it is therefore exempt from meeting the accessibility regulations and consequently a disproportionate burden within the meaning of the accessibility regulations.
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. We will make another assessment when the supplier contract is up for renewal, likely to be in [rough timing].
What we’re doing to improve accessibility
Our accessibility roadmap [add link to roadmap] shows how and when we plan to improve accessibility on this website.
Preparation of this accessibility statement
This statement was prepared on 28/08/2025. It was last reviewed on 28/08/2025.
This website was last tested on 28/08/2025. The test was carried out by Zoonou.
Zoonou used WCAG-EM to define a representative sample of pages and the test approach.