Oracle Cloud accessibility statement

Using this website

The University of Derby Oracle Cloud Enterprise Resource Planning (Financials, Procurement, Projects) website is run by Oracle on behalf of the University of Derby. We want as many people as possible to be able to use the site and are committed to ensuring digital accessibility for people with disabilities. For example, that means you should be able to:

AbilityNet has advice on making your device easier to use if you have a disability. AbilityNet is a UK charity that exists to change the lives of disabled people by helping them to use digital technology at work, at home or in education.

Measures to support accessibility 

We are using the following measures to ensure accessibility of the University of Derby Online Store website:

How accessible is our website? 

We know some parts of this website aren't fully accessible:

What to do if you can't access parts of this website or have a complaint 

We’re always looking to improve the accessibility of this website.  

If you have any issues with inaccessible content or are unable to obtain an accessible version, or you feel the need to complain about our site and content accessibility, please email us at finsys@derby.ac.uk or contact us via our central feedback form. 

Submit an accessibility support request

We’ll consider your request and get back to you in two working days.  

Enforcement procedure

The Equality and Human Rights Commission (EHRC) is responsible for enforcing the accessibility regulations. If you’re not happy with how we respond to your complaint after following the process set out above, contact the Equality Advisory and Support Service (EASS).

Technical information about our website's accessibility

The University of Derby is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances listed below.

Non-accessible content

The Content listed below is non-accessible for the following reasons:

Non-compliance with the accessibility regulations

Not all required elements display an appropriate alt-text. Text alternatives are a primary way for making information accessible because they can be rendered through any sensory modality (for example, visual, auditory or tactile) to match the needs of the user. See Oracle's Voluntary Product Accessibility Templates for the full list of instances where the software doesn’t meet WCAG 2.1 success criterion 1.1.1 Non-text Content (Minimum). The supplier is working on a solution to these issues.

Not all information displayed visually is also made available programmatically or in the text so that the information is accessible non-visually. See Oracle's Voluntary Product Accessibility Templates for the full list of instances where the software doesn’t meet WCAG 2.1 success criterion 1.3.1 Info and Relationships (Minimum). The supplier is working on a solution to these issues.

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, this may hinder people who rely on assistive technologies that read content aloud. See Oracle's Voluntary Product Accessibility Templates for the full list of instances where the software doesn’t meet WCAG 2.1 success criterion 1.3.2 Meaningful Sequence (Minimum). The supplier is working on a solution to these issues.

There are some places where it is unclear what the coloured text represents. See Oracle's Voluntary Product Accessibility Templates for the full list of instances where the software doesn’t meet WCAG 2.1 success criterion 1.4.1 Use of Colour (Minimum). The supplier is working on a solution to these issues.

There are some elements that do not provide enough colour contrast between text and its background so that it may be difficult to be read by people with moderately low vision (who do not use contrast-enhancing assistive technology). See Oracle's Voluntary Product Accessibility Templates for the full list of instances where the software doesn’t meet WCAG 2.1 success criterion 1.4.3 Contrast (Minimum). The supplier is working on a solution to these issues.

There are some places where content cannot be accessed with a keyboard or keyboard interface. When interactive content is operated using a keyboard or alternate keyboard, it is accessible to visually impaired people who cannot use devices requiring eye-hand coordination (eg, a mouse or touchscreen). See Oracle's Voluntary Product Accessibility Templates for the full list of instances where the software doesn’t meet WCAG 2.1 success criterion 2.2.1 Keyboard (Minimum). The supplier is working on a solution to these issues.

There is a place where a skip-to-main-content link navigates user to the Cancel button instead of the Save button. See Oracle's Voluntary Product Accessibility Templates for the full list of instances where the software doesn’t meet WCAG 2.1 success criterion 2.4.1 Bypass Blocks (Minimum). The supplier is working on a solution to these issues.

There are some places where the landing page Welcome text is not descriptive as to where the user is within the application flow. See Oracle's Voluntary Product Accessibility Templates for the full list of instances where the software doesn’t meet WCAG 2.1 success criterion 2.4.2 Page Titled (Minimum). The supplier is working on a solution to these issues.

There are some places where users navigate sequentially through content, they encounter information not in an order that is consistent with the meaning of the content or can be operated from the keyboard. See Oracle's Voluntary Product Accessibility Templates for the full list of instances where the software doesn’t meet WCAG 2.1 success criterion 2.4.3 Focus Order (Minimum). The supplier is working on a solution to these issues.

