accessibility

This accessibility statement applies to the Our Greenwich website and the Our Greenwich Success Measures Dashboard.

This website is run by the Royal Borough of Greenwich. 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, contrast levels and fonts
• 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.

How accessible this website is

We know some parts of this website are not fully accessible:

For the Our Greenwich website:

• you cannot modify the line height or spacing of text
• the Our Greenwich PDF document is not fully accessible to screen reader software. There is an Easy Read version available, which is accessible.

For the Our Greenwich Success Measures Dashboard:

• Some text elements have insufficient color contrast, which can make it difficult for users with visual impairments to read the content (WCAG 2.2 success criterion 1.4.3).
• Some buttons and other interactive elements do not receive focus when navigating using a keyboard, which hinders users who rely on keyboard navigation (WCAG 2.2 success criterion 2.1.1).
• Some links do not have descriptive text, which can make it difficult for screen reader users to understand the purpose of the link (WCAG 2.2 success criterion 2.4.4).
• Some page elements, such as the global navigation links, don't have the correct label attached to them and are therefore not determined correctly by assistive technology (WCAG 2.2 success criteria 1.3.1, 2.5.3, 3.3.2).
• Some images do not have alternative text, making it inaccessible for screen readers to convey the image's information to users (WCAG 2.2 success criterion 1.1.1).
• Some pages have headings that are not structured correctly, which can affect navigation for users using screen readers (WCAG 2.2 success criterion 1.3.1).
• All the pages are missing a descriptive page title that adequately describes the content, making navigation difficult for users (WCAG 2.2 success criterion 2.4.2).
• Some of the pages are missing a H1 header tag, which can affect the hierarchical structure and accessibility for screen readers (WCAG 2.2 success criterion 1.3.1).
• Some of the interactive elements don't have hover or active states, making it difficult for the user to know how they are interacting with them (WCAG 2.2 success criterion 2.5.1).
• The dashboard is not responsive to different screen widths, so it doesn't adapt to accommodate different screen orientations, such as landscape mode (WCAG 2.2 success criterion 1.3.4).
• There is no 'Contact Us' link on the dashboard, which may hinder users from easily reaching out for support (WCAG 2.2 success criterion 3.2.6).
• When zoomed in, some content does not reflow properly, causing issues for users who need to increase text size (WCAG 2.2 success criterion 1.4.10).
• On some pages, it is difficult to determine which element is in focus when navigating using a keyboard, which can cause problems for users who rely on keyboard navigation (WCAG 2.2 success criterion 2.4.7).
• Some dynamic content updates, such as filters and navigation links, are not announced to screen readers, which can cause confusion for users relying on assistive technology (WCAG 2.2 success criterion 4.1.3).
• Across all pages, the focus order is illogical, which can create navigation difficulties for keyboard and screen reader users (WCAG 2.2 success criterion 4.1.3).
• Across all pages, the 'Skip to main content' link doesn't direct you to the main content but sends you to the 'Return to Our Greenwich site' link instead (WCAG 2.2 success criterion 2.4.1).

Feedback and contact information

If you need information on this website in a different format, contact us. You can call, email, use our sign language video service or a text to speech service.

Contact us or visit us in person

We provide additional access options for people who are D/deaf, hearing impaired or have a speech impediment.

You can contact the Royal Borough of Greenwich using SignVideo, a free interpreting service. This is available from home, as well as in The Woolwich Centre or The Eltham Centre.

British Sign Language (BSL) interpreters are also available at The Woolwich Centre. Please contact us before your visit if you require BSL interpretation.

Reporting accessibility problems with this website

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 us about accessibility.

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).

Technical information about this website’s accessibility

The Royal Borough of Greenwich is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

This accessibility statement applies to the Our Greenwich website and the Our Greenwich Success Measures Dashboard.

Compliance status

This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances and exemptions listed below.

Non-accessible content

Issues found with the Our Greenwich website:

PDFs and other documents

There are a number of non-accessible elements within the Our Greenwich plan PDF. Our aim is to fix these as soon as possible.

The PDF of the main Our Greenwich plan provided is not accessible for the following reasons:

There is not a unique and descriptive title to each page of the PDF. This fails WCAG 2.1 success criterion 2.4.2 (page titles).

The PDF does not have bookmarks that parallel the document structure. This fails WCAG 2.1 success criterion 2.4.1 (bypass blocks).

The PDF contains some colours that may not be accessible for people who are colour blind. This fails WCAG 2.1 success criterions 1.4.1 (use of color) and 1.4.3 (Contrast).

Some of the annotations are not marked as artifacts. This fails WCAG 2.1 success criterion 1.3.1 (Info and relationships).

The images in the document do not have alternative text and are not marked as artifacts. This fails WCAG 2.1 success criterion 1.1(Non-text content).

