This accessibility statement applies to the MySouthampton mobile application, version 1.0.164 published on the 13th October 2026.
The University of Southampton runs this mobile application. We want as many people as possible to be able to use it. We know the app has barriers for disabled people, and we list them on this page so you can plan around them.
You should be able to:
- change colour, contrast levels and fonts using your device settings
- navigate most of the app using a keyboard
- listen to most of the app using a screen reader, including TalkBack on Android, VoiceOver on iOS, and the most recent versions of NVDA and JAWS in our web views
- adjust text spacing without losing content or function
- tap controls comfortably because we have made interactive elements large enough to use
We have also made the app text as simple as possible to understand.
AbilityNet has advice on making your device easier to use if you are disabled.
How accessible is this app
We know some parts of this app are not fully accessible:
- screen readers cannot read the filter and action panels that slide up from the bottom of the screen
- keyboard users can get stuck in the Calendar events list and in the email recipient field
- on Android, pressing Escape on a keyboard closes the whole app instead of the open panel
- some controls work only when you drag or swipe them
- at 150 per cent text size and above, fixed headers and footers cover most of the screen
Calendar and Email cause the most problems if you use a screen reader or a keyboard. If you cannot complete a task in the app, contact us and we will help you another way.
Feedback and contact information
If you find any problems not listed on this page, or you think we are not meeting accessibility requirements, contact the project team on the email below or report your issue using the IT Service Portal.
If you need information from this app in a different format, such as accessible PDF, large print, easy read, audio recording, or braille:
- email: mysouthampton@soton.ac.uk
We will consider your request and get back to you within three working days.
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 are not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).
Technical information about this app’s accessibility
The University of Southampton is committed to making its mobile application accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
Compliance status
LearningMate Solutions (UK) Limited tested this app against the Web Content Accessibility Guidelines (WCAG) 2.2 AA standard.
This mobile application is partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, due to the non-compliances listed below.
Non-accessible content
The content listed below is non-accessible for the following reasons.
Non-compliance with the accessibility regulations
We list the problems in each group from most to least serious.
Screen reader access
Bottom panels in Calendar and Email announce themselves as a slider. As a result, screen readers cannot read the filters and actions inside them. This fails WCAG 2.2 success criteria 1.3.1 (info and relationships) and 4.1.2 (name, role, value).
The email body field triggers alert announcements, which can interrupt you while you write. This fails WCAG 2.2 success criterion 4.1.2 (name, role, value).
Headings on the Home and Blackboard screens have no heading markup, so you cannot move between them with a screen reader. Some lists also report the wrong number of items. This fails WCAG 2.2 success criterion 1.3.1 (info and relationships).
Screen readers do not announce the “Email restored” and “Saving selections” messages or the character counters. This fails WCAG 2.2 success criterion 4.1.3 (status messages).
Every delete button in the inbox reads “Delete email” and does not name the email it deletes. Live Chat repeats generic labels in the same way. This fails WCAG 2.2 success criterion 2.4.6 (headings and labels).
Filter buttons come last in the reading order. On the AER screen, screen readers read the text before its links. This fails WCAG 2.2 success criterion 1.3.2 (meaningful sequence).
Some spoken names differ from the visible labels, which affects voice control users too. For example, the app reads “Add to Calendar” as “Date and Time Add to calendar”. This fails WCAG 2.2 success criterion 2.5.3 (label in name).
Two or three icons have no text alternative, including the calendar icons in event descriptions. You can still read the date and time text next to them. This fails WCAG 2.2 success criterion 1.1.1 (non-text content).
The Home, Preferences, and Theme screens all share the title “MySouthampton”, so you cannot tell them apart by title. This fails WCAG 2.2 success criterion 2.4.2 (page titled).
Keyboard access and focus
You cannot close bottom panels or some pop-up windows with a keyboard. On Android, pressing Escape closes the whole app. This fails WCAG 2.2 success criterion 2.1.1 (keyboard).
If you remove a recipient in Compose Email, your keyboard focus stays trapped in the recipient field and you cannot reach Send. This fails WCAG 2.2 success criterion 2.1.2 (no keyboard trap).
The Calendar events list scrolls without end and holds your keyboard focus, so you cannot reach the bottom navigation to leave Calendar. This fails WCAG 2.2 success criterion 2.1.2 (no keyboard trap).
When a filter window or bottom panel opens, focus stays on the screen behind it. Inside calendar event windows, focus moves to hidden controls you cannot see. This fails WCAG 2.2 success criteria 2.4.3 (focus order), 4.1.2 (name, role, value), and 1.3.2 (meaningful sequence).
After you delete an email, you cannot reach Undo with a keyboard. The “Deleting email” message closes on a timer, and screen readers do not announce it. This fails WCAG 2.2 success criteria 2.1.1 (keyboard), 4.1.3 (status messages), and 2.2.1 (timing adjustable).
Hidden delete buttons take focus before each email in your inbox. If you press Enter on one, you delete the email without seeing the button. This fails WCAG 2.2 success criteria 2.4.11 (focus not obscured (minimum)) and 2.4.7 (focus visible).
The focus outline loses two or three sides on calendar dates, Quick Links, and email list buttons. This fails WCAG 2.2 success criterion 2.4.7 (focus visible).
When you close a pop-up window, focus returns to the top of the screen instead of the button you used to open it. This fails WCAG 2.2 success criterion 2.4.3 (focus order).
Forms and error messages
The event creation and issue reporting forms do not link error messages to their fields. When a form rejects your entry, screen readers say nothing. This fails WCAG 2.2 success criterion 3.3.1 (error identification).
Touch and gestures
About five controls, including the bottom panels and the calendar expand and collapse control, work only when you drag or swipe. If you use switch access or voice control, you cannot operate them. This fails WCAG 2.2 success criteria 2.5.1 (pointer gestures) and 2.5.7 (dragging movements).
The formatting buttons in the email editor act as soon as you touch them. If you touch the wrong button, you cannot cancel by sliding your finger off. This fails WCAG 2.2 success criterion 2.5.2 (pointer cancellation).
Text size, zoom, and orientation
At 150–200 per cent text size, fixed headers and footers fill the screen in Calendar, More, and the filter windows. At 400 per cent zoom, controls overlap and some features stop working. This fails WCAG 2.2 success criteria 1.4.4 (resize text) and 1.4.10 (reflow).
In landscape view, the app cuts off content in Calendar, Quick Links, and pop-up windows. This affects you if you mount your device in landscape, for example on a wheelchair. This fails WCAG 2.2 success criterion 1.3.4 (orientation).
Colour and contrast
In high contrast modes, error text and hover states fall below a contrast ratio of 4.5:1. The colour pickers in the email editor ignore your system contrast settings. This fails WCAG 2.2 success criterion 1.4.3 (contrast (minimum)).
Pale blue button backgrounds and pop-up cards without borders fall below a contrast ratio of 3:1. This fails WCAG 2.2 success criterion 1.4.11 (non-text contrast).
What we are doing to improve accessibility
We will fix the problems that stop you using Calendar, Email, and the support forms first, and aim to release improvements over the coming months.
Preparation of this accessibility statement
This statement was prepared on 9 October 2026.
This mobile application was last tested on 9 October 2026 against the WCAG 2.2 AA standard.
LearningMate Solutions (UK) Limited carried out the test using Manual and automated tests, Windows 11, Firefox, NVDA, CCA, axe DevTools, browser developer tools, TalkBack (Android) and VoiceOver (iOS).