Skip to main content

Welcome to our new website. You may still see some pages from our old site as we move things over.

Accessibility statement

This accessibility statement applies to The National Lottery Community Fund (the Fund) website at https://www.tnlcommunityfund.org.uk.

This website is run and maintained by the Fund. Whatever your needs or abilities, you can expect equal access when applying for our funding. We’re happy to give you extra support if you need it. For example, you might need information in a different way, or may need extra time when talking to us.

On our website, you should be able to:

  • change colours, contrast levels and fonts
  • zoom in up to 400% without the text spilling off the screen
  • navigate using just a keyboard
  • navigate 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 tried to make the website content easy to understand.

The AbilityNet website has advice on how to make your device easier to use if you’re disabled.

How accessible this website is

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

  • most older PDF documents are not fully accessible to screen reader software
  • some of our application forms are difficult to navigate using just a keyboard

Feedback and contact information

If you need information on this website in a different format, you can contact us. For example, we can provide information in an accessible PDF, large print, easy read, audio recording or braille.

Reporting accessibility problems with this website

We're always looking to improve the accessibility of the website. If you find any problems that are not listed on this page, or think this website is not meeting accessibility requirements, contact us.

To help us understand and solve the problem, try to include as much as you can of the information described at 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. If you’re not happy with how we respond to your complaint, you can 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 in Northern Ireland.

Contacting us by phone

We provide a text relay service for people who are D/deaf, hearing impaired or have a speech impediment. You can contact us on:

  • 18001 plus 0345 410 2030 (England)
  • 18001 plus 028 9055 1431 (Northern Ireland)
  • 18001 plus 0300 123 7110 (Scotland)
  • 18001 plus 0300 1230735 (Wales)
  • 18001 plus 0345 410 2030 (for projects that work across the UK).

BSL users can contact us using:

Technical information about this website’s accessibility

The Fund 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 Fund 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

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

Non-compliance with the accessibility regulations

  • Some audio and video content does not have captions or transcripts. If a transcript is not available when new audio or video content is published, we aim to add one as soon as possible afterwards. We're currently creating transcripts of older content. This fails WCAG 1.2.2 Captions (A), 1.2.3 Audio Descriptions and Media Alternatives (A), and 1.2.5 Audio Descriptions (AA).
  • There are decorative images on the website that are audibly announced to users with screen readers. This fails WCAG success criterion 1.1.1 non-text content (A).
  • Some links are hidden for users with screen readers on the website. This means that these users will not get the same content as other users. This can lead to users with screen readers missing some of the context of the page. This fails WCAG success criterion 4.1.2 name, role, value (A).

Third party content

Our website contains third party content and we cannot always guarantee its accessibility.

Microsoft Forms

Non-compliance with the accessibility regulations:

  • aria roles do not contain the appropriate required roles. This fails WCAG success criterion 1.3.1 Info and Relationships (A), WCAG 4.1.2 Name, Role, Value (A)
  • error messages are not read by screen readers or other assistive technologies. This fails WCAG success criterion 1.3.1 Info and Relationships (A), WCAG 3.3.3 Error Suggestion (AA), and WCAG 4.1.3 Status Messages (AA)
  • the colour of forms fields, buttons, and validation messages does not meet the minimum color contrast requirements in relation to the background. This fails WCAG success criterion 1.4.3 Contrast (Minimum) (AA)
  • the calendar icon cannot be accessed using only the keyboard. This fails WCAG success criterion 2.1.1 Keyboard (A)
  • fields do not identify what their purpose is programmatically. This fails WCAG success criterion 1.3.5 Identify Input Purpose (AA)
  • image alternative text is not present. This fails WCAG success criterion 1.1.1 Non-text Content (A)
  • assistive technology can not identify the languages used within a page. This fails WCAG success criterion  3.1.2 Language of Parts (AA)
  • the line height is less than 1.5 times the font size. This fails WCAG success criterion 1.4.12 Text Spacing (AA)
  • content is not presented in a logical, meaningful order. This fails WCAG success criterion 1.3.2 Meaningful Sequence (A)
  • the focus indicator is hard to see, making it difficult for keyboard users to track their navigation. This fails WCAG Success Criterion 2.4.7 Focus Visible (AA)
  • labels are not programmatically associated with form controls. This fails WCAG Success Criterion 1.3.1 Info and Relationships (A) and 3.3.2 Labels or Instructions (A)

