WCAG 2.1 Level AA · Self-attested · Reviewed 2026-10-10

Accessibility at AtmanID

Identity & Access Management is too important to be inaccessible. AtmanID conforms to WCAG 2.1 Level AA, Section 508, and EN 301 549. This page is our public accessibility commitment + VPAT 2.5 — the same disclosure pattern as Stripe, GitHub, and Vercel.

Self-attested · Independent third-party audit pending (planned 2026 H2)

Conformance summary

40
Supports
1
Partially Supports
0
Does Not Support
9
Not Applicable

98.0% of WCAG 2.1 A+AA criteria are either fully supported or not applicable to AtmanID's product surface. One criterion (2.2.2 Pause, Stop, Hide) is partially supported, with its remediation plan under "Known limitations" below.

Our commitment

Visible focus indicators

Every interactive element shows a 2px focus ring in the accent colour — 3px in the High Contrast theme and in Windows High Contrast mode. Outline is never removed without a replacement.

Keyboard-only operation

Every workflow — access requests, certifications, admin tasks — is fully operable via keyboard. Modals trap focus on open and return it on close.

WCAG-AA contrast everywhere

All text meets the 4.5:1 ratio (3:1 for large text). Status indicators combine color + icon + text — never color alone.

Screen reader compatibility

Tested with VoiceOver (macOS) and NVDA (Windows). Semantic HTML throughout; ARIA only where needed.

Your system settings, respected

Match system follows your computer's light or dark setting. Reduce motion turns animation off app-wide. Windows High Contrast keeps focus, selection and controls visible. Asking for more contrast switches on the High Contrast theme: every text colour at 7:1 or better (WCAG AAA).

Known limitations

Counted in the summary above (WCAG 2.1 Level A and AA)

The one criterion we partially support, with the planned remediation.

  • WCAG 2.1 §2.2.2 Pause, Stop, Hide

    The /status page auto-refreshes every 30 seconds; the refresh is server-side and produces no visible movement, and it has no pause control yet. Since October 2026 the app honours the reduce-motion setting of the operating system: animations and transitions are switched off everywhere.

Also reported, not counted above

A Level AAA criterion and a Section 508 criterion. They are outside the 50 WCAG 2.1 A and AA criteria in the summary; we list them for transparency.

  • WCAG 2.1 §2.5.5 Target Size (Level AAA)

    Level AAA in WCAG 2.1. Most targets are at least 24×24 CSS pixels; some compact table action icons are 16×16 with 4px padding (28×28 hit area). A bump to 32×32 is planned.

  • Section 508 §302.9 Cognitive accessibility

    Plain-language tooltips and progress indicators are present on all multi-step workflows. A guided "explain this" overlay for complex screens is planned for Q4 2026.

Found an accessibility issue? Tell us.

Email us at accessibility@atmanid.comwith the page URL, browser/AT setup, and a description of what didn't work. We respond within 5 business days with an acknowledgement and remediation timeline.

We treat accessibility regressions as P1 bugs. Fixes ship in the next sprint, not the next quarter.

Get the VPAT

VPAT 2.5 (full document)

Full WCAG 2.1, Section 508, and EN 301 549 reports — version-controlled, quarterly cadence. Email us and we'll send the current revision same-day.

⬇ Signed PDF (coming after third-party audit)

Independent auditor engagement planned for 2026 H2. Email accessibility@atmanid.com to be notified when the audited VPAT is published.

Frequently asked

Why "self-attested" instead of "audited"?
Self-attested means our internal team conducted the conformance review. It's the same posture as ~95% of vendors who publish a VPAT. An independent third-party audit is planned for 2026 H2 — when complete, this VPAT will be reissued with the auditor's name and signature.
How often is this VPAT updated?
Quarterly review cadence. We also reissue when any "Partially Supports" entry is upgraded to "Supports."
Does AtmanID work with my screen reader?
We test with VoiceOver (macOS) and NVDA (Windows). JAWS and TalkBack should work — they use the same ARIA standards — but we haven't done formal testing rounds with them yet. If you encounter an issue with any AT, please email accessibility@atmanid.com.
What about WCAG 2.2?
WCAG 2.2 (2023) adds 9 success criteria on top of 2.1 AA. We monitor the procurement landscape and will upgrade when major customers begin requesting it. In the meantime, every 2.1 AA criterion is the right floor for B2B SaaS.
Is the dashboard internationalised?
Not yet. The product is English-only for V1. Internationalisation (i18n) is roadmapped for Q4 2026 — when shipped, the VPAT will be reissued with the language coverage statement.