Skip to content

docs(governance): document accessibility audit vocabulary - #6177

Merged
bokelley merged 4 commits into
mainfrom
docs/accessibility-compliance-governance
Aug 8, 2026
Merged

docs(governance): document accessibility audit vocabulary#6177
bokelley merged 4 commits into
mainfrom
docs/accessibility-compliance-governance

Conversation

@bokelley

@bokelley bokelley commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

Summary

Narrows the docs-only slice related to #4740:

  • documents accessibility_compliance as conventional, opaque response/audit vocabulary
  • removes the unsupported claim that governance categories are declared through get_adcp_capabilities
  • avoids presenting accessibility_compliance as an activated sync_plans category
  • states that this label does not activate policy or establish typed canonical format or asset requirements
  • keeps structured per-asset failures and the full accessibility lifecycle for follow-up protocol work

This PR does not complete or close #4740.

Verification

  • node --test --test-force-exit --test-timeout=30000 tests/accessibility-governance-category.test.cjs
  • git diff --check

Related: #4740

@bokelley
bokelley marked this pull request as ready for review August 3, 2026 14:38

@aao-secretariat aao-secretariat Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ladon verdict: Approve

Approve — small, well-scoped docs PR registering accessibility_compliance as a canonical governance validation category.

What I checked:

  • Schema↔docs coherence: category_id in sync-plans-response.json is an open string (no enum), and the referenced format.accessibility.wcag_level / requires_accessible_assets fields exist in format.json — no wire-shape edit required, no drift.
  • Changeset correctness: a minor changeset is the right type for a non-breaking, additive governance-category registration. Not a breaking-class change, so the hard breaking-change escalation gate does not apply.
  • No high-risk paths, no gated paths.

Decision path: No critical/high findings (row 1 n/a). gated_paths is false, so row 2 does not fire despite review_decision: REVIEW_REQUIRED. No deletions, no medium data-loss/schema/infra findings, no author-team gate, fewer than three mediums. The single finding is low (PR body verification note contradicts the added minor changeset — cosmetic, the changeset itself is correct). Falls through to row 9 → approve.

Nit (non-blocking): .changeset/register-accessibility-governance-category.md — the PR body claims it 'carries no protocol changeset' while a minor changeset is present; consider reconciling the PR description.

aao-secretariat[bot]
aao-secretariat Bot previously approved these changes Aug 3, 2026

@aao-secretariat aao-secretariat Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ladon verdict: Approve

Approve — docs-only Normative (non-breaking) addition registering the accessibility_compliance governance validation category.

What I checked:

  • No wire-shape change: category_id in sync-plans-response.json is a free-form string (not an enum), so adding a new category value is not schema drift.
  • Field references (format.accessibility.wcag_level, requires_accessible_assets at core/format.json:591-604) are accurate against the schema.
  • Docs-only, no-changeset is correct — docs/governance/** is outside PROTOCOL_SCOPED_PATHS.
  • Canonical-set framing does not contradict the opaque categories_evaluated labels in check_governance.mdx.
  • Content-presence test ships alongside the docs change.

Gates:

  • gated_paths: false — row 2 does not apply despite review_decision: REVIEW_REQUIRED.
  • No no-auto-approve team match (row 7 N/A).
  • high_risk: false; no deleted/modified high-risk files.
  • No critical/high/medium findings.

This is an Editorial/Normative non-breaking docs addition, not a Breaking-class change, so the human-ratification hard gate does not apply. No findings fired rows 1–8; falls through to row 9 → approve.

@bokelley bokelley changed the title docs(governance): register accessibility compliance docs(governance): document accessibility audit vocabulary Aug 6, 2026

@aao-secretariat aao-secretariat Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Re-approval: no reviewable delta since the prior approval; re-submitting after stale-review dismissal.

@bokelley
bokelley merged commit eaa84a3 into main Aug 8, 2026
18 of 27 checks passed
@bokelley
bokelley deleted the docs/accessibility-compliance-governance branch August 8, 2026 03:22
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.

RFC: Add accessibility as a first-class category in Content Standards

1 participant