Accessibility Statement

Fainaron is committed to making global news accessible to every reader, including readers with disabilities. We design, build, and test Fainaron with the principle that information is only valuable when everyone can reach it.

1. Standards we follow

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, published by the W3C. These guidelines set out how to make web content more accessible for people with visual, auditory, cognitive, and motor impairments.

2. Inclusive design principles

• Semantic HTML \u2014 every page uses meaningful headings, landmarks, and lists for assistive-tech navigation.
• Keyboard-first \u2014 every interactive element (menus, search, share buttons) is reachable and operable from the keyboard alone.
• Screen-reader friendly \u2014 alt text on images, ARIA labels on icon-only controls, and skip-to-content shortcuts.
• High-contrast palette \u2014 text colour and background colour exceed WCAG AA contrast ratios in both light and dark themes.
• Resizable text \u2014 typography scales without breaking layout up to 200% browser zoom.
• Motion-safe \u2014 we respect the operating-system prefers-reduced-motion setting and disable non-essential animations.
• Responsive layout \u2014 pages adapt to mobile, tablet, desktop, and assistive devices.
• Plain-language summaries on long-form articles where the topic is technical.

3. Known limitations

Despite our best efforts, some content may not be fully accessible. Known limitations include:

• A small number of historical images may have incomplete alt text \u2014 we are auditing and back-filling these.
• Some embedded third-party widgets (e.g., social media embeds, ad iframes) may not meet our standards. We are migrating to accessible alternatives where possible.

4. Continuous improvement

We test accessibility on every meaningful release using a combination of automated tools (axe-core, Lighthouse), keyboard-only walkthroughs, and screen-reader spot-checks (NVDA, VoiceOver). Issues we discover are tracked, prioritised, and resolved as part of our normal release cycle.

5. Getting help and giving feedback

If you encounter any part of Fainaron that is difficult to use, or if you need content delivered in a different format, please email news@fainaron.com with the subject line Accessibility support. We aim to respond within two business days.

Feedback about how we can make Fainaron more inclusive is always welcome. Reports of accessibility barriers help us prioritise improvements.

6. Formal complaints

If our response to an accessibility request does not satisfy you, you may escalate to our editor-in-chief at the same email address with the subject Accessibility escalation. We take such reports seriously and treat them as production-priority issues.