Reward Gateway Accessibility Statement

This accessibility statement applies to the University of Westminster Reward Gateway Guide CX.

This website is run by The University of Westminster. We want as many people as possible to be able to use this website.

We’ve also made the website text as simple as possible to understand.

My Computer My Way has advice on making your device easier to use if you have a disability and the AT Hive can help you find assistive technologies that work for you.

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 need information on this website in a different format such as accessible PDF, large print, easy read, audio recording or braille, or if you find any problems not listed on this page or think we’re not meeting accessibility requirements, email for information on how to report an accessibility problem and request alternative formats.

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 Westminster 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 non-compliances listed below.

Non-accessible content

The content listed below is non-accessible for the following reasons.

Non-compliance with the accessibility regulations

  • This fails WCAG 1.1.1 Non-text Content (A).
  • Disclosure widget does not notify all screen readers when they open or close. Ensure every form element has a label. Placeholder used for label and the label does not have a for attribute. Elements must only use permitted ARIA attributes. Multiple form labels used. aria-hidden used on parent of focusable element. Ensure elements are accessible by keyboard. Table headers are missing associated cells. No headings on page. List is not structured correctly and elements are not used semantically. This fails WCAG 1.3.1 Info and Relationships (A).
  • Links do not have required colour contrast. Underlined used. This fails WCAG 1.3.3 Sensory Characteristics (A).
  • The form field is missing a valid autocomplete="..." attribute. This fails WCAG 1.3.5 Identify Input Purpose (AA).
  • Links do not have required colour contrast. This fails WCAG 1.4.1 Use of Colour (A).
  • Elements must meet minimum colour contrast ratio thresholds. Links do not have required colour contrast. This fails WCAG 1.4.3 Contrast (Minimum) (AA).
  • Exclamation mark fails colour contrast. Focus indicator colour contrast. This fails WCAG 1.4.11 Non-text Contrast (AA).
  • Information is lost when the text space is customised. This fails WCAG 1.4.12 Text Spacing (AA).
  • Skip to main content link missing. aria-hidden used on parent of focusable element. Ensure elements are accessible by keyboard. This fails WCAG 2.1.1 Keyboard (A).
  • Multiple main landmarks. No nav landmarks. Skip to main content link missing. This fails WCAG 2.4.1 Bypass Blocks (A).
  • Page titles are not unique. This fails WCAG 2.4.2 Page Titled (A).
  • Ensure links have discernible text. No link text. Interactive controls must not be nested. This fails WCAG 2.4.4 Link Purpose (In Context) (A).
  • There is no sitemap or search. This fails WCAG 2.4.5 Multiple Ways (AA).
  • No headings on page. This fails WCAG 2.4.6 Headings and Labels (AA).
  • Focus is not visible when using the keyboard. This fails WCAG 2.4.7 Focus Visible (AA).
  • Language of page needs to be set. This fails WCAG 3.1.1 Language of Page (A).
  • Placeholder used for label and the label does not have a for attribute. title on a non-interactive element. This fails WCAG 3.3.2 Labels or Instructions (A).
  • ARIA input fields must have an accessible name. Disclosure widget does not notify all screen readers when they open or close. Ensure every form element has a label. Invalid aria-describedby and missing ID. No legend. Ensure links have discernible text. Elements must only use permitted ARIA attributes. Ensure buttons have discernible text. There is no label for button element. Active SVG missing aria-label. No link text. Multiple form labels used. Interactive controls must not be nested. Ensure elements are accessible by keyboard. This fails WCAG 4.1.2 Name, Role, Value (A).
  • Notify user that the password is visible or hidden when the button is activated. User is not made aware of new content. This fails WCAG 4.1.3 Status Messages (AA).

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

At this time, we have not made any disproportionate burden claims.

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

At this time, we have not identified any content that is not within scope of the accessibility regulations.

Preparation of this accessibility statement

This statement was prepared on 18 March 2026. It was last reviewed on 18 March 2026.

Testing was last carried out on 13 January 2026 against the WCAG 2.2 AA standard. The test was carried out internally by the University of Westminster Digital Accessibility Team, using a combination of manual techniques, automated and semi-automated tools and testing with a range of devices, browsers, operating systems and assistive technologies.