1. Website accessibility
Using this website
Brede Primary 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.
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.
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 alternative text or good alternative text
- many documents are in PDF and Word format and are not accessible
- some pages need improved hyperlinking
- some colours do not have high enough contrast
- some content has been hidden from screen readers
- some pages have errors with aria controls
- some form controls and buttons are not labelled or not unique
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.
- Web Support Team
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.
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.
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 content is hidden from screen readers, because of missing aria labels. This content can be navigated to, but someone using a screen reader will hear silence. This does not meet success criterion WCAG 2.1 A 1.3.1.
Some pages have errors with aria controls. This does not meet success criterion WCAG 2.1 A 1.3.1.
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.
These issues would require development work to fix.
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 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.
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.
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).
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.
- Some headings on some pages are empty or have no accessible name. This does not comply with HTML5 WCAG 2.1 AA G130.
6. Preparation of this statement and how we tested this website
This statement was prepared on 16 November 2020. It was last updated on 26 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 internally by the Web Support Team, using SortSite.