F Kitchen Sink

Accessibility audit rules

Keyboard Task Flow

Accessibility rule handbook metadata

Rule
AI.A11Y.GENERIC.KEYBOARD_TASK_FLOW · lane ai · scope generic
Page status
current
page_version
2e582f59785f7d770db13878d07bae384504398c6d3a5d84a512928ab7fdf93c
generated_at
2026-05-28T05:09:12.000Z
registry_fingerprint
b3797010c3ca988bb0d21d5e85d4efece0b9e83f311c2d4981ebbf402df7a7c2

Related WCAG success criteria

Indicative mapping for compliance reporting — not a conformance claim. Criteria: 2.1.1, 2.1.2, 2.4.3, 2.4.7

How this rule is checked

AI lane — enable with --enable-ai. Judgment runs via Cursor/agent using prompts under design-rules/ai/prompts/generated/.

Module: docs/design/a11y-audit/ai-enabled-a11y-principles.md#ai-a11y-generic-keyboard-task-flow. See Before / After below.

Purpose

AI judgment overlay (generic scope).

Passing signals

  • DOM and/or repo signals satisfy the rule implementation in tools/website-a11y-auditor.
  • For axe-backed WCAG criteria, use --lanes axe,det with an appropriate --standard preset.

Failing signals

  • Auditor emits a finding with ruleId AI.A11Y.GENERIC.KEYBOARD_TASK_FLOW on the crawled URL.
  • Harness: auditor-tests/invoke-a11y-ruleset-harness.sh AI.A11Y.GENERIC.KEYBOARD_TASK_FLOW expects ≥1 finding on the Before fixture.

Before example

Before (failing example)

Keyboard Task Flow

Content or UX likely fails human judgment for this AI overlay rule.

Rule: AI.A11Y.GENERIC.KEYBOARD_TASK_FLOW · scope: generic

After example

After (passing example)

Keyboard Task Flow (remediated)

Signals satisfy the AI rule prompt expectations on review.

AI judgment overlay (generic scope).

Evidence and remediation

  1. Reproduce with analyze-website-a11y.mjs --only-deterministic-rule-ids AI.A11Y.GENERIC.KEYBOARD_TASK_FLOW when lane is deterministic.
  2. Apply the After markup pattern (or fix generator source for KS rules).
  3. Re-run harness or audit until the rule is clean on the target URL.