Accessibility

How we work with accessibility.

We sell quality control. It would be odd not to check our own site. Here is what we do, what has been tested, and where we know it falls short.

What we aim for

The target is WCAG 2.1 level AA. It is not a legal requirement for a company of our kind, but it is the level normally used as a benchmark, and it is a reasonable one to hold.

What has been done

In concrete terms that means the following, among other things.

  • The whole site can be used with a keyboard alone, and it is always visible where focus sits
  • A link at the top skips past the menu straight to the content
  • Contrast against the background is checked for all text, including the small labels
  • Text can be enlarged without anything disappearing, and the page can be zoomed
  • Form labels are tied to their fields, and error messages point out which field is meant
  • Motion and transitions are turned off for anyone who has asked for that in their system settings
  • Every page works at phone width without anything needing to be scrolled sideways
  • Images have descriptive alternative text, and drawings are described in words because the dimensions in a drawing cannot be read aloud

How we check

Pages are checked automatically against WCAG level A and AA on every significant change, at both desktop and phone width. The most recent test found no failures.

Automated tools find roughly a third of all problems. The rest needs someone to try it, and we do that by hand for keyboard use and magnification.

What we know falls short

The process diagram on How we work is a drawing, and a drawing cannot be read aloud. It is therefore hidden from screen readers, and the whole content sits as text directly underneath instead. That works, but it is not the same experience.

The reporting page is in Chinese and English. The Chinese characters are set in the device own typefaces, because a self hosted Chinese typeface would make the page heavy to load on a slow connection. How it looks therefore varies between devices.

We have not tested with people who use screen readers daily. Automated tests and our own attempts are not a substitute for that.

If you find something

Write to hej@gemak.se and describe what does not work, and ideally what equipment you are using. We fix what we can and write the rest down here.

This page describes the position in October 2026.