Accessibility Statement for the Child Friendly Leeds Blog.
Content published on https://wearechildfriendlyleeds.com/ domain.
This website is run by Child Friendly Leeds. It 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:
- The links within the page when read out of context may confuse assistive technology users.
- The use of headers across the page may not be clear to assistive technology users
- Screen reader users rely on a frame title to describe the contents of the frame, there is no frame title
- There are hidden elements on the page which are not accessible to all users od assistive technologies
- CFL message video content does not have sufficient audio description or have a text alternative that describes the visual content of the video
- The social media share links don’t all have focus styling, this may impact keyboard only users.
- The contrast between the text colour and background colour for 4 of the page’s elements aren’t high enough, making the text difficult to read for those with visual impairments
- Certain images/links on the page do not have alternative text, so they will not be read out to assistive technology users
Feedback and contact information
If you need information on this website in a different format email childfriendlyleeds@leeds.gov.uk and tell us:
- the web address (URL) of the content
- your name and email address
- the format you need, for example, audio CD, braille, BSL or large print, accessible PDF
Reporting accessibility problems with this website
If you find any problems that are not listed on this page or you think we’re not meeting the accessibility requirements, email childfriendlyleeds@leeds.gov.uk.
Enforcement procedure
If you contact us with a complaint and you’re not happy with our response.
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
Child Friendly Leeds 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.1 AA standard any non-accessible content is currently being reviewed.
Non-accessible content
The content listed below is non-accessible for the following reasons.
Non-compliance with the accessibility regulations
Focus Visible
Some elements on our website don’t meet the contrast-ratio requirements meaning focus styling in not clear to all users in places
Some of the affected areas are:
- the social media share links don’t all have focus styling, this may impact keyboard only users.
This fails WCAG 2.1 success criteria 2.4.7 Focus visible (AA).
Skip to content link
There is no method to bypass the header and navigation across the site. Normally this is achieved by adding a “skip to content” link at the top of the page.
This fails WCAG 2.1 success criteria 2.4.1 Bypass blocks (A).
Images with no alternative text or not marked as decorative – Non-text content
Some images on our website are missing alternative text or haven’t being marked as decorative. Alternative text is used to describe the purpose of the image to visitors who are unable to see them. This can include screen readers and browsers that block images.
If an image is purely decorative then an alt tag should be included but left empty. This allows assistive technology to understand the image is there for decorative purposes. If an image serves a purpose (such as explaining what an entrance of a building looks like) then we must include descriptive alternative text.
Some of the images affected are:
- the social media icons in the header and footer
- The activity pack images
- ‘Recent comments’ has a gravatar link that has no text
- The Blog images don’t have alternative text
- The cricketer – this also fails 2.4.4
- The pintrest share button
This fails WCAG 2.1 success criteria 1.1.1 Non-text content (A). ‘The cricketer’ also fails 2.4.4 as mentioned above
Colour contrast
Some text on our website doesn’t have enough colour contrast against the background colour behind it. This can make the text hard to read for users with low vision or colour blindness. Some areas affected are:
- The title and subtitle text in the header
- ‘powered by Google translate’ button at the bottom of the page
- Twitter retweet credit (‘Child Friendly Leeds Retweeted’)
- ‘Share our blog with your networks’
- Thumbs up for the team
- Share our blog with your networks
- Orange text links
- White text on orange button
- Orange headings for activity pack
- Get involved title
- Highlights title
- Child Friendly Leeds Enrichment Winter Newsletter title
- Child Friendly Leeds Enrichment Winter Newsletter link
- Share our blog with your networks
This fails WCAG 2.1 success criterion 1.4.3 contrast (minimum)
Empty links (Link Purpose (In Context))
- Within the header there is an empty link, this can be unclear for those using assistive technology
- ‘Recent comments’ section has a gravatar link that has no text.
This fails WCAG 2.1 success criterion 2.4.4 Link Purpose (In Context) (A)
Keyboard
- There are hidden elements on the page which are not accessible to all users. The items in question are category links before the leave a reply section. This also fails 2.4.3 and 3.2.1
This fails WCAG 2.1 success criterion 2.1.1 Keyboard (A)
Mark up errors/warnings – Parsing
- Several mark-up errors that can cause problems with assistive technology.
- ID attribute values must be unique. The Facebook widget has two divs with the same ID ‘fb-root’, one of these needs deleting
This fails WCAG 2.1 success criteria 4.1.1 Parsing (A).
YouTube/video’s – Audio Description or Media Alternative (Prerecorded)
- There is no title attribute on the YouTube video that appears on the homepage. We need to add a title to the video that explains what the video is and the fact it is a video. This should allow screen reader users know they are about to interact with a video.
- CFL message video content does not have sufficient audio description or have a text alternative that describes the visual content of the video
- Need to add title attributes to YouTube embedded videos and the WordPress widget in the footer
- The captions that are provided by YouTube are not accurate enough, these need to be edited to be accurate for users.
This fails WCAG 2.1 success criteria 1.2.3 Audio Description or Media Alternative (Prerecorded) (A). success criteria 4.2.1 Name, Role, Value (A). Captions prerecorded 1.2.2 (A)
Labels or instructions
- The text area for the ‘leave a reply’ does not have a label associated with it.
This fails WCAG 2.1 success criteria 3.3.2 Labels or Instructions (A)
Error Identification
Multiple errors are not summarised at the top of the form. There’s no visual indication such as text and border highlights
This fails WCAG 2.1 success criteria 3.3.1 Error Identification (A).
Link text
- Some content on our website have links that don’t make sense when taken out of context. within the body content of the page there are links such as ‘here’ or ‘download’. Assistive technology users will sometimes use a list of links to navigate around the site. Having non descriptive links will be a barrier to entry.
WCAG 2.1 success criteria 2.4.4 Link purpose in context (A).
Info and relationships
If the required child roles aren’t present, assistive technologies may convey confusing information about your page, like announcing a tab set with no tabs.
- Certain ARIA roles must contain particular children
This fails WCAG 2.1 success criteria 1.3.1 Info and relationships (A).
Error identification
- Multiple errors are not summarised at the top of the form. There’s no visual indication such as text and border highlights. This also fails 3.3.1
This fails WCAG 2.1 success criteria 3.3.1 Error Identification (A)
Preparation of this accessibility statement
This statement was prepared on 02/05/2022. It was last reviewed on 24/05/2022.
