This accessibility statement applies to the MySouthampton App, version 1.0.136, published 20th April 2026
The University of Southampton runs this mobile application. We want as many people as possible to be able to use it. For example, that means 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 this app is
We know some parts of this app are not fully accessible:
- you cannot use the app in landscape orientation because we only support portrait
- some content on the home page does not read correctly with a screen reader, because we have used the wrong role on the events carousel
- the reading order is wrong in places, including the email content view and the More menu
- focus does not move into dialogue boxes on the calendar page, so screen reader users cannot read or interact with their content
- the buttons in the email compose toolbar are unlabeled, so screen readers cannot announce what they do.
- the email composing form fields do not have a clear focus indicator.
- text and icons in the email compose toolbar fail colour contrast in dark mode.
- splash screen content gets cut off when you zoom to 150% or more, and parts disappear at 300% and 400%.
- there are no spoken announcements when you send an email, delete an email, or add and remove an event from your favourites.
- on the Theme page, screen readers do not announce the labels or the checked state of the radio buttons.
- on the splash screen, swiping right with TalkBack moves to the next slide instead of the Skip button.
Feedback and contact information
If you find any problems not listed on this page, or you think we are not meeting accessibility requirements, contact [contact details for the team responsible for the app].
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 in two 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
The app has been tested against the Web Content Accessibility Guidelines (WCAG) 2.2 AA standard.
This app 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
Orientation
The app only supports portrait orientation. You cannot rotate your device to landscape. This fails WCAG 2.2 success criterion 1.3.4 (Orientation). We are reviewing this with our supplier and will confirm a fixed date once we have agreed the approach.
Information and relationships
Some content uses incorrect semantic structure. For example, the home page events carousel uses a slider role that hides its content from screen readers, and the More menu uses an unordered list element with no list items. This fails WCAG 2.2 success criterion 1.3.1 (Info and Relationships). We plan to fix the issues we have scheduled in coming sprints from May 2026.
Meaningful sequence and focus order
The reading order is wrong in the email content view, the More page and parts of the calendar. Focus does not move into dialogue boxes on the calendar page, and the Theme page nests interactive elements inside other interactive elements. This fails WCAG 2.2 success criteria 1.3.2 (Meaningful Sequence) and 2.4.3 (Focus Order). We plan to fix the issues we have scheduled in coming sprints from May 2026. The Theme page changes need wider framework discussion before we can confirm a date.
Name, role and value
The buttons in the email compose toolbar are unlabeled. The Theme page radio buttons do not announce their labels or their checked state. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value). The email compose toolbar uses the third-party Quill editor and needs a library-level fix; we are raising this with the supplier. We plan to fix the Theme page issues once we have agreed the framework changes with our development team.
Status messages
The app does not announce when you send an email, delete an email, or add and remove an event from your favourites. This fails WCAG 2.2 success criterion 4.1.3 (Status Messages). We plan to fix this in coming sprints from May 2026.
Focus visible
The ‘To,’ ‘Cc,’ ‘Subject’ and message fields on the email compose page do not show a clear focus indicator. This fails WCAG 2.2 success criterion 2.4.7 (Focus Visible). We plan to fix this once we have completed the component-level changes required and will confirm a date.
Contrast
The Styles, Foreground colour, Background colour and Align buttons in the email compose toolbar fail minimum contrast ratios when expanded. The same icons fail non-text contrast in dark high-contrast mode. This fails WCAG 2.2 success criteria 1.4.3 (Contrast (Minimum)) and 1.4.11 (Non-text Contrast). These are limitations of the Quill editor and need a library-level fix.
Resize text and reflow
Splash screen content gets cut off when you zoom to 150% or more, the chevron buttons become unusable at 200%, and the ‘Visit our website’ button is cut off at 400%. This fails WCAG 2.2 success criteria 1.4.4 (Resize text) and 1.4.10 (Reflow). We plan to change the component behavior at zoom and will confirm a date.
Pointer gestures and cancellation
On the splash screen, swiping right with TalkBack moves to the next slide instead of the Skip button. The toolbar buttons in the email compose page expand or collapse on mouse-down rather than mouse-up, and they also respond to right-click. This fails WCAG 2.2 success criteria 2.5.1 (Pointer Gestures) and 2.5.2 (Pointer Cancellation). We need to restructure the onboarding screen for the first issue. The toolbar issues are Quill editor limitations.
Error prevention
Pressing Delete on an email removes it without a confirmation step. This fails WCAG 2.2 success criterion 3.3.4 (Error Prevention (Legal, Financial, Data)). We plan to fix this in coming sprints from May 2026.
Label in name
Some buttons on the home page have an accessible name that does not contain their visible label. For example, screen readers read the ‘Add to Calendar’ button as “Date and Time Add to calendar.” This fails WCAG 2.2 success criterion 2.5.3 (Label in Name). We plan to fix this in coming sprints from May 2026.
Headings and labels
The disabled state on Academic and PAT cards is announced as “Disabled” with no further context. This fails WCAG 2.2 success criterion 2.4.6 (Headings and Labels). We plan to fix this in coming sprints from May 2026.
What we are doing to improve accessibility
Our supplier has scheduled eighteen fixes for delivery in sprints from May 2026. A further fourteen issues need wider discussion with the University because they depend on framework changes or affect a larger part of the app. We are working with our supplier to agree the approach and timing for these.
Preparation of this accessibility statement
This statement was prepared on 27 April 2026. It was last reviewed on 19 May 2026.
This app was last tested on 24 April 2026 against the WCAG 2.2 AA standard.
The test was carried out by LearningMate Solutions (UK) Limited. They tested the app using Windows 11, Firefox, NVDA, Colour Contrast Analyser, axe DevTools and browser developer tools, together with TalkBack on a real Android device.