Stopford are committed to making our forms accessible. We want as many people as possible to be able to use our forms.
This means you should be able to:
- change line height, spacing between paragraphs and fonts
- zoom in up to 300% without the text spilling off the screen
- navigate most of the website using just a keyboard
- 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 text we use as simple as possible to understand.
AbilityNet has advice on making your device easier to use if you have a disability.
Our accessibility issues
We know some parts of our forms aren’t fully accessible, for example:
- our headers do not always include the form name, or the form name may not be descriptive enough
- the forms do not always alert customers to new content or changes in content (dynamic text) as a result of something being entered on the form
- radio buttons and check boxes are not always contained within a group with a legend so that screen readers can interpret them correctly
- error messages are not always presented in a format or position that is easy for screen readers to interpret
Reporting accessibility problems with this website
We're working to improve the accessibility of our website, but if there's anything which you'd like us to prioritise please email us and let us know: register.headoffice@leeds.gov.uk
We’ll consider your request and get back to you in three working days.
The Equality and Human Rights Commission is responsible for enforcing the accessibility regulations for the council and other public sector bodies. If you’re not happy with our response, contact the Equality Advisory and Support Service.
Technical information about this website’s accessibility
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
Our aim was to have all issues mentioned below fixed by 28 August 2020.
Due to the COVID-19 coronavirus pandemic this project has been put on hold with priorities focussed elsewhere. The deadline has been pushed back until later in the year and we are awaiting confirmation of a new date. We will publish this here when we know the date.
The content listed below is non-accessible for the following reasons:
Headers
Not all headers include the form name.
Headings on the register a birth form go from a <h1> to a <h3> and should only increase by one level. Fails criteria 1.3.1 Info and relationships – Level A.
Radio buttons and check boxes
These need to be contained within a group and contain a legend so that screen readers can interpret them correctly. Radio buttons on the main landing page fail criteria 1.3.1 Info and relationships (When a form contains elements that are logically connected to each other it is necessary to group them) – Level A.
Radio buttons on the registration page fail criteria 1.3.1 Info and relationships (When a form contains elements that are logically connected to each other it is necessary to group them) – Level A.
Radio buttons on the registration page fail criteria 3.3.2 Labels or (Labels or instructions are provided when content requires user input) – Level A.
Users are not alerted to new content
New content that appears on the notice of marriage form fails criteria 4.1.3 Status (User not notified of dynamic text appearing) – Level AA.
When clicking on a date on the register a birth form, users are not notified the available appointments has appeared or changed. Fails criteria 4.1.3 Status (User not notified of dynamic text appearing) – Level AA.
On the civil partnership ceremony form, when clicking on next using a screen reader, users are not notified of the new content that has appeared. Fails criteria 4.1.3 Status (User not notified of dynamic text appearing) – Level AA.
Error messages
Error messages are not underneath the associated label so that when a screen reader user navigates to the form they know the field is required before clicking on the input field.
Text elements with sufficient colour contrast ratio
Error messages and date picker (currently selected date) don’t have sufficient colour contrast ratio for their font weight. Fails 1.4.3 (Contrast - minimum)
ARIA attributes must conform to valid values
aria-labelledby is not linked to anything. The input it’s relating to already have a label attached so remove this. Fails criteria 4.1.2 (Name, Role, Value).
Form elements must have labels
Some text fields don’t have labels attributed to them, so screen reader users won’t be prompted. Fails criteria 1.3.1 (Info and relationships) and 3.3.2 (Labels and instructions).
