Skip to content

Accessibility

What we have done to make the site and the app usable, what we have measured, and what we do not know.

The short version: we have built for readability, and we have measured what can be measured. We do not claim to meet a standard we have not tested against.

What we have done

The typeface is chosen for legibility, not for style. Body text is set in Atkinson Hyperlegible Next, drawn by the Braille Institute for low vision, with letterforms that are hard to confuse. It is 18 pixels and is not scaled down on mobile — a large share of our readers are 55 or older and read in poor light.

The site ships no JavaScript. Not a line. The menu is built from ordinary HTML elements and the form posts to the server the ordinary way. Nothing stops working because a script failed to arrive.

The app has three display modes. Forest for dawn and dusk, daylight in black on white for glare and sun, and night in red on black, which preserves your dark adaptation. Touch targets are sized to work in gloves.

What we have measured

Contrast. Every combination of text and background used on the site reaches at least 4.5:1, the WCAG requirement for body text. Several are above 7:1.

Keyboard. The whole home page can be reached with the tab key, in 22 steps, and every step has a visible focus indicator. The first stop is a link that skips past the menu to the content. The menu opens and closes with Enter.

Width. No page requires horizontal scrolling, from 320 pixels upwards. That is the equivalent of enlarging the text fourfold on an ordinary screen.

Automated auditing. Lighthouse scores 100 out of 100 on every page type.

What we do not know

Automated tools catch only part of what can go wrong. They see that an image description exists — not whether it describes the image.

We have not tested the site with a screen reader, nor with the equipment someone with an actual disability uses. That is why this page does not say we meet WCAG. It says what we have done and what we have measured.

If something does not work

Write to support@jaktapp.eu and describe what happened and what equipment you were using. That is the fastest route to having it fixed, and frankly the only one we have — we cannot test everything ourselves.