Accessibility statement for MyProgress

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

This accessibility statement applies to the MyProgress website.

We want as many people as possible to be able to use our websites and mobile apps, and accessibility is an essential part of our mission. On our ;Accessibility hub, you'll find everything you need to answer any questions you have about accessibility, whether you're a student or a member of staff.

To adapt the content to your needs or preferences you should be able to:

  • Change colours, contrasts levels and fonts.
  • Resize text up to 200% without impact on the functionality of the website.
  • Zoom in up to 400% without loss of information or functionality.
  • Navigate the website using just a keyboard.
    • tab to ‘Skip to content’ links at the top of the page to jump over repetitive information to the main content.
    • tab through the content; the current location will be indicated by a clear visual change.
    • control the embedded media player to play audio and video materials.
  • Use a screen reader (e.g. JAWs, NVDA) to:
    • listen to the content of web pages and use any functionality on the page.
    • list the headings and subheadings in the page and then jump to their location on the page.
    • bring up a list of meaningful links on the page.
  • Use transcripts or closed captions with most audio and video materials.
  • Download learning materials in alternative formats (e.g. Word document, PDF, ePub)
  • If you have a print disability we provide SensusAccess to students, which is an students, which is an automated service that converts files from one format to another, for example, PDF to text, audio, Word or Braille.
  • AbilityNet also provides advice on making your device easier to use if you have a disability.

Compliance status

This website is partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, due to the non-compliance and exemptions listed below.

Non-accessible content

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

Non-compliance with the accessibility regulations

Incorrect order of page title components

The order in which various components of the page title are presented is incorrect. This fails WCAG 2.2 Success Criterion 2.4.2 Page Titled (Level A). This will be resolved by the end of March 2027. 

Main navigation

The main navigation should be a standalone element and not be nested within other landmarks such as a complementary landmark, which is currently the case. This fails WCAG 2.2 Success Criteria 2.4.1 Bypass Blocks (Level A). This will be resolved by the end of March 2027. 

Breadcrumb navigation

Breadcrumbs are a type of navigation landmark that helps users understand their current location within a website's hierarchy. On some pages the breadcrumb navigation landmark is placed within the main content area and appears as the first item within this area. This fails WCAG 2.2 Success Criteria 2.4.1 Bypass Blocks (Level A). This will be resolved by the end of March 2027. 

Skip to content link

The Skip to Content link is titled Skip Navigation link. This fails WCAG 2.2 Success Criteria 2.4.4 Link Purpose (In Context) (Level A). This will be resolved by the end of March 2027.  

Colour as the only means of indicating error messages

If error messages are displayed on submitting a form, colour is used as the only means of indicating error messages. This fails WCAG 2.2 Success Criteria 1.4.1 Use of Colour (Level A). This will be resolved by the end of March 2027.  

Incorrect use of autocomplete attribute in forms

Due to the manner in which the autocomplete attribute has been used, screen readers read out the autocomplete values associated with certain form controls prior to the form labels. This fails WCAG 2.2 Success Criteria 1.3.5 Identify Input Purpose (Level AA). This will be resolved by the end of March 2027. 

Modal name

Modals do not always have an accessible name, meaning it can’t always be communicated effectively using assistive technologies. This fails WCAG 2.2 Success Criteria 4.1.2 Name, Role, Value (Level A). This will be resolved by the end of March 2027. 

Missing visible labels in fields

Visible labels are crucial for all users, particularly assistive technology users, to understand the information required in a particular field. Some fields do not contain visible labels.  This fails WCAG 2.2 Success Criteria 2.4.6 Headings and Labels (Level AA). This will be resolved by the end of March 2027. 

Toggle button in list with a single item

The toggle button for the complementary menu is the only item in a list, which may confuse screen reader users who might expect additional items in this list. This fails WCAG 2.2 Success Criteria 1.3.1 Info and Relationships (Level A). This will be resolved by the end of March 2027. 

Side menu lacks status announcement

The side menu toggle button does not communicate its expanded or collapsed state to screen reader users, creating an unclear interface for those relying on audio feedback. This fails WCAG 2.2 Success Criteria 1.3.1 Info and Relationships (Level A). This will be resolved by the end of March 2027. 

