Add WCAG 2.2 AA accessibility review plan and project delivery documents

[Copilot]

Commits the two planning documents referenced by the A11Y program umbrella issue. Without these files the issue has no source-of-truth for findings or delivery sequencing.

Description

Adds ACCESSIBILITY-REVIEW-PLAN.md and ACCESSIBILITY-GITHUB-PROJECT-PLAN.md to the repository root.

ACCESSIBILITY-REVIEW-PLAN.md

Component-by-component findings from source review of templates and JavaScript, mapped to WCAG 2.2 SC with priority tiers (P0–P3), required fixes, and acceptance criteria.

Finding	Component	WCAG SC	Priority
Broken skip link — <main> has no id="content"	az_barrio page/html templates	2.4.1 (A)	P0
Pager aria-label receives raw ID string; no aria-current on active page	az_barrio pager template	1.3.1, 2.4.6 (AA)	P1
Accordion circular aria-labelledby + wrong data-bs-parent target	az_accordion	4.1.2 (AA)	P1
Alpha listing: no nav landmark name, no live region for search, href missing #	az_alphabetical_listing	2.4.6, 4.1.3 (AA)	P1
Select menu form has no accessible name; aria-disabled on <select>	az_select_menu	1.3.1, 4.1.2 (AA)	P1
Carousel keyboard/pause audit required	az_carousel	2.1.1, 2.2.2 (A)	P1
Date picker keyboard/focus audit required	az_core (vanilla-calendar-pro)	2.1.1, 2.1.2 (A)	P1
Redundant role="contentinfo" on inner footer div	az_barrio page template	4.1.2 (AA)	P2
Publication type table missing <caption>	az_publication	1.3.1 (A)	P2
Marketing Cloud export scope decision pending	az_marketing_cloud	Scope-dep.	P3

Also includes a verification matrix of representative pages and four open questions requiring team decisions before Phase 1 implementation.

ACCESSIBILITY-GITHUB-PROJECT-PLAN.md

Phased delivery structure with per-deliverable file paths, code diffs, and acceptance criteria:

• Phase 0 — Automated axe scan in CI; baseline capture; manual test checklist
• Phase 1 — Global blockers: skip link target, pager aria-labelledby/aria-current, footer duplicate landmark
• Phase 2 — Interactive components: accordion ARIA, alpha listing nav/live region/href bug, select menu form name, carousel audit, date picker audit
• Phase 3 — Semantics: publication table <caption>, Marketing Cloud scope resolution
• Phase 4 — Rendered verification, axe CI promotion from informational to blocking, release notes

Also defines GitHub label/milestone taxonomy, a delivery issue body template, and conditions of satisfaction for the program umbrella issue.

Release notes

Related issues

Umbrella issue: A11Y Program: WCAG 2.2 AA accessibility remediation for az_quickstart

How to test

Read both documents and confirm:

• Every finding in ACCESSIBILITY-REVIEW-PLAN.md references an actual file path in the repository.
• ACCESSIBILITY-GITHUB-PROJECT-PLAN.md Phase 1–3 deliverables each specify the file to change, the before/after diff, and acceptance criteria.
• Variable names and template references (e.g. preform_text_sr_only, accordion_item_id, accordion_container_id) match what exists in the codebase.

Types of changes

Arizona Quickstart (install profile, custom modules, custom theme)

• Patch release changes
  • Bug fix
  • Accessibility, performance, or security improvement
  • Critical institutional link or brand change
  • Adding experimental module
  • Update experimental module
• Minor release changes
  • New feature
  • Breaking or visual change to existing behavior
  • Upgrade experimental module to stable
  • Enable existing module by default or database update
  • Non-critical brand change
  • New internal API or API improvement with backwards compatibility
  • Risky or disruptive cleanup to comply with coding standards
  • High-risk or disruptive change (requires upgrade path, risks regression, etc.)
• Other or unknown
  • Other or unknown

Drupal core

• Patch release changes
  • Security update
  • Patch level release (non-security bug-fix release)
  • Patch removal that's no longer necessary
• Minor release changes
  • Major or minor level update
• Other or unknown
  • Other or unknown

Drupal contrib projects

• Patch release changes
  • Security update
  • Patch or minor level update
  • Add new module
  • Patch removal that's no longer necessary
• Minor release changes
  • Major level update
• Other or unknown
  • Other or unknown

Checklist

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.
• My change requires release notes.