Climate Action Fund - Our Shared Future Form

Non-compliance with the accessibility regulations:

  • elements missing associated ARIA label IDs. This fails WCAG success criterion 1.3.1 Info and Relationships (A), WCAG 4.1.2 Name, Role, Value (A)
  • some elements are missing ARIA roles. This fails WCAG 4.1.2 Name, Role, Value (A)
  • fields do not identify what their purpose is programmatically. This fails WCAG success criterion 1.3.5 Identify Input Purpose (AA)
  • a form labels are not correctly associated with its corresponding form control. This fails WCAG success criterion 1.1.1 Non-text Content (A), 1.3.1 Info and Relationships (A), 2.4.6 Headings and Labels (AA), 3.3.2 Labels or Instructions (A)
  • error messages are not read by screen readers or other assistive technologies. This fails WCAG success criterion 1.3.1 Info and Relationships (A), 2.4.3 Focus Order (A), 3.3.1 Error Identification (A), 3.3.3 Error Suggestion (AA), and 4.1.3 Status Messages (AA)
  • placeholder text is used where accessible <label> elements are required. This fails WCAG success criterion 1.3.1 Info and Relationships (A), 1.3.5 Identify Input Purpose (AA)
  • form sections and grouping are not always semantically markup. This fails WCAG success criterion 1.3.1 Info and Relationships (A), 1.3.2 Meaningful Sequence (AA)
  • several elements are not marked up using appropriate semantic HTML, such as paragraphs and lists. This fails WCAG success criterion 1.3.1 Info and Relationships (A)
  • the checkboxes do not meet the minimum target size requirements. This fails WCAG success criterion 2.5.8 Target Size (Minimum) (A)
  • the form lacks a clear heading structure. This fails WCAG success criterion 1.3.1 Info and Relationships (A)
  • the calendar cannot be accessed using only the keyboard. This fails WCAG success criterion 2.1.1 Keyboard (A)
  • focus indicator is not visible. This fails WCAG success criterion 2.4.7 Focus Visible (AA)
  • the line height is less than 1.5 times the font size. This fails WCAG success criterion 1.4.12 Text Spacing (AA)
  • the purpose of each link cannot be determined from the link text alone or from its context. This fails WCAG success criterion 2.4.4 Link Purpose (In Context) (A)
  • the colour of forms fields, buttons, and validation messages does not meet the minimum color contrast requirements in relation to the background. This fails WCAG success criterion 1.4.3 Contrast (Minimum) (AA)
  • assistive technology cannot identify the languages used within a page. This fails WCAG success criterion 3.1.2 Language of Parts (AA)
  • the lang attribute is incorrectly set for the Welsh form. This fails WCAG success criterion 3.1.1 Language of Page (A)
  • multiple pages have identical page titles. This fails WCAG success criterion 2.4.2 Page Titled (A)

Disproportionate burden

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

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

PDFs and other documents

Some of our PDFs and Word documents are essential to providing our services. For example, we have PDFs with information on how users can access our services, and application forms published as Word documents. Over time we’ll fix these essential documents or replace them with accessible HTML web pages.

The accessibility regulations do not require us to fix PDFs or other documents published before 23 September 2018 if they’re not essential to providing our services.

Any new PDFs or Word documents we publish will meet accessibility standards..

What we’re doing to improve accessibility

Where possible, we try to test our services with a representative range of users, including disabled people.

We also test components to ensure they work with a range of browsers, devices and assistive technologies. This includes screen magnifiers, screen readers and speech recognition tools.

Preparation of this accessibility statement

This statement was prepared on 24 September 2025.

This website was last tested on 3 September 2025 against the WCAG 2.2 AA standard. This test of a representative sample of pages was carried out by the Digital Accessibility Centre (DAC).

We also used findings from our own testing when preparing this accessibility statement.