You are here

Unibuddy Accessibility Information

The following accessibility issues with Unibuddy were identified during the audit by the Shaw Trust in November 2020:  

  • A small number of images have been found with a text alternative (ALT attribute) which is ambiguous. Input fields without a text-alternative have been found during the latest audit. This fails WCAG 2.1 success criteria 1.1.1 Non-text Content. 
  • Some form elements have been found to have unclear labels. Missing notification of mandatory form fields. This fails WCAG 2.1 success criteria 1.1.1 Non-text Content.
  • Some pages across the applications have illogical heading structure. This fails WCAG 2.1 success criteria 1.3.1 Info and Relationships.
  • An aria-label is missing from some links and buttons which are the primary "operating content". This fails WCAG 2.1 success criteria 1.3.3 Sensory Characteristics.
  • Links in blogs page of the Unibuddy platform are not distinguishable from surrounding text using a non-colour identifier. This fails WCAG 2.1 success criteria 1.4.1 Use of Color.
  • A skip to content and scroll to top/bottom of page buttons are provided across the public facing Unibuddy Platform, but it is not at the top of the page. There is no "skip to content" link present on the University Dashboard pages, Ambassador Dashboard or Live events pages. This fails WCAG 2.1 success criteria 2.4.1 Bypass Blocks.
  • The order of focus during navigation of some components in the Unibuddy Platform is not performed in an order that preserves functionality and meaning. This fails WCAG 2.1 success criteria 2.4.3 Focus Order.
  • Link text is descriptive and the link’s purpose is clearly communicated to the user across the majority of the platform. Two exceptions have been found in the University dashboard during the latest audit. Additionally, the Powered by Unibuddy logo and some ambassador pictures sometimes result in empty links. This fails WCAG 2.1 success criteria 2.4.4 Link Purpose (In Context).
  • The autocomplete form fields do not announce the new results found as the screen reader user types. When the popcard is clicked, screen readers do not announce that the screen is opened in the new tab. This fails WCAG 2.1 success criteria 3.2.2 On Input.
  • Some form elements have been found to not have alerts for screen readers. This fails WCAG 2.1 success criteria 3.3.1 Error Identification.
  • Some form elements have been found to have unclear or missing labels. This fails WCAG 2.1 success criteria 3.3.2 Labels or Instructions and 4.1.2 Name, Role, Value.
  • Some input fields lack the "type" attribute to define its purpose. This fails WCAG 2.1 success criteria 1.3.5 Identify Input Purpose.
  • A small number of places in the applications fail the expected colour contrast. This fails WCAG 2.1 success criteria 1.4.11 Non-text Contrast.
  • Some pages across the platform have illogical heading structure. This fails WCAG 2.1 success criteria 2.4.6 Headings and Labels.
  • Some components have been found to not work well with screen readers because they use non-standard markup to change the functionality of an item. This fails WCAG 2.1 success criteria 3.2.4 Consistent Identification.
  • Some form elements have been found to not have error descriptions for screen readers. This fails WCAG 2.1 success criteria 3.3.3 Error Suggestion.
  • When submitting the form, required field errors are not detected by screen readers. This fails WCAG 2.1 success criteria 4.1.3 Status Messages.

Unibuddy expect to have all these issues resolved by 30 April 2021. Further information on accessibility can be found in our accessibility statement.