Accessibility

Barrier-free access is what this organisation works on, so the site has to match what it says. Below: what has been done, what has been done badly, and what we have not checked.

What has been done

  • The team honeycomb is a list of links, not clickable blocks: full keyboard navigation, visible focus, accessible names carrying name and role.
  • The focus ring is two-colour — visible both on the light background and on the hover fill.
  • State is never conveyed by colour alone: every event in the venue calendar carries a word, and a past day carries the word “past”, not just a grey tone.
  • The venue calendar is a real table: column headers are weekdays, row headers are weeks; below 720px the grid is hidden and a day list remains, reading linearly. Months are browsed with ordinary links, so they work without JavaScript.
  • prefers-reduced-motion disables the hero map animation and all transitions.
  • prefers-contrast: more switches to a 7:1 palette.
  • The “Vision” button in the header opens a version for people with visual impairment: black on white or white on black (21:1), text up to 150%, no animation, no ornaments. The choice is stored in the browser and applied before first paint, so nothing flickers.
  • Animations respond only to scrolling or an action, never change text opacity, and are disabled both by the system prefers-reduced-motion and by the switch in the “Vision” panel.
  • Windows High Contrast is supported: nothing disappears, hexagons keep an outline.
  • Latin programme and donor names carry language markup so screen readers do not read them with Ukrainian phonetics.
  • Layout does not break at 320px or at 200% zoom.
  • Touch targets are at least 44px where a finger is used.
  • Field errors sit under the field and are read together with it.
  • The request form does not ask about access needs: instead we publish facts about the venue so a person can judge for themselves without disclosing anything.

Known deviations

An accessibility statement is a promise, so it must also name what did not work out. Otherwise it is worth nothing.

  • JavaScript sizeA public page is 105 kB gzipped against a 100 kB target. This is the framework runtime; over zstd, which the server serves, it is 92 kB.
  • Honeycomb cell captionIt may clip when text spacing is increased. The same list of names and roles sits as text below the honeycomb and reflows freely, so no content is lost.
  • Plain languageThe mechanism exists, the texts are not written yet. Until they are, there is no plain-language switch — we do not promise what we do not have. The “Vision” panel is not a substitute: it changes the look, not the text.
  • Sign languageNo video.
  • Venue accessibilitySome facts are not established yet and are shown as such. We do not pretend to know.

What we have not checked

  • Loading metrics on a mobile network have not been measured on a real server.
  • No third-party accessibility audit has been carried out.
  • Screen reader testing is limited to automated checks and a manual keyboard pass.

Hit a barrier? Write to us

Describe what did not work, on which page, and what you were using. We will reply and fix it. There is deliberately no separate form: email does not disappear and does not ask anything extra of you.

  • [уточнити: пошта]
  • Target levelWCAG 2.2, рівень AA
  • Last reviewed[уточнити: ДД.ММ.РРРР]

This page ages faster than the code. If what is written here no longer matches reality, that is a barrier too — and worth telling us about. Contact