Additional recommendations #400
Description
AI transparency & control
Requirement: If AI is used to generate or alter content that affects understanding, decisions, or assessments, users are informed and provided human-readable explanations and accessible controls to review, correct, or opt out.
Why in WCAG 3: WCAG 3 is expanding toward outcome- and task-based methods; AI-driven UIs are now common and materially affect accessibility outcomes.
Required tool/plugin disclosure
Requirement: If content requires a specific tool, plugin, or feature flag, the requirement is disclosed up front with accessible install/enable steps and an accessible fallback or equivalent experience.
Why in WCAG 3: WCAG 2.2 already ties conformance to accessibility-supported tech and non-interference; WCAG 3 keeps aligning minimums while modernizing conformance.
Login-gated content notice
Requirement: If critical content/actions are available only to logged-in users, disclose this before sign-in and ensure authentication is accessible (no cognitive-load traps) and offers an equivalent guest preview when feasible.
Why in WCAG 3: “Complete processes” and authentication burdens are long-standing barriers; WCAG 3’s task-based testing supports measuring real user flows, including authentication.