Stand with Ukraine against Russian aggression. Donate through United24 (opens in a new tab)
Alekos (home)

Accessibility

Built for everyone. Here's how.

This site aims to meet WCAG 2.2 at level AA, the international standard for accessible websites, so you can use it whatever your screen, eyesight or way of getting around a page.

  • Perceivable
  • Operable
  • Understandable
  • Robust
  • AAWCAG 2.2 level

Checked 1 October 2026

What I do so everyone can use it

  • Works with a keyboard

    Every link, button and question works from the keyboard; a skip link jumps to the content.

  • Easy to read

    Text contrast is at least 6:1 in light and dark mode, well above the 4.5:1 required.

  • Zoom and small screens

    Pages reflow down to 320 pixels wide, or 400% zoom, with no sideways scrolling.

  • Ready for screen readers

    Real headings, named buttons and clear links; decorative icons and emoji stay silent.

  • Calm motion

    Nothing flashes, the one pulse stops after two beats, and motion obeys your settings.

  • Light and dark

    Follows your system's light or dark setting, with a switch in the footer to change it.

How I checked it

Last checked 1 October 2026, on every page.

  • Every page, two themes

    Titles, headings, landmarks, labels, alt text and target sizes, in light and dark mode.

  • Contrast, measured

    Every piece of text measured against its real background, not guessed from the design.

  • Keyboard and focus

    A visible focus ring everywhere, a logical tab order and nothing hidden under the banner.

  • Phones and zoom

    Checked at phone widths down to 320 pixels, and with larger letter and line spacing.

What I haven't done yet is test with people who use screen readers and other assistive technology every day. If that's you, your feedback would help the most.

Known limitations

  • The PDF CV is not tagged for screen readers yet. The CV page has the same content in an accessible form.
  • Other websites I link to, such as social networks and the organisations I support, have their own accessibility, which I cannot control.

The standard behind it

WCAG, the Web Content Accessibility Guidelines, is published by the W3C. Version 2.2 at level AA is the level the European standard for accessible websites, EN 301 549, builds on. Read WCAG 2.2 (opens in a new tab).

Found a barrier?

If something here is hard to read or use, tell me what and where. I'll reply and fix it as fast as I can.