Our own site, held to the same bar.

ADAGuard is committed to ensuring that adaguard.io is accessible to all users, including those with disabilities. We hold ourselves to the same standards we help our customers achieve. We actively use our own scanner to test adaguard.io and work continuously to resolve barriers identified.

Partially conformant with WCAG 2.2 Level AA.

adaguard.io partially conforms with the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. Some content does not yet fully conform due to the limitations described in Section 4.

Technical specification: HTML5, CSS3, WAI-ARIA 1.2. We test with NVDA + Chrome on Windows and VoiceOver + Safari on macOS/iOS. WCAG 2.2 supersedes 2.1 — all 2.1 AA criteria are included.

We take the following measures to ensure accessibility of adaguard.io:

1. Run our own ADAGuard accessibility scanner against adaguard.io on every major release.
2. Maintain keyboard navigation throughout the application — all interactive elements are reachable and operable without a mouse.
3. Provide sufficient color contrast — all text meets the WCAG 2.2 AA 4.5:1 contrast ratio requirement.
4. Label all form inputs, buttons, and interactive controls with descriptive text or ARIA attributes.
5. Include skip-navigation links on every page.
6. Ensure all images include descriptive alt text.
7. Design responsive layouts that work at 320 px viewport width and 400% browser zoom.
8. Test with axe-core and our custom accessibility engine before deploying to production.

Despite our best efforts, some content on adaguard.io is not yet fully accessible. Known limitations — open and recently resolved — are listed below.

• Scan results dashboard

  Complex data tables did not announce all column/row relationships correctly in some screen readers.
  Resolved — Aug 2026
• PDF reports

  Generated PDF reports were not tagged for screen reader navigation.
  Resolved — Aug 2026
• Code diff views

  Syntax-highlighted before/after code blocks lacked sufficient color contrast in dark contexts.
  Resolved — Aug 2026
• Third-party embeds

  Dodo Payments iframes and some OAuth provider buttons may not fully conform — these are outside our direct control.
  Ongoing

ADAGuard assessed the accessibility of adaguard.io using the following approaches:

• Self-evaluation — we scan adaguard.io with ADAGuard itself (axe-core plus our own checks) across the pages in its sitemap.
• Manual testing — keyboard navigation and screen reader testing with NVDA (Chrome) and VoiceOver (Safari).
• Last scanned: May 20, 2026 using ADAGuard — run your own scan free →

We welcome feedback on the accessibility of adaguard.io. If you experience any barriers not listed above, or have suggestions for improvement, please contact us:

Email

support@adaguard.io

Subject line

Accessibility Feedback — adaguard.io

Response time

We aim to acknowledge all accessibility reports within 2 business days and provide a resolution timeline within 10 business days.

If you are not satisfied with our response to your accessibility report, you have the right to escalate:

• USUnited States (ADA): File a complaint with the U.S. Department of Justice via ADA.gov or contact the relevant federal agency.
• EUEuropean Union (EAA): Contact the national market surveillance or enforcement authority in your EU member state. The European Accessibility Act applies from June 28, 2025.
• CACanada (AODA): File a complaint with the Accessibility Directorate of Ontario if you are in Ontario.

We prefer to resolve accessibility issues directly and promptly. If you believe your feedback has not been adequately addressed, you may also contact ADAGuard’s designated accessibility contact at accessibility@adaguard.io. We commit to responding to formal complaints within 5 business days.