This accessibility statement applies to all instances of EventApp and FilmApp (all accessible via app1.apply4.com and app2.apply4.com). app1.apply4.com and app2.apply4.com are run by Apply4 Technology.
We want as many people as possible to be able to use the website. For example, that means you should be able to:
We’ve also made the website text as simple as possible to understand.
We know some parts of the website are not fully accessible:
If you need information on the 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 5 days.
We’re always looking to improve the accessibility of the website. If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact firstname.lastname@example.org and leave us a note telling us how we can do better. We’ll try to get back to you within 5 days.
In the UK, 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)
Apply4 Technology is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
Our platform is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances listed below.
The content listed below is non-accessible for the following reasons.
Content on the site does not “reflow” to match the size of the screen a user is using, or how zoomed in the screen is. This means we are not compliant with WCAG 1.4.10 (Reflow).
The purpose of fields asking “common” questions (like address, username or first name) is sometimes not tagged, meaning it cannot always be programmatically determined. This means we are not compliant with WCAG 1.3.5 (Identify Input Purpose).
Some information, structure, and relationships conveyed through presentation cannot be programmatically determined. This means we are not compliant with 1.3.1 (Info and Relationships).
Some element IDs are not unique. This means we’re not compliant with 4.1.1 (Parsing).
This statement was prepared on September 18th 2020. It was last reviewed on the same date.
This website was last tested on June 2nd 2020. The tests were carried out by our Chief Technology Officer, Matt Collins, and our Product Manager, Sam Mills.
The cookies that are categorised as “Necessary” are stored on your browser as they are essential for enabling the basic functionalities of the site.
We also use third-party cookies that help us analyse how you use this website and store your preferences. These cookies will only be stored in your browser with your prior consent.
You can choose to enable or disable some or all of these cookies but disabling some of them may affect your browsing experience.