Accessibility statement

This accessibility statement applies to this website, www.east15.ac.uk/ and to www1.essex.ac.uk/e15apply

How accessible is this website/s?

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

• you cannot modify the line height or spacing of text
• most older PDF documents are not fully accessible to screen reader software
• live video streams do not have captions
• some of our videos do not have captions
• some of our online forms can difficult to navigate using just a keyboard
• some of our pages can be difficult to navigate with a screen reader
• not all of our images have alternative text added to them
• on some pages our headings are not nested correctly.

If you need information on this website/s in a different format like accessible PDF, large print, easy read, audio recording or braille:

• email - wedm@essex.ac.uk
• call +44 (0)1206 873333
• Web Editing and Digital Media Team, University of Essex, Wivenhoe Park, Colchester CO4 3SQ

We’ll consider your request and get back to you in 10 days.

Reporting accessibility problems with this website/s

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 University Web Editing and Digital Media Team: wedm@essex.ac.uk

Enforcement procedure

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 the University can be found on our contact us webpages. Alternatively, information on visiting us in person can be found on each of our two campus pages:

• Loughton Campus
• Southend Campus

Technical information about this website’s accessibility

East 15 Acting School, University of Essex is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

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 www.east15.ac.uk

• Some images do not have a text alternative, so people using a screen reader cannot access the information. This fails WCAG 2.1 success criterion 1.1.1 (non-text content). We plan to add text alternatives for all images by December 2022. When we publish new content we’ll make sure our use of images meets accessibility standards.
• Some of our videos do not have a captions, that require this cannot access the information. This fails WCAG 2.1 success criterion 1.2.2 (captions (pre-recorded)). We plan to add captions for all our video media by December 2022. When we publish new content we’ll make sure all our videos contain captions.
• Some of our input fields are missing their descriptions. This means it is hard for some assisted technologies to know what the field is for. This fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships) 3.3.2 (labels or instructions),  4.1.2 (Name, Role, Value). We plan to ensure all input fields have descriptions by December 2022. When we publish new input fields we'll make sure they have descriptions.
• On some of our pages HTML has been used for format content rather than CSS. This can make reading text with some assisted technologies confusing. This fails WCAG 2.1. success criterion 1.3.1 (Info and Relationships). We plan to ensure all content is formatted with CSS only by December 2022. When new content is added, we'll make sure it is not formatted with HTML.
• On some of our pages the language has not be set. This makes it difficult for some assisted technologies to know how to pronounce words or know what language the website is in. This fails success criterion 3.1.1 (Language of Page). We plan to ensure every web page has its language set by December 2022. 
• On some of our pages we have used code similarly to a form, but have not included a 'submit' button. This means it confusing for assisted technologies to know what the intended behaviour of this section is. This fails WCAG 2.1. success criterion 3.2.2 (On input). We plan to ensure every page that uses form code has a submit button, or the code is removed by December 2022. When new content is added we'll make sure either to not use form code, or include a submit button where we do.
• On some of our links, the only identifiable mark that it is a link is a colour change. This makes it difficult for people who cannot perceive colour to know that a link is in use. This fails WCAG 2.1. success criterion 1.4.1 (Use of color). We plan to ensure all links have at least two identifiable elements to them by December 2022. When new links are added we'll make sure that colour isn't the only way one can identify a link.
• Some of our Element ID's are not unique. This makes it hard for assisted technologies to understand what the purpose of the element is. This fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships). We plan to ensure all our Element IDs are unique by December 2022. We'll make sure any new element IDs added are unique.
• Some of our link text is the same but used for multiple different destinations on the same page. This makes it difficult for some people to know where the link points to without further explanation. This fails WCAG 2.1 success criterion 2.4.4  (Link purpose (in context)). We plan to ensure all of our link text is unique for each new destination by December 2022. We'll make sure any new links added are unique.
• On some of our pages labels are used that are not connected to a form control. This makes it difficult for assisted technologies to know how to refer to each label when presenting a form control. This fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships). We plan to ensure that our labels are connected to a form control by December 2022. We'll make sure any new forms or labels added will be linked.
• In some areas the functionality we have used have added in Heading tags, but we have not added a heading in its place. This can be confusing for assisted technologies as they will not understand why the heading is empty. This fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships). We plan to ensure all heading tags are either removed or text is present by December 2022. Where possible, we'll make sure all heading tags have complete text when new content is added.
• On some of our images our alternative text is identical to the image link text. This means that assisted technologies will read this twice and it could be confusing. This fails WCAG 2.1 success criterion 1.1.1 (non-text content). We aim to ensure link text and alternative text are different, or only one piece of text is used by December 2022. When we add new images, that are also links will have unique text from now on.
• On some of our webpage, the functionality we have used has added local link (anchor links) but the destination does not exist. This makes it confusing for assisted technologies to navigate the site. This fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships). We plan to ensure all local links have destinations on the page by December 2022. In future, any local links we add to a web page we'll be sure to include the destination on the page too.
• Some of our navigation menus are very long, and there is no logical order to how they are shown. This makes it hard to navigate. This fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships). We plan to resolve all navigation issues and implement an order to our navigation by December 2022. In future we'll make sure there is a logical order to all our navigation going forward.
• Some of our WAI-ARIA roles do not match the functionality of the element. This makes it confusing for assisted technologies to interpret the website. This fails WCAG 2.1 success criterion 4.1.2 (Name, Role, Value). We plan to ensure each WAI-ARIA role matches the functionality of the element by December 2022.
• Some of the tabbing sequences on our pages are not logical. This makes it hard for users who rely upon a keyboard to navigate our website. This fails WCAG 2.1 success criterion 2.4.3 (Focus Order). We plan to resolve tabbing and navigation issues by December 2022.
•  Some of our images should be marked as decorative? This makes it confusing for screen readers to know whether the image is of value to the content on not. This fails WCAG 2.1 success criterion 1.1.1  (non-text content). We plan to ensure all decorative images are marked as such by December 2022.
•  Some of our form elements are not grouped with a field-set to make them easier to navigate through. This fails WCAG 2.1 success criterion  1.3.1  (Info and Relationships) 3.3.2 (Labels or instructions). We plan to address all form issues, and ensure elements of a similar nature are grouped together by December 2022.
• Some of our text areas on forms do not have descriptions. This makes it hard for uses of assisted technologies to know what the area is for. This fails WCAG 2.1 success criterion  1.3.1  (Info and Relationships) 3.3.2 (Labels or instructions) 4.1.2 (Name, Role, Value). We plan to address all forms and text area descriptions by December 2022.
• On some of our pages, there is no option to skip repeated content. This means that users of assisted technologies have no option to skip this content. This fails WCAG 2.1 success criterion 2.4.1 (Bypass Blocks). We plan to address this, so users can skip repeated content by December 2022.
• When using HTML5, not all of our content is included in landmarks. It is best practice to include all content on the page in landmarks. In this way users of assistive technologies can use the landmarks for navigating the page without losing track of content. This fails WCAG 2.1 success criterion  1.3.1 (Info and Relationships). We plan to ensure all our content is included within landmarks when using HTML5 by December 2022.
•  On occasion, we have have used two or more HTML5 or WAI-ARIA landmarks of the same type that have not been named. Users might not know the difference if it's not somehow explained. This fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships). We plan to address all landmarks and ensure they are distinguishable by December 2022.
•  On some occasions, certain pages will have no top-level heading on the page. This makes it difficult for people to know where they are on the website. This fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships). We plan to address all top-level heading issues by December 2022
• On some occasions the WAI-ARIA attribute is used but is redundant since is doesn't provide the user with any additional information. This fails WCAG 2.1 success criterion 4.1.2 (Name, Role, Value). We plan to address all WAI-ARIA issues by December 2022.
• On some pages when navigating by keyboard focused components can be visually identified. If the focused component is not somehow highlighted, the user cannot be sure which component has focus. This fails WCAG 2.1 success criterion 2.4.7 (Focus visible). We plan to address this issue to ensure all areas are clearing highlighted when in focus by December 2022.
• On the majority of our webpages, in certain areas the colour contrast is insufficient. This can present a problem for users with low-vision or colour-blindness. This fails WCAG 2.1 success criterion 1.4.3 (Contrast minimum). We plan to address all contrast issues by December 2022.
• On all of our student pages (/students) the contrast between our logo and the background is insufficient. Which can make it tricky for someone to see clearly. This fails WCAG 2.1 Success Criterion 1.4.11 (Non-text contrast). We plan to fix this by December 2025.

