Accessibility Statement

This accessibility statement applies to the website https://telucation.tugraz.at. (external site)

Measures for accessibility

Graz University of Technology takes the following measures to ensure accessibility of its websites:

• Website accessibility is part of our technical, graphical and editorial guidelines.
• We take the following editorial measures to make content accessible: on the website as a whole, through a WordPress theme that enables accessibility; in texts, through predefined headings and format templates; for images, through alternative texts and captions; for videos, through subtitles; for audio, through transcripts; through accessible documents and accessible web forms.
• Guidelines and opportunities for further training on accessibility are provided for website editors.
• We conduct regular quality checks of websites in terms of accessibility.
• We involve people with disabilities in the development of website accessibility.

Status of compliance with requirements

This website is partially compliant with compliance level AA of the Web Content Accessibility Guidelines – WCAG 2.1. (external site)

Non-accessible content

The content listed below is only partially accessible or not accessible for the following reasons:

• Videos: Since linked videos are mostly hosted on the video platform Youtube or TUbe, it is currently not possible to provide audio descriptions for these videos.
• Documents: Some documents, such as the author’s guide in PDF format, are not yet accessible. For resource reasons, there is currently no accessible alternative to the PDF files of the English TELucation articles, but the articles can be read online as an accessible version.
• Color contrast: Deviations from the required color contrast cannot be ruled out for logos or in exceptional cases for colored boxes with text content.
• Navigation with keyboard: The page is in principle navigable by keyboard, but the current position is not always highlighted.
• Heading formats: Some of the headings in the category overview are tagged as h3 instead of h1. This is a bug that is being worked on to fix.
• Überschriftenformate: Die Überschriften in der Kategorienübersicht werden zum Teil als h3 statt als h1 getaggt. Dies ist ein Bug, an dessen Behebung gearbeitet wird.

Creation of this accessibility statement

This declaration was created on 2.12.2021.

This declaration was created based on a self-assessment conducted by Graz University of Technology.

Verification of compliance with the WCAG 2.1 guidelines is planned through regular self-assessment.

Feedback and contact details

The content of our website is constantly being revised and improved. Usability and accessibility are of great concern to us.

If you notice any barriers that prevent you from using our website, please let us know. Please send all suggestions to telucation@tugraz.at. Please describe the problem and include the URL of the affected web page.

Enforcement prodecure

In the event of unsatisfactory responses from the above contact option, you may contact the Complaints Office of the Austrian Research Promotion Agency with Limited Liability (FFG) by means of a complaint. The FFG accepts complaints electronically via the contact form of the Complaints Office. (external site)

The complaints are examined by the FFG to determine whether they relate to violations of the requirements of the Web Accessibility Act, in particular deficiencies in compliance with accessibility requirements, by the federal government or an institution attributable to it.

If the complaint is justified, the FFG must issue recommendations for action to the federal government or the legal entities concerned and propose measures to remedy the deficiencies at hand.

Further information on the complaint procedure (external site)

Accessibility Statement 2026

In 2026 the website was migrated from WordPress to a statically generated site (SvelteKit). The target standard of the rebuild is WCAG 2.2 conformance level AA, i.e. EN 301 549. This section describes the current state: what is tested automatically before every release, what the rebuild paid attention to, and which items still need to be checked manually.

Automated checks before every release

Before every release a test suite runs over all pages in both languages. The list of tested pages is generated from the content itself, so new pages are covered automatically. The suite checks:

• axe-core (WCAG 2.0/2.1 level A and AA as well as WCAG 2.2 AA) on every page in both languages – additionally in operated states (expanded submenu, opened accordions) and in Windows high-contrast mode (forced colors).
• Heading structure: The first heading of every page is an h1, heading levels do not skip (WCAG 1.3.1).
• Keyboard operation: The skip link becomes visible on focus and jumps to the main content (WCAG 2.4.1). The two-level menu reports its state via aria-expanded, Escape closes it and returns focus.
• Focus indicator: Every link and every button has a visible focus ring with a contrast of at least 3:1 against its actual background (WCAG 2.4.7, 1.4.11) – measured at 1280 px and 375 px viewport width.
• Contrast of controls: Borders and fills of buttons reach at least 3:1 against their background (WCAG 1.4.11).
• Links are underlined, not distinguished by colour alone (WCAG 1.4.1). External links carry a text equivalent for screen readers and do not open in a new window unasked.
• Target sizes: Controls are at least 24 px tall, also at a viewport width of 320 px (WCAG 2.5.8).
• No horizontal scrolling at 320 px width or at 200% zoom (WCAG 1.4.4, 1.4.10). Increased letter, word and line spacing does not break the layout or clip any content (WCAG 1.4.12).
• The language switcher leads to the counterpart of the current page, not to an error page.
• The website remains fully usable without JavaScript: navigation and content are laid open, buttons that would have no effect are hidden. The checks also run with JavaScript disabled.
• Functional check: The controls are actually operated and the pages are monitored for script errors and missing resources.

Checks at content-authoring time

In addition, the website’s data model enforces accessibility while content is being written – violations prevent publication:

• Every image needs either a meaningful alternative text or an explicit marking as decorative (WCAG 1.1.1).
• Every audio recording (podcast) needs a transcript (WCAG 1.2.1).
• No content exists in one language only. English terms within German text are marked as such so that screen readers pronounce them correctly (WCAG 3.1.1, 3.1.2).
• External links cannot be written without a text equivalent. All references are checked for valid, encrypted addresses.

What the rebuild paid attention to

• Statically generated pages: All content is contained in the delivered HTML, no content depends on JavaScript.
• Semantic HTML with landmarks (header, navigation, main content, footer) and correct ARIA states. The navigation follows the recommended disclosure pattern instead of a menu role.
• Colours are defined centrally and designed for the contrast requirements of level AA. Background and text colour are always set together so that no unreadable combinations can occur.
• System settings for readability are respected: If “Reduce transparency” or “Increase contrast” is enabled in the operating system and the browser passes this setting on, page headers and bands with a background photo show a plain colour instead – white text on dark blue with a contrast ratio of about 12:1 instead of the 6:1 guaranteed by the veil over the photo (WCAG 1.4.3, 1.4.6). Even without this setting, every photo lies beneath a dark overlay so that the text remains readable regardless of what the image shows. With “Reduce motion” enabled, animations and smooth scrolling are switched off (WCAG 2.3.3).
• The content taken over from WordPress was migrated in a structured way: heading hierarchies, alternative texts, transcripts and accessible document versions are part of the content records.

Still to be checked manually

• TODO: Screen reader walkthrough (e.g. NVDA, VoiceOver) of the main page types – automated tests do not replace a usage test.
• TODO: Review the documents taken over from WordPress (PDF, DOCX) for accessibility. Accessible versions were migrated but have not yet been re-checked.
• TODO: Check subtitles and descriptions of the linked or embedded videos (YouTube, TUbe).
• TODO: Editorially review the quality of the migrated alternative texts – the automated check only ensures that they exist and are not too short.
• TODO: Update the section “Non-accessible content” above – it still describes the state of the former WordPress website (WordPress theme, heading bug, English labels).
• TODO: Update the creation date and self-assessment of this statement once the manual checks are complete.

Updated: 2 September 2026