Toggle side menu button

After users activate the toggle button to open the side menu, they have to navigate through unrelated elements before reaching the toggled menu. This disrupts the logical navigation flow, especially for keyboard-only and screen reader users. This fails WCAG 2.2 Success Criteria 1.3.2 Meaningful Sequence (Level A). This will be resolved by the end of March 2027. 

Menu item lacks status in collapsed mode

When the side menu is collapsed (toggle button not pressed), only menu icons are displayed, but the items do not announce their collapsed status. Screen reader and keyboard users cannot identify if these items have submenu items and can be expanded or collapsed. This fails WCAG 2.2 Success Criteria 1.4.13 Content on Hover or Focus (Level AA). This will be resolved by the end of March 2027. 

Menu items do not announce as submenus in expanded side menu

When the side menu is expanded (toggle button pressed), the menu items have an icon to indicate they have submenus and can be expanded/collapsed, but they do not announce as submenus, or announce their collapsed or expanded state to screen readers. This fails WCAG 2.2 Success Criteria 4.1.2 Name, Role, Value (Level A). This will be resolved by the end of March 2027. 

Submenu items can be tabbed when visually hidden in expanded menu

When the menu is expanded (toggle button pressed) and the menu items names are fully visible, keyboard and screen reader users can tab to the submenu item links (e.g. users, groups, organizations, providers, forms, program instances, and frameworks) even though they are visually hidden. This can confuse and disrupt the logical flow for these users.  This fails WCAG 2.2 Success Criteria 1.4.13 Content on Hover or Focus (Level AA). This will be resolved by the end of March 2027. 

Buttons lack expand/collapse indicators

The 'Change Product' and ‘Change Language’ buttons do not visually or verbally indicate their ability to expand or collapse content, which may lead users to overlook additional options available when these buttons are expanded.  This fails WCAG 2.2 Success Criteria 1.3.3 Sensory Characteristics (Level A). This will be resolved by the end of March 2027. 

Focus escapes modal dialogs

When modal dialogs are open, users can still access background content, leading to disorientation, especially for screen reader and keyboard-only users who expect focus to remain constrained within the modal. This fails WCAG 2.2 Success Criteria 2.4.7 Focus Visible (Level AA). This will be resolved by the end of March 2027. 

Focus resets to top of page after closing modal

After closing a modal, the focus resets to the top of the page rather than returning to the trigger element, disorienting users, especially those using assistive technology.  This fails WCAG 2.2 Success Criteria 2.4.7 Focus Visible (Level AA). This will be resolved by the end of March 2027. 

Colour contrast

Some text within links and buttons does not provide enough contrast with the background, making it more difficult to read. This fails WCAG 2.2 Success Criteria 1.4.3 Contrast (Minimum) (Level AA). This will be resolved by the end of March 2027. 

Text re-size

When text is resized up to 200% using browser zoom settings, important content on some pages is truncated or obscured. This fails WCAG 2.2 Success Criteria 1.4.4 Resize Text (Level AA). This will be resolved by the end of March 2027.

Input fields are unlabelled in the preview mode

When viewing forms in the preview mode, the input fields are not labelled. This fails WCAG 2.2 Success Criteria 2.4.6 Headings and Labels (Level AA). This will be resolved by the end of March 2027.  

Edit avatar button is not displayed in the tab order

The edit avatar button is not displayed in the tab order and can’t be accessed using a keyboard. This fails WCAG 2.2 Success Criteria 2.1.1 Keyboard (Level A). This will be resolved by the end of March 2027.  

ARIA attributes

Some ARIA attributes don’t contain the relevant data/IDs, meaning they are invalid. This fails WCAG 2.2 Success Criteria 4.1.2 Name, Role, Value (Level A). This will be resolved by the end of March 2027.  

Focus sequence of forms is not intuitive

Within a form submission, the submit, save and close draft and saved button are displayed prior to the main form fields which not logical and can confuse users, particularly keyboard and screen reader users. This fails WCAG 2.2 Success Criteria 2.4.3 Focus Order (Level A). This will be resolved by the end of March 2027.  

