This statement covers this website and the Ding That fonts.
Our target
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA.
How the website is designed
- Text uses Atkinson Hyperlegible Next, a typeface designed for readers with low vision.
- Every text colour meets WCAG AA contrast, in both the light and the dark scheme. The dark scheme follows your system setting.
- Every link and control shows a clear focus ring, and a skip link lets keyboard users jump to the content.
- Buttons and menu items are at least 44 pixels tall.
- Glyph pictures are hidden from screen readers, and each one has its name written next to it in text.
- The site supports Windows High Contrast (forced colours), reduced motion, and printing.
How the fonts are designed
- Where a standard Unicode symbol exists, such as ★, ✓ or ✈, the glyph is at that code point too, so text that uses the real symbol is read by its Unicode name.
- The Help page explains how to hide decorative glyphs and label meaningful ones.
Known limitations
- A screen reader reads glyphs typed with letter keys as letters. This is how all dingbat fonts work, so authors need to hide or label them.
- The glyphs are pictures and can’t be described by the font itself.
- A full audit against every WCAG 2.2 AA criterion, including testing with NVDA, JAWS and VoiceOver, has not been completed yet. We will update this statement with the results.
Feedback and contact
If anything on Ding That doesn’t work for you, or you need information in a different format, please tell us. Email [email protected] or open an issue on GitHub.
Enforcement
{{ENFORCEMENT_PROCEDURE: if you are a public body, describe your complaints procedure and the enforcement body here, as required by the EU Web Accessibility Directive. Otherwise, delete this section.}}
About this statement
This statement was prepared on 20 October 2026 and will be reviewed at least once a year, and whenever a new version of the fonts is released.