Accessibility Statement
Last updated: October 22, 2026
EV Hub is a research site for importers, analysts and buyers. If the information here cannot be read — by a screen reader, by keyboard, at high zoom, or on a slow connection — then it is not doing its job. This statement explains the standard we work to and how to tell us when we fall short.
Standard we aim for
We target conformance with the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. This is a self-assessed target rather than an audited certification: we review pages as we publish them rather than claiming a formal audit we have not commissioned.
What is in place
- semantic HTML landmarks and a logical heading order on every page;
- descriptive alternative text for photographs and charts, generated from the same data the page displays;
- keyboard-operable navigation, links and interactive controls, with a visible focus state;
- text and background combinations chosen for contrast, with dark-mode support on system preference;
- responsive layouts that remain usable from narrow phone widths to desktop, and support for browser zoom without loss of content;
- data tables marked up with header cells so screen readers can associate labels with values;
- no autoplaying media, and no content that flashes or animates aggressively.
Known limitations
We would rather name these than pretend they do not exist:
- Dense data tables. Landed-cost and comparison tables carry a lot of numbers. They work with screen readers, but reading them aloud is verbose; where we can, we also publish the same figures as prose in the surrounding text.
- Interactive calculators. The landed-cost calculator needs JavaScript. Without it, the underlying method and worked examples remain readable on the methodology pages.
- Third-party content. Embedded or linked material we do not control may not meet the same standard.
- Ongoing maintenance. Accessibility is reviewed as part of our publishing and maintenance process, and alternative text is generated from the same structured data each page displays. If you find a page that is causing you trouble, tell us and it moves to the front of the fix queue.
Technical compatibility
The site is built as static HTML and tested in current versions of Chrome, Edge, Firefox and Safari on desktop and mobile, and with common screen readers (NVDA, JAWS, VoiceOver, TalkBack). Older browsers may render it correctly but are not specifically tested.
How to report a problem
Email [email protected] with the page URL, what you were trying to do, the device or assistive technology you were using, and what went wrong. We acknowledge accessibility reports within 5 business days, give you a view on whether and when we can fix the issue, and prioritise anything that blocks access to information rather than merely inconveniencing it.