Accessibility statement for u:space

The University of Vienna is committed to providing an accessible website in accordance with the Austrian Web-Zugänglichkeits-Gesetz (WZG, web accessibility act) as amended to implement the Directive (EU) 2016/2102 of the European Parliament and of the Council of 26 October 2016 on the accessibility of the websites and mobile applications of public sector bodies (OJ L 327 issued on 2 December 2016, p. 1).

This accessibility statement applies to the u:space website under the domain https://uspace.univie.ac.at.  

The texts in u:space use the gender star to include inter-gender, transgender and non-binary people. The gender star may be read by the screen reader as 'pause', 'star' or 'asterisk', sometimes not at all, which creates the effect that only the female form is pronounced.

Status of compliance with the requirements

Due to the aspects that are not compliant listed below, this website is partially compliant with standard AA as specified in the Web Content Accessibility Guidelines (WCAG) 2.1 in accordance with the applicable harmonised European standard European Standard EN 301 549 V2.1.2 (2018-08).

Applications containing content that is not accessible are listed in alphabetic order below. Unless otherwise specified, the issues listed below will be resolved in the next development stage. A contionously updated list of resolved problems can be found on the page Accessibility improvements.

Parts of the website that are not fully accessible

a) Aspects that are not compliant with the accessibility regulations

General information

Some assistive technologies (VoiceOver) do not correctly display the status of some menus (4.1.3 Status Messages).

Apply for admission

The calendar cannot be operated properly when using the text descriptions alone (1.3.1 Info and Relationships). Using some form elements is made difficult and/or not entirely possible with mobile screen readers (VoiceOver, TalkBack) (4.1.2 Name, Role, Value). Information messages are not prioritised during output by some screen readers (TalkBack) (3.3.3 Error Suggestion).

Dashboard (home page)

The purpose of the degree programme tags in the list of degree programmes cannot be perceived by screen reader users (4.1.2 Name, Role, Value). When selecting the profile picture, the name of the profile picture is read out twice by screen readers. For some screen readers (JAWS), the focus jumps to the back of the dialogue field after selecting the profile picture (2.4.3 Focus Order). In the Registrations widget, the details of the registrations are not output by screen readers (4.1.2 Name, Role, Value). When activating the editing mode, some screen readers (TalkBack, JAWS) jump back to the top of the page (2.4.3. Focus Order). In the editing mode, the entire content of the widget is available to screen readers not only the elements relevant for editing (2.4.3. Focus Order). When selecting widgets with VoiceOver, the status of the toggle is read out only after the subsequent focus (3.3.2 Labels or Instructions, 4.1.2 Name, Role, Value).

Emergency text messaging

For some form fields, the label for the current selection is not visible well (2.4.7 Focus Visible).When entering or deleting a telephone number, no explicit confirmation message is displayed (4.1.3 Status Messages). Some assistive technologies do not output error messages (4.1.3 Status Messages). Some interactive elements cannot be used correctly with assistive technologies (4.1.2 Name, Role, Value). Some interactive elements are not output in the correct order by assistive technologies (2.4.3 Focus Order).

Help

The screen reader focus may jump from the help section to the underlying page content in case of VoiceOver on iPhone (2.4.3 Focus Order, 2.4.8 Location).

Library – initial registration

Some WAI-ARIA attributes are not used correctly (1.1.1 Non-text Content). Some screen readers do not read out the text descriptions of some form fields (3.3.2 Labels or Instructions). Some form elements cannot be operated using mobile screen readers (TalkBack). 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).

Payment process for the u:card

Some screen readers do not automatically read out the text instructions for the form fields (3.2.2 Labels or Instructions).

Performance Scholarships

Some buttons are not accessible using a keyboard (2.1.1 Keyboard). Some interactive elements cannot be operated correctly using assistive technologies (4.1.2 Name, Role, Value). Does not apply for screenreaders JAWS and NVDA.

The ‘Performance Scholarships’ tool will be redeveloped in the next development stage. The related accessibility issues will be resolved in the process. There are also other options for applying for a performance scholarship.

Preference and point system

The colour contrast of some elements is too low (1.4.3 Contrast (Minimum)). The order of elements accessed by keyboard navigation does not always correspond with the logical reading order (2.4.3 Focus Order).

Recognitions

Some buttons are not accessible using a keyboard (2.1.1 Keyboard). Some interactive elements cannot be operated correctly using assistive technologies (4.1.2 Name, Role, Value).

The ‘Recognitions’ tool is expected to be replaced with a new accessible tool in 2021. You can also always contact your StudiesServiceCenter regarding the recognitions.

Recognition history

Tooltips cannot be read. (1.1.1 Non-text content). Some assistive technologies (VoiceOver) do not correctly display the status of some menus. (4.1.3 Status Messages).

Registration for courses

