The Friedrich Schiller University Jena strives to make its websites barrier-free accessible in accordance with the national legislation implementing Directive (EU) 2016/2102 of the European Parliament and of the Council.
This accessibility statement applies to https://portal.uni-jena.de as well as for all subdomains in the current layout.
Result of the self-assessment
|Evaluation according to BITV/WCAG||partially compliant|
If you are of the opinion, by an insufficient barrier-free design of the services of the university computer center to be disadvantaged or if we do not process your feedback to your satisfaction, you can contact the enforcement office according to the ThürBarrWebG:
Thuringian State Commissioner for People with Disabilities
+49 361 -573811741
Feedback mechanism and contact details
As a user, you can inform us of deficiencies in compliance with accessibility requirements or request information that is not presented barrier-free.
The IT service center is your first point of contact and will forward your request to the responsible departments.
IT service center
Entrance B, Room 1209
+49 3641 9-404777
|Test step||Why is this checked?|
|220.127.116.11a Alternative texts for control element|
For blind users or for users who disable loading of graphics for faster access times, graphics are not accessible. The text alternative then takes the place of the graphic, it should replace the graphic.
Icon Fonts are fonts that contain icons instead of letters. They are included via CSS and are either not output by assistive technologies or a Unicode equivalent is rendered, which does not convey the meaning in context.
|18.104.22.168b Alternative texts for graphics and objects|
For blind users or for users of plain text browsers, graphics and images are not accessible. The text alternative then takes the place of the graphic, it should replace the graphic.
When objects (such as video files, audio files, or applets) cannot be displayed, short descriptive alternative texts shall allow the user to identify the content.
Icon fonts are fonts that contain symbols instead of letters. They are included via CSS and are either not rendered by assistive technologies or a Unicode equivalent is rendered, which does not convey the meaning in context.
|Test step||Why is this checked?|
|22.214.171.124 Alternative access methods|
Users prefer different access paths to reach content. Some follow hierarchical navigation menus, others use a table of contents (sitemap), still others prefer a search function. Visually impaired users in particular often find their way to the desired content more quickly via a search.
Therefore the offer should provide different ways to access the content.
|Test step||Why is this checked?|
|126.96.36.199d Content structured|
Subdividing content into smaller units makes it easier to use and understand.
Using the provided HTML structural elements ensures that this subdivision is defined and accessible on an abstract level, regardless of presentation. Users who are not comfortable with the default visual presentation of the elements on the page will still be able to find their way around, or they can apply their own more appropriate presentation.
If content is embedded via CSS, it is not available for users of assistive technologies.
|188.8.131.52e Data tables properly structured|
Visually oriented people use the value range, if necessary, in addition to the headings to orient themselves in a data table. It is therefore relatively easy for them to recognize and deal with structural deficiencies, for example changes in the meaning of rows or columns.
Visually impaired and blind users, on the other hand, access the data tables more analytically. They develop an idea of the structure of the table based on the headings and other information available in the context. This idea is the basis for accessing the offered data.
Two conditions must be met for this to be possible and to work:
The table must have a clear structure, the meaning of the rows and columns must be graspable, and it has to be as easy as possible to infer from the headings or supporting contextual information. The headings has to be easy to find and it must be clear which data they refer to, so they must be correctly labeled.
Clear structure is the basis of accessibility of data tables. It is not possible to make a poorly structured data table accessible by special labeling. However, based on a clear, understandable structure, correct markup is useful and important.
Possible applications of table heading markup:
|184.108.40.206 Input fields to user data convey purpose|
Specifying the input purpose allows new assistive technologies to display additional information for form fields that refer to user data, regardless of the field's caption and regardless of the natural language of the offer.
Additional information can be images or icons provided by a browser plugin or external assistive technology that are displayed above or in front of the respective input field, for example when users press a certain key combination. For people who have difficulty reading or prefer to communicate via images, this makes it easier to identify user-related fields in forms.
|220.127.116.11 Skippable areas|
Visually, web pages are structured using means such as headings, columns, or boxes. Thanks to this structuring, the user knows what belongs together, can easily survey what the website has to offer, and can specifically access the content that interests him.
Users who cannot take advantage of this visual order - for example, because they are blind or can only see a small section of the page - depend on the structure being accessible and usable regardless of how it is displayed on the screen. The use of (often invisible) area headers, jump links, or HTML5 elements to mark up regions is essential to this.
For frames, a meaningful title is important for orientation with screen readers. Common screen readers evaluate the
The use of HTML5 elements for regions is now well supported by assistive technologies. However, the additional consideration of a role attribute (WAI ARIA document landmarks) can improve region support.
This allows users to apply region headings, jump links, HTML5 elements for regions, and WAI-ARIA document landmarks, respectively:
|18.104.22.168 Labels of form elements present|
If visible labels are provided, users know what inputs are expected. Errors can be avoided.
Placing labels directly in front of or above the input field conforms to standard design conventions. Even in partial views (e.g. in magnification software), it quickly becomes clear which labeling belongs to which field.
|22.214.171.124 Status messages available programmatically||In many contexts of use, sighted users of web applications receive status messages (some of them temporary) that provide feedback about the outcome of interactions (e.g., the number of items returned when filtering a search results list) or the success or failure of transactions. These messages are equally important to non-visual users and should be available to assistive technologies so that users are aware of them without having to change their current focus or viewpoint.|
The Friedrich Schiller University Jena endeavors to make all offers accessible and to improve all currently non-accessible content.
Due to the technical structure, it is not possible with the current implementation to fully meet all accessibility requirements. We are trying to improve this in the future.