F Kitchen Sink

Accessibility audit rules

Change On Request

Accessibility rule handbook metadata

Rule
DET.A11Y.GENERIC.CHANGE_ON_REQUEST · lane deterministic · scope generic
Page status
current
page_version
b5f903faa162827c61df0cc12c6c5246adc374d0cc6a65c4343d322a12d78e77
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: 3.2.5

How this rule is checked

Deterministic lane — scope generic. Detected by det-a11y-generic-*.check.js or the axe lane for WCAG-tagged violations.

  • Harness: auditor-tests/invoke-a11y-ruleset-harness.sh on the Before fixture.
  • Audit: analyze-website-a11y.mjs --only-deterministic-rule-ids DET.A11Y.GENERIC.CHANGE_ON_REQUEST

Module: docs/design/a11y-audit/deterministic-a11y-rules.md#det-a11y-generic-change-on-request. See Before / After below.

Purpose

Deterministic accessibility check (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 DET.A11Y.GENERIC.CHANGE_ON_REQUEST on the crawled URL.
  • Harness: auditor-tests/invoke-a11y-ruleset-harness.sh DET.A11Y.GENERIC.CHANGE_ON_REQUEST expects ≥1 finding on the Before fixture.

Before example

Before (failing example)

Change On Request

DOM or content signals fail DET.A11Y.GENERIC.CHANGE_ON_REQUEST (change on request).

Rule: DET.A11Y.GENERIC.CHANGE_ON_REQUEST · scope: generic

After example

After (passing example)

Change On Request (remediated)

DOM and content satisfy DET.A11Y.GENERIC.CHANGE_ON_REQUEST after remediation.

Deterministic accessibility check (generic scope).

Evidence and remediation

  1. Reproduce with analyze-website-a11y.mjs --only-deterministic-rule-ids DET.A11Y.GENERIC.CHANGE_ON_REQUEST 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.