Accessibility Statement

Each section outlines the WCAG 2.2 failure and associated issues. 

​

• Meaningful Sequence (WCAG 2.2 success criterion 1.3.2)

  • ​A screenreader user is unable to read through content of the main page other than backwards via VoiceOver and left arrow which inhibits natural understanding of a logical page structure.

  • A heading level 3 “What do I need to apply?” is read out of order by screen readers and comes last in a section after the body text. This could make it difficult for screenreader users to navigate the page logically. 

  • After the section “Recruitment process”, heading and body text elements are read out of order by screen readers making it hard to distinguish meaning. This could make it difficult for screenreader users to navigate the page logically.

• Use of Colour (WCAG 2.2 success criterion 1.4.1)

  • ​​​​​Some links have no clear visual styling to indicate that they are links (e.g., underlined or color differentiation). This may be difficult for several users who are expecting all links to be styled the same way to aid navigation. 

• Keyboard access (WCAG 2.2 success criterion 2.1.1)

  • ​When using a keyboard only via a screenreader, there is no way for the user to access the images of the clients logos that appear when hovering over the logos without a mouse.

  • A keyboard-only user cannot interact with some content such as the ‘x’ clear button on the search field or links on some pages. 

• Bypassing blocks of content (WCAG 2.2 success criterion 2.4.1) 

  • The skip to main content jumps to the bottom of the page and reads from “Signed on behalf of the supplier” missing most of the page's meaningful content. This could be confusing for screenreader users.

• Focus order (WCAG 2.2 success criterion 2.4.3)

  • When a screenreader tabs through the page some content is read out as ‘undefined’. This would be confusing for a screenreader user as the content is not labelled correctly or visually present. There is a focus in the tabbing order that covers the whole main content on the page. It is unclear for a keyboard user what interactive element this is or whether they can even interact with this. ​

  • On some pages when tabbing, users are able to focus on some content e.g. heading level 2s and text labels but cannot interact with the text that it is focused on. Keyboard-only users would expect to be able to interact with elements that are in the tabbing order so this may be confusing.

  • On the footer banner, cookie banner and Job Application and Contact Us page the tabbing sequence is in an order that does not make sense. This would be confusing for keyboard-only and screenreader users. 

• Links purpose (WCAG 2.2 success criterion 2.4.4)

  • The ‘See all’ link to view all posts is not clear in the context, as there are several groups it could refer to on the page. Some links only display the URL and have no descriptive content. This means that users navigating via links will struggle to understand the purpose of the links. ​

• Headings and labels (WCAG 2.2 success criterion 2.4.6)

  • On the ‘Insights’ page when viewing the page through the landmarks menu, several ‘articles’ do not have specific names so screen reader users may be unclear on what they are accessing. In addition, there are 2 landmarks labels present that take the user to the same content on the screen. Heading hierarchy skips levels, jumping from H1 to H3 for most page headings and then back to H2 - making it difficult to navigate the page by headings. ​

  • The first heading on the “Carbon Reduction Plan” page is duplicated in different heading levels (H1 and H3) causing ambiguity in the hierarchy for users who may navigate via headings. 

  • There are missing attributed heading levels for multiple sections, and heading levels are skipped. This could make it difficult for screenreader users who rely on headings for navigation. 

• Focus is visible (WCAG 2.2 success criterion 2.4.7)

  • ​The blue outline that demonstrates keyboard focus is not clear on the Solirius logo. This means that users who may experience colour blindness may not be able to see where their focus is. 

• On input (WCAG 2.2 success criterion 3.2.2)

  • All social media links and privacy links take the user out of the page but this is not communicated via a screenreader (or in visual text). This may be disorientating for a user if they do not expect this change in context. ​

  • The file name replaces upload guidance text when a wrong file format is uploaded. This means that a user will no longer get access to the input guidance, which they will not expect. 

  • A user cannot swipe/scroll on a mobile on the pdf viewer. 

• Error identification (WCAG 2.2 success criterion 3.3.1)

  • ​On the Job Application page, the input fields become red (suggesting an error has been made) before any information has been submitted by the user. This could cause confusion for a user if they try to rectify an error they have not created. 

  • ​Errors appear on screen but are not read out by a screenreader. This means assistive technology users may not be aware that the error has appeared. This fails WCAG 2.2 success criterion 3.3.1 (Error Identification).

• Labels or instructions (WCAG 2.2 success criterion 3.3.2)

  • Field labels that are required in the form are not clearly identified as required. This is because the asterisk text is separate from the editable fields. This means that several assistive technology users may not know which fields are required. ​

• Name, role, value (WCAG 2.2 success criterion 4.1.2)

  • Some button labels are not unique. This means that several assistive technology users may not be able to differentiate between different button purposes. ​

  • The ‘close’ button on the Share link modal does not have a name so this may not be communicated for a screenreader user. 

  • The image thumbnails that accompany the blog posts under ‘Recent Posts’ are not identified as images (and also have no alt text). They are communicated as ‘article’ which could be confusing for screenreader users. 

  • After each checkbox ‘invalid data’ is read out via a screenreader. This may cause confusion for screenreader users.

  • On some pages the page number button is not read out accurately as ‘page X, button’ e.g. page 5, button. Not having this clarity may be confusing for screenreader users navigating via buttons.

  • Some plain text in the error message is identified as a link. This could be confusing for assistive technology users if they think that plain text is a link. 

  • A pdf is not marked up with tags so it is not clear what is a heading, text or content in a table. 

  • Some tables on the carbon reduction page are not marked up as tables so it is not clear what data relates to column headers. This means assistive technology users may struggle with understanding the relationships of the data in the table.