Skip to main content
Accessibility statement for AI4GREEN

Accessibility statement for AI4Green


This accessibility statement applies to the AI4Green website only and applies to pages under the following domain ai4green.app

This website is run by the University of Nottingham. 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 using browser or device settings
  • zoom in up to 400% without the text spilling off the screen
  • navigate most of the website using a keyboard or speech recognition software
  • listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)

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.

  • Some user interface components are not fully operable using a keyboard alone and some do not have a clearly visible focus indicator.
  • Not all user interface components have accessible descriptions, which may cause issues for users of assistive technology.
  • Some images lack accessible descriptions and some complex images have accessible descriptions which do not provide enough detail to fully understand what the image portrays.
  • Some images contain text, and users of assistive technology may not be able to fully understand the image's content from its accessible description alone.
  • The text on a number of buttons does not have sufficient contrast against their backgrounds which may cause issues for users with vision deficiencies.
  • Some hyperlinks rely on color alone to distinguish themselves, which may make them difficult to recognize for users with colour vision deficiencies.
  • The auto-generated captions for an embedded YouTube video do not fully or accurately describe the video content, and an audio description is not available.
  • On some pages, when the content updates or changes the change will not be announced to assistive technologies. This includes status alert messages.
  • Most pages do not have a mechanism to skip to the main content, which may affect keyboard-only users.
  • Some page content becomes inaccessible or obscured when zooming in to 200%. Some content may be hidden or partially obscured when text spacing is increased above the default settings.
  • Many pages may not be usable on small screens, such as mobile phones, due to overlapping content or content that does not resize appropriately to fit the screen.

Feedback and contact information

If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille:

We’ll then consider your request and get back to you within 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

The University of Nottingham 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

