Barrierefreiheitserklärung: URZ-Service-Portal

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.

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.

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.

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.

The markings strong and em are general and not representation-related (like b , i or a visual highlighting realized only with CSS).

If content is embedded via CSS, it is not available for users of assistive technologies.

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:

• The screen reader provides information about the position and number of rows of headings.

• The screen reader reads out the (new) row or column heading when the user changes the table row or column.

• Headings are highlighted in a form more suitable for the user.

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.

Further provides autocomplete input suggestions for the field, which users can easily accept. This makes text entry easier.

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 title- and the name -attribute, which is commonly used in programming. The attribute title is given priority at that. Screen readers pronounce the title of the active frame when switching between frames with the keyboard shortcuts.

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:

• Skip constant areas at the top of the page, such as navigation or page header, to go directly to content.

• Switch back and forth between areas

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.