Web accessibility of Staff

Linnaeus University is responsible for this website, the intranet Staff. We want to make sure that as many people as possible can use it. This web page describes how the intranet Staff meets the legal requirements of accessibility to digital public service, any known accessibility problems and how you can report flaws to us so that we can fix these.

How accessible is the website?

We are aware that some parts of the website are not fully accessible. See the section below on content that is not accessible for more information.

What can you do if there are parts of the website that you cannot use?

If you need to take part of content on Staff that is not accessible to you, you can contact us:

Report any flaws in the accessibility of the website

We always strive to improve the accessibility of the website. In case you discover any problems that are not already described below, or if you believe that we do not meet the legal requirements, please contact us and inform us about the problem.

Supervision

The Agency for Digital Government is responsible for supervision of the Law on Accessibility to Digital Public Service. In case you are not pleased with our handling of your comments, you can contact the Agency for Digital Government and inform them about this.

Technical information about the accessibility of the website

This website is partly compatible with the Law on Accessibility to Digital Public Service, due to the flaws described below.

Content that is not accessible

  • Some pictures do not have an alt text. In some cases, these pictures may be information-bearing, which means that visitors who cannot see the picture may miss out on information.
    (WCAG 1.1.1)

  • There are not always alternatives to sound or video. (WCAG 1.2.1)

  • Some videos lack subtitles. (WCAG 1.2.2)

  • We do not always state in the code what role the different parts of a page have. Once we have adjusted this and use the html elements in the right way, we increase the chance of the information being presented correctly regardless of what tools are used by the user. (WCAG 1.3.1)

  • There may be some pages where the contrast between text and background is not adequate, which can make it difficult to read the text. (WCAG 1.4.3)

  • The wording in some links is vague. This means that it can be difficult to know where the link directs you if you do not see the context of the link. (WCAG 2.4.4)

  • On some pages, it can be difficult to navigate using the tab key because it is not clearly marked what field or element is in focus. (WCAG 2.4.7)

  • The language of the page is not specified in the code. (WCAG 3.1.1)

  • Some forms with input fields lack a clear description. (WCAG 3.3.2)

  • Certain element IDs are not unique. This means that the code does not fully validate with the standard. (WCAG 4.1.1)

  • There are some tailor-made components that do not function when using tools. (WCAG 4.1.2)

Problems when using PDF files:

  • Some PDF documents are not machine-readable.

  • Some PDF documents have not been labelled correctly, they can lack headings, titles, etc. This can involve difficulties for people who use screen readers.

Our ambition is to solve all known accessibility problems by 31 December 2020 at the latest.

How we have tested the website

We have carried out a self-assessment (internal testing) of Staff, in which we have used a web accessibility evaluation tool to test the website. 

The latest assessment was carried out on 14 August 2020.
The account was last updated on 17 September 2020.