Some tables do not have headers. This fails WCAG 2.1 success criterion 1.3.1 (Info and relationships).

Some headings are not nested properly. This fails WCAG 2.1 success criterion 2.4.6 (Headings and labels).

Some of the content is not presented in sequence and could affect its meaning. This fails WCAG 2.1 success criterion 1.3.2 (meaningful sequence).

Issues found with the Our Greenwich Success Measures Dashboard:

Some text elements have insufficient color contrast
Some text elements on this website have insufficient color contrast, making it difficult for users with visual impairments to read the content. This fails WCAG 2.2 success criterion 1.4.3 (Contrast (Minimum)).

Some buttons and interactive elements do not receive focus when navigating via keyboard
Some buttons and other interactive elements do not receive focus when navigating using a keyboard, hindering users who rely on keyboard navigation. This fails WCAG 2.2 success criterion 2.1.1 (Keyboard).

Some links do not have descriptive text
Some links on the website lack descriptive text, making it difficult for screen reader users to understand the purpose of the links. This fails WCAG 2.2 success criterion 2.4.4 (Link Purpose (In Context)).

Some page elements are incorrectly labeled
Certain page elements, such as global navigation links, are missing correct labels, making it difficult for assistive technologies to interpret them accurately. This fails WCAG 2.2 success criteria 1.3.1 (Info and Relationships), 2.5.3 (Label in Name), and 3.3.2 (Labels or Instructions).

Some images do not have alternative text
Some images on this website do not have alternative text, preventing screen reader users from accessing the information conveyed by the images. This fails WCAG 2.2 success criterion 1.1.1 (Non-text Content).

Some pages have incorrect heading structures
Some pages have headings that are not structured correctly, affecting navigation for users using screen readers. This fails WCAG 2.2 success criterion 1.3.1 (Info and Relationships).

Some pages are missing descriptive page titles
Certain pages lack a descriptive title that adequately describes the content, making navigation difficult for users. This fails WCAG 2.2 success criterion 2.4.2 (Page Titles).

Some pages are missing H1 header tags
Some of the pages are missing a H1 header tag, affecting the hierarchical structure and accessibility for screen readers. This fails WCAG 2.2 success criterion 1.3.1 (Info and Relationships).

Some interactive elements lack hover and active states
Some interactive elements do not display hover or active states, making it difficult for users to know how they are interacting with them. This fails WCAG 2.2 success criterion 2.5.1 (Pointer Gestures).

The dashboard is not responsive to different screen orientations
The dashboard does not adapt to different screen orientations, such as landscape mode, which may limit accessibility for users on various devices. This fails WCAG 2.2 success criterion 1.3.4 (Orientation).

There is no 'Contact Us' link on the dashboard
The dashboard lacks a 'Contact Us' link, which may prevent users from easily seeking support. This fails WCAG 2.2 success criterion 3.2.6 (Consistency).

Some content does not reflow properly when zoomed in
When zoomed in, some content does not reflow properly, which can make it difficult for users who need to increase text size to read the content. This fails WCAG 2.2 success criterion 1.4.10 (Reflow).

It is difficult to determine which element is in focus when using a keyboard
On some pages, it is difficult to determine which element is in focus when navigating via keyboard, making it challenging for users who rely on keyboard navigation. This fails WCAG 2.2 success criterion 2.4.7 (Focus Visible).

Some dynamic content updates are not announced to screen readers
Some dynamic content updates, such as when filtering options are selected, are not announced to screen readers, potentially causing confusion for users relying on assistive technology. This fails WCAG 2.2 success criteria 3.3.1 (Error Identification) and 4.1.3 (Status Messages).

The focus order is illogical on some pages
The focus order on some pages is illogical, which can make it difficult for users navigating with a keyboard or screen reader. This fails WCAG 2.2 success criterion 4.1.3 (Status Messages).

The 'Skip to main content' link does not work properly
The 'Skip to main content' link does not direct users to the main content but instead sends them to an incorrect location. This fails WCAG 2.2 success criterion 2.4.1 (Bypass Blocks).

What we're doing to improve accessibility

Regarding improvements to the Our Greenwich website:
We are currently working on a new website which will have all the content from the plan onsite in an accessible format, as well as an html version of the plan.

Regarding improvements to the Our Greenwich Success Measures Dashboard:
We plan to review the accessibility issues on the Our Greenwich Success Measures Dashboard by 30/06/2025.

Preparation of this accessibility statement

The Our Greenwich website was last tested on 03/05/2023. The test was carried out by the Royal Borough of Greenwich using WAVE by WebAIM, in conjunction with manual accessibility testing. We used this approach to test the whole site.

The Our Greenwich Success Measures Dashboard was last tested on 14/08/2024