Reward Gateway Accessibility Statement

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

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

  • No image role. Missing link alt attribute. This fails WCAG 1.1.1 Non-text Content (A).
  • Duplicate labels used. Ensure elements with an ARIA role that require parent roles are contained by them and elements with an ARIA role that require child roles contain them. ARIA attribute is not allowed. ul and ol must only directly contain li, script or template elements. The list contains empty list elements. There is no main landmark. Accordions do not notify all screen readers when they open. Accordion is only partly keyboard accessible. aria-hidden used on focusable element. aria-hidden used on parent of focusable. Elements marked as presentational. List item has no list parent. Two-dimensional table – item column in table rows not programmatically available. A data table is marked up as presentation. Missing ID. Label for has no matching id. Label does not have a for attribute. This fails WCAG 1.3.1 Info and Relationships (A).
  • Content behind “modals” not marked “inert”. This fails WCAG 1.3.2 Meaningful Sequence (A).
  • Autocomplete missing. The form field is missing a valid autocomplete="..." attribute. Autocomplete value is invalid. This fails WCAG 1.3.5 Identify Input Purpose (AA).
  • Mobile view loses links and money values for total savings etc. Text is obscured at the bottom of the Terms and Conditions. A horizontal scrollbar appears at 400%. This fails WCAG 1.4.10 Reflow (AA).
  • Focus indicator colour contrast against changing background images. Back to basket image does not have enough colour contrast. This fails WCAG 1.4.11 Non-text Contrast (AA).
  • Keyboard user cannot tab back to the navigation buttons. Accordions do not notify all screen readers when they open. Accordion is only partly keyboard accessible. aria-hidden used on focusable element. aria-hidden used on parent of focusable. Elements marked as presentational. This fails WCAG 2.1.1 Keyboard (A).
  • There is no way to pause, stop or hide the content of the carousel. This fails WCAG 2.2.2 Pause, Stop, Hide (A).
    Content behind “modals” not marked “inert”. Keyboard user cannot tab back to the navigation buttons. This fails WCAG 2.4.3 Focus Order (A).
  • Ensure links have discernible text. Missing link alt attribute. No link text. Link text is different between the Basket page and the Basket modal. This fails WCAG 2.4.4 Link Purpose (In Context) (A).
  • Content behind “modals” not marked “inert”. Focus is not visible when using the keyboard. This fails WCAG 2.4.7 Focus Visible (AA).
  • Content behind “modals” not marked “inert”. This fails WCAG 2.4.11 Focus Not Obscured (Minimum) (AA).
  • Multiple naming techniques used. Accessible text does not contain visible text. This fails WCAG 2.5.3 Label in Name (A).
  • Content behind “modals” not marked “inert”. This fails WCAG 3.2.3 Consistent Navigation (AA).
  • Link text is different between the Basket page and the Basket modal. This fails WCAG 3.2.4 Consistent Identification (AA).
  • Title on non-interactive element. This fails WCAG 3.3.2 Labels or Instructions (A).
  • There is no accessible name for the X. Ensure links have discernible text. Duplicate ID found. Non-active element in tab order. Multiple naming techniques used. ARIA attribute is not allowed. ul and ol must only directly contain li, script or template elements. ARIA attribute value is missing. There is no main landmark. No legend. Accordions do not notify all screen readers when they open. Accordion is only partly keyboard accessible. No link text. Duplicate for and ID. Label does not have a for attribute. Missing required ARIA attribute. Required ARIA attributes must be provided. This fails WCAG 4.1.2 Name, Role, Value (A).

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.