Accessibility statement
CryptoPriceTicker.com aims to be usable by everyone, including people who use a screen reader, a keyboard, zoom or reduced motion. We target WCAG 2.1 level AA, the standard behind the European norm EN 301 549. This statement was last reviewed on 2 November 2026.
Conformance status
Partially conformant with WCAG 2.1 AA: most of the site meets the standard, with the known limits listed below. We use "partially" because a fully automated check cannot prove conformance, and some parts of a live price site are hard by nature.
How we test
- Every page type is checked with the axe-core engine (WCAG 2.0/2.1 A and AA rules plus best practices) in both light and dark themes, at desktop and phone widths. The most recent run found no violations.
- Every text colour in the default and light themes has a measured contrast of at least 4.5:1 against the backgrounds it appears on.
- All controls work with a keyboard, show a visible focus ring and have accessible names. The page layout has a skip link, landmarks and one heading level 1 per page.
- Animations respect the "reduce motion" setting: the logo, page transitions and hover effects stand still.
- Pages reflow without horizontal scrolling down to 320 px wide and support browser zoom.
Known limitations
- Live prices are not announced one by one. Prices change many times a second, so reading each change aloud would make the page unusable. Screen-reader users can read the current value of any row at any time; price alerts are announced.
- The scrolling price tape is decorative and hidden from assistive technology; the price table shows the same data.
- The heatmap is visual. Every tile has a text label with the coin, its 24-hour change and price, and the same data is available in the price table and on each coin page.
- Colour is not the only signal: rises and falls are also shown with "+" and "−" signs and arrows.
- Embedded widgets on other websites follow this statement inside the widget frame; the surrounding page is the responsibility of its owner.
Report a barrier
If something on the site doesn't work for you, please open an issue on GitHub and describe the page, what you were trying to do, and the device, browser and assistive technology you use. We aim to reply within 5 working days and to fix confirmed barriers as a priority.