Accessibility Statement for Sellafield Careers This accessibility statement applies to https://careers.sellafieldsite.co.uk This website is run by Sellafield Ltd. 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. How accessible this website is We know some parts of this website are not fully accessible: images do not have appropriate alternative attributes headings and lists are not always marked up correctly related link elements aren’t grouped appropriately elements of the page are not accessible using keyboard only a ‘Skip to Main Content’ link does not function as expected headings are not appropriately structured across the site the tabbing order of the website may not always be logical a focus indicator is not always visible visual names of user interface elements do not always match the accessible label navigation elements are displayed inconsistently across the site Feedback and contact information If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact: Email Ross.gardner@sellafieldsites.com (careers website manager – Sellafield Ltd) If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille: email recruitment@sellafieldcloud.co.uk call (0)19467 81000 – please request to be put through to the recruitment team (Option 1). We’ll consider your request and get back to you in 10 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 Sellafield Ltd 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 and exemptions are listed below. Non-accessible content The content listed below is non-accessible for the following reasons. Non-compliance with the accessibility regulations Some images do not have a text alternative, so people using a screen reader cannot access the information. This fails WCAG 2.2 success criterion 1.1.1 Non-text Content. We plan to resolve this by: 31/03/2027 Decorative images have informative alternative attributes, which presents unnecessary information to screen reader users. This fails WCAG 2.2 success criterion 1.1.1 (Non-text Content). We plan to resolve this by: 31/03/2027 Adjacent image and text links are not combined, which may result in screen readers announcing these elements multiple times. This fails WCAG 2.2 success criterion 1.1.1 (Non-Text Content). We plan to resolve this by: 31/03/2027 Pre-recorded videos do not have a text transcript or audio description track. This fails WCAG 2.2 success criterion 1.2.3 (Audio Description or Media Alternative). We plan to resolve this by: 31/03/2027 Pre-recorded videos do not have an audio description track. This fails WCAG 2.2 success criterion 1.2.5 (Audio Description (Pre-Recorded)). We plan to resolve this by: 31/03/2027 Headings and lists are not marked up appropriately, which may cause screen readers to announce them incorrectly. This fails WCAG 2.2 success criterion 1.3.1 (Info and Relationships). We plan to resolve this by: 31/03/2027 Grouped fields are not contained within a fieldset element, which may result in confusing announcements by screen readers. This fails WCAG 2.2 success criterion 1.3.1 (Info and Relationships). We plan to resolve this by: 31/03/2027 ARIA Landmarks have confusing accessible labels. This may cause content to be missed by screen reader users. This fails WCAG 2.2 success criterion 1.3.1 (Info and Relationships). We plan to resolve this by: 31/03/2027 Some navigational links on the page are not contained within a navigation element. This stops users who navigate using landmarks from being able to directly access the navigational links. This fails WCAG 2.2 success criterion 1.3.1 (Info and Relationships). We plan to resolve this by: 31/03/2027 Variations in text, such as highlighted search results, are used to communicate information. This may result in users with visual impairments missing information. This fails WCAG 2.2 success criterion 1.3.1 (Info and Relationships). We plan to resolve this by: 31/03/2027 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: 31/03/2027 Rendering issues are present with text when zooming text only to 200% using browser zoom controls. This fails WCAG 2.2 success criterion 1.4.4 (Resize Text). We plan to resolve this by: 31/03/2027 Images of text are present on the page, which cannot be resized or styled by browsers. This fails WCAG 2.2 success criterion 1.4.5 (Images of Text). We plan to resolve this by: 31/03/2027 Two-dimensional scrolling is required to access page content, and some page content is obscured 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: 31/03/2027 Some non-textual content lacks contrast against the background page. This includes carousel pagination, close and view buttons. This fails WCAG 2.2 success criterion 1.4.11 (Non-Text Contrast). We plan to resolve this by: 31/03/2027 Applying spacing or custom styling to text results in a loss of content. This fails WCAG 2.2 success criterion 1.4.12 (Text Spacing). We plan to resolve this by: 31/03/2027 Some content is inaccessible when using a keyboard to navigate the site. This includes the ‘Create Job Alert’ button on the Vacancies page. This fails WCAG 2.2 success criterion 2.1.1 (Keyboard). We plan to resolve this by: 31/03/2027 Content that moves automatically is present, with no mechanism available to be able to pause, stop, or hide the moving content by the user. This fails WCAG 2.2 success criterion 2.2.2 (Pause, Stop, Hide). We plan to resolve this by: 31/03/2027 A correctly formed heading structure is not present to facilitate navigation across the site, with skipped or no heading levels present. This fails WCAG 2.2 success criterion 2.4.1 (Bypass Blocks). We plan to resolve this by: 31/03/2027 A ‘Skip to Main Content’ link is not functional, and users must tab through repetitive breadcrumb content. This fails WCAG 2.2 success criterion 2.4.1 (Bypass Blocks). We plan to resolve this by: 31/03/2027 The focus order of the page is not logical. Users who rely on keyboard access or a screen reader for operating a page benefit from a logical, usable focus order. This fails WCAG 2.2 success criterion 2.4.3 (Focus Order). We plan to resolve this by: 31/03/2027 Empty links that contain no text or images without alternative text, as well as links with generic text, are present. The function or purpose of these links will not be presented to screen reader users. This fails WCAG 2.2 success criterion 2.4.4 (Link Purpose (In Context)). We plan to resolve this by: 31/03/2027 Links with identical text are not distinguished by their accessible labels. This could confuse screen reader users. This fails WCAG 2.2 success criterion 2.4.4 (Link Purpose (In Context)). We plan to resolve this by: 31/03/2027 The focus indicator is not visible for some user interface elements. This can make it difficult for keyboard-only users to keep track of the elements currently in focus. This fails WCAG 2.2 success criterion 2.4.7 (Focus Visible). We plan to resolve this by: 31/03/2027 The displayed name of a user interface component does not always match the accessible label. This may result in navigation issues for speech recognition users. This fails WCAG 2.2 success criterion 2.5.3 (Label in Name). We plan to resolve this by: 31/03/2027 Targets on the page do not meet the minimum size requirement of 24 by 24 pixels. This may make it more difficult for users with motor impairments to interact with targets. This fails WCAG 2.2 success criterion 2.5.8 (Target Size (Minimum)). We plan to resolve this by: 31/03/2027 When navigation menu items or search fields receive focus, this results in unexpected behaviour such as content displaying without selection. This fails WCAG 2.2 success criterion 3.2.1 (On Focus). We plan to resolve this by: 31/03/2027 The cursor when hovering over an image or show more button has the same display across pages, but performs different functions. This could cause confusion about how to interact with this component. This fails WCAG 2.2 success criterion 3.2.4 (Consistent Identification). We plan to resolve this by: 31/03/2027 Some uses of ARIA are not appropriate and may result in some content announcing incorrectly by screen readers. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value). We plan to resolve this by: 31/03/2027 Separator content, expandable menus, hidden content and form submission errors are announced incorrectly by screen readers. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value). We plan to resolve this by: 31/03/2027 Images, carousel pagination, icons and dropdown options are announced incorrectly by mobile screen readers. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value). We plan to resolve this by: 31/03/2027 Content which is not displayed on the page is highlighted by speech recognition software such as Dragon NaturallySpeaking. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value). We plan to resolve this by: 31/03/2027 Status messages are announced incorrectly or not announced by screen readers. This may result in users being unable to correct input errors. This fails WCAG 2.2 success criterion 4.1.3 (Status Messages). We plan to resolve this by: 31/03/2027 Content that’s not within the scope of the accessibility regulations Uploading Files using Speech Recognition Software It is not possible to upload files using the upload button on the Apply page. This is a known issue of speech recognition software, such as Dragon NaturallySpeaking, and cannot be fixed. What we’re doing to improve accessibility We are developing our accessibility roadmap which will show how and when we plan to improve accessibility on this website. This will be made available here once published. Preparation of this accessibility statement This statement was prepared on 29/05/2026. It was last reviewed on 17/06/2026. This website was last tested on 28/05/2026. The test was carried out by Zoonou. Zoonou used WCAG-EM to define the pages tested and test approach.
