Your feedback helps us to improve our website.

Translate

Accessibility statement for the births and deaths registration website

This accessibility statement applies to: https://regoffice.walsall.gov.uk/eCeremonyPlanner/BirthBookingProcess 

This website is run by Walsall Council. 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 using browser or device settings 
  • zoom in up to 400% without the text spilling off the screen 
  • navigate most of the website using a keyboard or 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: 

  • not all page functionality is available for keyboard users  
  • some custom controls do not have their roles, names, or states properly defined 
  • some form fields lack labels 
  • some error messages are not clearly identified and described 
  • some error messages were not specific enough 
  • the tabbing order is not always logical 
  • updates to content are not announced to screen reader users 
  • you cannot skip over repeated content on multiple pages 
  • the dropdown event triggers when using the keyboard 
  • colour is used solely to visual displaying content 

Feedback and contact information

Tell us if you need information on this website in a different format. In your message, include: 

  • the web address (URL) of the content 
  • your name and email address
  • the format you need (for example, BSL, large print, accessible PDF, audio recording, easy read or  braille) 

We'll consider your request and get back to you as soon as possible.

Reporting accessibility problems with this website  

We're always looking to improve the accessibility of this website. We are working on our content and will continue to make this more readable. All of our pages let you provide feedback to us and we encourage you to tell us what you think.  

If you find any problems not listed on this page or think we’re not meeting accessibility requirements, let us know via: 

  • feedback buttons on pages 
  • feedback button on a BETA banner at the top of the page to report how you find the look and feel and navigation of our pages 
  • email webproject@walsall.gov.uk
  • phone: +44 1922 650000
  • visitor address: Walsall Council, The Civic Centre, Walsall, WS1 1TP

We will respond to feedback within 5 working days.

Enforcement procedure

If you contact us with a complaint and you’re not happy with how we respond, contact the Equality Advisory and Support Service (EASS).

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

 Technical information about this website's accessibility

Walsall Council is committed to making its website 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.2 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 

Webpages

  1. Some buttons and form fields are not labelled. This fails WCAG 2.2 success criterion 1.3.1 Info and relationships. We plan to amend this by April 2025. 
  2. Some parts of the content in a not in a logical order. This arrangement renders the content order non-meaningful. This fails WCAG 2.2 success criterion 1.3.2 Meaningful sequence. We plan to amend this by April 2025..
  3. Some form field inputs do not have an auto-complete feature. This makes it harder for users to fill out the field, especially for users with cognitive impairments. This fails WCAG 2.2 success criterion 1.3.5 Identify Input Purpose. We plan to amend this by April 2025. 
  4. Some links use colour as the only visual means of conveying information. This fails WCAG 2.2 success criterion 1.4.1 (Use of colour) We plan to amend this by April 2025.
  5. Some parts of the website do not have sufficient contrast between the text and background colours. This fails WCAG 2.2 success criterion 1.4.3 Contrast (Minimum). We plan to amend this by April 2025.
  6. Some text cannot be resized without loss of content or functionality. Which means people with visual impairments may be unable to access some content This doesn’t meet WCAG 2.2 success criterion 1.4.4 Resize text. We plan to amend the this by April 2025. 
  7. Not all page functionality is available to keyboard only users, This may affect blind users or have low vision. This fails WCAG 2.2 success criterion 2.1.1 Keyboard We plan to amend this by April 2025. 
  8. There is no “Skip to Content link” present. This may affect blind users or have low vision. This fails WCAG 2.2 success criterion 2.4.1 Bypass Blocks. We plan to amend this by April 2025.
  9. Some pages do not have a unique page title. The page title should describe the topic of the page, purpose of the page or the subject of the page. This doesn’t meet WCAG 2.2 success criterion 2.4.2 Page titled. We plan to amend this by April 2025. 
  10. On some pages the tabbing order is not logical when navigating with a keyboard. This fails WCAG 2.2 success criterion 2.4.3 Focus order We plan to amend this by April 2025.
  11. Some links are written out of context. This fails WCAG 2.2 success criterion 2.4.4 Link Purpose (In Context). We plan to amend this by April 2025.
  12. Some of the targets that can be chosen are too small for the minimum target size requirements.  Some people with physical impairments cannot click small buttons that are close together. This fails WCAG 2.2 success criterion 2.5.8 Target size. We plan to amend this by April 2025.
  13. Some elements on the page keyboard focus is unclear. This would affect users with low vision and cognitive impairments. This doesn’t meet WCAG 2.2 Success criterion 2.4.7 Focus visible. We plan to amend this by April 2025.
  14. The Language of the Page is not detectable on some pages. This would make it difficult for screen reader users to access the content. This does not meet WCAG 2.2 success criterion 3.1.1 Language of the page We plan to amend this by April 2025.
  15. Some interface elements change context or activate other elements when focused, disrupting navigation for users with low vision or motor impairments. This does not meet WCAG 2.2 success criterion 3.2.1 On Focus. We plan to amend this by April 2025. 
  16. Some required form fields do not provide error messages. This fails WCAG 2.2 success criterion 3.3.1 Error identification. We plan to amend this by April 2025.
  17. Some of our forms are missing clear instructions on how to fill them out. This fails WCAG 2.2 success criterion 3.3.2 Labels or Instructions. We plan to amend this by April 2025.
  18. If an input error is automatically detected, suggestions for correction may not be presented to the user in text. This fails WCAG 2.2 success criterion 3.3.3 Error suggestion We plan to amend this by April 2025.
  19. Some form labels have incorrect labels. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role and Value). We plan to amend this by April 2025.
  20. Some status and error messages are not announced in the correct format for screen reader users. This fails WCAG 2.2 success criterion 4.1.3 Status message. We plan to amend this by April 2025.

What we’re doing to improve accessibility  

We are currently in the process of launching a new website in early 2025 

Preparation of this accessibility statement

This statement was prepared on 21 October 2024. It was last reviewed on 21 October 2024. 

This website was last tested on 25 April 2024. The test was carried out by the accessibility team in Walsall Council. The tests included: 

  • a mixture of simple manual checks and automated tests to find only the most common barriers to users with accessibility needs 
  • manual checks using each page without a mouse, viewing the page at different zoom settings, and simulating viewing the page on a small screen 

The automated tests were completed using the latest version of Axe and WAVE. 

Tests were completed using different settings in the Internet Explorer browser on Lenovo ThinkPad with a 13-inch screen 

Rate this page