This accessibility statement applies to the LBHF school job website. There’s a separate accessibility statement for the main H&F website.
The LBHF school jobs website is run by Hammersmith & Fulham Council through our third-party supplier Jobs Go Public.
Using this service
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 300% 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
Some people may find parts of this service difficult to use:
- links in blocks of text may be hard to see as the colour contrast with text is low
- you cannot skip to the main content using a keyboard
- some link text is generic and doesn't describe where the link goes
- the heading structure won't appear logical to screen readers
- some form fields will missed when using assistive technology as labels are missing
Feedback and contact information
If you have difficulty using this service, please get in touch by emailing us at webmaster@lbhf.gov.uk
Reporting accessibility problems with this service
We're always looking to improve the accessibility of the H&F careers website.
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.
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).
Non-accessible content
The content listed below is non-accessible for the following reasons.
Technical information about this service’s accessibility
Hammersmith & Fulham Council is committed to making this website 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.
Non-accessible content
The content listed below is non-accessible for the following reasons.
Non-compliance with the accessibility regulations
Colour contrast
Links in blocks of text are only identifiable by colour and don’t meet the minimum colour contrast ratio needed between links and surrounding text. This fails WCAG 2.1 success criterion 1.4.1 (use of colour).
The contrast ratio between text and the overlay on images is very low. This fails WCAG 2.1 success criterion 1.4.3 (contrast - minimum). We also fail on this success criterion with the colour of the carousel buttons and the background colour on the supporting staff page.
Interactive tools
Where we ask for users for their details, for example, so they can log in or register for an account, these forms are difficult to navigate using assistive technology because some form controls are missing a ‘label’ tag. This fails WCAG 2.1 success criterion 1.3.1 (information and relationships).
Navigation and accessing information
There’s no way to skip the repeated content in the page header, for example, a ‘skip to main content’ option. This fails WCAG 2.1 success criterion 2.4.1 (bypass blocks).
Elements such as links and buttons don't become highlighted with a focus ring when using a keyboard to navigate a page. This fails WCAG 2.1 success criterion 2.4.7 (focus visible).
Some link text is too generic, such as 'read more', meaning the purpose of the link cannot be identified by some users. This fails WCAG 2.1 success criterion 2.4.4 (link purpose - in context). We also fail on this success criterion as some jobs advertised will have the same job title, such as 'teaching assistant'. This means the same link text will be used to access multiple different adverts.
The links to the terms and conditions and privacy policy open in a pop-up window and are difficult to navigate and exit from when using a keyboard only. This fails success criterion 2.1.2 (no keyboard trap).
The navigation and icon links in the listing part of the website are missing link text. This fails success criterion 2.4.4 (link purpose).
Headings tags have been used incorrectly, for example, some pages have more than one H1, and some heading text has been duplicated. This means our pages have an illogical heading structure when viewed using a screen reader and other assistive technology. This does not meet WCAG 2.1 success criterion 1.3.1 (information and relationships).
Documents
Documents published with job adverts have been supplied by the recruiting schools and will not be edited by us to make them accessible. We will work with our schools to improve the accessibility of their documents, but in the meantime, applicants can contact the school directly for the information in a different format.
Content that’s not within the scope of the accessibility regulations
We use a map to show all the schools in Hammersmith & Fulham. Although the map isn't intended for navigational use, it does contain the location and website addresses for the schools which won't be accessible to some users. We will link to this information on the main H&F website or present it on the same page as the map, the 'our schools' page.
How we tested this website
This website was last tested on 19 September 2019 by the Hammersmith & Fulham web team using Siteimprove, Wave and NVDA.
What we’re doing to improve accessibility
We're working with the supplier, Jobs Go Public, to fix the issues in this statement and to make the system more usable for all users.
This statement was prepared on 23 September 2019. It was last updated on 9 April 2021.