Error message
One or dates reference a missing recurring rule: 2Accessibility statement for the births and deaths registration website
This accessibility statement applies to: Walsall Registrars | Registrars
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:
- some form fields lack labels
- some custom controls do not have their names properly defined
- updates to content are not announced to screen reader users
- some form error messages are not properly associated with their corresponding field inputs
- some buttons are too small to select
- focus does not always remain on the activated item
- some forms do not have sufficient labels or instructions
- some content is not presented in a meaningful sequence
- some content does not have sufficient colour contrast
- 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:
- 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
- Some error icons do not have appropriate text alternatives. This may impact people who are blind or have low vision and use screen readers. This issue fails WCAG 2.2 AA Success Criterion 1.1.1 (Non-text Content). We plan to address this by July 2027.
- Some dropdown fields use a programmatic name that differs from the question presented for the field. This may impact people who are blind and use screen readers or refreshable braille displays. This issue fails WCAG 2.2 AA Success Criterion 1.3.1 (Info and Relationships). We plan to address this by July 2027.
- Some headings do not reflect the visual and logical structure of the page, and some visually presented headings are not marked up as headings. This may impact people who are blind and use screen readers or refreshable braille displays. This issue fails WCAG 2.2 AA Success Criterion 1.3.1 (Info and Relationships). We plan to address this by July 2027.
- The skip-to-content link does not work, preventing users from bypassing repeated navigation and moving directly to the main content. This may impact people who use screen readers or navigate using a keyboard. This issue fails WCAG 2.2 AA Success Criterion 2.4.1 (Bypass Blocks). We plan to address this by July 2027.
- Some page titles do not clearly describe the content or purpose of the page. This may impact people who are blind or have low vision, particularly when navigating between pages or browser tabs. This issue fails WCAG 2.2 AA Success Criterion 2.4.2 (Page Titled). We plan to address this by July 2027.
- Keyboard focus does not move into the search panel when it opens, and instead continues through the underlying page. This may impact people who navigate using a keyboard, including people who use screen readers and people with motor disabilities. This issue fails WCAG 2.2 AA Success Criterion 2.4.3 (Focus Order). We plan to address this by July 2027.
- Some dropdown and date field labels do not clearly describe the information users need to enter or select. This may impact people who use screen readers and people with cognitive or learning disabilities. This issue fails WCAG 2.2 AA Success Criterion 2.4.6 (Headings and Labels). We plan to address this by July 2027.
- Some functional images used as links do not have a visible keyboard focus indicator. This may impact people who navigate using a keyboard, including people with low vision. This issue fails WCAG 2.2 AA Success Criterion 2.4.7 (Focus Visible). We plan to address this by July 2027.
- Some controls have accessible names that differ from their visible labels control. This may impact people who use speech recognition software to activate controls by their visible labels. This issue fails WCAG 2.2 AA Success Criterion 2.5.3 (Label in name). We plan to address this by July 2027.
- Some form interactions cause unexpected changes without clearly informing users in advance. This may impact people with visual, cognitive or motor disabilities who need predictable form behaviour. This issue fails WCAG 2.2 Success Criterion 3.2.2 (On Input). We plan to address this by July 2027.
- Some inline error messages displayed when users leave a field or submit a form are not reliably brought to the attention of screen reader users. This may impact people who are blind or have low vision and use screen readers. This issue fails WCAG 2.2 AA Success Criterion 3.3.1 (Error identification). We plan to address this by July 2027.
- The required-field asterisk in the form instructions is presented differently from the asterisks beside required fields. This may impact people with cognitive or learning disabilities and people with low vision. This issue fails WCAG 2.2 AA Success Criterion 3.2.4 (Consistent Identification). We plan to address this by July 2027.
- Error messages are presented using different visual styles within the form, which may make them harder to recognise consistently. This may impact people with cognitive or learning disabilities and people with low vision. This issue fails WCAG 2.2 AA Success Criterion 3.2.4 (Consistent Identification). We plan to address this by July 2027.
- Some loading indicators do not provide meaningful status text explaining that content is being loaded. This may impact people who use screen readers or other assistive technologies. This issue fails WCAG 2.2 AA Success Criterion 4.1.3 (Status Message). We plan to address this by July 2027.
- Some modal dialogs do not expose their dialog role and accessible name together to assistive technologies. This may impact people who use screen readers or other assistive technologies. This issue fails WCAG 2.2 AA Success Criterion 4.1.2 (Name, Role, Value). We plan to address this by July 2027.
What we’re doing to improve accessibility
We are currently liaising with our vendor to review and address the accessibility issues.
Preparation of this accessibility statement
This statement was prepared on 11 November 2026. It was last reviewed on 17 November 2026.
This website was last tested on 20 October 2026. 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