Pillar D

Detectable

AGAG-D1

All Meaning Must Be Programmatically Detectable

Any meaning conveyed visually (color, icon, position, shape, animation) must also be exposed as text or semantic data.

Agents and assistive tech cannot reliably infer meaning from visuals alone.

WCAG:1.1.11.3.14.1.2

AGAG-D2

All Interactive Elements Must Have Stable Semantic Identity

Interactive elements must expose consistent, machine-detectable roles, names, and purposes.

WCAG:4.1.22.4.6

AGAG-D3

Complex Content Must Provide Structured Alternatives

Charts, diagrams, maps, and instructional visuals must include structured descriptions or data equivalents.

WCAG:1.1.1

AGAG-D4

Every Form Control Must Have an Explicit Programmatic Label

Every input, select, textarea, toggle, and custom form control must have a programmatically associated label.

Agents and assistive tech need unambiguous control identity.

WCAG:1.3.13.3.24.1.2

AGAG-D5

Related Inputs Must Be Grouped Semantically

Related fields must be grouped using semantic containers such as fieldset and legend, or equivalent accessible grouping structures.

Grouping exposes task logic and prevents cognitive fragmentation.

WCAG:1.3.13.3.2

AGAG-D6

Data Tables Must Expose Header Relationships

Tables must use proper header cells and associations so agents and assistive tech can interpret row and column meaning.

WCAG:1.3.1

AGAG-D7

Layout Must Not Masquerade as Data

Tables must not be used for layout, and visual layout structures must not impersonate tables unless they expose true tabular semantics.

Bots and assistive tech need to know whether content is spatial decoration or relational data.

WCAG:1.3.11.3.2

AGAG-D8

Media Must Expose Its Accessibility Assets

Audio and video must expose whether captions, transcripts, and audio descriptions are available.

WCAG:1.2.21.2.31.2.5

AGAG-D9

Every Page Must Expose a Landmark Skeleton

Pages must expose core landmarks such as header, navigation, main content, search, complementary, and footer where applicable.

WCAG:1.3.12.4.1

AGAG-D10

Primary Language Must Be Declared Programmatically

Pages must declare their primary language, and major language switches must be marked where feasible.

WCAG:3.1.13.1.2

Pillar O

Observable

AGAG-O1

All State Changes Must Be Exposed Programmatically

Dynamic updates must be announced via machine-readable mechanisms.

WCAG:4.1.3

AGAG-O2

Error States Must Include Recovery Instructions

Errors must include clear, actionable next steps.

WCAG:3.3.13.3.3

AGAG-O3

Context and Task Position Must Be Exposed

The system must expose where the user or agent is within a process.

WCAG:2.4.83.2.x

AGAG-O4

Validation Errors Must Be Bound to the Relevant Input

Every validation error must be programmatically associated with the field that caused it.

WCAG:3.3.13.3.34.1.3

AGAG-O5

Required Fields Must Be Declared Programmatically, Not Only Visually

Required status must not rely only on asterisks, color, or layout.

WCAG:1.3.13.3.24.1.2

AGAG-O6

Media Controls Must Be Explicit and Keyboard Reachable

Play, pause, mute, captions, speed, and transcript access must be discrete controls, not gesture-only or hover-only.

WCAG:2.1.12.1.22.5.x

AGAG-O7

Overlays Must Announce Their Purpose and Consequence

Dialogs, alerts, and popovers must announce why they appeared and what the next choices are.

WCAG:3.3.13.3.24.1.3

AGAG-O8

Loading and Refresh States Must Be Exposed

Lazy-loaded, streaming, or asynchronously refreshed content must expose loading state, completion state, and failure state.

WCAG:4.1.31.3.1

AGAG-O9

Session Expiry and Timeout Events Must Be Announced Before Loss Occurs

If a session is about to expire, the system must announce this in time for action and expose a path to extend or save progress.

WCAG:2.2.13.3.4

Pillar N

Navigable

AGAG-N1

All Actions Must Be Gesture-Independent

Any gesture-based action must have a discrete alternative.

WCAG:2.1.12.5.x

AGAG-N2

Focus Order Must Match Task Logic

Focus navigation must follow the logical order of the task.

WCAG:2.4.31.3.2

AGAG-N3

All Functionality Must Be Executable Without Timing Constraints

No required action may depend on timing, holding, or rapid input.

WCAG:2.2.x2.1.1

AGAG-N4

Repeated Content Must Be Bypassable

Users and agents must be able to skip repeated navigation and jump to primary task content.

WCAG:2.4.1

AGAG-N5

Link and Control Text Must Be Specific in Context

Links and buttons must expose destination or action meaning without requiring visual inference.

WCAG:2.4.42.4.6

AGAG-N6

Overlays Must Preserve Focus Logic

When a modal or dialog opens, focus must move into it, remain meaningfully constrained, and return to the invoking control when closed.

WCAG:2.1.12.4.34.1.2

AGAG-N7

Authentication Must Not Depend on Visual Puzzles or Ambiguous Human-Proof Rituals

Authentication and abuse prevention must not require image interpretation, press-and-hold behavior, cursor path tracing, or other mechanisms that exclude legitimate assistive agents or disabled humans when no accessible alternative exists.

WCAG:2.1.12.5.x3.3.2

Pillar E

Economic

AGAG-E1

Interfaces Must Minimize Structural Noise

Avoid unnecessary DOM complexity that obscures meaning.

AGAG-E2

Provide Direct Structured Access When Possible

Expose structured data or APIs for repeatable tasks.

Pillar V

Verifiable

AGAG-V1

Action Meaning Must Be Explicit and Truthful

Buttons and actions must clearly represent their real outcome.

AGAG-V2

Critical Data Must Include Provenance and Freshness

Time-sensitive information must expose source and date.

AGAG-V3

Critical Instructions Must Be Explicit, Not Implied

Instructions required for task completion must be visible, textual, and machine-detectable. They must not depend on inference from layout, color, or prior hidden knowledge.

WCAG:3.3.23.3.3

Pillar C

Consent & Control

AGAG-C1

High-Risk Actions Must Require Explicit Confirmation

Medical, financial, or irreversible actions must require confirmation.

AGAG-C2

Agent Scope Must Be Declared

The system must expose what an agent is allowed to do.

AGAG-C3

Human Override Must Always Be Available

Users must be able to interrupt or override agent actions.

AGAG-C4

Delegated Access Paths Must Be Explicit

A system must distinguish between harmful automation and authorized delegated assistance, and must expose a compliant path for trusted assistive or authorized agents.

The web cannot treat all bots as abuse if some bots are literally performing accessibility support.

AGAG-C5

In-Progress Work Must Be Recoverable

For multi-step tasks, the system must preserve or restore in-progress state wherever possible, especially for high-stakes processes.

Loss of state is both an accessibility failure and an agentic failure.