Cookies on Find a Crown Development Application

We use some essential cookies to make this service work.

We’d also like to use analytics cookies so we can understand how you use the service and make improvements.

View cookies
Skip to main content
Find a Crown Development Application

Beta This is a beta service - your feedback will help us to improve it

Accessibility statement for Find a Crown development

This accessibility statement applies to https://find-crown-development.planninginspectorate.gov.uk.

This website is run by the Planning Inspectorate. 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)

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 service is

We know some parts of this website are not fully accessible. For example:

  • The focus order on some form pages may not always be logical when using iOS devices.
  • The header logo link contains no text.
  • There are missing focus styles on pagination elements.
  • Some navigational elements are missing the navigation role.
  • Some link text is missing context.
  • Some input fields are missing labels.
  • Some grouped form elements are missing a fieldset element.
  • Some content is not ordered correctly.
  • There are some usability issues with the file upload component.

Feedback and contact information

If you find any problems not listed on this page or think we’re not meeting accessibility requirements, use our customer contact form.

If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille:

We’ll consider your request and get back to you in 10 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.

If you’re not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).

Technical information about this website’s accessibility

The Planning Inspectorate 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

The website has been tested against the Web Content Accessibility Guidelines (WCAG) 2.2 AA standard.

This website is partially compliant with the Web Content Accessibility Guidelines (WCAG) 2.2 AA standard, due to the non-compliances listed below.

Non-accessible content

Non-compliance with the accessibility regulations

  1. On some form pages, the focus order after selecting ‘continue’ may not follow a logical sequence when using assistive technologies on iOS devices. This may make it harder for users to understand their position on the page.

    This fails WCAG 2.2 Success Criterion 2.4.3 (Focus Order).

    This issue is caused by a known platform-level behaviour in iOS and is not something we can fix within this service. We will continue to monitor this issue and review any changes to iOS that may allow us to address it in the future.

  2. In the header, the ‘Planning Inspectorate’ logo Scalable Vector Graphic (SVG) contains an empty link. This can introduce confusion for keyboard and screen reader users.

    This fails WCAG 2.2 WCAG 2.4.4 Link Purpose (In Context).

    We expect to resolve this issue by 28 August 2026.

  3. Our ‘results per page’ pagination element is missing a visible focus style.

    This fails WCAG 2.2 WCAG 2.4.7 Focus Visible.

    We expect to resolve this issue by 28 August 2026.

  4. Some elements are missing a navigation role within semantic HTML:

    • Left hand navigation menu on an application
    • Footer navigation links

    This fails WCAG 2.2 WCAG 1.3.1 Info and Relationships.

    We expect to resolve this issue by 28 August 2026.

  5. The link text on the application information page is not sufficiently detailed.

    This fails WCAG 2.2 WCAG 2.4.4 Link Purpose (In Context).

    We expect to resolve this issue by 28 August 2026.

  6. The search input fields on the written representations and documents page on an application are missing a label.

    This fails WCAG 2.2 WCAG 3.3.2 Labels or Instructions.

    We expect to resolve this issue by 28 August 2026.

  7. In our written representations filters, related checkboxes are not grouped in a fieldset.

    This fails WCAG 2.2 WCAG 1.3.1 Info and Relationships.

    We expect to resolve this issue by 28 August 2026.

  8. The order of content on the have your say start page is in an order that means that it appears after the ‘Start’ button. This means that it may be missed by screenreader users.

    This fails WCAG 2.2 WCAG 1.3.2 Meaningful Sequence.

    We expect to resolve this issue by 28 August 2026.

  9. The file upload component has issues that may affect users of assistive technologies:

    • The file remove action link needs contextual information to tell users which file they are removing.
    • When a user selects a file to upload, it is possible to select the ‘Continue’ button before the upload has finished. This can cause confusion, because there is no indication that the upload is incomplete.
    • Keyboard users cannot move past the upload component until the upload has completed. This creates an inconsistent user experience and may prevent some users from progressing when expected.

    This fails:

    • WCAG 2.2 Success Criterion 4.1.2 (Name, Role, Value)
    • WCAG 2.2 Success Criterion 3.3.2 (Labels or Instructions)
    • WCAG 2.2 WCAG 2.4.4 Link Purpose (In Context)

    We expect to resolve this issue by 31 December 2026.

Preparation of this accessibility statement

This statement was prepared on 26 March 2025. It was last reviewed on 25 March 2026.

This website was last tested on 18 March 2026 against the WCAG 2.2 AA standard.

The test was carried out by our internal team. The most viewed pages were tested using automated testing tools. A further audit of the website was carried out to the WCAG 2.2 AA standard.