Accessibility statement

This website is run by Ealing Council.

We want as many people as possible to be able to use this website.

  • Plain English 
    We aim to use plain language and avoid unnecessary jargon and acronyms on this website. There are pages or documents, such as planning documents or council reports, where complex or technical language is often necessary and used. 
    We have set up tasks and transactions to be as straightforward as possible. 

  • Browsers 
    • The site has been tested in the following browsers: 
      • IE8 (basic) and above 
      • Chrome 
      • Firefox 
      • Safari 
      • Android 
      • IOS
    • The browsers that support My Account:
      • Chrome 
      • Edge
      • Firefox 
      • IE8 and above
      • Safari Chrome
      • Find out more 
  • Making your computer work for you 
    There are many ways you can change your browser, computer, keyboard and mouse settings to make the web more accessible for you. 
    The AbilityNet my computer my way guide has helpful advice on customising your computer. 
  • Changing your font size and colour 
    If you do have problems with the default colours and font sizes on the site it is possible to change these settings so all web pages are displayed in a larger typeface and clearer colour scheme. 
    Change colours and fonts 
  • Documents 
    • Adobe Acrobat - PDF documents 
      Some documents on this website are available in PDF format. You need to have Acrobat Reader installed on your computer to view these documents. The reader is free to download from the Adobe Reader download page. 
      Adobe provides advice on accessibility for those who have difficulty viewing documents in PDF format. 

How accessible this website is

We know some parts of this site are not fully accessible at the moment. For example:

  • ​you cannot skip to the main content when using a screen reader
  • most of the documents are not fully accessible to screen reader software
  • some of the images do not have alternate text
  • some link text is used for multiple destinations

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, please complete this form.

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)

Third-party applications

We use platforms and websites developed by external suppliers to provide most of our online services for residents, businesses and organisations that live or operate in Ealing. Because third-party applications are partly or wholly out of our control, they may not conform to the same levels of accessibility as this website. Third-party applications include, amongst others:

  • Bookings
  • Job search
  • My Account
  • Parking permits
  • Payments
  • Planning applications
  • Reporting

Technical information about this website's accessibility

Ealing Council is committed to making this site accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018. 

This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances. 

Non-accessible content

The content listed below is non-accessible. We will work on fixing them as soon as we can but there are thousands of pages.

Navigation and accessing information

There is no option to skip repeated content on our pages. This fails WCAG 2.1 success criterion 2.4.1 (bypass blocks).

  • We plan to add skip to content by the end of September 2020.


Some images in the news pages do not have a text alternative (alt text), so the information in them is not available to people using a screen reader. This fails WCAG 2.1 success criterion 1.1.1 (non-text content). 

  • We plan to add text alternatives for all images by the first quarter of 2021.
  • When we publish new content we will make sure our use of images meets accessibility standards. 


On some pages the same link text is used for different link destinations. This fails WCAG 2.1 success criterion 2.4.4 Link purpose (in context). 

  • We plan to resolve this issue on all pages by the first quarter of 2021. 
  • When we publish new pages we’ll make sure link text meets accessibility standards.

PDFs and other documents

Some of our PDFs and other documents do not meet accessibility standards - for example, they may not be marked up so they're accessible to a screen reader. This fails WCAG 2.1 success criterion 4.1.2 (name, role value).

  • We are currently reviewing all documents (there are thousands) to identify which can be deleted, replaced with accessible HTML pages, or made accessible. 
  • By the first quarter of 2021, we plan to have fixed at least the top 10% most viewed documents.
  • Any new documents from January 2021 we publish (when training on making documents accessible has been provided to staff) should meet accessibility standards unless we determine that they represent a disproportionate burden within the meaning of the accessibility regulations.

There may be other technical issues which are not listed here. This website is maintained through the Jadu content management system (CMS) which is currently being upgraded. We expect the upgrade to fix some of the technical issues.

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

PDFs and other documents

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


Online maps and mapping services are exempt from meeting the accessibility regulations.

What we are doing to improve accessibility

  • We are currently working on upgrading the content management system which we anticipate will fix some accessibility technical issues, after which we'll carry out another automated audit.
  • We will work on fixing issues identified in the August audit as soon as we can.
  • We will review and update existing content, in order of most viewed pages, to ensure it meets accessibility guidelines.
  • When we update our website, we will check that new content meets accessibility standards.
  • We will work to improve the accessibility of documents published on the website.
  • We plan to carry out testing in the future with assistive technology.
  • We will run audits whenever new functionality is added to the site. 

Preparation of this accessibility statement

This statement was prepared on 21 September 2020.

This website was last tested in August 2020 by Ealing Council. We used automated software Siteimprove.