Tollgate Community Junior School

Using this website

Tollgate Community Junior School runs this website. 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.

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

• some pages and document attachments are not clearly written
• the language has not been set on webpages
• some images do not have alternative text or good alternative text
• many documents are in PDF and Word format and are not accessible
• some tables do not have row headers
• some embedded content doesn’t have a title
• some heading elements are blank or not consistent
• some pages use tables for layout without identifying them as such
• some pages need improved hyperlinking
• some content popups can only be closed using a mouse, not a keyboard
• some content has been hidden from screen readers
• some form controls and buttons are not labelled or not unique
• some colours on the homepage do not have high enough contrast

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 email the school office in the first instance.

• office@tollgate-jun.co.uk

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.

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.

Some pages on this website have the same title or no 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 lang attribute is not used to identify the language of the page. This means that assistive technologies will not be able to discern the default language to convert text into synthetic speech. This does not meet with success criterion WCAG 2.1 A 3.1.1.

Some content can only be accessed using a mouse. Some users are unable to use a mouse, so use the keyboard instead.  There is no equivalent keyboard event handler to help these users. This does not comply with WCAG 2.1 A F54.

Some content on our website is automatically inserted using CSS. This means it cannot be read out by a screen reader or will not be available to users who turn stylesheets off. This does not comply with WCAG 2.1 A F87.

Some pages have coding or nesting errors. This does not meet success criterion WCAG 2.1 A 4.1.1.

The contrast of some of the colours 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.

Forms

Some of our form fields and buttons are not labelled correctly. This means some users will not be able to identify the purpose of the form field. This does not comply with WCAG 2.1 A F68.

This issue might require development work to fix.

Images

Some images might 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 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 a duplicate ID has been used on more than one element. This does not comply with HTML5 WCAG 2.0 A 4.1.1.