This website is run by Chalmers University of Technology. We want as many people as possible to be able to use it, and this document describes how chalmers.se complies with the accessibility regulations, any known accessibility issues, and how you can report problems so that we can fix them.
How accessible is the website?
We know some parts of this website aren’t fully accessible. See the section on non-accessible content below for more information.
What to do if you can’t access parts of this website?
If you need content from this website in a different format, for example an accessible pdf or with enlarged text, please contact us the following way:
Our normal response time is 2-5 days.
Reporting accessibility problems with this website
We’re always looking to improve the accessibility of this website. If you find any problems that aren’t listed on this page or if we’re not meeting the requirements of the accessibility regulations, please let us know about the problem. Use the form 'Leave feedback' that is available at the bottom of our webpages.
The Agency for Digital Government is responsible for enforcing the accessibility regulations. If you’re not happy with how we respond to your complaint about web accessibility or your request to make content accessible, submit a complaint to the Agency for Digital Government.
Technical information about this website’s accessibility
This website is to a large degree compliant with level AA of the Web Content Accesibility Guideline version 2.1. Web content that is not fully accessible is listed below. We work continuously in order to address problems.
- Visible label and accessible name do not correspond in a few places. Using two different names for a single page element can create a confusing user experience for assistive technology users. For example, speech-input users may have difficulty activating a control if the label displayed on-screen does not match its accessible name. WCAG 4.1.2, WCAG 2.5.3
- A few content blocks fetched from a database are empty, which leads to missing information in the content structure, and how page elements fit together. WCAC 1.3.1
- There are instances of element-IDs that are not unique on a page. Sometimes it's important to know how different page elements fit together. Whereas sighted visitors may be able to get this information from the visual layout, visitors using screen readers rely on page elements being marked up correctly in the HTML. WCAG 4.1.1
- A few scrollable tables cannot be navigated by using a keyboard. Visitors who can't easily use a mouse may instead use a keyboard (or keyboard alternative) for navigation. This includes people who are blind and people with motor disabilities. WCAG 2.1.1
- There are a few instances where there is an empty heading. Headings help to break up content and make it easier for visitors to scan a page for information. WCAG 1.3.1
- There are instances where links do not have a text alternative. This can be problematic for visitors who are blind or have low vision. WCAG 2.4.4, WCAG 2.4.9, WCAG 4.1.2
- A few buttons lack a text alternative. If a text alternative is not provided, buttons represented by images or icons may be unusable to visitors using assistive technology. WCAG 4.1.2
- There are documents, such as a PDF-document, with known accessibility issues relating to content, structure or functionality. We continuously improve documents, also upon request.
- In addition to the above, a few external third party services which are not fully compliant are used.
How we tested this website
We use an external tool to support the web editors' content work with accessibility. We also use self-assessment, internal audit, of chalmers.se. Based on these tests and reports, we have regular meetings with both web editors and developers. In addition to the above, Chalmers' website supplier has performed functionality reviews via their own expert as well as external tools.
The last assessment was made on January 30, 2023.
The website was published February 2023.
The statement was last updated on January 30, 2023.