Accessibility at Trelson: for everyone

At Trelson, we believe that education and technology should be for everyone. That’s why we work hard to make our website easy to use and understand. This applies to everyone, regardless of disability. As a result, we are constantly improving our content. The aim is to ensure that all visitors have a good and inclusive experience.

This is how we think about accessibility

Firstly, we aim to comply with WCAG 2.1 Level AA. These international guidelines make websites more usable for people with different disabilities. For example, visual, hearing, physical, speech, cognitive, language, learning or neurological disabilities. These can affect movement or sensitivity to flicker. In addition, we are determined to constantly improve and fix errors to both reach and exceed these requirements.

How accessible is our website today?

Our website is partially accessible, but we’ve really understood how much difference accessibility makes! That’s why we are so keen to improve our website. We are now working hard to address the shortcomings.

What we’re working on and what we know that doesn’t quite work yet

We know that some areas of our website are not fully compliant. Many of these challenges are due to limitations in the way our website is built (our wordpress theme). In addition, it is affected by embedded content from other companies. This is often difficult to fully control.

These are the problems with the highest impact, which we are prioritizing to address:

  • WCAG 2.1.1 Keyboard: Some parts of the website, especially around embedded videos, are difficult to use with keyboard only. Therefore, we are working to make everything accessible and activated using only the keyboard.
  • WCAG 1.3.2 Meaningful Sequence: Information is not always clear to screen readers. Consequently, we make sure that content flows logically, regardless of visual layout.
  • WCAG 4.1.2 Name, Role, Value:
    • Hidden information: Important interactive elements are sometimes inadvertently hidden from screen readers. This makes them invisible.
    • Unclear information for tools: We have examples where information for screen readers and similar tools is not entirely accurate. This can cause confusion.
    • Forms: Forms from other companies sometimes do not group related questions clearly. This makes them more difficult to understand for the assistive technology user.
  • Missing group titles for forms (related to WCAG 1.3.5 Identify Input Purpose): These embedded forms often lack clear main headings for questions in groups. This is important to understand what should be filled in.
  • WCAG 2.4.4 Link Purpose (in context) Some links, especially closely embedded videos, do not always have clear enough descriptions about where they lead. Therefore, the purpose becomes difficult to understand.
  • WCAG 1.1.1 Non-text Content: Some graphical elements conveying information are sometimes not correctly described for screen readers. We are working to improve this.
  • WCAG 2.4.1 Bypass Blocks: We currently lack a direct link to “jump to the main content”. This can make it difficult for keyboard users and screen readers to quickly bypass the navigation.
  • WCAG 1.3.3 Sensory Characteristics: We review content. The goal is that instructions based only on color (“click the red button”) or sound (“listen for the signal”) always have an alternative, non-sensory way of being understood. For example, “click on the red ‘Send’ button” or “listen for the signal and look for the message ‘download complete’”.
  • WCAG 3.3.2 Labels or Instructions: Some non-interactive elements may have extra descriptions that are read by screen readers. However, these are not always helpful for content you cannot interact with.

These issues are also being addressed to provide an even better user experience:

  • WCAG 1.4.3 Contrast (Minimum) & 1.4.11 Non-text Contrast: Some text and important visual elements from embedded content, such as forms, may lack sufficient color contrast. This makes them difficult to see for some. We are actively working on this where we have control.
  • Headings clarity WCAG 2.4.6 Headings and Labels: Repeated headings on pages can confuse screen reader users. Therefore we are reviewing this.
  • WCAG 1.2.3 Audio Description or Media Alternative (Prerecorded) & 1.2.5 Audio Description (Prerecorded): Our prerecorded videos, mainly on YouTube, sometimes lack audio descriptions or extensive text versions. This is crucial for users who cannot see the video.
  • WCAG 1.4.12 Text Spacing: We ensure that text can be enlarged or spread out without breaking content or functionality.
  • WCAG 3.2.4 Consistent Identification: Some older elements of our website design do not match our updated style. Consequently, this can create small inconsistencies in how elements are recognized.
  • WCAG 3.3.3 Error Suggestion: For our embedded forms, we are investigating how we can provide helpful suggestions in case of input errors.
  • WCAG 1.4.1 Use of Color: We work to ensure that color is never the only way to convey important information.
  • WCAG 1.4.5 Images of Text: We minimize the use of text embedded in images. This improves flexibility and accessibility.

We are dedicated to continuously improving the accessibility of our website. We do this by:

  • Regularly review our website for accessibility issues. This is done both with automated tools and manual tests.
  • Prioritize fixing identified problems. We focus on the most critical ones first.
  • Collaborate with our external content providers. The aim is to address accessibility limitations in their embedded components whenever possible.
  • Train our content creators on accessibility best practices.

Your opinion is important!

We welcome any feedback on the accessibility of our website. If you encounter any obstacles when using it, please do not hesitate to contact us.

  • E-mail: Support@trelson.com

We aim to respond within 5 working days. Please note that cases submitted via our form will not receive a personal reply.

Authorization

This accessibility statement is formally approved by: Trelson, Paulina Juhlin & Mimmi Berg, 2025-06-23.

Last updated

This statement was created on 2025-06-23 and last updated on the same day.