There are some places where labels are not distinctive or descriptive enough for a screen reader to advise what the context and usage are. See Oracle's Voluntary Product Accessibility Templates for the full list of instances where the software doesn’t meet WCAG 2.1 success criterion 2.4.6 Headings and Labels (Minimum). The supplier is working on a solution to these issues.

There are some places where visual indication of the location of the focus is incorrect or missing. See Oracle's Voluntary Product Accessibility Templates for the full list of instances where the software doesn’t meet WCAG 2.1 success criterion 2.4.7 Focus Visible (Minimum). The supplier is working on a solution to these issues.

There are some places where changes in the value of user interface components results in a substantial change to the page, an additional change of keyboard focus, or the spawning of a pop-up window. See Oracle's Voluntary Product Accessibility Templates for the full list of instances where the software doesn’t meet WCAG 2.1 success criterion 3.2.2 On Input (Minimum). The supplier is working on a solution to these issues.

There are some places where labels or instructions are not provided when the product requires user input. See Oracle's Voluntary Product Accessibility Templates for the full list of instances where the software doesn’t meet WCAG 2.1 success criterion 3.3.1 Error Identification (Minimum). The supplier is working on a solution to these issues.

There are some places where images and controls are used and identified are consistent throughout the product. See Oracle's Voluntary Product Accessibility Templates for the full list of instances where the software doesn’t meet WCAG 2.1 success criterion 3.3.2 Labels or Instructions (Minimum). The supplier is working on a solution to these issues.

There are some places where suggestions for fixing an input error are known, they are not provided to the user. See Oracle's Voluntary Product Accessibility Templates for the full list of instances where the software doesn’t meet WCAG 2.1 success criterion 3.3.3 Error Suggestion (Minimum). The supplier is working on a solution to these issues.

There are some places where custom interactive user interface components do not expose proper role, state and property information needed for assistive technologies. As a result, people with disabilities have difficulty identifying and interacting with the components. See Oracle's Voluntary Product Accessibility Templates for the full list of instances where the software doesn’t meet WCAG 2.1 success criterion 4.1.2 Name, Role, Value (Minimum). The supplier is working on a solution to these issues.

Oracle's Voluntary Product Accessibility Templates

Disproportionate burden

Our Supplier is aware of the accessibility requirements and is committed to developing new products in conformance with Revised Section 508 and the WCAG 2.0 AA standards to the extent practicable. As new products and revisions are released that conform to the Revised Section 508 and WCAG 2.0 standards, they will publish Voluntary Product Accessibility Templates (VPATs) that use the updated VPAT 2.0 template. Until then, they have VPATs that include a table of all of the WCAG 2.0 'A' and 'AA' standards, in addition to the old Section 508 standards. For VPATs that contain only the old Section 508 standards, you may use information from the US Access Board and the WAI to assess the degree of conformance with WCAG 2.0 that the products may already exhibit.

In 2017 the US Access Board announced the Revised Section 508 standard that is based on the WCAG 2.0 AA standards. In 2014, the European Union standard EN 301 549 ‘Accessibility requirements suitable for public procurement of ICT products and services in Europe’ (PDF) was issued in response to Mandate 376, and it too was based on the WCAG 2.0 AA standards. Oracle has been an active participant in the development of these guidelines and is closely tracking their progress.

Any standard is subject to some amount of interpretation. See Standards Interpretation for a detailed look at how Oracle addresses specific standards.

We will ensure new accessibility requirements are requisite criteria when the system is comes up for review.

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

We are not aware of any content that falls outside the scope of the accessibility regulations.  

Additional accessibility considerations

The Web Content Accessibility Guidelines (WCAG) define three levels of conformance: level A, level AA and level AAA. Although our goal is WCAG 2.1 Level AA conformance, we have also applied some level AAA success criteria as follows:

How we tested this website

Oracle products are tested for accessibility using a variety of techniques including automated tools, expert heuristic review, visual inspection, manual operation, and testing with various AT by both disabled and non-disabled users. The outcome of that testing is reported using the Voluntary Product Accessibility Template (VPAT) to create the Accessibility Conformance Report. The VPAT was developed by ITI and GSA to assist Federal contracting officials and other buyers in making preliminary assessments regarding the availability of commercial ICT products and services with features that support accessibility.

What we’re doing to improve accessibility

We have a rolling programme of updating content in accordance with the guidelines set out by the WCAG.

This statement was prepared on 5 February 2020. It was last updated on 5 February 2020.

Website accessibility information form 

You can contact us in via our central feedback form.

Submit an accessibility support request

We first prepared this statement on 5 February 2020. We are logging every change we make to this page.

  • 11 August, 2020: statement first published