Claverham Community College

Claverham Community College

Website accessibility

Using this website

Claverham Community College runs this website with support from the Web Support Team. We aim to make it as easy to use as possible. We want you to be able to:

  • change colours, contrast levels and fonts
  • zoom in up to 300% without the text spilling off the screen
  • navigate most of the website using only a keyboard
  • listen to our website using a screen reader.

Go to AbilityNet to find out how to make these changes.

Language

We use plain English to make the text easy to read. We aim to create content for a reading age of 11. We regularly run readability audits on our content and make continual improvements.

Our content does not fully meet WCAG 2.1 AA accessibility standards, but we are auditing the website and will make improvements.

How accessible is this website?

We know some parts of this website are not fully accessible:

  • some pages and document attachments are not clearly written
  • some images do not have alternative text or good alternative text
  • many documents are in PDF and Word format and are not accessible
  • some pages use tables for layout without identifying them as such
  • some embedded content doesn’t have a title
  • some pages need improved hyperlinking
  • some colours do not have high enough contrast

What to do if you can’t access parts of this website

We are not legally required to fully comply with the Web Content Accessibility Guidelines version 2.1 AA standard.

However, we are always looking to improve the accessibility of this website. If you find any problems that are not listed on this page please contact us.

Technical information about this website’s accessibility

As part of our commitment to accessibility we are required to publish where we know there are issues with our website.

Compliance status

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

The content listed below is non-accessible for the following reasons.

Content

Some pages on this website have the same title. This means that web visitors may not be able to identify whether the information contained in the Web page is relevant to their needs. This does not comply with WCAG 2.1 A F25.

HTML

The contrast of some colours in the social media feed on the homepage is not high enough. This means that some users will have difficulty reading the content. This does not meet with success criterion WCAG 2.1 AA 1.4.3.

These issues would require development work to fix.

Links

On some pages the links do not contain any text or an image with alt text. This means that assistive technologies cannot identify the purpose of the links. This does not comply with WCAG 2.1 A F89.

Some links contain generic link text, such as “click here”. This means that assistive technologies cannot identify the purpose or context of the links. This does not comply with WCAG 2.1 A F63.

Images

Some images do not have a text alternative, or the text alternative is the name of the file, so people using a screen reader cannot access the information. This fails WCAG 2.1 success criterion 1.1.1 (non-text content).

We are working to and add correct alternative text. When we publish new content we’ll make sure our use of images meets accessibility standards.

PDFs and other documents

Some of our PDFs and Word documents are essential to providing our services, but may not be structured so they’re accessible to a screen reader. This does not meet WCAG 2.1 success criterion 4.1.2 (Name, role value).

We are working to either fix these or replace them with accessible HTML pages. Any new PDFs or Word documents we publish should meet accessibility standards.

Tables

Some presentation tables are not marked up as such. This means that assistive technologies will read the content of these tables out of context. This does not comply with WCAG 2.1 A F91.

This issue might require development work to fix.

iFrames

Some of the iFrames do not have a title attribute. This means that assistive technologies will read out the frame filename, which may be meaningless. This does not meet WCAG 2.1 success criterion 2.4.1 (Bypass blocks) and WCAG 2.1 success criterion 4.1.2 (Name, Role, Value – Frames must have a title attribute).

This issue might require development work to fix.

Other web development issues

  • On some pages, the div and ul elements have been nested as children where they shouldn’t be. This does not comply with HTML5 WCAG 2.0 A 4.1.1.

Preparation of this statement and how we tested this website

This statement was prepared on 23 November 2020. It was last updated on 24 November 2020.

This site was most recently tested in November 2020. This website was and is currently being tested for compliance with the Web Content Accessibility Guidelines V2.1 level A and level AA. These tests have been carried out by the Web Support Team, using SortSite.