On this page:
- How accessible this website is
- How we tested this website
- Technical information about this website’s accessibility
- Non-accessible content
- Disproportionate burden
- Content that’s not within the scope of the accessibility regulations
- Reporting accessibility problems with this website
- What to do if you can't access parts of this website
- Enforcement procedure
We want as many people as possible to be able to use this website. For example, that means you should be able to:
- change colours and contrast levels
- zoom in up to 300% without the text spilling off the screen
- navigate most of the website using just a keyboard
- navigate most of the website using speech recognition software
- listen to most of the website 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.
We know some parts of this website aren’t fully accessible:
- you can’t modify the line height or spacing of text on our homepage, search page and navigation page
- most older PDF documents aren’t fully accessible to screen reader software
- embedded videos and live video streams don’t have captions
- there’s no option to skip to main content when using a screen reader on our website and also on some third party applications
- some of our online forms are difficult to navigate using just a keyboard, for example:
- on some third party applications the text will not reflow in a single column when you change the size of the browser window, for example:
This website was last tested on 27 August 2019. The test was carried out by Gillian Newman, in-house accessibility expert.
We used sample pages that included all the different types of functionality on the website.
We tested our main website platform: https://hackney.gov.uk.
You can read the full accessibility test report.
We are committed to making our 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-compliance with the accessibility regulations
- on some pages layout tables are being used when a data table would format the text correctly when the page is linearised or read by a screen reader. This fails WCAG 2.1 guideline 1.3.1 info and relationships. We plan to change the layout table style to a data table style by May 2020
- there may be a colour contrast problem between foreground text and background colour in sitewide, sectionwide and page announcements. This fails WCAG 2.1 guideline 1.4.3 contrast (minimum). We plan to fix this issue by May 2020
- external links open in a new tab or the same tab. This fails WCAG 2.1 guideline 3.2.4 consistent identification. We plan to ensure that all external links open in the same window by May 2020
- links to PDFs, Word documents, Google docs etc don’t indicate what type of document they are. We plan to ensure that all document links display which type of document they are by May 2020
- some images are being used as links, but they don’t have alt text. This fails WCAG 2.1 guideline 2.4.4 link purpose (in context). We plan to fix this by May 2020
- the image alternative for the Hackney logo can’t be viewed when images are turned off as the text and the background are both black. This fails WCAG 2.1 success criterion 1.1.1 non-text content. We plan to fix this by May 2020
- using a keyboard only, a user is unable to enable focus on an embedded Google map and can’t use the map controls eg zoom in / out. This fails WCAG 2.1 success criterion 1.1.1 non-text content. We plan to fix this or provide an alternative by September 2020
- embedded videos don’t have captions or an audio only version of the content. From 23 September 2020 all our new videos will have captions and we’ll also provide an audio only version
Navigation and accessing information
In some of our third party forms and applications:
- 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)
- it’s not always possible to change the device orientation from horizontal to vertical without making it more difficult to view the content. This fails WCAG 2.1 success criterion 1.3.4 (orientation)
- it’s not possible for users to change text size without some of the content overlapping. This fails WCAG 2.1 success criterion 1.4.4 (resize text)
Interactive tools and transactions
Some of our interactive forms and applications are difficult to navigate using a keyboard. For example, because some form controls are missing a ‘label’ tag.
Some of our forms and applications are built and hosted through third party software and ‘skinned’ to look like our website. This fails WCAG 2.1 success criterion 1.3.1 (information and relationships).
We’ve assessed the cost of fixing these issues and believe that doing so now would be a disproportionate burden within the meaning of the accessibility regulations. Where the issue is with a third party system or application, we will make an assessment when each supplier contract is up for renewal.
PDFs and other documents
Many of our older PDFs and Word documents don’t meet accessibility standards – for example, they may not be structured so they’re accessible to a screen reader. This does not meet WCAG 2.1 success criterion 4.1.2 (name, role value).
Some of our PDFs and Word documents are essential to providing our services. For example, we have PDFs with information on how users can access our services, and forms published as Word documents. By September 2020, we plan to either fix these or replace them with accessible HTML pages.
The accessibility regulations don’t require us to fix PDFs or other documents published before 23 September 2018 if they’re not essential to providing our services. For example, we don’t plan to fix evidence base PDFs in the planning section.
Any new PDFs or Word documents we publish will meet accessibility standards.
Live video streams don’t have captions. This fails WCAG 2.1 success criterion 1.2.4 (captions – live).
We don’t plan to add captions to live video streams because live video is exempt from meeting the accessibility regulations.
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, contact: email@example.com.
If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille contact: firstname.lastname@example.org.
We’ll consider your request and get back to you in 5 working days.
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).