Accessibility statement for the Lilla Huset website
This website is run by Hammersmith & Fulham Council through our third party supplier iSev.
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 200% 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 website text as simple as possible to understand.
AbilityNet has advice on making your device easier to use if you have a disability.
How accessible this website is
We know some parts of this website are not fully accessible:
- forms fields do not have labels
- there’s no way to skip repeated links
- the heading structure across the site is not correct
- the colour contrast between foreground and background colours is not sufficient
- some functionality such as calendars are not keyboard accessible
- links do not make sense out of context
- documents may not be usable by screen readers
- images and icons may not have alt text.
Feedback and contact information
If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille:
- email email@example.com
- call 020 8846 2580
Reporting accessibility problems with this service
We're always looking to improve the accessibility of the Lilla Huset 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.
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.
Technical information about this website’s accessibility
Hammersmith & Fulham is committed to making the Lilla Huset website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
This website is not compliant with the Web Content Accessibility Guidelines version 2.1 AA standard.
The content listed below is non-accessible for the following reasons.
Non-compliance with the accessibility regulations
There are lots of instances across the site where there is very low contrast between foreground and background colours. The contrast ratio between normal text and background colours should, at least, be 4.5:1 and 3:1 for large text. This fails WCAG 2.1 success criterion 1.4.3 (contrast - minimum)
Images, video and audio content
Images and icons are used as links to documents and other websites. However, not all of them have alt text or adequate alt text to act as the link text. For images with no alt text, screen readers will present the file name or empty links to users. This fails WCAG 2.1 success criterion 1.1.1 (non-text content) and 2.4.4 (link purpose - in context).
Interactive tools and transactions
None of the form labels or hint text on the training booking form are correctly associated with their form fields. An incorrectly associated label does not provide functionality or information about the form control to the user. This fails WCAG 2.1 success criterion 1.3.1 (info and relationships) and 3.3.2 (labels or instructions).
The are some issues with the error summary message.
For example the:
- dialog box it appears in doesn’t receive focus and isn’t marked up in a way so that it can be read out to users of assistive technology
- message can’t be dismissed using a keyboard and fades away after a few seconds.
These issues fail WCAG 2.1 success criterion 2.1.1 (keyboard), 2.2.1 (time adjustable) and 4.1.3 (status message).
Navigation and accessing information
There is no way to skip repeated links and move to the main content. This fails WCAG 2.1 success criterion 2.4.1 (bypass blocks).
PDFs and other documents
The documents we provide may not be suitable for assistive technology users. This fails WCAG 2.1 success criterion 4.1.2 (name, role, value).
Some elements cannot be accessed by keyboard alone. This includes the calendars and dropdown menus in the site navigation. This fails WCAG 2.1 success criterion 2.1.1 (keyboard).
When the site is zoomed to 200% the menu and search icons are not keyboard accessible. This fails WCAG 2.1 success criterion 1.4.4 (resize text) and 2.1.1 (keyboard).
The search box does not highlight when it receives focus. This fails WCAG 2.1 success criterion 2.4.7 (focus visible).
Text, links and tables
Some text has been formatted using incorrect styling techniques which can cause issues for some users. For example, there is underlined text which may be interpreted as being a link and cause confusions when it does not activate. These issues fail WCAG 2.1 success criterion 1.3.1 (info and relationships).
The heading structure across the website is illogical as some elements should not be tagged as a heading, heading levels are skipped and headings have no text. This fails WCAG 2.1 success criterion 1.3.1 (info and relationships).
A lot of links are not descriptive of their destination and use generic terms that don’t make sense when read out of context. This fails WCAG 2.1 success criterion 2.4.4 (link purpose - in context).
The social media links are empty and contain no text meaning their purpose might not be known by screen reader users. This fails WCAG 2.1 success criterion 2.4.4 (link purpose - in context).
Tables used on the document download pages are missing header cells. This fails WCAG 2.1 success criterion 1.3.1 (info and relationships).
Tables have also been used for layout purposes which can cause issues for screen reader users. This fails WCAG 2.1 success criterion 1.3.1 (info and relationships).
When the CSS is removed an audio player can be seen at the bottom of every page. Another audio player can also be seen on document download pages. Neither player has an audio track and should be removed. This fails WCAG 2.1 success criterion 1.3.2 (meaningful sequence).
On the COVID-19 update page, the topics and archive sections are both marked up using the aside element but neither have an accessible name. This fails WCAG 2.1 success criterion 1.3.1 (info and relationships).
We are assessing the cost of fixing the issues identified in this statement as we believe it may be a disproportionate burden on our website maintenance and support budget, within the meaning of the accessibility regulations. We will update this section of the section when the assessment has concluded.
Content that’s not within the scope of the accessibility regulations
Use headings below or say 'Not applicable'
PDFs and other documents
Older PDFs and other documents may not be suitable for users of assistive technology. This fails WCAG 2.1 success criterion 4.1.2 (name, role, value). 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.
How we tested this service
This service was last tested on 24 August 2020 by Hammersmith & Fulham Council using:
- Accessibility insights for web
- Browser inspection tools
- Manual testing
- Text spacing
- Web developer.
What we’re doing to improve accessibility
We're working with the supplier, iSev, to fix the issues in this statement and to make the website more usable for all users.
Preparation of this accessibility statement
This statement was prepared on 23 September 2020. It was last reviewed on 23 September 2020.