Some ARIA attributes are not defined correctly (1.1.1 Non-text Content). Navigation is not always consistent with certain assistive technologies (TalkBack) (3.2.3 Consistent Navigation). Some buttons are not available in text and cannot be identified and/or operated by some screen readers (1.3.1 Info and Relationships and 3.3.2 Labels or Instructions). Some interactive elements cannot be properly operated with some assistive technologies (4.1.2 Name, Role, Value).

Registration overview

Some ARIA attributes are not defined correctly (1.1.1 Non-text Content). Heading levels are not always specified correctly (4.1.1 Parsing). Some assistive technologies (TalkBack) do not read out some headings (4.1.2 Name, Role, Value). Following a query, screen readers do not receive feedback (4.1.3 Status Messages) and the focus does not jump to the search result (1.3.2 Meaningful Sequence and 3.2.2 Predictable on Output). The heading of the individual registrations is not output correctly for screen readers (4.1.2 Name, Role, Value). The screen reader focus does not jump to the first date after expansion (2.4.3 Focus Order). Some input fields are focussed several times by certain screen readers (JAWS, VoiceOver) (3.2.4 Consistent Identification, 3.3.2 Labels or Instructions).

Room details

Some buttons are not labelled (3.3.2 Labels or Instructions). Form elements cannot be operated using some assistive technologies (TalkBack) (4.1.2 Name, Role, Value).

Study documents – PDF

The study documents (PDF) are not tagged (2.4.5 Multiple Ways), the language is not specified in the text (3.1.1 Language of Page, 3.1.2 Language of Parts) and the title of the document is not visible in the title bar (2.4.2 Page Titled). The tab order is not consistent with the sequential navigation order (2.4.3 Focus Order). Tables and lists are not indicated correctly and headings are not organised in an appropriate order (1.3.1 Info and Relationships). The logo of the University of Vienna is not provided as a text alternative (1.1.1 Non-text Contents). The document structure of some documents is not organised logically in accordance with the reading order (1.3.2 Meaningful Sequence).

The barriers related to study documents are going to be removed in the following months. The technical requirements have been recently met.

Tuition fees/Students’ Union fee

Some contents cannot be operated through a keyboard when using assistive technologies (2.1.1 Keyboard).

b) Disproportionate burden

Registering for courses and practical trainings

When registering for courses and/or practical trainings as part of the teacher education programme, students can specify an order according to their preferences. This is currently not possible when using the JAWS screen reader as well as when using screen readers on mobile devices.

This function is based on software that has not been developed by the University of Vienna. Therefore, an adjustment would impose a disproportionate burden as specified in article 5 of the Directive (EU) 2016/2102.

Semester planner

The ‘Semester planner’ tool is a pilot project in individual degree programmes. It is currently not optimised for use on mobile devices and for accessible use.

Therefore, resolving the associated accessibility issues would impose a disproportionate burden as specified in article 5 of the Directive (EU) 2016/2102.

Third party content

Payment by credit card is processed via a given integrated interface offered by the credit card companies. These barriers might appeare during the payment process: Some screenreaders (TalkBack, VoiceOver) do not read the mandatory field labels and the error messages.

This function is based on software that has not been developed by the University of Vienna. Therefore, an adjustment would impose a disproportionate burden as specified in article 5 of the Directive (EU) 2016/2102.

Release of this accessibility statement

This statement has been released on 23 September 2020 and has been updated on 2 May 2023.

Feedback and contact details

The offers and services provided on this website are being continuously improved, replaced and expanded. Usability and accessibility are our key concerns in this endeavour.

Please send us an e-mail if you encounter any accessibility problems that prevent you from using our website. This applies to issues that are not listed in this accessibility statement or shortcomings relating to the accessibility requirements.

We will examine your request and contact you as soon as possible.

Please send all your messages and suggestions to wzg@univie.ac.at. Describe the problem you encountered and provide the URL(s) of the website or document concerned.

Contact:
University of Vienna
Universitätsring 1, 1010 Vienna
wzg@univie.ac.at

Enforcement procedure

If you are not satisfied with how we respond to your request sent to us using the contact option specified above, you can contact the Austrian Research Promotion Agency (FFG) and file a complaint. You can file your complaint with the FFG by electronic means using the contact form.

Contact form of the FFG complaints office:
www.ffg.at/form/kontaktformular-beschwerdestelle (in German)

The FFG will investigate your complaint to determine whether the accessibility issues you addressed represent a violation of the provisions specified in the Austrian Web-Zugänglichkeits-Gesetz (web accessibility act), in particular shortcomings in compliance with the accessibility requirements, by the Federal Government or an institution affiliated with the Federal Government.

If the compliant is justified, the FFG issues recommendations to the Federal Government or the legal entity concerned and proposes measures that aim at resolving the issue.

Further information about the complaints procedure:
www.ffg.at/barrierefreiheit/beschwerdestelle