Standards Ingestion

Overview

A11YSmith maintains a standards catalog that maps Target Accessibility Standards to WCAG 2.2 success criteria. This mapping drives the standards basis reported in every finding.

Standards Precedence Rules

1. Target Accessibility Standards are the primary authority.
2. Target platform-specific implementation guidance is the primary implementation reference for native apps.
3. WCAG 2.2 AA is the fallback only when Target guidance is missing, less specific, or not directly applicable.
4. Never emit a WCAG-only finding without first attempting to map it to a related Target standard.
5. If both apply, report both, but lead with Target framing.
6. Every rule and finding must declare which standard source was used and why.

Current Catalog

Phase 1 includes a stub catalog of 10 Target standards covering:

• Semantics (buttons vs. links)
• Structure (headings and landmarks)
• Forms (labels and error messaging)
• Images (alternative text)
• Modals (focus management)
• Tables (data table structure)
• Focus (indicators and tab order)
• Target size (touch and click targets)
• Live regions (dynamic announcements)
• Name, role, value (custom controls)

Ingestion Process

In production, the catalog would be ingested from Target's internal standards repository. The @a11ysmith/standards package provides:

• lookupTargetStandard(id) — look up a standard by ID
• getStandardsByCategory(category) — filter by category
• getStandardsByPlatform(platform) — filter by platform
• buildCrosswalk() — generate the full Target-to-WCAG crosswalk
• buildStandardsBasis(targetStandard, wcagScId) — build a standards basis object for a finding