Technical Accessibility Statement

Technical Information about this website’s accessibility

Aberystwyth University 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 and exemptions listed below.

Non accessible content

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

Non-compliance with the accessibility regulations

Animation

Some pages have image sliders which move automatically. They can be stopped by mouseover, but there is no mechanism to pause the slider while continuing to use the page. This can be very distracting for some people and can make it hard to access the information on the sliders. This doesn’t meet WCAG 2.1 success criterion 2.2.2 Pause, Stop, Hide. We are working on changing the way our image sliders function so that they can be paused correctly.

Some pages have image sliders which interfere with the ability of screen readers to read out the text on the page. This means that the content doesn't make sense to people using screen readers. This doesn’t meet WCAG 2.1 conformance requirement 5.2.5 Non-Interference. We are working on changing the way our image sliders function so that they don't interfere with screen readers.

Documents

Some documents are only available in PDF format. This can mean that people cannot enlarge text in the document without needing to scroll left to right to read it. This doesn’t meet WCAG 2.1 success criterion 1.4.10 Reflow. When we publish new documents, we’ll make sure that they are provided in more than one file type to make them as accessible as possible.

Some documents available on our website are not structured correctly using headings. This is confusing when the pages are accessed using assistive technology. This doesn’t meet WCAG 2.1 success criterion 1.3.1 Info and Relationships. When we publish new documents, we’ll make sure that they are structured correctly. We will work our way through non-archive documents to improve them.

Some documents available on our website do not have alternative text on all images. This means that the information in them isn’t available to people using assistive technology. This doesn’t meet WCAG 2.1 success criterion 1.1.1 Non-Text Content. When we publish new documents, we’ll make sure that all images have text alternatives (unless they are purely decorative).  We will work our way through non-archive documents to improve them.

Some documents on our website do not have sufficient colour contrast in places. This can mean that text cannot be read by people with visual impairments. This doesn’t meet WCAG 2.1 success criterion 1.4.3 Contrast (Minimum). When we publish new documents, we’ll make sure that they have sufficient colour contrast. We will work our way through non-archive documents to improve them.

Forms                      

On some forms, the focus indicator is not visible when accessing a set of radio buttons or check boxes. This can mean that people are not sure where they are on the page while trying to fill out the form using a keyboard. This doesn’t meet WCAG 2.1 success criterion 2.4.7 Focus Visible. We are working on making improvements to all of our forms.

Some form fields do not have appropriate autocomplete attributes defined. This can mean that it's more difficult for people using assistive technology to understand what data should be entered. This doesn't meet WCAG 2.1 success criterion 1.3.5 Identify Input Purpose. We are working on making improvements to all of our forms.

Some forms contain fieldsets which have no legends. This can mean that it's not clear to people filling out the form what fields are included in the fieldset. This doesn’t meet WCAG 2.1 success criterion 3.3.2 Labels or Instructions. We are working on making improvements to all of our forms.

Some forms do not have labels set correctly for some fields and are using a placeholder rather than a label. This can mean that it's not clear to people filling out the form what data they should enter into the field. This doesn’t meet WCAG 2.1 success criterion 1.3.1 Info and Relationships. We are working on making improvements to all of our forms.

Some forms have orphaned form labels. This can mean that it's not clear to people filling out the form what field the label belongs to. This doesn’t meet WCAG 2.1 success criterion 3.3.2 Labels or Instructions. We are working on making improvements to all of our forms.

Headings

Some pages have multiple heading 1s. This is confusing when the pages are viewed using assistive technology. This doesn’t meet WCAG 2.1 success criterion 1.3.1 Info and Relationships. When we publish new content, we’ll make sure that there is only one heading 1 per page. We will work our way through the site, updating pages to remove excess heading 1s. We are educating our content editors to ensure that they create accessible content.

Some pages may not include headings to separate the sections of the page. This can mean that people using assistive technology are not aware of when they have moved from one section to another. This doesn’t meet WCAG 2.1 success criterion 2.4.10 Section Headings. When we publish new content, we’ll make sure that headings are used appropriately. We will work our way through the site, updating pages add headings where necessary. We are educating our content editors to ensure that they create accessible content.

Some pages skip a heading level. This is confusing when the pages are viewed using assistive technology. This doesn’t meet WCAG 2.1 success criterion 1.3.1 Info and Relationships. When we publish new content, we’ll make sure that headings are ordered correctly. We will work our way through the site, updating pages to fix up the heading order. We are educating our content editors to ensure that they create accessible content.

Some pages use formatting such as bold to highlight text as a heading. This means that people using assistive technology may not know that the text is a heading. This doesn’t meet WCAG 2.1 success criterion 1.3.1 Info and Relationships. When we publish new content, we’ll make sure that headings are used correctly. We will work our way through the site, updating pages to mark up headings correctly. We are educating our content editors to ensure that they create accessible content.

Some pages use headings to highlight text that isn't really a heading. This is confusing when the pages are viewed using assistive technology. This doesn’t meet WCAG 2.1 success criterion 1.3.1 Info and Relationships. When we publish new content, we’ll make sure that heading tags are only used for headings. We will work our way through the site, updating pages to remove heading tags from non-heading text. We are educating our content editors to ensure that they create accessible content.

Images

Some images don’t have a text alternative. This means that the information in the images isn’t available to people using assistive technology. This doesn’t meet WCAG 2.1 success criterion 1.1.1 Non-Text Content. When we publish new content, we’ll make sure that all images have text alternatives (unless they are purely decorative). We will work our way through the site, adding appropriate alternative text to existing images. We are educating our content editors to ensure that they create accessible content.

