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 Leda Project website (https://ledaproject.org.uk/)
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 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-compliances and listed below.
Non-accessible content
Tag all PDFS:
PDF documents must be tagged to ensure accessibility and compliance with digital standards. This fails WCAG 2.2 Success Criterion 1.3.1: Info and Relationships (Level A) and will be resolved by the end of October 2026
Avoid linking to anchors that do not exist:
Do not link to an anchor on the page that does not exist. For example: linking to #content without a valid destination such as <body id="content"></body>. This fails WCAG 2.2 Success Criterion 2.4.1: Bypass Blocks(Level A) and will be resolved by the end of October 2026
Avoid using the same link text for different destinations:
Screen reader users will see links on a page listed without context, so you should ensure the same link text is not used to point to different web addresses. This fails WCAG 2.2 Success Criterion 2.4.4: Link Purpose (In Context) (Level A) and will be resolved by the end of October 2026
Ensure PDFs specify a default language:
Ensure that PDF documents specify a default language, so that assistive technologies can accurately interpret their contents. This fails WCAG 2.2 Success Criterion 3.1.1: Language of Page (Level A) and will be resolved by the end of October 2026
Specify headings for every PDF:
Ensure that PDF documents specifies headings for accessibility. This fails WCAG 2.2 Success Criterion 1.3.1: Info and Relationships (Level A) and will be resolved by the end of October 2026
Ensure headings include text:
Heading elements (<h1>, <h2>, …) must contain some machine-readable text content. This fails WCAG 2.2 Success Criterion 1.3.1: Info and Relationships (Level A) and will be resolved by the end of October 2026
Ensure lists are marked up correctly:
Lists (e.g., <ul> or <ol>) should only contain list items (<li>) as a direct descendant to ensure that screen readers can accurately report the amount of items contained in the list. This fails WCAG 2.2 Success Criterion 4.1.1: Parsing (Obsolete and Removed) (Level A) and will be resolved by the end of October 2026
Ensure controls change appearance when they are selected:
All controls on the page – including links, buttons, and fields – should show when they have been selected by the keyboard. This fails WCAG 2.2 Success Criterion 2.4.7: Focus Visible (Level AA) and will be resolved by the end of October 2026
Ensure interactive components are far enough apart:
All interactive components on a page, such as buttons or menus, should be far enough apart from other interactive areas, to avoid them being used by mistake. This fails WCAG 2.2 Success Criterion 2.5.8: Target Size (Minimum) (Level AA) and will be resolved by the end of October 2026
Identify the purpose of fields programmatically:
To comply with WCAG 2.1, fields must identify what their purpose is programmatically. If done correctly, this allows browsers to help users fill in forms with known information, such as their name and email address. This fails WCAG 2.2 Success Criterion 1.3.5: Identify Input Purpose (Level AA) and will be resolved by the end of October 2026
Ensure form controls contrast sufficiently with their surroundings:
To comply with WCAG 2.1, Form controls must appear sufficiently distinct from their surroundings, so that people with visual impairments are still able to clearly see them.This fails WCAG 2.2 Success Criterion 1.4.11: Non-text contrast (Level AA) and will be resolved by the end of October 2026
Preparation of this accessibility statement
This statement was prepared on 11 February 2026
This statement was last reviewed on 11 February 2026
This website was last tested on 11 February 2026
The testing approach taken involved:
- W3C (World Wide Web Consortium) checks (alternative text, content structure, language of page, keyboard navigation, skip links)
- Silktide (a continuous site-wide monitoring tool that regularly scans/crawls pages to surface accessibility and quality issues e.g., broken links, readability/content checks, usability and compliance risks, so they can be tracked and remediated over time).
- Manual checks (content resizing, captions)
This included the following test methods:
- WAVE, Web Accessibility Evaluation Tool
- Keyboard-only testing
- Zoom testing.
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)
