Accessibility statement for the Registrars' appointment system

This accessibility statement applies to the Registrars' appointment system. There’s a separate accessibility statement for the main H&F website.

This service is part of the wider H&F website and is managed by Hammersmith & Fulham Council through our third party supplier Stopford. 

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 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:

  • some form fields don't have labels meaning their purpose can't be explained to assistive technology users
  • radio options are not grouped in fieldsets with a descriptive legend to explain their purpose
  • some elements do not meet minimum colour contrast requirements
  • the date picker is not accessible for keyboard users
  • there is no way to skip repeated links and move to the main content
  • every page has the same page title
  • the links to select a time slot are not programmatically associated with the appointment times.

What to do if you're having difficulty using this service

If you have difficulty using this service email us at registeroffice@lbhf.gov.uk or call us on 020 8753 2140.

As part of providing this service, we may need to send you messages or documents.

We’ll ask you how you want us to send messages or documents to you, but contact us if you need them in a different format. For example large print, audio recording or braille.

Reporting accessibility problems with this service

We're always looking to improve the accessibility of the Registrars' appointment system.

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.

Report an accessibility issue

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

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.

The register office is wheelchair accessible through our ground floor entrance on Beavor Lane.

Find out how to contact the register office.

Technical information about this website’s accessibility

Hammersmith & Fulham is committed to making Registrars' appointment system accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

Compliance status

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

Some elements do not meet minimum colour contrast requirements. This includes the:

  • focus style of the navigation tabs
  • footer links
  • asterisks (*) in form field labels
  • error messages. 

These issues fail WCAG 2.1 success criterion 1.4.3 (contrast - minimum).

Form fields also do not meet minimum colour contrast requirements. This fails WCAG 2.1 success criterion 1.4.11 (non-text contrast).

Interactive tools and transactions

Some form fields and select boxes are missing a label meaning their purpose may not be given to assistive technology users. This fails WCAG 2.1 success criterion 1.3.1 (info and relationships) and 3.3.2 (labels or instructions). These form fields are grouped with the text that explains their purpose using table rows and some screen readers will read them out together in a meaningful way. This isn't the best approach and we are working with the supplier to provide programmatically associated labels.

Radio buttons are not grouped in a fieldset with a descriptive legend. This means assistive technology users won’t know the purpose of the radio buttons. This fails WCAG 2.1 success criterion 1.3.1 (info and relationships) and 3.3.2 (labels or instructions).

Important messages appear on screen that are not marked up in a way that assistive technology users will be aware of them. This fails WCAG 2.1 success criterion 4.1.3 (status message).

Some form fields do not include instructions on the format that data should be entered. Where instructions are provided these are not included in form labels or programmatically associated with form labels. This fails WCAG 2.1 success criterion 1.3.1 (info and relationships) and 2.4.6 (headings and labels).

On some pages, mandatory fields are only indicated by an asterisk (*) and it is not explained in text what the asterisk means. This fails WCAG 2.1 success criterion 1.1.1 (non-text content) and 3.3.2 (labels or instructions).

Autocomplete tokens are not used on any form fields. This fails WCAG 2.1 success criterion 1.3.5 (identify input purpose). Modern browsers such as Chrome will still offer users autocomplete options on appropriate fields.

The available appointment times are not programmatically associated with their booking links. This means assistive technology users will only hear the link text 'select' and not the appointment time they are visually associated with. This fails WCAG 2.1 success criterion 2.4.4 (link purpose - in context).

Language

The language of the appointment system has not been set. This fails WCAG 2.1 success criterion 3.1.1 (language of page).

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

The search field is missing a label. This fails WCAG 2.1 success criterion 1.3.1 (info and relationships) and 3.3.2 (labels or instructions).

The search button doesn’t have a name meaning its purpose won’t be presented to assistive technology users. This fails WCAG 2.1 success criterion 1.1.1 (non-text content) and 2.4.4 (link purpose - in context).

Most pages are missing a top-level H1 heading. This fails WCAG 2.1 success criterion 1.3.1 (info and relationships) and 2.4.6 (headings and labels).

Every page has the same page title ‘Registration Service – London Borough of Hammersmith & Fulham’. This fails WCAG 2.1 success criterion 2.4.2 (paged titled).

Technology

When keyboard users select a radio option this element loses focus and no other option can be selected. When they press the tab key, the focus returns to the first radio option in the first question meaning they must navigate through all the questions they've answered.

When users select an option for 'Where was the baby born?' on the birth registration form, the focus moves to the 'Continue' button skipping over the form fields that need to be answered.

These issues fail WCAG 2.1 success criterion 3.2.2 (on input).

The date picker is not keyboard accessible. This fails WCAG 2.1 success criterion 2.1.1 (keyboard). 

Text, links and tables

The heading structure on some pages does not follow a logical hierarchy. This fails WCAG 2.1 success criterion 1.3.1 (info and relationships).

Some headings are not descriptive enough and some users may be confused as to what page they are on. This fails WCAG 2.1 success criterion 2.4.6 (headings and labels).

The H&F logo in the header does not have descriptive alternative text, while the H&F logo in the footer is a link but is missing alternative text meaning the purpose of the image is not presented to assistive technologies. These issues fail WCAG 2.1 success criterion 1.1.1 (non-text content) and 2.4.4 (link purpose - in context). We plan to improve the alternative text for these images when we next update the payment portal.

The social media icons in the footer are empty links meaning their purpose is not presented to assistive technology users. This fails WCAG 2.1 success criterion 2.4.4 (link purpose - in context). The icons will have link text when we next update the payment portal.

Some text is formatted using the bold and underline tags. The bold tag has no semantic meaning and underlining text that isn’t a link can confuse users. These both fail WCAG 2.1 success criterion 1.3.1 (info and relationships).

Tables and table elements are used to present headings and group form fields with text. Tables should only be used to present data. These issues fail WCAG 2.1 success criterion 1.3.1 (info and relationships).

Website code

The desktop and mobile search fields both have the same ID. This fails WCAG 2.1 success criterion 4.1.1 (parsing). 

Disproportionate burden

Not applicable.

Content that’s not within the scope of the accessibility regulations

Not applicable.

How we tested this service

This service was last tested on 19 September 2020 by Hammersmith & Fulham Council using:

  • Accessibility insights for web
  • Browser inspection tools
  • Manual testing
  • NVDA
  • Siteimprove
  • Text spacing
  • WAVE
  • Web developer.

What we’re doing to improve accessibility

We're working with the supplier, Stopford, 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 21 September 2020. It was last reviewed on 21 September 2020.