Content found on www1.essex.ac.uk/e15apply

• Our form is missing some labels, so people using a screen reader cannot access the information. This fails WCAG 2.1 success criterion 1.1.1 (non-text content). We plan to add labels for all our forms by October 2022. When we publish new content we’ll make sure to add labels to our forms to meet accessibility standards.
• We’ve used tables to set out our form so you can’t easily navigate through it using different devices. This fails WCAG 2.1 success criterion 1.3.1 (Info and relationships). We plan to ensure our pages properly adapt on different devices by December 2025. In future when publishing any new applications on our website we’ll make sure to use proper adaptive technologies.
• We have missed a heading level, so people using a screen reader can find navigating our content confusing. This fails WCAG 2.1 success criterion 1.3.1 (Info and relationships). We plan to add address this by December 2025. When we publish new content, we’ll make sure to add headings appropriately to our forms to meet accessibility standards.
• Our form is missing their labels, so people using a screen reader cannot access the information. This fails WCAG 2.1 success criterion 1.3.1 (Info and relationships). We plan to add labels for all our forms by December 2025. When we publish new content, we’ll make sure to add labels to our forms to meet accessibility standards.
• We are missing a page regions. This means it only visually looks different, so screen readers cannot tell the region or mark-up of the page. This fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships). We plan to ensure all of our pages have correctly marked up regions by December 2025.
• This section of our website relies on solely using landscape orientation. This fails WCAG 2.1 success criterion 1.3.4 (Orientation). We plan to ensure our pages properly adapt on different devices by October 2022. In future when publishing any new applications on our website we’ll make sure to use proper adaptive technologies.
• Most of our input fields do not have a corresponding label, so people using a screen reader cannot access the information. This fails WCAG 2.1 success criterion 1.3.5 (Identity Input Purpose). We plan to add labels for all our forms by October 2022.
• At times on our page the contrast we have used is not strong enough. This can make it hard to see for some people. This fails WCAG 2.1 success criterion 1.4.3 (Contrast (Minimum). We plan to fix this by October 2022.
• As our pages does adapt to different devices, when switching to portrait mode, horizontal scroll appears. This makes it hard for people who rely on using different devices to access our form. This fails WCAG 2.1 success criterion 1.4.10 (Reflow). We plan to fix this by December 2025.
• It is not possible to use shortcut keys on a keyboard to navigate through this form. This makes it tricky for many users who are unable to use a mouse.. This fails WCAG 2.1 Success Criterion 2.4.1 (Bypass Blocks). We plan to address this by October 2022.
• On some web pages our page titles are set correctly so they do not clearly outline the purpose of the page. This fails WCAG 2.1 Success Criterion 2.4.2 (Page Titled). We plan to address this October 2022. When we publish new content, we’ll make sure pages are title correctly.
• Occasionally we have accidentally added link without it’s link text. This means assisted technologies might indicate a link is present by it can be confusing what the purpose of the link is. This fails WCAG 2.1 Success Criterion 2.4.4 (Link Purpose). We plan to address this by October 2022. In future, we’ll make sure all of our links have link text.
• Occasionally we have accidentally added link without it’s link text. This means assisted technologies might indicate a link is present by it can be confusing what the purpose of the link is. This fails WCAG 2.1 Success Criterion 2.4.4 (Link Purpose). We plan to address this by October 2022. In future, we’ll make sure all of our links have link text.
• At times we have two adjacent links pointing to the same location. When using assisted technologies this can be quite confusing for the used. This fails WCAG 2.1 Success Criterion 2.4.4 (Link Purpose). We plan to address this by October 2022. In future, we’ll make sure our links aren’t so confusing for all our users.
• Some of our links have an empty value attribute or it’s button is missing, this can be very confusing for some users. This fails WCAG 2.1 Success Criterion 2.4.4 (Link Purpose). We plan to address this by October 2022. In future, we’ll make sure our links aren’t so confusing for all our users.
• On some of our labels we haven’t used the name attribute to clearly indicate a label item. This means it can be confusing for people using assisted technologies to know what the label is. This fails WCAG 2.1 Success Criterion 2.5.3 (Label in Name). We plan to address this by October 2022.
• We do not provide a consistent error warning throughout our website, which means it can be hard for people to determine when an error has occurred. This fails WCAG 2.1 Success Criterion 3.2.4 (Consistent Identification). We plan to ensure this is addressed by October 2022. In future, when we publish new content we’ll make sure to use an consistent error message throughout
• Some of our form input elements do not contain labels to make them easier to navigate through. This fails WCAG 2.1 success criterion 3.3.2 (Labels or Instructions). We aim to ensure all our form elements that require labels have them by October 2022.
• Sometimes we have used malformed HTML, meaning that users, who use assistive technologies might not be able to accurately interpret and parse content. This fails WCAG 2.1 Success Criterion 4.1.1 (Parsing) We plan to address this by October 2022 and ensure that all our content can be correctly parsed.
• When using error messages sometimes it isn’t clear for assisted technologies that an error has occurred. This fails WCAG 2.1 Success Criterion 4.1.3 (Status Messages). We need to use role=error attribute for all our error messages. We plan to address this by October 2022 and make sure our error messages are helpful for everyone.

Disproportionate burden

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’s 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 our services, and forms published as Word documents. By September 2025, we plan to either fix these or replace them with accessible 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.

Live video

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 20 September 2019. It was last reviewed on 30 May 2022.

This website was last tested on 30 May 2022. The test was carried out by the University's Web Editing and Digital Media Team.

We use a third-party company Siteimprove to continually monitor our website and highlight accessibility issues. Siteimprove's method and policy can be found on their website.