Web accessibility statement for Tampere Universities
Web accessibility statement for Tampere Universities
The updated accessibility statement has been published on 6 July 2023 and updated on 16 May 2024
Organisation: Tampere Universities
Website/application: www.tuni.fi
The accessibility of the digital service has been assessed by third party.
This statement is based on the assessment conducted by third party and will be updated as the identified issues are resolved.
The digital service referred to herein partly meets the critical Level A and AA requirements.
The digital service contains the following content that is not accessible
When the focus is on a component, the focus is not always clear enough
When the focus is in the tab option, the contrast ratio of the focus to the adjacent color is less than the allowed 3:1.
On mobile, focus is not visible, for example with Skip to content button, breadcrumb and language selection, and the close menu button when stepping backwards.
When returning from the Content and Search menu, the focus is not visible.
WCAG 2.1: 2.4.7 Focus Visible: Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. (Level AA)
Links lead to another site without mention/icon
Some of the links lead to another web address, but there is no mention or icon of this in connection with the link.
WCAG 2.1: 2.4.4 Link Purpose (in context): The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general. (Level A)
WCAG 2.1: 3.2.4 Consistent Identification: Components that have the same functionality within a set of Web pages are identified consistently. (Level AA)
There is not always a mention of links opening in a new window
Some of the links will open in a new window, but this is not always mentioned with the link.
WCAG 2.1: 2.4.4 Link Purpose (in context): The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general. (Level A)
WCAG 2.1: 3.2.4 Consistent Identification: Components that have the same functionality within a set of Web pages are identified consistently. (Level AA)
Links change the language of the site without prior warning
There are links on the pages that change the language of the whole site, but this is not always stated in connection with the link.
WCAG 2.1: 2.4.4 Link Purpose (in context): The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general. (Level A)
WCAG 2.1: 3.2.4 Consistent Identification: Components that have the same functionality within a set of Web pages are identified consistently. (Level AA)
Link icons mislead the user
Some of the links to another web address have incorrectly an internal link icon, and some of the internal links on the site have incorrectly an external link icon.
WCAG 2.1: 2.4.4 Link Purpose (in context): The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general. (Level A)
WCAG 2.1: 3.2.4 Consistent Identification: Components that have the same functionality within a set of Web pages are identified consistently. (Level AA)
Unclear or missing link texts
The website contains links whose purpose or destination is not sufficiently apparent from the link text itself (e.g. here) or they are http addresses. YouTube video links lack a link text describing the actual content when cookies are disabled.
WCAG 2.1: 2.4.4 Link Purpose (in context): The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general. (Level A)
The service contains files that do not meet the accessibility requirements
Some PDF forms and files are not accessible by a screen reader.
WCAG 2.1: 4.1.2 Name, Role, Value: For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies. (Level A)
WCAG 2.1: 2.4.3 Focus Order: If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability. (Level A)
Text in different languages is not indicated
The pages contain text in other languages that is not marked, which means that the screen reader reads them in the language of the page. The site also has some texts in other languages that should be in Finnish, e.g. when the search found nothing.
WCAG: 3.1.2 Language of Parts: The human language of each passage or phrase in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text. (Level AA)
Header structures partially incorrect
The use of site headings does not comply with the requirements of hierarchy and logic on all pages, for example. there is no heading text, heading levels are in the wrong order, or some heading levels are skipped.
WCAG 2.1: 1.3.1 Info and Relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. (Level A)
WCAG 2.1: 2.4.1 Bypass Blocks: A mechanism is available to bypass blocks of content that are repeated on multiple Web pages. (Level A)
Some buttons lack a name, the name is not clear, or it is in a different language
Individual buttons do not have a name that indicates their purpose or content for assistive technologies.
Some buttons are named in a different language than the language of the site.
WCAG 2.1: 4.1.2 Name, Role, Value: For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies. (Level A)
Unclear text alternatives for images in different languages
Not all image elements on the site have a text alternative that indicates their purpose or content to assistive technologies, or the text alternative is unclear or it is the filename of the image. Some images have text equivalents in a different language. On some pages, some images have a text alternative in the same section, while others have it marked as blank.
WCAG 2.1: 1.1.1 Non-text Content: All non-text content that is presented to the user has a text alternative that serves the equivalent purpose. (Level A)
WCAG 2.1: 3.2.4 Consistent Identification: Components that have the same functionality within a set of Web pages are identified consistently. (Level AA)
Not everything is consistently labeled
Some buttons are difficult to understand as buttons because they lack frames.
Some links look more like text than a link.
On a narrow screen advanced search has a confirm selections button, which is missing on large screens.
On the big screen, the advanced search doesn't have a dedicated Confirm Selections button, but the narrow screen does.
The main menu, breadcrumb and search section are different in different entities.
When searches don't find anything in different sections, the answers are different.
WCAG 2.1: 3.2.4 Consistent Identification: Components that have the same functionality within a set of Web pages are identified consistently. (Level AA)
Not all lists are marked as lists
Lists appear on pages that are not marked as lists.
WCAG 2.1: 1.3.1 Info and Relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. (Level A)
Navigation browses invisible components
The breadcrumb is not visible on mobile, but mobile navigation goes it through.
In advanced search, as well as in the menu and search menu, there are invisible fields that navigation goes through on mobile.
On the research pages, if a person does not have a picture, then navigation will go through the place reserved for the image.
WCAG 2.1: 3.2.3 Consistent Navigation: Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user. (Level AA)
WCAG 2.1: 1.4.10 Reflow: Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions. (Level AA)
Using advanced search filters is tricky
Some of the filters in Advanced search hides the other options, so the user has to select the Show All option in order to select some other filter.
WCAG 2.1: 3.2.3 Consistent Navigation: Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions. (Level AA)
Screen reader reads event registration information illogically
On the screen reader, the registration button is read in the middle of the basic information of the event, and not after the basic information.
WCAG 2.1: 3.2.3 Consistent Navigation: Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions. (Level AA)
Using advanced search changes the browsing context unpredictably
When the advanced search checkboxes are targeted or one of the available options is selected, the advanced search functionality disappears and the displayed search results dynamically change according to the selected option before the user confirms the selection, with the exception of narrow screens. In this case, the user is also not informed of the changing context in advance.
WCAG 2.1: 3.2.1 On Focus: When any user interface component receives focus, it does not initiate a change of context. (Level A)
WCAG 2.1: 3.2.2 On Input: Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component. (Level A)
WCAG 2.1: 4.1.3 Status Messages: In content implemented using markup languages, status messages can be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus. (Level AA)
As a result of the increase in text size, individual texts are hidden from the user
On the IT services pages, some link texts do not wrap and thus remain invisible.
WCAG 2.1: 1.4.4 Resize text: Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality. (Level AA)
Increasing the text size does not enlarge all texts
Increasing the text size does not enlarge the text in the chat window.
WCAG 2.1: 1.4.4 Resize text: Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality. (Level AA)
Enlarging the screen causes problems
When the screen is enlarged or viewed on a small screen, some of the content is lost e.g.
- The text at the top of the cookie banner is hidden
- Pagination in advanced search partially hides
- The chat button disappears
WCAG 2.1: 1.4.10 Reflow: Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions. (Level AA)
Part of the text is in a different language
Advanced search results contain text and link names in different languages.
WCAG: 3.1.2 Language of Parts: The human language of each passage or phrase in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text. (Level AA)
A single component has a name in a different language
The name of the chat window is in a different language.
WCAG 2.1: 4.1.2 Name, Role, Value: For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies. (Level A)
Embedded YouTube videos have contrast issues
When cookies are enabled, the buttons and title of YouTube videos don't always meet the contrast requirements against the background.
WCAG 2.1: 1.4.3 Contrast (Minimum) (AA): The visual presentation of text and images of text has a contrast ratio of at least 4.5:1. (Level AA).
WCAG 2.1: 1.4.11 Non-text Contrast: The visual presentation has a contrast ratio of at least 3:1 against adjacent color(s). (Level AA).
Some pages have chat window that is not fully accessible
The chat button breaks the consistent navigation order
On pages with a chat button, its focus order is before Skip to main content.
WCAG 2.1: 2.4.1 Bypass Blocks: A mechanism is available to bypass blocks of content that are repeated on multiple Web pages. (Level A)
WCAG 2.1: 3.2.3 Consistent Navigation: Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions. (Level AA)
The contrast ratio of a few buttons to the adjacent color is not sufficient
The chat function has buttons with a contrast ratio to the adjacent color below the required 3:1.
WCAG 2.1: 1.4.11 Non-Text Contrast: The visual presentation has a contrast ratio of at least 3:1 against adjacent color(s) (Level AA).
The contrast ratio of individual texts with background is not sufficient
The chat function has some texts that have a contrast ratio to the background colour or background image below the allowed 4.5:1.
WCAG 2.1: 1.4.3 Contrast (minimum) (AA): The visual presentation of text and images of text has a contrast ratio of at least 4.5:1. (Level AA).
When a component receives focus, the focus is not always clear enough
When a component receives a focus, the focus is not visible at all in the chat button and chat window functions.
WCAG 2.1: 2.4.7 Focus Visible: Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. (Level AA)
The status of individual components is not indicated by a screen reader
The status of the chat window is not determined.
WCAG 2.1: 4.1.2 Name, Role, Value: For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies. (Level A)
In the chat window, the screen reader always reads the entire conversation
In the chat window, after adding your own message, the screen reader reads the entire conversation.
WCAG 2.1: 1.1.1 Non-text Content: All non-text content that is presented to the user has a text alternative that serves the equivalent purpose. (Level A)
A single component has a name in a different language
The name of the chat window is in a different language.
WCAG 2.1: 4.1.2 Name, Role, Value: For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies. (Level A)
Some pages have Thinglink embeds that are not fully accessible
In mobile, focus is not always clearly visible
The focus button is so large that it is difficult to know which component the focus is on.
The focus is not visible because the button may hide behind other buttons.
The focus is implemented by enlarging the button, which is sometimes difficult to detect.
WCAG 2.1: 2.4.7 Focus Visible: Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. (Level AA)
The additional information window does not get focus when using a screen reader
The additional information window does not get focus when using a screen reader, allowing you to browse only the underlying elements.
WCAG 2.1: 2.4.7 Focus Visible: Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. (Level AA)
When a component receives focus, the focus is not always clear enough
When the buttons receive focus in the additional info window, the contrast ratio of the focus to the adjacent color is less than the allowed 3:1.
WCAG 2.1: 2.4.7 Focus Visible: Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. (Level AA)
The info window disappears when you hover it
The info window disappears when you hover it.
WCAG 2.1: 1.4.13 Content on Hover or Focus: Where receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden. (Level AA)
The contrast ratio of individual buttons to the adjacent color is not sufficient
The site has a few buttons with a contrast ratio to the adjacent color below the required 3:1:
- The button that can be used to look around the image does not meet the contrast requirements on top of the image.
- The Close and Immersive Reader buttons in the additional info window do not meet the contrast requirements on top of the image.
- Close button on the VR headset start screen
WCAG 2.1: 1.4.11 Non-text Contrast: The visual presentation has a contrast ratio of at least 3:1 against adjacent colors. (Level AA).
When the focus is on the button, the focus is not clear enough
When the focus is on the button, the contrast ratio of the focus to the adjacent color is less than the allowed 3:1.
WCAG 2.1: 2.4.7 Focus Visible: Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. (Level AA)
Links look like buttons
The links in the additional info windows look like a button.
WCAG 2.1: 3.2.4 Consistent Identification: Components that have the same functionality within a set of Web pages are identified consistently. (Level AA)
It is not possible to change the angle of the view on the keyboard
The button to look around doesn't work on the keyboard.
WCAG 2.1: 2.1.1 Keyboard: All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints. (Level A)
Visited status of pages is not reported
In the menu of other pages, an icon is indicating if the page in question has been visited, but the information is not available for a screen reader.
WCAG 2.1: 4.1.2 Name, Role, Value: For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies. (Level A)
The Other pages button does not provide status of the more information window
The Other pages button does not tell you whether the more information window is open or closed.
WCAG 2.1: 4.1.2 Name, Role, Value: For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies. (Level A)
360-degree image rotation cannot be stopped
The 360-degree image rotates automatically on its own and cannot be stopped by the user.
WCAG 2.1: 2.2.2 Pause, Stop, Hide: For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it unless the movement, blinking, or scrolling is part of an activity where it is essential; and For any auto-updating information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it or to control the frequency of the update unless the auto-updating is part of an activity where it is essential. (Level A)
The user is not told when the search found nothing
When the search for other pages finds nothing, it is not told to the user.
WCAG 2.1: 1.1.1 Non-text Content: All non-text content that is presented to the user has a text alternative that serves the equivalent purpose. (Level A)
Some buttons lack a name, the name is not clear, or it is in a different language
Individual buttons do not have a name that indicates their purpose or content for assistive technologies.
Some buttons have a name in different language, than what is the language of the site.
The name of the Exit fullscreen button does not match the function.
WCAG 2.1: 4.1.2 Name, Role, Value: For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies. (Level A)
WCAG 2.1: 2.4.4 Link Purpose (in context): The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general. (Level A)
Navigation moves to browse the page in the background
After going through the Other pages window, navigation starts to browse the actual page in the background.
WCAG 2.1: 3.2.3 Consistent Navigation: Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user. (Level AA)
Links lead to another site without a mention or icon
Some links lead to another web address, but this is not indicated by a text or an icon.
WCAG 2.1: 2.4.4 Link Purpose (in context): The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general. (Level A)
WCAG 2.1: 3.2.4 Consistent Identification: Components that have the same functionality within a set of Web pages are identified consistently. (Level AA)
With a single button, the name does not match the name tag
The name indicating the Thinglink button's content for assistive technologies does not match the name tag.
WCAG 2.1: 2.5.3 Label in Name: For user interface components with labels that include text or images of text, the name contains the text that is presented visually. (Level A)
The contrast of the info buttons is not always sufficient
The contrast ratio of red info buttons to the background color is sometimes below the allowed 3:1.
WCAG 2.1: 1.4.11 Non-Text Contrast: The visual presentation has a contrast ratio of at least 3:1 against adjacent color(s) (Level AA).
The focus order is not always logical
The focus order of the image info buttons is not always logical.
WCAG 2.1: 2.4.3 Focus Order: If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability. (Level A)
Unclear link texts
The website contains links whose purpose or destination is not sufficiently apparent from the link text itself (e.g. here) or they are http addresses. YouTube video links lack a link text describing the actual content.
WCAG 2.1: 2.4.4 Link Purpose (in context): The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general. (Level A)
The name shown on individual buttons is not descriptive
The name shown on individual buttons does not clearly describe the function of the button, e.g. Read More.
WCAG 2.1: 2.4.6 Headings and Labels: Headings and labels describe topic or purpose. (Level AA)
Images in additional info windows lack text alternatives
Not all image elements in Additional information window have a text alternative that indicates their purpose or content for assistive technologies.
WCAG 2.1: 1.1.1 Non-text Content: All non-text content that is presented to the user has a text alternative that serves the equivalent purpose. (Level A)
WCAG 2.1: 3.2.4 Consistent Identification: Components that have the same functionality within a set of Web pages are identified consistently. (Level AA)
The additional info window doesn't get focus, so navigation browses the page in the background
Navigation is going through the actual page in the background because the additional information window is not getting focus.
WCAG 2.1: 3.2.3 Consistent Navigation: Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user. (Level AA)
Viewing the image of the additional info window in full size is not possible
You can enlarge an image in the additional info window, but because there is no scroll bar in the window, the enlarged image is only partially visible.
It is not possible to reduce the enlarged image in the additional info window
In the additional information window, it is not possible to return from the enlarged image to the reduced image, and there are no separate instructions on how to get out.
WCAG 2.1: 2.1.2 No Keyboard Trap: If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away. (Level A)
Timetable
Most of the above shortcomings will be addressed during 2024.
Feedback
You can give feedback on accessibility by email to verkkosaavutettavuus at tuni.fi. Name the message "Accessibility feedback".
If you find accessibility problems on the site, first give feedback to the person maintaining the page. Depending on the workload, getting a response may take up to two weeks. If you are not happy with the response or get no response within two weeks, you can notify the supervisory authority.
Contact details of the supervisory authority:
Regional State Administrative Agency of Southern Finland
Unit for supervising accessibility
https://www.saavutettavuusvaatimukset.fi
saavutettavuus [at] avi.fi (saavutettavuus[at]avi[dot]fi)
telephone switchboard 0295 016 000