Horizon

Accessibility statement for Oracle Cloud

This accessibility statement applies to the Oracle Cloud System implemented as Horizon at University of Greenwich (UoG). This website is run by Oracle and UoG has limited ability to review or change the website.

How accessible this website is

We know some parts of this website are not fully accessible. You can see a full list of any issues we currently know about in the Non-accessible content section of this statement.

Feedback and contact information

If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact: itservicedesk@greenwich.ac.uk

If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille email: itservicedesk@greenwich.ac.uk

We’ll review your request and get back to you in a working week.

Read tips on contacting organisation about inaccessible websites.

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).

If you are in Northern Ireland and are not happy with how we respond to your complaint you can contact the Equalities Commission for Northern Ireland who are responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (the ‘accessibility regulations’) in Northern Ireland.

Technical information about this website’s accessibility

Oracle 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 partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, due to the areas further outlined below.

For clarity Oracle maintains this website is fully compliant with the Web Content Accessibility Guidelines version 2.2 AA standard.

Non-accessible content

The content listed below is non-accessible for the following reasons. All issues have been reported to the vendor though as outlined above Oracle consider their system compliant, so fixing issues is slow.

Low contrast for text:

  • There is a high contrast mode for the system, but this functionality currently does nothing, without this functionality there is a very low contrast between text on backgrounds on parts of the page due to the inconsistent colour gradient of the background of the pages, this can be as low as 3:1, while a 4.5:1 or better is required to be compliant. Also, there is coloured text in some places with no explanation for the colour change.
  • Adequate contrast of text is necessary for all users, especially users with low vision, this is covered by part 1.4.3 Contrast (Minimum) (Level AA) in the legislation.
  • There is no current work around for this issue, though enlarging the text and manually highlighting it can help.

Links containing no text:

  • There have been links found in the system which have no text label on them, rather they have text unlinked beside them or are fully unlabelled.
  • Links require text rather than just a picture to comply with 2.4.4 Link Purpose (In Context) (Level A).
  • There is no current work around for this issue, though most of the links without text are next to a second link, with text that takes you to the same place.

Headings containing no content:

  • Headings have been found without content attached in parts of the system, this can often be due to access restrictions on data, but can be confusing for users.
  • Heading require content under them to comply with 1.3.1 Info and Relationships (Level A), 2.4.1 Bypass Blocks (Level A), 2.4.6 Headings and Labels (Level AA).
  • There is no current work around for this issue, though the headings that have been found are in areas where most users do not have access to the data in that area. If you think your role should have access to the content of a heading, please contact ILS.

Order of page is not mirrored programmatically for assistive technologies:

  • There are some places where visual order of information on the page is in an important meaningful order but not available programmatically to assistive technologies.
  • Information must be provided programmatically to comply with 1.3.1 Info and Relationships (Level A).
  • There is no current work around for this, though all the information is presented, it will just not present in the correct order.

Some areas are inaccessible or not ordered sequentially when navigating with a keyboard:

  • When using a keyboard to navigate some areas have been found to be inaccessible. Also, the keyboard will not always follow the exact page layout when navigating causing confusion.
  • Information must be provided programmatically and fully accessible by keyboard to comply with 1.3.1 Info and Relationships (Level A).
  • There is no current work around for this, though inaccessible areas have not been found in manager or employee areas, only in background areas, if you find inaccessible areas, please contact ILS. The other keyboard issues are navigational and the keyboard will eventually get to the required field.

Landing page text not appropriate for the page:

  • There are pages where the landing page welcome text is not descriptive as to where the user is within the application flow.
  • 2.4.6 Headings and Labels (Level AA).
  • There is currently no work around for this, though the flow can still be completed within the framework and as the input fields are labelled but if found this should be reported to ILS.

Labels and instructions missing:

  • There are some places where labels or instructions are not provided and some of these are when the product requires user input.
  • Labels should be used on all links and instructions should be added where input is required to comply with, 1.3.1 Info and Relationships (Level A) and 2.4.4 Link Purpose (In Context) (Level A).
  • Currently there is no work around, but help can be requested from the Horizon team in ILS if a form cannot be completed.

Some images and controls are not consistently used throughout the product:

  • There are some inconsistent labels of controls in the system e.g. Save, Submit, save and submit. Also, some symbols are inconsistently used.
  • 2.4.4 Link Purpose (In Context) (Level A).
  • If you contact ILS, we can offer you guidance on the difference between the options where they are used differently.

If you find an issue that we have yet to identify, please contact us using one of the routes described in the ‘Feedback and contact information’ section of this statement.

Disproportionate burden

Currently, we have not made any disproportionate burden claims.

Content that’s not within the scope of the accessibility regulations

PDFs and other documents

Some of our PDFs and Word documents are essential to providing our services. For example, we have PDFs with information on how users can access our services, and forms published as Word documents. We are currently working on fixing these essential documents or replacing them with accessible html web pages. We are currently removing and reviewing our documentation on the system and hope to have completed that work by the end of 2025.

Video content

Our video content is in the process of being retired due to the new look redwood skin coming in March 2025. Once this is completed a review of all supporting documentation of Horizon will take place and hopefully completed by the end of 2025.

3rd Party system

This system is provided by Oracle and we have limited access to change pages, text and layouts. Oracle provide these parts of the system in the same format to all customers, so all changes to them must go through extensive and long change procedures, which as one customer, we have no control over. As a result some known issues cannot be fixed by us.

Preparation of this accessibility statement

This statement was prepared in January 2025. This statement was last reviewed was last tested on 01/25.

The test was carried out by 3 parties the Oracle Product area of UoG and Namos our support partner. The testing included manual testing, using semi-automated tools, testing with assistive technologies.

In this section