[kelvinalfaro]

Summary

• add an explicit audit <target> --accessibility route
• add a read-only WCAG 2.2 AA audit receipt with evidence labels, severity, task paths, reflow, input and assistive-technology coverage
• keep untested paths visible and state that automated findings alone do not establish conformance
• document the new audit option and refresh the generated theme-index date required by repository verification

Why

Hallmark already checks several accessibility-related design failures, including contrast, focus and reduced motion. Its audit flow did not distinguish an automated or source finding from behaviour actually exercised with a keyboard, touch input or assistive technology.

This route makes that evidence boundary explicit. It also reports WCAG 2.2 SC 2.5.8 (Level AA, 24 by 24 CSS px or an allowed exception) separately from SC 2.5.5 (Level AAA, 44 by 44 CSS px) and Hallmark gate 39b.

The reference is newly written for Hallmark from its v2 gates and the W3C guidance linked in the file. It adds no runtime dependency.

Validation

• node skills/hallmark/scripts/refcheck.mjs - clean across 100 reference files
• node skills/hallmark/scripts/theme.mjs validate ... - all 48 themes passed
• node skills/hallmark/scripts/theme.mjs index - generated index is current
• focused contract checks passed for explicit routing, read-only scope, evidence labels, AA/AAA target-size distinction and the conformance-claim boundary

[vercel]

@kelvinalfaro is attempting to deploy a commit to the Together AI Team on Vercel.

A member of the Team first needs to authorize it.