Accessibility
We want as many people as possible to be able to use the NIHR Maternity Disparities Consortium website.
Statement prepared: 18 September 2026
Our commitment
The NIHR Maternity Disparities Consortium is committed to making this website accessible. We are working towards the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA.
Using this website
Our aim is that users can zoom content, navigate using a keyboard, use a screen reader, understand page structure and access information without relying only on colour. We also aim to use clear language, descriptive links and meaningful alternative text for informative images.
Compliance status
This website is currently in development and has not yet completed a full accessibility audit. We therefore do not claim full compliance with WCAG 2.2 AA at this stage.
Known limitations
Some editor-supplied or legacy images, documents and third-party content may not yet meet every accessibility requirement. Third-party embeds may also have controls or labels that we cannot directly change. We are reviewing new components and content as the website is developed.
Requesting an accessible format
If you need information from this website in another format, such as accessible PDF, large print, easy read, audio recording or braille, email nihr-mdc@contacts.bham.ac.uk. Tell us the page or document you need and the format that would work for you.
Reporting an accessibility problem
If you find an accessibility problem or think we are not meeting accessibility requirements, email nihr-mdc@contacts.bham.ac.uk. We will review the issue and respond as soon as reasonably possible.
Enforcement
If you are not satisfied with our response, the Equality Advisory Support Service can advise on equality and human rights issues in England, Scotland and Wales. In Northern Ireland, contact the Equality Commission for Northern Ireland.
How we tested this website
This statement is based on an internal review during development. A broader accessibility assessment should be completed before the production launch, and this statement should then be updated with the test method, scope, findings and planned fixes.