KitePages.

Design & accessibility

Light or dark? Why your website should give visitors a choice

Some people prefer a light background, others a dark one. I don’t want to impose either. KitePages initially follows the device and lets visitors switch with one click.

An additional display, not a quality seal

A dark interface may be more comfortable in a dim environment. That is not true for everyone. Age or a visual impairment alone does not determine which view is easier to read.

On your first visit, KitePages uses your device’s colour scheme. The control at the top switches directly between light and dark. Your manual choice is saved.

Contrast still matters in dark mode

Pay particular attention to small notes, form labels and links. Light grey on dark grey can be just as hard to read as pale text on white.

WCAG 2.2 level AA requires at least 4.5:1 contrast for normal text. Large text can use 3:1 under the specified conditions. Check the actual colour combinations used.

Treat images, forms and example projects separately

Photos remain photos. They do not need a filter over the entire page. Surfaces, borders and labels need deliberate dark-mode colours instead.

KitePages project previews adapt their surfaces too, while retaining their individual palettes. Form field boundaries and keyboard focus remain visible.

Four checks beyond dark mode

Zoom in. Use the menu and form with the keyboard alone. Check that error messages make sense. Repeat in both colour schemes.

Motion matters too. Tickers should be pausable. Visitors who request reduced motion on their device should receive a calmer experience.