Skip to main content

This is a new service. Help us improve it and give your feedback (opens in new tab).

Accessibility Statement for Submit a General Aviation Report (GAR)

This accessibility statement applies to the service at Submit a General Aviation Report (GAR).

This website is run by the Home Office. We want as many people as possible to be able to use this website. For example, that means you should be able to:

  • Zoom in up to 200% without the text spilling off the screen
  • Navigate most of the website using just a keyboard
  • Navigate most of the website using speech recognition software
  • Listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)

We've also made the website text as simple as possible to understand. AbilityNet has advice on making your device easier to use if you have a disability.

How accessible this website is

We know some parts of this website are not fully accessible. You can see a full list of any issues we currently know about in the Non-accessible content section of this statement.

Feedback and contact information

If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille, please contact us via GARSupport@Homeoffice.gov.uk

Reporting accessibility problems with this website

We're always looking to improve the accessibility of this website. If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact: GARSupport@Homeoffice.gov.uk

Read tips on contacting organisations about inaccessible websites.

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

If you're in Northern Ireland and are not happy with how we respond to your complaint you can contact the Equalities Commission for Northern Ireland who are responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications)(No. 2) Accessibility Regulations 2018.

Technical information about this website's accessibility

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

Compliance status

This website is partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard. The non-compliances are listed below.

Non-accessible content

The content listed in the non-compliance with the accessibility regulations section provides details of non-accessible content on this website.

Non-compliance with the accessibility regulations

  1. On the customs details screen, the text areas have placeholder text within them which clears when the user starts inputting information, they also have unclear labels. This means the user must remember the placeholder text when inputting information and assistive technologies may not read this out and instructions will not be associated with the text area. This fails WCAG 2.2 success criterion 3.3.2 (Labels or instructions) and 1.3.1 (Info and relationships).
  2. All tables are structured incorrectly, so assistive technology users might become confused as information in tables is not structured in a logical manner. This fails WCAG 2.2 success criterion 1.3.1 (Info and relationships).
  3. On the manifest details and GAR summary screens, the travel document details are not navigable using assistive technologies. This means that some assistive technology users will not be able to navigate to the travel document details for people on the manifest. This fails WCAG 2.2 success criterion 4.1.2 (Name, role, value) and 4.1.3 (Status messages).
  4. There are several accessibility issues with all search inputs including placeholder text that clears on user input and missing labels for field inputs. This means people that rely on assistive technologies will not be told what the field is for, and placeholder text may not be read out. This fails WCAG 2.2 success criterion 3.3.2 (Labels or instructions) and 1.3.1d (Info and relationships - Form fields).
  5. In the organisation section, there is a button to search for organisation users which only has an icon and no accessible name. This means people who rely on assistive technology may not understand what the button is for. This fails WCAG 2.2 success criterion 4.1.2 (Name, role, value) and 2.4.6 (Headings and labels).
  6. On the organisation page, the table search functionality is inconsistent with table search functionality used across the service. This means that a user may have difficulty using this functionality and needs to learn a new way of carrying out their search for this page. This fails WCAG 2.2 success criterion 3.2.4 (Consistent identification).

Disproportionate burden

At this time, we have not made any disproportionate burden claims.

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

At this time, we have not identified any content that's not within the scope of the accessibility regulations.

What we're doing to improve accessibility

We are working to fix content which fails to meet the Web Content Accessibility Guidelines version 2.2 AA standard.

Our plan below describes how and when we plan to improve the accessibility of this service:

  • We will train our staff to create accessible services.
  • We will implement automated and manual accessibility testing in our development process.
  • We will conduct user research and testing with users who have access needs.
  • We will put in place alternative arrangements for those who need them and be willing to make additional adjustments if these are not enough.

Preparation of this accessibility statement

This statement was prepared on 7 December 2023. It was last reviewed and updated on 6 October 2026.

This website was last tested on 12 June 2026. The test was carried out by the internal Quality Assurance team.