{
  "name": "resources/accessibility",
  "title": "Accessibility Commitment",
  "description": "eurodata-ui recognizes the need for all users to have undeterred access to the websites and applications that are created with it.",
  "docs": "https://test-apps.eurodata.de/a/eurodata-ui/docs/resources/accessibility/",
  "sections": [
    {
      "heading": "Accessibility Commitment",
      "markdown": "**eurodata-ui** is committed to ensuring that all users — regardless of ability, device, or context — have equal and unhindered access to the websites and applications built with it. Accessibility is not just a feature; it’s a fundamental goal of the project.\n\nMany people ask, _“Is this accessible?”_ Unfortunately, the answer is rarely a simple _yes_ or _no._ Accessibility isn’t binary — what feels perfectly usable for one person may be completely inaccessible to another. A component that works well for sighted users may fail entirely for non-sighted users relying on screen readers. Even when optimizing for assistive technologies, we must also consider users with low vision, color blindness, hearing loss, mobility impairments, and many other diverse needs.\n\nAccessibility is a **continuous process**, not a one-time achievement. No single developer or even an entire team can claim that their software is _100% accessible_ — the diversity of users, devices, assistive technologies, and real-world scenarios makes this an ever-evolving challenge.\n\nMoreover, accessibility doesn’t stop at the **component level**. Building accessible components doesn’t automatically make an entire website or application compliant. There is no library, plugin, or overlay that can make software “fully accessible” without ongoing, thoughtful effort. It’s also important to note that web accessibility standards are still evolving — browsers, assistive devices, and even [emerging specifications](https://wicg.github.io/aom/spec/) continue to improve the accessibility landscape.\n\nAt **eurodata-ui**, our goal is to make every component as accessible and future-proof as possible. While accessibility is often associated with supporting users with disabilities, its benefits go far beyond that. Implementing correct ARIA attributes and ensuring components are compatible with assistive technologies also supports **automation**, **testing**, and **voice-controlled workflows**.\n\nIn short, accessibility isn’t just about inclusion — it’s about building more robust, flexible, and intelligent software for everyone."
    }
  ]
}