project-diada.org should be usable by everyone, including people using screen readers, keyboard navigation, magnification or reduced motion. This page states what we aim for, what we know is imperfect, and how to tell us when something blocks you.
Our target
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. That is the standard most accessibility law refers to, and it is a reasonable bar for a text-based publication.
We are describing an aim, not claiming certification. No independent audit has been carried out on this site. Saying so is more useful to you than a confident claim we cannot back.
What we do
- Semantic structure. Real headings in a logical order, so screen reader users can navigate by heading rather than reading everything.
- Alt text on images. Feature images carry a description of what is actually in the picture, written for someone who cannot see it — not a repeat of the headline.
- Descriptive links. Link text says where it goes. No bare “click here” or “read more” without context.
- Colour contrast. Body text and interface elements aim for the WCAG AA contrast ratios.
- Colour is never the only signal. Anything indicated by colour is also indicated another way.
- Keyboard navigation. Links, forms and controls reachable and operable without a mouse, with a visible focus indicator.
- Resizable text. The layout holds at 200% zoom without content being lost.
- Readable prose. Plain language, short paragraphs, jargon explained. This is an accessibility feature as much as a style choice.
- No motion traps. No autoplaying video, no flashing content, no animation that cannot be escaped.
Known limitations
Being honest about the gaps:
- Third-party embeds. Content embedded from other services carries their accessibility, not ours, and we cannot fix it. We keep embeds rare.
- Older articles. Pieces published before our current standards may have weaker alt text or heading structure. We fix these as we find them.
- Linked sources. We link to journals, PDFs and statistical agencies so you can check our work. Academic PDFs in particular are frequently inaccessible, and that is outside our control.
- No formal audit. We test as we build, but no independent expert review has been done.
Tell us when something blocks you
If any part of this site is difficult or impossible to use, we want to know. Please email [email protected] with:
- The page you were on
- What you were trying to do
- What happened instead
- Your browser and any assistive technology, if you know it
We will acknowledge within 3 working days, tell you honestly whether and when we can fix it, and provide the content another way in the meantime if that helps. Accessibility reports are treated with the same priority as corrections.
Feedback shapes this page
Where a reported barrier is real and we cannot fix it immediately, it goes into the known limitations above rather than being quietly forgotten.
Last updated August 22, 2026.