Accessibility statement

1. Website accessibility

Using this website

St Catherine’s College runs this website with support from the IT 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 have audited the website and are making improvements.

2. 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 good alternative text or contain text within them
many documents are in PDF and Word format and are not accessible
some pages use tables for layout without identifying them as such
some heading elements are blank or not consistent
some pages need improved hyperlinking
on some pages, users cannot zoom to make text bigger
some colours do not have high enough contrast
some buttons are not labelled

3. 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.

IT Support Team
itsupport@stcatherines.college

4. 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.

5. Non-accessible content

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

Content

On some of our pages, headings have been left blank. This means that their purpose cannot be understood by assistive technology. This does not meet with success criterion WCAG 2.1 AA G130.

HTML

Some pages have disabled zoom on the ‘viewport’. This means that users cannot control the size of parts of the page. This does not meet with success criterion WCAG 2.1 AA 1.4.4.

The contrast of some of the colours 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. There is a high visibility version of the website for those with visual disabilities.

These issues would require development work to fix.

Images

Some images contain text, so people with dyslexia or using a screen reader will not be able to read the information. This does not meet WCAG success criterion 1.4.5 (Images of Text).

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 remove all images that contain text 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 on the forms do not have a title attribute. 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).