Trust CenterAccessibility conformance

WCAG 2.1 AA. From day one.

Accessibility is a launch criterion at ArthurAI™, not a roadmap item. The standard we target is WCAG 2.1 AA — the standard cited by Section 508 of the Rehabilitation Act and by the Title II ADA Web Rule (28 CFR Part 35). Public-sector and many institutional buyers require demonstrated WCAG conformance; the platform is built to satisfy that requirement on day one of any deployment.

What WCAG 2.1 AA means in our build

  • Perceivable. Color contrast meets the 4.5:1 ratio for body text and 3:1 for large text. No information is conveyed by color alone. Text alternatives exist for non-text content. Educator-uploaded media prompts the educator for alt text at upload time.
  • Operable. Every interactive surface is keyboard-navigable. Focus is always visible. Skip-links jump past the navigation. No keyboard traps. Custom UI components carry appropriate ARIA roles and states.
  • Understandable. Form labels are present and correctly associated. Error messages are programmatically linked to the field. Language of the page is set and updates correctly when locale switches. Predictable navigation across pages.
  • Robust. Semantic HTML structure (landmarks, headings, lists). Custom widgets follow the WAI-ARIA Authoring Practices. The platform tests against current screen-reader behavior (NVDA, JAWS, VoiceOver, TalkBack).

How we verify

  • Automated checks at build time. Every product portal ships with axe-core integrated into the test suite. The CI pipeline blocks merges that introduce accessibility regressions detected by axe-core.
  • Lint-time enforcement. eslint-plugin-jsx-a11y flags accessibility anti-patterns at the source-code level (missing alt text, click handlers without keyboard handlers, missing form labels, etc.).
  • Manual review per release. Each release is reviewed for keyboard navigation, screen-reader behavior, color contrast in branded themes, focus management, and text alternatives across every learning-flow surface.
  • RTL-aware design. Document direction flips automatically for Arabic and Urdu locales. Layouts are mirrored, not just translated.

Section 504 and Section 508 alignment

Section 504 of the Rehabilitation Act and Title II of the Americans with Disabilities Act place obligations on the educational institution; ArthurAI™ supports those obligations with accessible interfaces and content. Section 508 of the Rehabilitation Act applies to federal procurement; the WCAG 2.1 AA target satisfies the technical baseline cited by Section 508.

VPAT (Voluntary Product Accessibility Template)

A formal VPAT 2.5 document covering WCAG 2.1, Section 508 Refresh, and EN 301 549 (European accessibility standard) is available to institutional buyers under NDA. The VPAT is updated on every major release that touches user-facing surfaces. To request the current VPAT, talk to our team.

What we do not claim

We do not claim WCAG 2.1 AAA conformance. AAA is a stricter standard not applicable to all content, and not required by Section 508 or Title II. We target AA, verify AA, and represent AA. We also do not claim conformance for third-party content educators upload to the platform; we provide tools that help (alt-text prompts at upload, automated contrast checks on themed backgrounds), but the educator is responsible for the accessibility of content they author.

See also: accessibility statement · full compliance posture · data handling.