Accessibility statement for the 2 year old childcare funding form
This service is part of the wider H&F website and is run by Family Support and Hammersmith & Fulham Council through our third party supplier Servelec.
We want as many people as possible to be able to use this service. For example, that means you should be able to:
- change colours, contrast levels and fonts
- zoom in up to 500% without the text spilling off the screen
- get from the start of the service to the end using just a keyboard
- get from the start of the service to the end using speech recognition software
- listen to the service using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver).
We’ve also made the text in the service as simple as possible to understand.
AbilityNet has advice on making your device easier to use if you have a disability.
How accessible is this service
We know some parts of this website are not fully accessible:
- some form labels are not descriptive enough
- the date picker is not keyboard accessible
- instructions are not given that some form fields are mandatory
- there is no way to skip repeated links
- the focus order doesn't always follow a logical sequence
- heading tags are missed or not used correctly.
What to do if you're having difficulty using this service
If you need help completing this application, please contact your local children’s centre or call Family Information Service on 0845 313 3933.
Reporting accessibility problems with this service
We're always looking to improve the accessibility of the 2 year old childcare funding form.
If you find any problems that aren't listed on this page or think we're not meeting the requirements of the accessibility regulations, please use our report form to let us know.
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).
Contacting us by phone or visiting us in person
We provide a text relay service for people who are Deaf, hearing impaired or have a speech impediment. Please call 18001 followed by 020 8748 3020.
Alternatively, you can use Relay UK service. Relay UK (previously Next Generation Text) - helps people with hearing and speech difficulties communicate with anyone over the phone, using the national relay service.
Find out how to contact your local children's centre.
Technical information about this service’s accessibility
Family Support and Hammersmith & Fulham Council are committed to making this service 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 listed below.
The content listed below is non-accessible for the following reasons.
Non-compliance with the accessibility regulations
The red used for warning text on the homepage does not have enough contrast with the background. This fails WCAG 2.1 success criterion 1.4.3 (contrast - minimum).
Interactive tools and transactions
Some form field labels are not descriptive enough of their field’s purpose. For example, on the sign-in page, we ask for the user’s username when it should be their email address. It’s also not clear what ‘Primary’ and ‘Secondary’ are when we ask for an address. This fails WCAG 2.1 success criterion 2.4.6 (headings and labels).
The date picker on the date of birth field is not keyboard accessible. This fails WCAG 2.1 success criterion 2.1.1 (keyboard).
On some pages, there is no instruction that any of the form fields are mandatory, other than a red asterisk at the end of a form label. This fails WCAG 2.1 success criterion 1.1.1 (non-text content), 3.3.2 (labels or instructions).
The gender radio buttons are presented using a layout table which is announced to screen readers. This fails WCAG 2.1 success criterion 1.3.1 (info and relationships).
The requirements for setting a password when creating an account are not displayed to users until they make an error. This fails WCAG 2.1 success criterion 3.3.2 (labels or instructions).
Navigation and accessing information
There is no skip to content link on any pages. This fails WCAG 2.1 success criterion 2.4.1 (bypass blocks).
There is a redundant aria role in the site navigation. This fails WCAG 2.1 success criterion 4.1.2 (name, role, value).
On the create account page, the focus order doesn’t always follow a logical sequence with what’s presented on screen. This fails WCAG 2.1 success criterion 2.4.3 (focus order).
Also, on the create account page, keyboard users have to tab back to enter or search for their address after selecting the Add Address button. This won’t be clear to users who also use a screen reader. This fails WCAG 2.1 success criterion 3.3.2 (labels or instructions).
Text, links and tables
There are several issues to do with headings, these are:
- missing H1 headings on some pages
- a heading tag with no text
- text marked up as headings when they are not
- text marked up using the bold and strong tags when they are headings.
These issues fail WCAG 2.1 success criterion 1.3.1 (info and relationships).
Some text has formatting styles that are not native to the website. This includes use of inline font styles, colours, sizes and the 'u' tag. These errors fail WCAG 2.1 success criterion 1.3.1 (info and relationships).
Some text is underlined and might cause users to think it is a link. This fails WCAG 2.1 success criterion 1.3.1 (info and relationships).
Content that’s not within the scope of the accessibility regulations
How we tested this service
This service was last tested on 29 August 2020 by Hammersmith and Fulham Council using:
- Accessibility insights for the web
- browser developer tools
- manual testing
- Text spacing
- Web developer.
What we’re doing to improve accessibility
We're working with the supplier, Servelec, to fix the issues in this statement and to make the system more usable for all users.
Preparation of this accessibility statement
This statement was prepared on 15 September 2020. It was last reviewed on 15 September 2020.