Accessibility improvements

In the accessibility statement u:space applications are listed that are not accessible. We are trying to gradually remove the barriers that currently exist.

On this page you find a list of resolved problems.

Resolved until May 2023

My u:card

Navigation is inconsistent in some parts (2.4.3 Focus Order). Certain screen readers (TalkBack) do not read out error messages correctly (3.3.1 Error Identification). Some form elements are announced inconsistently by screen readers (3.2.4 Consistent Identification). The colour contrast of some elements is too low (1.4.3 Contrast (Minimum)). Assistive technologies do not read out some messages and contents and/or do not read them out at the right time (4.1.3 Status Messages, 1.3.1 Information and Relationships).

Registration for students

Some WAI-ARIA attributes are not used correctly (1.1.1 Non-text Content). Text descriptions of errors are missing in some assistive technologies (3.3.1 Error Identification).

Resolved until September 2021

Checklist (application for bachelor's, master's and diploma programmes

The colour contrast of some texts is too low (1.4.3 Contrast (Minimum)) and some WAI-ARIA attributes are not used correctly (1.1.1 Non-text Content). Some dynamically generated content and form elements are not pointed out to assistive technology users (1.3.1 Info and Relationships). Some form elements cannot be operated using some assistive technologies (TalkBack) (4.1.2 Name, Role, Value).

Resolved until May 2021

Apply for admission

The colour contrast of some elements is too low (1.4.3 Contrast (Minimum)). Some dynamically generated content and form elements are not pointed out to assistive technology users (1.3.1 Info and Relationships). Assistive technologies do not read out some status messages and/or do not read them out with priority (3.3.1 Error Identification, 4.1.3 Status Messages).

My u:card

Required form fields are not read out as such by some screen readers; text descriptions of the form fields are not read out by some screen readers or are read out incorrectly (3.3.2 Labels and Instructions).

Payment process for the u:card

Some ARIA attributes are not defined correctly. As a result, screen readers do not read out form fields correctly (1.3.1 Info and Relationships). Some form elements cannot be operated using some assistive technologies (TalkBack) (4.1.2 Name, Role, Value).

Record of examinations

The status of some buttons is not specified correctly (4.1.3 Status Messages) and some functions cannot be accessed using a keyboard or assistive technologies (2.1.1 Keyboard). A few texts are hidden to some assistive technologies (VoiceOver on iPhone). As a result, the meaning of the texts is not clear (1.3.1 Info and Relationships).

Resolved until March 2021

General

Users of assistive technology cannot determine what language is currently selected in the language button for the presentation of u:space (1.3.1 Info and Relationships).

Apply for admission

Some buttons cannot be operated with certain assistive technologies (VoiceOver – iOS).

Help

Some contents in the Help section do not have a clear ID (4.1.1 Parsing). Some buttons are not labelled (3.3.2 Labels or Instructions) or cannot be accessed using a keyboard (2.1.1 Keyboard). Some elements do not have a visible keyboard focus indicator (2.4.7 Focus Visible). Navigation within the Help section is not consistent when using assistive technologies (2.4.3 Focus Order).

My documents

The colour contrast of some texts is too low (1.4.3 Contrast (Minimum)), some elements are not applied correctly in the markup language and some form fields are not labelled or are labelled incorrectly (1.1.1 Non-text Contents, 4.1.1 Parsing). Some dynamically generated content and form elements are not indicated to assistive technology users (1.3.1 Info and Relationships, 4.1.3 Status Messages).

Payment process following application for admission

Some screen readers do not automatically read out the text instructions for the form fields (3.2.2 Labels or Instructions). Assistive technologies do not read out some messages and/or do not read them out at the right time (4.1.3 Status Messages).

Personal data

Some ARIA attributes are not defined correctly (1.1.1 Non-text Content). Some form elements cannot be operated using certain assistive technologies (TalkBack) (4.1.2 Name, Role, Value).

Registration for courses

The colour contrast of some texts is too low (1.4.3 Contrast (Minimum)).

Study overview

Some screen readers do not automatically read out the text instructions for the form fields (3.3.2 Labels or Instructions). Some form elements are announced inconsistently by screen readers (3.2.4 Consistent Identification). Some WAI-ARIA attributes are not used correctly (1.1.1 Non-text Content).

Resolved until December 2020

Registration for practical trainings as part of the teacher education programme

The colour contrast of some texts is too low (1.4.3 Contrast (Minimum)) and some WAI-ARIA attributes are not applied correctly (1.1.1 Non-text Content). Some buttons cannot be programmatically determined and/or contain other languages that are not determined and that differ from the rest of the website (1.1.1 Non-text Content and 3.1.2 Language of Parts). Some buttons are not consistently located (3.2.4 Consistent Identification).

Record of examinations

The status of some buttons is not specified correctly (4.1.3 Status Messages) and some functions cannot be accessed using a keyboard or assistive technologies (2.1.1 Keyboard).