Accessibility statement for writtle.ac.uk
This accessibility statement applies to this website, writtle.ac.uk
This website is run by Writtle University College. We want as many people as possible to be able to use this website. For example, that means you should be able to:
- change colours, contrast levels and fonts
- zoom in up to 400% without the text spilling off the screen
- navigate the website using just a keyboard
- navigate the website using speech recognition software
- listen to the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)
We’ve also made the website text as simple as possible to understand.
Making changes to your browser and operating system
Please find advice from AbilityNet, showing users how to make full use of accessibility settings in browsers and operating systems.
How accessible this website is
We know some parts of this website are not fully accessible:
- Some PDF documents are not fully accessible to screen reader software
- There are some supplementary forms which remain in PDF format. These will be replaced with accessible Word or HTML versions by September 2021
- There are PDF versions of printed brochures for our Schools which are not fully accessible to screen readers, the information contained within these is available elsewhere on our website in html format
- Our videos do not have audio descriptions
- Captions/synchronised transcripts provided with our videos are usually generated by Automated Speech Recognition and although we have endeavoured to ensure the greatest level of accuracy there may be some errors especially with complex technical terms
- Some of our online forms are difficult to navigate using just a keyboard
- Some of our pages can be difficult to navigate with a screen reader
- Some of our pages can be difficult to navigate with voice navigation
- Not all of our images have alternative text added to them
- On some pages our headings are empty
Feedback and contact information
If you need information on this website/s in a different format like accessible PDF, large print, easy read, audio recording or braille:
- Email - firstname.lastname@example.org
- Call +44 (0)1245 424200
- Digital Accessibility Team, Writtle University College, Chelmsford, Essex, CM1 3RR
We will acknowledge your request within 72 hours. Depending on the nature of your request, we will aim to meet your needs within 10 days.
Reporting accessibility problems with this website
We’re always looking to improve the accessibility of this website. If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact the Web Accessibility Team, email@example.com.
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’). If you’re not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).
Contacting us by phone or visiting us in person
Information on how to contact or visit Writtle University College can be found on our contact us webpage.
Technical information about this website’s accessibility
Writtle University College is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
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:
Issues with interactive elements
- Our 360 virtual tour (https://writtle.ac.uk/virtual-tour) uses mouse click, so users with no vision (who cannot use devices such as mice that require eye-hand coordination) as well as users who must use alternate keyboards or input devices that act as keyboard emulators will be unable to access the function of the content. This fails WCAG 2.1 A F54 Success Criterion 2.1.1 due to using only pointing-device-specific event handlers (including gesture) for a function and should have an equivalent keyboard event (onkey) handler. The virtual tour was developed by a third party and we are working with them to add equivalent onkey handlers. We plan to have onkey handlers added by July 2021.
- Some HTML form controls have no accessible name, so users using screen readers to voice the label will not be able to identify the purpose of the form control. This fails WCAG 2.1 A F68 Success Criterion 4.1.2 due to a user interface control not having a programmatically determined name. We plan to add missing labels to form controls by August 2021.
- Some forms use an onchange handler to open information windows, so users who navigate using a keyboard cannot operate the select lists because the handler fires as the user moves the selection up and down using the keyboard. This fails WCAG 2.1 A F36 Success Criterion 3.2.2 due to automatically submitting a form and presenting new content without prior warning when the last field in the form is given a value. We plan to give users advanced warning when opening a new window by August 2021.
- Some pages have form field labels which are not unique, this makes it difficult for users to identify specific components within the content. This fails WCAG 2.1 AA 2.4.6 Success Criterion 2.4.6 (Headings and Labels). We plan to add unique labels or add extra context (such as a heading) to explain the differences between the fields by June 2021.
Issues with Portable Document Formats - PDFs
- One PDF has no title, so people are unable to identify the contents or purpose of the document. This failsWCAG 2.1 A F25 Success Criterion 2.4.2 due to the title not identifying the contents. The PDF was produced by a third party. The PDF is published annually, and we will work with the third party to add a title to the next publication by January 2022.
- One PDF document has no lang attribute, the default human language of this document cannot be programmatically determined. This fails WCAG 2.1 A 3.1.1 Success Criterion 3.1.1 Language of Page. The PDF was produced by a third party. The PDF is published annually, and we will work with the third party to add a lang attribute to the next publication by January 2022.
- Some PDF documents have figures and images with blank alt text. If there is no source of text to provide an alternative for the image, then assistive technologies are not able to identify the image or to convey its purpose to the user. This fails WCAG 2.1 A F65 Success Criterion 1.1.1 due to omitting the alt attribute or text alternative on img elements, area elements, and input elements of type "image". When we publish new PDF content, we’ll make sure alt attributes are added to images. Where possible new PDF documents will have an accessible Word or HTML alternative. We plan to add alt attributes to images in all historic PDF documents by December 2021.
- Some PDF documents are not tagged, so are not accessible for screen reader users. This fails WCAG 2.1 A 1.3.1 Success Criterion 1.3.1 (Info and Relationships). When we publish new PDF content, we’ll make sure they are tagged. Where possible new PDF documents will have accessible Word or HTML alternative. We plan to add tags all historic PDF documents by February 2022.
Navigation / links
- Some pages contain link elements which do not contain text or an image with an alt attribute. A link name allows screen readers to voice what the links does. If there is no link text or the ‘alt’ text is blank, screen readers have nothing to read, so read out the URL instead. This fails WCAG 2.1 A F89 Success Criteria 2.4.4, 2.4.9 and 4.1.2 due to not providing an accessible name for an image which is the only content in a link. We plan to add text or alt attributes to images for links by June 2021.
- Some links are not underlined, this makes it hard for colour-blind users to see them. This fails WCAG 2.1 A F73 Success Criterion 1.4.1 due to creating links that are not visually evident without colour vision. We plan to add the text-decoration:underline property to our link styles, or add other style attributes in addition to colour changes to make links visible without colour vision by June 2021.
- Some links and controls have visual labels that do not appear in the accessible name. People who use speech control rely on being able to select elements using the visual label displayed on screen. If this is not part of the accessible name, they can't select elements by name. This fails WCAG 2.1 A F96 Success Criterion 2.5.3: Label in Name. We plan to include the text of the visible label as part of the accessible name for all links by July 2021.
- Soma pages have several links that share the same link text and surrounding context but go to different destinations. This could cause confusion for screen reader users. This fails WCAG 2.1 A F63 Success Criterion 2.4.4 due to providing link context only in content that is not related to the link. We plan to make link text unique for each target page or/and add an aria-label or aria-describedby to links by July 2021.
- Some data tables do not use header elements (th) or other appropriate table mark-up, so screen readers users are unable to understand column and row relationships. This fails WCAG 2.1 A F91 Success Criterion 1.3.1 for not correctly marking up table headers. We plan to add header elements or appropriate table mark-up to data tables by July 2021.
- Some iframe elements do not have a title attribute, so some screen readers read out the iframe filename. This fails WCAG 2.1 A 2.4.1 Success Criterion 2.4.1 - Bypass Blocks. We plan to add title attributes to all iframe elements by July 2021.
Alternative text for images
- Some images do not have a text alternative, so people using a screen reader cannot access the information. This fails WCAG 2.1 A F65 Success Criterion 1.1.1 due to omitting the alt attribute or text alternative on img elements, area elements, and input elements of type "image". We plan to add text alternatives for all images by June 2021. When we publish new content, we will make sure our use of images meets accessibility standards.
- Some pages have the same title, so the title cannot be used to distinguish pages. This fails WCAG 2.1 A F25 Success Criterion 2.4.2 due to the title of a Web page not identifying the contents. We plan to add unique titles by July 2021.
- Some pages have empty headings, this makes it difficult for users to find specific content and orient themselves within the Web page. WCAG 2.1 AA G130 Success Criterion 2.4.6 (Headings and Labels). We plan to add context to empty headings by July 2021.
We currently have no items we would classify as disproportionate burden. This may change as regulations and content changes, or if items are discovered that we would classify under this heading.
Content that is not within the scope of the accessibility regulations
PDFs and other documents
Some of our PDFs and Word documents are essential to providing our services. For example, we have PDFs with information on how users can access and use our services, and forms published as Word documents. By September 2021, we plan to either fix these or replace them with accessible Word documents or HTML pages.
The accessibility regulations do not require us to fix PDFs or other documents published before 23 September 2018 if they’re not essential to providing our services.
Any new PDFs or Word documents we publish will meet accessibility standards.
We do not plan to add captions to live video streams because live video is exempt from meeting the accessibility regulations.
Preparation of this accessibility statement
This statement was prepared on 16th April 2021. It is was reviewed on May 1st, 2021.
This website was last tested on 1st May 2021. The test was carried out by the Writtle University College Principal Technical Developer.
We use PowerMapper SortSite Desktop to routinely test our website and highlight accessibility issues. SortSite checks sites against W3 WCAG accessibility standards.
More information about testing using SortSite can be found on their website, https://www.powermapper.com/products/sortsite/tests/