Technical Accessibility Statement
Technical Information about this app’s accessibility
Aberystwyth University is committed to making its apps accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
Compliance status
This app 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
Some images in the app don’t have a text alternative. 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.
Some form fields in the app don’t have labels. 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.
On some devices (Android) some of the text in the app cannot be read out by a screen reader. This means that people using assistive technology are unable to access this information. This doesn’t meet WCAG 2.1 success criterion 1.3.1 Info and Relationships.
Most of the buttons in the app do not have sufficient contrast between the colour of the text and the colour of the background. This means that the text is difficult to read for people with visual impairments. This doesn’t meet WCAG 2.1 success criterion 1.4.3 Contrast (Minimum).
Some buttons and links in the app don’t have names or link text. This means that people using assistive technology don’t know what each of the buttons or links does. This doesn’t meet WCAG 2.1 success criterion 2.4.4 Link Purpose (In Context).
Some buttons in the app do not have names. This means that people using speech to text will be unable to access them. This doesn’t meet WCAG 2.1 success criterion 2.5.3 Label in Name.
Some buttons and form fields in the app are too small. This means that it can be hard for some people to activate them. This doesn’t meet WCAG 2.1 success criterion 2.5.5 Target Size (AAA)
On some pages and some devices (iOS), the back button doesn’t work when using a screen reader. This means that it is difficult for people using assistive technology to go back to a previous page. It’s also inconsistent as back buttons on some pages work and others don’t. This is related to WCAG 2.1 success criterion 3.2.3 Consistent Navigation.
Some tiles in the app are marked up as buttons but don’t have an associated action. This is confusing for all users as they expect an action to occur when activating the button. This doesn’t meet WCAG 2.1 success criterion 4.1.2 Name, Role, Value.
Some select boxes in forms in the app don’t have names. This means that people using assistive technology don’t know what the purpose of the select box is. This doesn’t meet WCAG 2.1 success criterion 4.1.2 Name, Role, Value.
What we’re doing to improve accessibility
We will look at changing the colours used on the app and will work with the provider to make other improvements.
Preparation of this accessibility statement
This statement was prepared on 10th June 2021. It was last reviewed on 10th June 2021.
This app was last tested on 10th June 2021. The test was carried out internally using a combination of manual and automated testing.