Accessibility Statement for HAKI

We strive to make haki.no accessible to as many users as possible. Accessibility is a fundamental part of our digital quality and user experience, and we actively work to follow the Web Content Accessibility Guidelines (WCAG). These international guidelines help us create a web environment that works for everyone.

As of 25 June 2025, digital accessibility requirements were expanded through the European Accessibility Act. This means that private organisations are also covered by legal accessibility requirements.

We aim to meet the requirements of WCAG 2.2 Level AA and continuously work to improve the accessibility of our website. Accessibility is an ongoing process, where we test and improve as new needs and insights arise.

How accessible is the website?

We have actively worked to improve accessibility on the website. Among other things, this includes the following:

Images and Media

  • All images that convey information have alternative texts or descriptions.
  • Decorative images have empty alt attributes.

Structure and Semantics

  • The website uses semantic HTML and a consistent heading structure to make navigation easier with assistive technologies.
  • Content and components are structured so they can be interpreted correctly by screen readers and other assistive tools.
  • The heading hierarchy has been corrected on the homepage, product pages, service and support pages, and document pages to ensure a logical structure.

Links and Navigation

  • Links have clear and descriptive link texts that make it possible to understand where they lead.
  • Navigation areas and menus have clear accessible names.
  • Links without distinguishable names have been corrected on the homepage, service and support pages, and document pages.

Buttons and Interactive Elements

  • Buttons that previously lacked accessible names have been updated on the homepage and document pages.
  • Interactive components have been reviewed to ensure they work with assistive technologies.

Keyboard Navigation

  • The website can, in general, be navigated using a keyboard.
  • Menus and functions can be accessed without using a mouse.
  • Users can skip directly to the main content of the page.

Contrast and Readability

  • Colours and contrast have been improved on the homepage, product pages, product detail pages, service and support pages, and document pages to meet accessibility requirements and make content easier to read.

Touchscreens and Mobile Devices

  • The size and spacing between clickable elements have been improved on document pages to make them easier to use on touchscreens.

Known Accessibility Limitations

We are aware that some parts of the website can still be improved. This includes, for example:

  • Certain parts of keyboard navigation, such as side panels or some menu levels.
  • The website is under continuous development and is regularly updated with new content. Despite established routines, individual deviations in heading hierarchy or semantic structure may occur when new content is published.

We continuously work to address these issues and improve usability for all users.

How We Work with Accessibility

To ensure accessibility, we carry out:

  • Tests using automated tools such as Lighthouse and Axe DevTools.
  • Manual testing with keyboard navigation.
  • User testing with screen readers to identify real accessibility barriers.

Our goal is to maintain a high standard of digital accessibility through both technical quality and good user experiences.

Feedback and Contact

We appreciate all feedback that helps us improve. If you discover something that does not work as expected, please do not hesitate to contact us.

Our normal response time is [7-14] working days.

Supervision

The Agency for Digital Government (Digg) is responsible for supervising compliance with the law on accessibility to digital public services. You can report to Digg if you believe that our digital service has accessibility shortcomings, or if you believe that our handling of your request for accessibility improvements is incorrect.

This accessibility statement is based on a self-assessment through internal testing of haki.se. We work according to established tools and guidelines to identify and resolve accessibility issues.

Last updated: 5 June 2026