Inaccessible forms

Some forms are not accessible. There are multiple unlabelled buttons and form fields. This fails WCAG 2.2 Success Criteria 2.4.6 Headings and labels (Level AA). This will be resolved by the end of March 2027.  

Missing sitemap or site index

Given the large amount of content on the site, it can be difficult to locate and complete what is needed. There is no search functionality, site index or sitemap available to make this process easier. This fails WCAG 2.2 Success Criteria 2.4.5 Multiple Ways (Level AA). This will be resolved by the end of March 2027.  

Combo boxes and select elements are not accessible

When attempting to submit a timesheet, it is not possible to select the approver from the Approved By combo box either by using the mouse or the keyboard. This makes it impossible to submit the timesheet. This fails WCAG 2.2 Success Criteria 2.1.1 Keyboard Level A).  This will be resolved by the end of March 2027.  

Radio button labelling

Not all radio buttons are labelled. Screen readers and other assistive technologies rely on labels to convey the purpose of each option to users. This makes it impossible to submit the timesheet. This fails WCAG 2.2 Success Criteria 2.4.6 Headings and labels (Level AA). This will be resolved by the end of March 2027.  

Tabs and submenus incorrectly implemented on homepage

On the homepage, tabs and submenus are not built using correct semantic roles or interaction patterns. Keyboard-only users cannot navigate between tabs, and screen reader users are not informed of tab relationships or active states, preventing effective navigation. This fails WCAG 2.2 Success Criteria 2.4.6 Name, Role, Value (Level A). This will be resolved by the end of March 2027.  

Progress view tab order issue

Within Progress Views keyboard focus order does not follow the visual layout. Keyboard and screen reader users experience disorientation as focus jumps unpredictably. This fails WCAG 2.2 Success Criteria 2.4.3 Focus Order (Level A). This will be resolved by the end of March 2027.  

EPad expand/collapse not accessible

The expand/collapse control can’t be operated using a screen reader, preventing non-visual users from accessing hidden content. This fails WCAG 2.2 Success Criteria 2.1.1 Keyboard (Level A).  This will be resolved by the end of March 2027.  

PDF and Word documents

Some PDFs and Word documents may not provide the information required to make them easy to use with assistive technology like screen readers. You may find this information about accessing PDFs with a screen reader useful.  This will be resolved by the end of March 2027.  

The content is not within the scope of the accessibility regulations

PDFs and other documents

PDFs or other documents published before 23 September 2018.

Third party content not within OU control

Third party content that is not funded, developed by, or under the control of the OU.

Archived websites

Websites and mobile applications that only contain content that is not needed for active administration purposes and is not updated or edited after 23rd September 2019.

Preparation of this accessibility statement

This statement was prepared on 10 September 2021.

This statement was last reviewed on 30 July 2026.

The MyProgress website was tested in November 2025. 

The tests were carried out by Open University staff from the Accessibility and Usability Evaluation team. Sample pages from the MyProgress website were chosen to be representative of different types of content and layout and included the most commonly used aspects of the system. Testing was undertaken by a combination of manual and automated methods. The team will continue to assess the MyProgress website and act upon any issues of non-compliance or feedback from users in order to ensure that the Open University is constantly monitoring and improving accessibility.

Feedback and contact information

If you find that a certain section of our website is not accessible and you can’t get access to the information that you need please use the Open University Accessibility Feedback Form to request support and we will ensure that you are provided with the information you require. You will need to provide your contact details and Personal Identifier if you are a student so we can get back to you. You should expect to hear back from us within 5 working days.

The OU is very experienced in meeting accessibility needs for our students. In many cases we are able to provide module and other study support materials in alternative formats for students who indicate a need for this when completing a Disability Support Form.

In addition, some module materials are available in different formats and can be downloaded from module websites. Students can contact their Student Support Team for advice.

If you are a student, or someone who has had contact with the University before, and have a complaint about the accessibility of our websites, you should raise a complaint via the complaints and appeals process.

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 are based in the UK, and you’re not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).