Skip to content
Create a free account
WCAG 2.1 AA

Accessibility

Ejerblik is built for everyone. We work actively to make our platform and website accessible to people with disabilities.

This English translation is provided for convenience. In case of discrepancy, the Danish version prevails.

Accessibility statement

Ejerblik aims to meet WCAG 2.1 AA (the Web Content Accessibility Guidelines) across ejerblik.com and app.ejerblik.com. These guidelines are published by the W3C and are the international standard for web accessibility.

We are a private company and are not directly covered by the Danish accessibility act (L60), which applies to public bodies. We have set ourselves the target of meeting WCAG 2.1 AA anyway, because we believe good software has to work for everyone, whatever their sight, motor or cognitive impairment, and whatever assistive technology they use.

From May 2026 onwards we have carried out a systematic WCAG audit and implemented fixes across the whole platform.

What we have done

Keyboard navigation
Every interactive element, including navigation, forms, tables and dialogs, can be operated fully by keyboard. The focus indicator is clear and consistent.
Colour contrast
All text and background combinations meet the WCAG 2.1 AA requirements of at least 4.5:1 for normal-size text and 3:1 for large text and UI components.
Screen reader compatibility
Pages, forms and dialogs carry correct ARIA roles, labels and structures. Dynamic content is announced through aria-live regions.
Semantic HTML
Every page has a correct heading hierarchy (h1→h2→h3), semantic landmarks (main, nav, header, footer) and meaningful link text.
"Skip to content" link
Every page has a visible "Skip to content" link, activated by Tab, so keyboard and screen reader users can skip past the navigation.
Reduced motion
The platform respects the operating system setting for reduced motion (prefers-reduced-motion). Animations are disabled automatically for users who have turned that setting on.
Forms and error handling
Every form field has a programmatically associated label. Required fields are marked with aria-required. Error messages are implemented as role="alert" and announced automatically.

Standards and test methods

We test continuously with the following methods and tools:

  • WCAG 2.1 AA: our target standard
  • axe DevTools: automated scanning of every page
  • Keyboard testing: manual walkthrough of every flow
  • Lighthouse: accessibility and performance
  • Contrast verification: every colour combination measured with the WebAIM Contrast Checker

Known limitations

We are a small company in active development. There may be faults we have not found yet. Below is an honest list of the known outstanding points we are working to fix:

  • Some PDF reports exported from the platform are not yet fully accessible
  • The map visualisation in asset relationships (a force-directed graph) is not yet keyboard navigable
  • Third-party integrations (the Stripe payment flow) are partly outside our control

Run into an accessibility barrier?

If you hit a barrier that stops you using our platform or website, we would very much like to hear from you. Write to us, and we will respond within two working days.

Last updated: May 2026 · Ejerblik ApS