Accessibility statement for STEM Research Archive

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 https://research-archive.stem.open.ac.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.

Accessibility Features

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

  • Change colours, contrast 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 provideSensusAccess 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 (WCAG) version 2.2 AA standard, due to the non-compliances listed below.

Non-accessible Content

Ensure functionality is available to keyboard users
All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user’s movement and not just the endpoints. This fails WCAG 2.0 Success Criterion 2.1.1 Keyboard and will be resolved by 07/12/2027.

Ensure text alternatives are provided for non-text content
Some adjacent links point to the same destination but are not combined, some images have alternative text that duplicates nearby text, some linked images are missing alternative text, PDF images require alternative text, and PDF text must be mapped to Unicode so it can be interpreted by assistive technologies. This fails WCAG 2.0 Success Criterion 1.1.1 Non-text Content and will be resolved by 07/12/2027.

Ensure information, structure, and relationships are programmatically determinable
Some tables are missing header cells, some table headers do not identify whether they apply to rows or columns, some headings contain no text, some form controls are missing labels, some lists and groups of links are not marked up correctly, PDF content is not fully tagged or structured, PDF heading levels are not used in order, some PDF tables are not structured correctly, some labels reference non-existent form fields, and some ARIA roles are missing required child elements. This fails WCAG 2.0 Success Criterion 1.3.1 Info and Relationships and will be resolved by 07/12/2027.

Ensure content reflows on small screens without horizontal scrolling
Some pages require zooming and two-dimensional scrolling on small screens, making content difficult to use on mobile devices and at high magnification levels. This fails WCAG 2.1 Success Criterion 1.4.10 Reflow and will be resolved by 07/12/2027.

Ensure frames have descriptive titles
Some frames are missing titles, preventing screen reader users from understanding the purpose of the frame and navigating content efficiently. This fails WCAG 2.0 Success Criterion 2.4.1 Bypass Blocks and will be resolved by 07/12/2027.

Ensure documents have meaningful titles
Some PDF documents display the file name instead of a meaningful title, and some PDFs do not contain a document title. This fails WCAG 2.0 Success Criterion 2.4.2 Page Titled and will be resolved by 07/12/2027.

Ensure focus follows a logical reading order
Annotated PDF pages do not always provide a logical structure-based tab order, which can result in keyboard users navigating content in an order that does not preserve meaning or functionality. This fails WCAG 2.0 Success Criterion 2.4.3 Focus Order and will be resolved by 07/12/2027.

Ensure links clearly describe their purpose
Some links use identical text but point to different destinations, some links do not clearly indicate their destination or purpose, and some PDF links and annotations are not sufficiently descriptive. This fails WCAG 2.0 Success Criterion 2.4.4 Link Purpose (In Context) and will be resolved by 07/12/2027.

Ensure interactive controls meet minimum target size requirements
Some interactive controls are too small or positioned too close together, making them difficult to activate accurately for users with limited dexterity or those using touch input devices. This fails WCAG 2.2 Success Criterion 2.5.8 Target Size (Minimum) and will be resolved by 07/12/2027.

Ensure the default language is programmatically identified
Some PDF documents do not declare a document language, preventing assistive technologies from accurately applying language-specific pronunciation and reading rules. This fails WCAG 2.0 Success Criterion 3.1.1 Language of Page and will be resolved by 07/12/2027.

Ensure user interface components expose correct name, role, and value information
Some links cannot be used effectively by screen readers, and some elements have conflicting or redundant ARIA roles that prevent assistive technologies from accurately identifying their purpose, state, or value. This fails WCAG 2.0 Success Criterion 4.1.2 Name, Role, Value and will be resolved by 07/12/2027.

Preparation of this Accessibility Statement

This statement was prepared on 23 October 2026.

This statement was last reviewed on 23 October 2026.

This website was last tested on 23 October 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 including broken links, readability/content checks, usability and compliance risks).
  • 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 cannot access the information that you need, please use The Open University Accessibility Feedback Form to request support. 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 are not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS)