§Accessibility statement
Accessibility statement
Last reviewed: 19 August 2026. Costely is built to be usable with a keyboard, a screen reader, a magnifier or a small phone, because a table of numbers is worth nothing to a reader who cannot reach it.
Standard we aim at
We target the Web Content Accessibility Guidelines, version 2.2, level AA — the standard behind EN 301 549 in the European Union and behind the practice expected under the Americans with Disabilities Act and Section 508 in the United States. This is a self-assessment; the site has not been audited by a third party.
What is in place
- A skip link to the main content, semantic landmarks and headings in order.
- Every control reachable and operable by keyboard, with a visible focus ring.
- Names for controls that need them, and live regions kept quiet so a screen reader is not interrupted by decoration.
- Figures in tabular numerals with contrast well above the 4.5:1 minimum — the values in the comparison tables sit at roughly 16:1 against their background.
- Colour is never the only carrier of meaning: differences are stated in words and in numbers as well as in red and green.
- All animation, including the shimmer on the headline pills and the row transitions, stops for readers whose system asks for reduced motion.
- Layouts reflow to a single column on narrow screens, and the comparison tables restack so that no horizontal scrolling is needed.
- Text scales with browser zoom without loss of content.
Known limitations
- Wide comparison tables carry a lot of numbers in one row. With a third country added they become denser still, and on a very small screen they are demanding to read even though they remain reachable.
- The mini bars beside the difference column are decorative; the same information is always given as a number in the same row.
- Some source names and dataset codes are technical by nature and are not simplified.
Tell us what does not work
If a control does not work with your assistive technology, or a page is unreadable in your setup, write to us with the page address and what happened. We treat access defects as bugs, not as requests. [State a target response time, and the enforcement or complaints route required in the operator’s country — in the EU this is the national accessibility monitoring body.]