Non-compliance with the accessibility regulations
Leeds City Council logo in the footer
The Leeds City Council logo in the footer is contained inside a link but has no accessible text to describe the purpose of the link to screen reader users.
This issue fails WCAG 220.127.116.11 Non-text content (A) and 2.4.4 Link purpose in context (A).
Some headings on our website have been made to look like normal paragraph text, using CSS to control the styling. This can be confusing for screen reader users as headings are used to understand the hierarchy of content on the page.
This fails WCAG 2.1 1.3.1 Info and Relationships (A) and 2.4.6 Headings and Labels (AA).
We have a couple of links on our website which do not make sense when taken out of context. This can make it difficult for screen reader users to navigate the page using links.
This fails WCAG 2.1 2.4.4 Link purpose (in context) (A).
Colour contrast issues
Some areas of our website have insufficient colour contrast. This can make text hard to read for users who may be colour blind. Some areas affected are:
- the footer links when focused on by keyboard only users who have zoomed in
- form field border colours against the surrounding background colour
- Default text when user has no calls when signed in as SME
- Error messages that appear if you incorrectly fill in create new call form
These issues fails WCAG 2.1 1.4.3 Contrast (Minimum) (A) and/or 1.4.1 Use of color (A).
Form field colour
When logged in as SME and creating a new call there is a form that background colour is dusty pink and form fields are white. There is insufficient colour contrast between these two colours. This fails 1.4.11 Non-text contrast (AA).
Some interactive elements on our website do not receive any different visual styling (focus styling) when using a keyboard to navigate down the page meaning users may not be aware which element they are interacting with.
This fails WCAG 2.1 2.4.7 Focus visible (AA).
When using a browser extension to increase the font size to 200% some content disappears off the page as it has not moved down to adjust itself. This is apparent in the header and footer.
This fails WCAG 2.1 1.4.4 Resize text (AA).
You are able to resize the whole page content using your browsers built in zoom functionality to 200% and all the content is visible and readable.
It is not possible to open and close the burger navigation (for users who are zoomed in on desktop) using only a keyboard.
This fails WCAG 2.1 2.1.1 Keyboard (A).
Screen reader accessibility
The burger icon does not announce to screen reader users whether it is collapsed or expanded when changing between the two states.
This fails WCAG 2.1 4.1.2 Name, Role, Value (A).
Skip repeated content
It is not possible to skip repeated content on the page as a keyboard or screen reader user. This is normally possible by including a ‘Skip to content’ link as the first interactive element a user can interact with.
This fails WCAG 2.1 2.4.1 Bypass Blocks (A).
Our website’s HTML mark-up does not validate when running it through W3C validator. There are numerous errors that need looking into.
This fails WCAG 2.1 4.1.1 Parsing (A).
Where forms collect information about the user (such as sign up forms) we should have auto complete on the form fields so people with language or memory problems can benefit from the browsers auto filling their information in. Some fields don’t currently have auto complete on them.
This fails WCAG 2.1 1.3.5 Identify Input Purpose (AA).
If a user incorrectly fills out a form error messages and an error summary appear but screen reader users aren’t alerted to the errors on the page.
This fails WCAG 2.1 3.3.1 Error identification (A) and 4.1.3 Status message (AA).
Required form fields
The website has asterisks against required form fields but there isn’t information about this before filling in forms. This fails WCAG 2.1 3.3.2 Labels or Instructions (A).
Some form fields have asterisks in their label but haven’t got the appropriate HTML mark-up against the input field that tells screen reader users they are required. This fails WCAG 2.1 3.3.3 Error Suggestion (AA).
Form fields flowing off the page
The form fields on Sign up as SME page flow off the page if a user zooms to 400% using their browsers built in zoom functionality.
This fails WCAG 2.1 1.4.10 Reflow (AA).
The browser tab page title is the same on Sign up for SME and Sign up as Levy Payer pages. Page titles should be unique so users can quickly navigate between tabs and so screen reader users can quickly identify which page they have navigated to.
This fails WCAG 2.1 2.4.2 Page titled (A).
Multiple ways of finding content
When signed in as SME it is only possible to find some pages using links on the homepage. Users should be offered two methods of finding content.
This fails WCAG 2.1 2.4.5 Multiple Ways (AA).
Create a call pop ups
After submitting the Create new call form a pop up appears. The pop up is not announced to screen reader users and it is not possible to close or interact with the form using only a keyboard. This fails WCAG 2.1 2.1.1 Keyboard (A) and 2.1.2 No Keyboard Trap (A).
Content that’s not within the scope of the accessibility regulations