Skip to content

Add accessibility checks before a page ships - #13

Closed
dbalders wants to merge 1 commit into
UCSD:mainfrom
dbalders:accessibility-before-publishing
Closed

dbalders wants to merge 1 commit into
UCSD:mainfrom
dbalders:accessibility-before-publishing

Conversation

@dbalders

@dbalders dbalders commented Oct 10, 2026 •

Copy link
Copy Markdown
Member

Why

The accessibility rule lists what to get right in the markup but says nothing about checking it before a page ships. An agent can follow every rule, run nothing, and report the page as done. The TritonAI Skills Library had that missing piece in its ucsd-branding skill (dbalders/UCSD-Skills-Library#8). That skill was retired in favor of ucsd-decorator, which now syncs from this repo, so the check belongs here.

What changed

rules/40-accessibility.md gains "Before a page ships"

  • Always loaded: two sentences in the rule files. A page isn't done until its automated and manual checks pass; only an authorized owner can waive a failure, never an agent; and a pass is not a claim of full compliance.
  • On demand: the rest sits behind <!-- on-demand: before you call a page done or publish it -->:
    • The automated check: one command the project keeps (test:a11y or equivalent), run from the default test command, in PR checks, and in the production deploy. It scans every route at mobile and desktop widths, fails on violations, browser errors, overflow and keyboard failures, and saves a report artifact.
    • Chrome findings: a finding in the chrome follows the canvas rule. Stop and say so, and don't edit the chrome to clear it.
    • The manual pass: six steps (keyboard, focus, zoom and reflow, contrast, screen reader, untested states), plus a table of checks per Decorator component: navbar and drawer, carousels, tabs, modals, forms with MaxChar and Wizard, DataTables, status messages, FullCalendar, media.
    • Waivers: who can grant one and what it records. An agent never grants or infers one.
    • The report: what ran, what was fixed, what still needs a person, and what couldn't run.
  • Standards: the old closing paragraph ("Automated checks do not replace manual verification…") is folded into the new section. The UCSD tools page (Siteimprove, the brand contrast checker, NVDA, VoiceOver) is linked from the manual pass.

Skill: skills/ucsd-decorator/SKILL.md adds one paragraph to its Accessibility section pointing to the new section. references/accessibility.md carries the full text, so the skill works without DECORATOR.md.

Generated: CLAUDE.md, AGENTS.md, .cursorrules, .github/copilot-instructions.md, DECORATOR.md, and the reference page were recompiled. library/ was resynced.

Budget

CLAUDE.md compiles to 24,891 characters, under the 25,000 KIT_BUDGET, which leaves 109 characters of headroom. That's why the always-loaded part is two sentences. Everything else is on demand.

Not in this PR

The 3:1 contrast line in "Content and presentation" is still wrong for normal-size text (WCAG 2.1 AA requires 4.5:1). That fix is tracked separately in #12.

Verification

rules/40-accessibility.md gains a section requiring an automated check the
project keeps, a manual pass with per-component checks for the Decorator's
widgets, a report of what ran, and waivers only from an authorized owner.

The rule files keep two sentences and point to DECORATOR.md for the rest, so
CLAUDE.md stays within the kit's 25,000-character budget (24,891). The skill's
reference page carries the full text. A finding in the chrome follows the
canvas rule: stop and say so rather than editing the chrome.

Adapted from the accessibility gate in the TritonAI Skills Library's retired
ucsd-branding skill (dbalders/UCSD-Skills-Library#8).
@dbalders

Copy link
Copy Markdown
Member Author

Closing this one. Looking closer, a written process for agents to follow doesn't fit how the kit enforces things (CI checks like verify, not prose). If an accessibility check comes back, it's better designed with you as a kit feature. Sorry for the noise.

@dbalders dbalders closed this Oct 10, 2026
@dbalders
dbalders deleted the accessibility-before-publishing branch October 10, 2026 05:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant