Accessibility statement

ORR is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018. 

We want as many people as possible to be able to use this website. For example, that means you should be able to:

• change colours, contrast levels and fonts using browser or device settings
• zoom in up to 400% without the text spilling off the screen
• navigate most of the website using a keyboard or speech recognition software
• listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)

AbilityNet has 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 exemptions listed below.  

Non-accessible content

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

Non-compliance with the accessibility regulations

We use Microsoft Power BI to publish interactive dashboards on our website. This feature does not meet the accessibility standards in the following ways:

• Some interactive charts and visualisations do not have appropriate alternative text descriptions. This means screen reader users may not be able to understand the purpose, content or key findings of a visual without being able to see it. This fails WCAG success criterion 1.1.1 (alt-text).
• Some interactive charts do not currently follow a logical reading and navigation order. When using a screen reader or keyboard navigation, the order in which elements receive focus may differ from the visual layout presented on screen. This means users may be taken to content in an unexpected sequence, making it more difficult to understand the relationship between visuals. This fails WCAG success criterion 1.3.2 (meaningful sequence) and 2.4.3 (focus order).
• Some charts include information icons that provide additional explanatory content. These icons cannot currently be accessed or activated using keyboard navigation. This means keyboard-only users may be unable to access information that is available to mouse users. This fails WCAG success criterion 2.1.1 (keyboard).
• Some information icons used to provide additional explanatory content are smaller than the minimum target size recommended by WCAG 2.2. This means users with limited dexterity, tremors, or those using touch devices may have difficulty selecting accurately. This fails WCAG success criterion 2.5.8 (target size (minimum)).
• When users interact with slicers, drill throughs or expand or collapse hierarchical data, charts and tables may update automatically. These changes are not always communicated to assistive technologies. This means screen reader users may not be aware that the content has changed. This fails WCAG success criterion 4.1.3 (status messages).

We plan to review these issues by March 2027.

Content that's not within the scope of the accessibility regulations

The accessibility regulations do not require us to fix PDFs or other documents published before 23 September 2018 if they are not essential to providing our services. For example, we do not plan to fix PDF publications launched before this date.

Some documents we publish are submitted to ORR by third parties and may not be compliant. We do not fund, develop or control this content. Examples include access contracts between third parties, and responses to consultations. The accessibility regulations do not require us to make such content submitted to us by third parties accessible.

Many of the third party PDF documents we publish do not meet accessibility standards. For example:  

• they may not be structured so they’re accessible to a screen reader. This does not meet WCAG 2.2 success criterion 2.4.10 (section headings)
• they may be not written in plain English

Contact us if you need any of these documents in an alternative accessible format. 

We use maps to visualise some data. The accessibility regulations do not require us to fix online maps so long as essential information is available in an accessible manner where maps are intended for navigational use.

Preparation of this accessibility statement

This statement was first prepared on 20 September 2019. It was last reviewed on 1 July 2026.

This website was last tested for accessibility in May 2026. We tested it internally applying:

• automated testing
• technical manual review

It was previously tested by The Shaw Trust in March 2024.

Feedback and contact information

We are always looking to improve the accessibility of this website. If you find any problems that are not listed on this page or think we are not meeting the requirements of the accessibility regulations, contact us with the details below.

If you cannot access parts of this website or need any information in a different format like accessible PDF, large print, easy read, audio recording or braille, please contact us via:

• email: web.team@orr.gov.uk
• telephone: 020 7282 2000 (select option 3)
  Please note: we do not provide a text relay service for people who are d/Deaf, hearing impaired or have a speech impediment. If you require this service, please talk to us in advance.
• post: 
  Public Correspondence Team 
  Office of Rail and Road 
  25 Cabot Square 
  London 
  E14 4QZ

We will consider your request and will endeavour to get back to you with the accessible format within 20 working days.

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

The Enforcement procedure is set out in Part 5 of the Accessibility Regulations.