Partially conformant with WCAG 2.2 AA. Three known gaps, all minor, all logged.

Plain English: We aim to make this site usable for everyone, including people with disabilities.

OS Domains is committed to making our website and customer portal accessible to people with disabilities. We treat accessibility as a product-quality concern, not a legal checkbox. The current site has been designed and built with accessibility considered at the design-system level — every component in our design system has accessibility annotations, every page is checked against WCAG 2.2 AA criteria before deployment, and every release includes a pre-deployment accessibility check. We are not perfect and we publish our known gaps below honestly rather than glossing over them. If you encounter a barrier we have not listed, please tell us using the feedback channels at the end of this page.

Plain English: Partially conformant with WCAG 2.2 Level AA. The minor gaps are listed below.

This website conforms to the Web Content Accessibility Guidelines 2.2 Level AA and to EN 301 549 v3.2.1 (the European harmonized standard for ICT accessibility), with three known minor exceptions documented in the "Known issues" section below. "Partially conformant" means that some parts of the content do not fully conform to the accessibility standard. The customer portal at app.osdomains.com is tested separately on the same schedule and has its own conformance documentation available on request. We do not use accessibility overlay tools — the European Disability Forum has stated explicitly that overlays do not satisfy EAA requirements and may introduce new accessibility issues. Our compliance comes from the underlying code and design, not from a third-party widget.

Plain English: The methodology, tools, and people involved in producing the conformance claim above.

Our accessibility testing combines automated and manual methods. Automated scanning: axe DevTools (Deque Systems), Lighthouse accessibility audits, Pa11y for batch testing, and WAVE for individual page checks. These tools catch approximately 30–40% of WCAG issues, mostly machine-checkable items like color contrast, missing alt attributes, and ARIA syntax errors. Manual testing: keyboard-only navigation of every flow, screen-reader testing with NVDA (Windows, Firefox), JAWS (Windows, Chrome), VoiceOver (macOS Safari, iOS), and TalkBack (Android Chrome). Manual review covers the 60–70% of issues automated scanners miss — meaningful alt text, logical reading order, focus management on dynamic content, error recovery patterns. The most recent comprehensive audit was conducted on 2026-04-12 by our internal accessibility lead with IAAP CPACC certification. A third-party audit by an independent accredited firm is scheduled for Q3 2026.

Plain English: How to tell us about accessibility barriers. We respond within 5 business days.

If you encounter accessibility barriers on this site, we want to know. The fastest way to reach our accessibility team is email: [email protected] — a real person reads every message, typically responds within 5 business days. Please include the URL of the page where you experienced the barrier, the assistive technology you were using (screen reader name and version, browser and version, operating system), and a brief description of what you were trying to do. If we cannot resolve the issue immediately, we will give you a workaround within 5 business days and a fix timeline. If you prefer to call, the same team can be reached at +43 1 205 11 80 during Vienna business hours (Monday–Friday, 9:00–17:00 CET).

Plain English: What to do if our response is unsatisfactory — including national supervisory bodies.

If you contact us about an accessibility barrier and are not satisfied with our response, you have the right to escalate to the national accessibility enforcement body in your EU/EEA Member State. In Austria, the responsible body is the Bundesministerium für Soziales, Gesundheit, Pflege und Konsumentenschutz (Federal Ministry of Social Affairs, Health, Care and Consumer Protection), which oversees the implementation of the European Accessibility Act in Austria. For other Member States, see the European Commission's list of national accessibility authorities at https://ec.europa.eu/social/main.jsp?catId=1486. You can also lodge a complaint with the European Disability Forum (https://www.edf-feph.org) for cross-border issues that affect users in multiple Member States. We strongly prefer that you contact us first at [email protected] so we have a chance to fix the problem directly, but you are not required to do so before escalating.

Plain English: The specific technical references that our accessibility work targets.

Our accessibility work targets the following standards: (a) Web Content Accessibility Guidelines (WCAG) 2.2 Level AA — the W3C standard, ISO/IEC 40500:2025; (b) EN 301 549 v3.2.1 — the European harmonized standard for ICT accessibility, which incorporates WCAG 2.2 AA for web content and adds additional ICT criteria for non-web ICT; (c) the EU European Accessibility Act (Directive (EU) 2019/882) effective 28 June 2025, which mandates the above for consumer-facing services in EU Member States; (d) WAI-ARIA 1.2 for dynamic content patterns where native HTML semantics are insufficient. We track ongoing WCAG updates and our internal accessibility audit is rerun whenever new success criteria become normative.