Keyboard

On some pages, the focus indicator is not visible when you tab onto image sliders. This can mean that people are not sure where they are on the page while accessing it via a keyboard. This doesn’t meet WCAG 2.1 success criterion 2.4.7 Focus Visible.

Some pages have areas that cannot be accessed via keyboard. This includes pages using ‘accordions’ or ‘tabs’. This means that the information contained in the accordions or tabs is not available to people navigating via keyboard. This doesn’t meet WCAG 2.1 success criterion 2.1.1 Keyboard. We are working on changing the way our accordions and tabs function so that the content within them is accessible via keyboard.

Landmarks

Some of the content of our pages is outside of any ARIA landmark. This could be confusing to people using assistive technology. This doesn't meet WCAG 2.4.1 Bypass Blocks. We will improve page structure to ensure that all content is contained within an ARIA landmark.

Links

Links used to open and close the sub-sections in our global navigation do not have text or titles. This means that people using assistive technology may not know what the links do. This doesn’t meet WCAG 2.1 success criterion 2.4.4 Link Purpose (In Context). We will work on improving the global navigation so that is clear what these links do.

Some linked images have alternative text which describes the image rather than what it is linking to. This can mean that people using assistive technology don't know where the image will take them if they follow the link. This doesn’t meet WCAG 2.1 success criterion 2.4.4 Link Purpose (In Context). When we publish new content, we’ll make sure that all linked images have text alternatives that tell people about the link purpose rather than describing the image. We will work our way through the site, updating alternative text to existing images.  We are educating our content editors to ensure that they create accessible content.

Some of our links open in a new browser window. This can be confusing for people using assistive technology. This doesn’t meet WCAG 2.1 success criterion 3.2.5 Change on Request. Where it is necessary to open links in a new browser window, we will add this information to the link so that people will know that this behaviour will occur. We will work our way through other links and ensure they open in the current browser window.

Some pages have links to videos, but the link text doesn’t specify that it will open a video. This could be confusing for people using assistive technology. This doesn’t meet WCAG 2.1 success criterion 2.4.4 Link Purpose (In Context).

Some pages have links using text that doesn’t tell the user where the link will take them. This could be confusing for people using assistive technology. This doesn’t meet WCAG 2.1 success criterion 2.4.4 Link Purpose (In Context). When we publish new content, we’ll make sure that all link text is useful and doesn't rely on context. We will work our way through the site, updating link text where necessary. We are educating our content editors to ensure that they create accessible content.

Some pages have multiple links using the same text. This could be confusing to people using assistive technology. This doesn’t meet WCAG 2.1 success criterion 2.4.4 Link Purpose (In Context). When we publish new content, we’ll make sure that we don't use the same text for multiple links. We are educating our content editors to ensure that they create accessible content.

Tables

On some pages, there are tables which do not have headers. This can mean that it's more difficult for people using assistive technology to understand what data the table contains. This doesn’t meet WCAG 2.1 success criterion 1.3.1 Info and Relationships. When we publish new content, we’ll make sure that tables always have headers. We will work our way through the site, updating existing tables to ensure they have headers. We are educating our content editors to ensure that they create accessible content.

Text

On a small number of pages, text may overlap if you increase text spacing. This can mean that people who need to change the text spacing in order to read the page will miss some of the content. This doesn’t meet WCAG 2.1 success criterion 1.4.12 Text Spacing. We are working on improving the CSS for these areas to ensure that the text will reflow when text spacing is increased.

Some pages use ‘accordions’ or ‘tabs’ which can mean that the content within them is not available to a screen reader user or that the content is available, but not in an obvious way (e.g. by skipping through lists on the page). This means that the content may not be available to some people and is likely to be confusing. This doesn’t meet WCAG 2.1 success criterion 1.3.1 Info and Relationships. We are working on changing the way our accordions and tabs function so that the content within them is accessible via screen reader.

Video

Some videos embedded in our pages do not have captions. This means that people with hearing impairments may not be able to understand the video. This doesn’t meet WCAG 2.1 success criterion 1.2.2 Captions (Prerecorded).

Some videos embedded in our pages have text visible which isn't available in the audio. This means that people with visual impairments may not be able to understand the video. This doesn’t meet WCAG 2.1 success criterion 1.2.1 Audio-only and Video-only (Prerecorded).

Some videos embedded in our pages only have automatically created captions. This means that people with hearing impairments may not be able to understand the video if the auto-captioning is not accurate. This doesn’t meet WCAG 2.1 success criterion 1.2.2 Captions (Prerecorded).

Content that’s not within the scope of the accessibility regulations

Many of our older PDFs and Word documents don’t meet accessibility standards. 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.  

We do not plan to add captions to live video streams because live video is exempt from meeting the accessibility regulations.

What we’re doing to improve accessibility

Our testing identified issues with some of our templates that were affecting large numbers of pages across our website. We are working on these issues now.

We have provided training and guidance for staff who edit the website, so that they can improve the accessibility of the content they are responsible for.

We are ensuring that our development processes include accessibility considerations and testing as standard.

We have introduced a digital accessibility policy.

Information on improvements we have made to the site.

Preparation of this accessibility statement

This statement was prepared on 3rd September 2020. It was last reviewed on 22nd September 2020.

This website was last tested on 3rd September 2020. The test was carried out internally using a combination of manual and automated testing.