Legal
Accessibility Statement
Last updated: May 20, 2026 · Applies to: adaguard.io
1. Our Commitment
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.
2. Conformance Status
Partially Conformant — 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.
3. Measures We Take
We take the following measures to ensure accessibility of adaguard.io:
- 1Run our own ADAGuard accessibility scanner against adaguard.io on every major release.
- 2Maintain keyboard navigation throughout the application — all interactive elements are reachable and operable without a mouse.
- 3Provide sufficient color contrast — all text meets the WCAG 2.2 AA 4.5:1 contrast ratio requirement.
- 4Label all form inputs, buttons, and interactive controls with descriptive text or ARIA attributes.
- 5Include skip-navigation links on every page.
- 6Ensure all images include descriptive alt text.
- 7Design responsive layouts that work at 320 px viewport width and 400% browser zoom.
- 8Test with axe-core and our custom accessibility engine before deploying to production.
4. Known Limitations
Despite our best efforts, some content on adaguard.io is not yet fully accessible. Known limitations are listed below. We are working to fix them.
| Area | Issue | Target fix |
|---|---|---|
| Scan results dashboard | Complex data tables may not announce all column/row relationships correctly in some screen readers. | Q3 2026 |
| PDF reports | Generated PDF reports are not tagged for screen reader navigation. | Q3 2026 |
| Code diff views | Syntax-highlighted before/after code blocks lack sufficient color contrast in dark contexts. | Q3 2026 |
| Third-party embeds | Dodo Payments iframes and some OAuth provider buttons may not fully conform — these are outside our direct control. | Ongoing |
5. Assessment Approach
ADAGuard assessed the accessibility of adaguard.io using the following approaches:
- Self-evaluation — we run our own full-site accessibility scanner against adaguard.io.
- Automated testing — axe-core 4.x integrated into our CI pipeline flags regressions on every deploy.
- Manual testing — keyboard navigation and screen reader testing with NVDA (Chrome) and VoiceOver (Safari).
- Ongoing monitoring — weekly automated scans with ADAGuard's multi-page crawler.
- Last scanned: May 20, 2026 using ADAGuard — run your own scan free →
6. Feedback and Contact
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:
7. Enforcement Procedure
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.
8. Formal Complaints
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 [email protected]. We commit to responding to formal complaints within 5 business days.
This statement was prepared on May 20, 2026 following a self-assessment conducted using ADAGuard's own accessibility scanner and manual testing. It will be reviewed and updated at least annually, or when significant changes to adaguard.io are made.
Standards reference: WCAG 2.2 · ATAG 2.0 · WAI-ARIA 1.2