The website has been tested against the Web Content Accessibility Guidelines (WCAG) 2.2 AA standard.

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

  • Some images lack text alternatives, preventing people using assistive technologies from understanding their meaning. Additionally, some images contain text, making their content inaccessible to these users.

    This fails WCAG 2.2 success criteria 1.1.1 (Non-text Content) and 1.4.5 (Images of Text), respectively.

    We plan to address these issues by Q4 2026.

  • An embedded video has automatically generated captions which do not accurately describe the content of the media. Additionally the video has no audio description and the content of the video is not fully described by the audio commentary.

    This fails WCAG 2.2 success criteria 1.2.2: Captions (Prerecorded), 1.2.3: Audio Description or Media Alternative (Prerecorded) and 1.2.5: Audio Description (Prerecorded).

    We plan to fix these issues by Q4 2026.

  • Information, structure, and relationships conveyed through presentation can not always be programmatically determined or are available in text. For instance, some form labels are not correctly bound to their respective form inputs.

    This fails WCAG 2.2 success criterion 1.3.1: Info and Relationships.

    We plan to fix these issues by Q4 2026.

  • A user interface icon "i" ( which can render popover information ) assumes that users will associate it with "information." However this user interface element does not provide an accessible alternative for users who may not perceive visual cues.

    This fails WCAG 2.2 success criterion 1.3.3: Sensory Characteristics.

    We plan to fix these issues by Q4 2026.

  • The purpose of some form fields ( which serve a purpose identified in the Input Purposes for User Interface Components) cannot be programmatically determined.

    This fails WCAG 2.2 success criterion 1.3.5: Identify Input Purpose.

    We plan to fix these issues by Q4 2026.

  • A large number of user interface components, such as buttons, have insufficient text-to-background contrast and do not meet the minimum required ratio. Additionally, some user interface components fail to maintain a contrast ratio of at least 3:1 against adjacent colors.

    This fails WCAG 2.2 success criterion 1.4.3: Contrast (Minimum) and 1.4.11: Non-text Contrast respectively.

    We plan to fix this issue by Q4 2026.

  • Some text and user interface components, such as buttons, are partially obscured, not visible, or overlapped by other content at 200% zoom level.

    This fails WCAG 2.2 success criterion 1.4.4: Resize text.

    We plan to fix this issue by Q4 2026.

  • Some content cannot be presented without loss of information or functionality, or without requiring scrolling in two dimensions for:

    • Vertical scrolling content at a width equivalent to 320 CSS pixels;
    • Horizontal scrolling content at a height equivalent to 256 CSS pixels.

    This fails WCAG 2.2 success criterion 1.4.10: Reflow.

    We plan to fix this issue by Q4 2026.

  • Some content may be obscured or truncated when text spacing and/or line height is adjusted.

    This fails WCAG 2.2 success criterion 1.4.12: Text Spacing.

    We plan to fix this issue by Q4 2026.

  • The "i" information popover displays help content on mouse hover; however, there is no mechanism to dismiss the content without moving the mouse away.

    This fails WCAG 2.2 success criterion 1.4.13: Content on Hover or Focus.

    We plan to fix this issue by Q4 2026.

  • Some functionality of the website is not operable through a keyboard interface alone. This includes Ketcher, the chemical structure editor.

    This fails WCAG 2.2 success criterion 2.1.1: Keyboard.

    We plan to fix this issue by Q4 2026.

  • The website lacks a "Skip to Content" feature to bypass repeated blocks of content across multiple pages..

    This fails WCAG 2.2 success criterion 2.4.1: Bypass Blocks.

    We plan to fix this issue by Q4 2026.

  • The purpose of a link cannot be determined from the link text alone or from the link text together with its programmatically determined link context.

    This fails WCAG 2.2 success criterion 2.4.4: Link Purpose (In Context).

    We plan to fix this issue by Q4 2026.

  • The website does not implement breadcrumb navigation trails or a site map.

    This fails WCAG 2.2 success criterion 2.4.5: Multiple Ways.

    We plan to fix this issue by Q4 2026.

  • Some headings or labels do not accurately describe their topic or purpose.

    This fails WCAG 2.2 success criterion 2.4.6: Headings and Labels.

    We plan to fix this issue by Q4 2026.

  • The visible focus outline of a button is not fully rendered within the viewable area of the page.

    This fails WCAG 2.2 success criteria 2.4.7: Focus Visible and 2.4.11: Focus Not Obscured (Minimum).

    We plan to fix this issue by Q4 2026.

  • Changing the setting of some interface components can cause a change of context on the page, which has not been previously advised to the user.

    This fails WCAG 2.2 success criterion 3.2.2: On Input.

    We plan to fix this issue by Q4 2026.

  • Some form input errors are ambiguous and not described in sufficient detail to the user.

    This fails WCAG 2.2 success criterion 3.3.1: Error Identification.

    We plan to fix this issue by Q4 2026.

  • A number of forms have labels not programatically bound to their field inputs or rely on placeholder attributes alone.

    This fails WCAG 2.2 success criterion 3.3.2: Labels or Instructions.

    We plan to fix this issue by Q4 2026.

  • Some form validation errors are ambiguous and may not be described in sufficient detail for the user to know how to fix them.

    This fails WCAG 2.2 success criterion 3.3.3: Error Suggestion.

    We plan to fix this issue by Q4 2026.

  • A form allowing a change of email address does not have a mechanism for reviewing, confirming, or correcting information before submission.

    This fails WCAG 2.2 success criterion 3.3.4: Error Prevention (Legal, Financial, Data) .

    We plan to fix this issue by Q4 2026.

  • A number of user interface components have names or roles that cannot be programmatically determined, are missing, or have invalid ARIA attributes.

    This fails WCAG 2.2 success criterion 4.1.2: Name, Role, Value.

    We plan to fix this issue by Q4 2026.

  • Some status messages are not announced to assistive technology.

    This fails WCAG 2.2 success criterion 4.1.3: Status Messages.

    We plan to fix this issue by Q4 2026.

Preparation of this accessibility statement

This statement was prepared on 28th March 2024. It was last reviewed on 28th March 2024.

This website was last tested on 26th March 2024 against the WCAG 2.2 AA standard.

A self-assessment of this website was performed using a combination of automated and manual accessibility test practices across a subset of pages and typical functions. The assessment used a range of browser plugins and Chrome browser devtools for analysis.

The assessment was carried out by an in-house web developer employed by the University of Nottingham and was carried out to the WCAG 2.2 AA standard.