docs: accessibility planning package

ACCESSIBILITY-EXECUTIVE-EMAIL-DRAFT.md

@@ -0,0 +1,52 @@
+# Executive Email Draft - Accessibility Program Setup Complete
+
+## Subject Line Options
+
+1. az_quickstart accessibility program is organized and ready for review
+2. Accessibility planning and GitHub dashboard are ready for Friday discussion
+3. WCAG 2.2 AA planning structure is now in place for az_quickstart
+
+## Email Draft
+
+Hello,
+
+I completed the accessibility planning and GitHub organization work for the az_quickstart WCAG 2.2 AA effort today.
+
+The main result is that the work is now organized as a structured program rather than a flat list of defects. We now have a live GitHub board, a single umbrella issue, phased parent issues, and a linked set of delivery issues that the team can use for Friday’s planning discussion.
+
+Key artifacts:
+
+- Project board: https://github.com/orgs/az-digital/projects/285
+- Umbrella issue: https://github.com/az-digital/az_quickstart/issues/5533
+- Review plan in GitHub: https://github.com/az-digital/az_quickstart/blob/docs/accessibility-planning-2026-04-23/ACCESSIBILITY-REVIEW-PLAN.md
+- GitHub execution plan in GitHub: https://github.com/az-digital/az_quickstart/blob/docs/accessibility-planning-2026-04-23/ACCESSIBILITY-GITHUB-PROJECT-PLAN.md
+
+The work is organized into five phases:
+
+1. Accessibility guardrails and verification setup
+2. Global user experience blockers
+3. High-risk interactive components
+4. Content and template semantics
+5. Verification and release readiness
+
+This gives the team a clearer way to prioritize the work by user impact and release risk.
+
+The recommended approach is intentionally well targeted. Rather than spreading effort evenly across every finding, the first wave should focus on changes that create immediate and noticeable improvement in common user journeys.
+
+For Friday, the most important remaining decisions are:
+
+1. What verification standard should apply before implementation begins.
+2. Which issues are patch-safe versus minor-release work.
+3. Which ambiguous items should remain in the discussion queue until the team agrees on scope.
+
+No implementation work has started as part of this setup. The purpose of today’s work was to create the planning structure so the team can have a more disciplined discussion before coding begins.
+
+Because this package is broader than a normal issue review, it may make sense to hold a dedicated meeting focused on reviewing the planning materials and confirming the initial direction.
+
+The project dashboard itself is a standing program asset and is not tied to a feature or bug branch. The dedicated planning branch only stores the supporting documents for review.
+
+This message is ready to send as written. It uses live GitHub links for the board, umbrella issue, and supporting documents.
+
+Thanks,
+
+Jeff

ACCESSIBILITY-FINAL-REVIEW-EMAIL.md

@@ -0,0 +1,90 @@
+# Final Review Email - Accessibility Program Package
+
+## Subject Line Options
+
+1. az_quickstart accessibility review package and Friday planning materials
+2. Accessibility program review materials are ready for Friday
+3. WCAG 2.2 AA planning package for az_quickstart is ready for review
+
+## Send-Ready Email
+
+Hello everyone,
+
+I completed the accessibility planning and GitHub organization work for the az_quickstart WCAG 2.2 AA effort today, and the full review package is now ready for everyone to review before Friday.
+
+## Executive Summary
+
+The accessibility work is now organized as a structured program rather than a flat list of findings. We have:
+
+1. A completed source-level accessibility review.
+2. A phased remediation and verification plan.
+3. A live GitHub project board.
+4. An umbrella issue and linked phase and delivery issues.
+5. A narrowed Friday decision queue.
+6. Meeting materials and supporting documents for discussion.
+
+No implementation work has started. The purpose of today’s work was to make sure the team can review the findings, discuss the open decisions, and align on scope and sequencing before any coding begins.
+
+## Primary Review Links
+
+- [Project board](https://github.com/orgs/az-digital/projects/285)
+- [Umbrella issue](https://github.com/az-digital/az_quickstart/issues/5533)
+- [Consolidated send-out brief](https://github.com/az-digital/az_quickstart/blob/docs/accessibility-planning-2026-04-23/ACCESSIBILITY-SENDOUT-BRIEF.md)
+- [One-page Friday handout](https://github.com/az-digital/az_quickstart/blob/docs/accessibility-planning-2026-04-23/ACCESSIBILITY-FRIDAY-HANDOUT.md)
+
+## Detailed Planning Documents
+
+- [Accessibility review plan](https://github.com/az-digital/az_quickstart/blob/docs/accessibility-planning-2026-04-23/ACCESSIBILITY-REVIEW-PLAN.md)
+- [GitHub execution plan](https://github.com/az-digital/az_quickstart/blob/docs/accessibility-planning-2026-04-23/ACCESSIBILITY-GITHUB-PROJECT-PLAN.md)
+- [Phase 0.1 verification proposal](https://github.com/az-digital/az_quickstart/blob/docs/accessibility-planning-2026-04-23/ACCESSIBILITY-P0.1-VERIFICATION-PROPOSAL.md)
+- [Phase 0.2 scanner workflow plan](https://github.com/az-digital/az_quickstart/blob/docs/accessibility-planning-2026-04-23/ACCESSIBILITY-P0.2-SCANNER-WORKFLOW-PLAN.md)
+- [Manual verification playbook](https://github.com/az-digital/az_quickstart/blob/docs/accessibility-planning-2026-04-23/ACCESSIBILITY-MANUAL-VERIFICATION-PLAYBOOK.md)
+- [Scanner triage guide](https://github.com/az-digital/az_quickstart/blob/docs/accessibility-planning-2026-04-23/ACCESSIBILITY-SCANNER-TRIAGE-GUIDE.md)
+- [Release sign-off checklist](https://github.com/az-digital/az_quickstart/blob/docs/accessibility-planning-2026-04-23/ACCESSIBILITY-RELEASE-SIGNOFF-CHECKLIST.md)
+- [Representative URL inventory and environment map](https://github.com/az-digital/az_quickstart/blob/docs/accessibility-planning-2026-04-23/ACCESSIBILITY-REPRESENTATIVE-URL-INVENTORY.md)
+
+## Friday Meeting Materials
+
+- [Meeting agenda](https://github.com/az-digital/az_quickstart/blob/docs/accessibility-planning-2026-04-23/ACCESSIBILITY-FRIDAY-MEETING-AGENDA.md)
+- [Facilitator script](https://github.com/az-digital/az_quickstart/blob/docs/accessibility-planning-2026-04-23/ACCESSIBILITY-FRIDAY-FACILITATOR-SCRIPT.md)
+- [Presentation talk track](https://github.com/az-digital/az_quickstart/blob/docs/accessibility-planning-2026-04-23/ACCESSIBILITY-LIVE-PRESENTATION-TALK-TRACK.md)
+- [Project views handoff](https://github.com/az-digital/az_quickstart/blob/docs/accessibility-planning-2026-04-23/ACCESSIBILITY-PROJECT-VIEWS-HANDOFF.md)
+- [Post-meeting notes template](https://github.com/az-digital/az_quickstart/blob/docs/accessibility-planning-2026-04-23/ACCESSIBILITY-POST-MEETING-NOTES-TEMPLATE.md)
+
+## Friday Decision Queue
+
+These are the issues that currently require explicit team decisions before implementation should begin:
+
+1. [#5533 - Umbrella program issue](https://github.com/az-digital/az_quickstart/issues/5533)
+2. [#5541 - Verification policy and representative page matrix](https://github.com/az-digital/az_quickstart/issues/5541)
+3. [#5550 - Marketing Cloud export route decision](https://github.com/az-digital/az_quickstart/issues/5550)
+4. [#5544 - Gallery carousel release direction](https://github.com/az-digital/az_quickstart/issues/5544)
+5. [#5545 - Date picker release direction](https://github.com/az-digital/az_quickstart/issues/5545)
+
+## Recommended First-Wave Candidates
+
+If the Friday decisions are confirmed, these are the strongest first-wave candidates:
+
+1. [#5541](https://github.com/az-digital/az_quickstart/issues/5541)
+2. [#5539](https://github.com/az-digital/az_quickstart/issues/5539)
+3. [#5538](https://github.com/az-digital/az_quickstart/issues/5538)
+4. [#5540](https://github.com/az-digital/az_quickstart/issues/5540)
+5. [#5537](https://github.com/az-digital/az_quickstart/issues/5537)
+6. [#5514](https://github.com/az-digital/az_quickstart/issues/5514)
+
+## What I Recommend Everyone Review Before Friday
+
+If time is limited, review these in order:
+
+1. The [one-page Friday handout](https://github.com/az-digital/az_quickstart/blob/docs/accessibility-planning-2026-04-23/ACCESSIBILITY-FRIDAY-HANDOUT.md)
+2. The [project board](https://github.com/orgs/az-digital/projects/285)
+3. The [umbrella issue](https://github.com/az-digital/az_quickstart/issues/5533)
+4. The [review plan](https://github.com/az-digital/az_quickstart/blob/docs/accessibility-planning-2026-04-23/ACCESSIBILITY-REVIEW-PLAN.md)
+
+Thanks,
+
+Jeff
+
+## Notes
+
+This email is ready to send as written. It uses live GitHub links for the board and issues, while the supporting documents are published from the dedicated planning branch so recipients can review everything in the browser.

ACCESSIBILITY-FRIDAY-FACILITATOR-SCRIPT.md

@@ -0,0 +1,199 @@
+# Friday Facilitator Script - az_quickstart Accessibility Program
+
+## Purpose
+
+This script is a facilitator aid for the Friday accessibility planning meeting. It is designed to keep the conversation focused on decisions, sequencing, and ownership rather than drifting into solution design.
+
+Use this alongside:
+
+- [ACCESSIBILITY-FRIDAY-MEETING-AGENDA.md](ACCESSIBILITY-FRIDAY-MEETING-AGENDA.md)
+- [ACCESSIBILITY-P0.1-VERIFICATION-PROPOSAL.md](ACCESSIBILITY-P0.1-VERIFICATION-PROPOSAL.md)
+- [ACCESSIBILITY-P0.2-SCANNER-WORKFLOW-PLAN.md](ACCESSIBILITY-P0.2-SCANNER-WORKFLOW-PLAN.md)
+- [ACCESSIBILITY-MANUAL-VERIFICATION-PLAYBOOK.md](ACCESSIBILITY-MANUAL-VERIFICATION-PLAYBOOK.md)
+- [ACCESSIBILITY-SCANNER-TRIAGE-GUIDE.md](ACCESSIBILITY-SCANNER-TRIAGE-GUIDE.md)
+- [ACCESSIBILITY-RELEASE-SIGNOFF-CHECKLIST.md](ACCESSIBILITY-RELEASE-SIGNOFF-CHECKLIST.md)
+- [ACCESSIBILITY-REPRESENTATIVE-URL-INVENTORY.md](ACCESSIBILITY-REPRESENTATIVE-URL-INVENTORY.md)
+- [GitHub project board](https://github.com/orgs/az-digital/projects/285)
+- [Umbrella program issue #5533](https://github.com/az-digital/az_quickstart/issues/5533)
+
+These Phase 0 support documents are preliminary working drafts. The facilitator should frame them as decision aids for [#5532](https://github.com/az-digital/az_quickstart/issues/5532), [#5541](https://github.com/az-digital/az_quickstart/issues/5541), and [#5539](https://github.com/az-digital/az_quickstart/issues/5539), not as finalized policy.
+
+## Facilitator Goal
+
+At the end of the meeting, the team should be aligned on:
+
+1. What the program includes.
+2. What decisions are still open.
+3. Which work should be considered first.
+4. What must be true before implementation begins.
+
+## Opening Script
+
+Suggested opening:
+
+"The purpose of today’s meeting is to review the accessibility program structure, confirm the decisions that affect scope and release planning, and agree on the first wave of work. We are not starting implementation today. We are making sure the work is organized correctly before implementation begins."
+
+Suggested framing note for the facilitator:
+
+"The recommended approach is intentionally targeted. We should start with the changes that create immediate, noticeable improvement for users on common journeys, then use the broader program structure to sequence the deeper work responsibly."
+
+## Section-by-Section Talking Points
+
+### 1. Program Overview
+
+Open with:
+
+- [Project board](https://github.com/orgs/az-digital/projects/285)
+- [Umbrella issue #5533](https://github.com/az-digital/az_quickstart/issues/5533)
+
+Talking points:
+
+1. The work is now structured as a program, not a flat accessibility backlog.
+2. The issues are grouped into phases so the team can prioritize by user impact and delivery risk.
+3. The project board contains the umbrella issue, the phase parents, and the child issues needed for planning.
+
+Prompt:
+
+"Does the program structure itself feel right before we discuss individual items?"
+
+Likely decision to capture:
+
+- Confirm or adjust the five-phase structure.
+
+### 2. Prioritization Lens
+
+Talking points:
+
+1. The current backlog is written to prioritize the user experience, not just technical cleanup.
+2. Global barriers and high-risk interaction failures should generally come before lower-visibility semantic cleanup.
+3. The board metadata now distinguishes likely patch work, minor work, and items that still need a release decision.
+
+Prompt:
+
+"Do we agree that the default order should be global blockers first, then high-risk components, then semantic and governance cleanup?"
+
+Likely decision to capture:
+
+- Confirm the prioritization model or note any institutional override.
+
+### 3. Phase Review
+
+Walk the team through these parent issues in order:
+
+1. [#5532](https://github.com/az-digital/az_quickstart/issues/5532)
+2. [#5535](https://github.com/az-digital/az_quickstart/issues/5535)
+3. [#5531](https://github.com/az-digital/az_quickstart/issues/5531)
+4. [#5536](https://github.com/az-digital/az_quickstart/issues/5536)
+5. [#5534](https://github.com/az-digital/az_quickstart/issues/5534)
+
+For each phase, ask:
+
+1. "Is this phase scoped correctly?"
+2. "Is anything missing?"
+3. "Is anything here actually a later or earlier phase item?"
+4. "Do the current release target assumptions feel right?"
+
+Likely decisions to capture:
+
+- Scope confirmation by phase
+- Phase shifts if any issues are misplaced
+
+### 4. Friday Decision Queue
+
+Use these issues as the explicit decision queue:
+
+- [#5533](https://github.com/az-digital/az_quickstart/issues/5533)
+- [#5541](https://github.com/az-digital/az_quickstart/issues/5541)
+- [#5550](https://github.com/az-digital/az_quickstart/issues/5550)
+- [#5544](https://github.com/az-digital/az_quickstart/issues/5544)
+- [#5545](https://github.com/az-digital/az_quickstart/issues/5545)
+
+These issues now carry the `needs discussion` label and are intended to represent the narrowest useful Friday decision queue.
+
+Talking points:
+
+1. [#5541](https://github.com/az-digital/az_quickstart/issues/5541) determines the verification standard for everything else.
+2. [#5539](https://github.com/az-digital/az_quickstart/issues/5539) is now supported by a preliminary scanner workflow plan, manual verification playbook, triage guide, sign-off checklist, and URL inventory.
+2. [#5550](https://github.com/az-digital/az_quickstart/issues/5550) is an architectural and product-boundary decision.
+3. [#5544](https://github.com/az-digital/az_quickstart/issues/5544) and [#5545](https://github.com/az-digital/az_quickstart/issues/5545) are currently set to `Undecided` because they are the most likely to shift between a narrower patch approach and a fuller minor-release approach.
+
+Additional framing note:
+
+"The new Phase 0 documents should be reviewed as working drafts that support the board's Phase 0 placemarkers. They are here to accelerate decisions, not to bypass them."
+
+Recommended starting positions to bring into the room:
+
+1. Treat Marketing Cloud export routes as browser-facing until the team explicitly confirms fragment-only usage.
+2. Approve a representative page matrix that is intentionally narrow, high-value, and built around common journeys plus the highest-risk widgets.
+3. Use the representative page matrix as the release gate for both patch and minor releases rather than waiting for full-site coverage.
+4. Keep gallery carousel and date-picker structural rewrites in minor-release territory unless the team identifies a narrower patch-safe path.
+
+Prompts:
+
+1. "Which of these truly need a team decision before work begins?"
+2. "Which of these are clearly minor-release work, and which might still be narrowed into patch-safe work?"
+3. "Which open questions require discovery versus a policy decision?"
+4. "Are the preliminary Phase 0 working drafts directionally correct enough to use as the working basis for implementation planning on #5541 and #5539?"
+
+Likely decisions to capture:
+
+- Final Friday decision list
+- Patch versus minor direction for the ambiguous items
+- Any spikes or follow-up analysis needed
+
+### 5. First Implementation Wave
+
+Recommended candidates to confirm:
+
+- [#5541](https://github.com/az-digital/az_quickstart/issues/5541)
+- [#5539](https://github.com/az-digital/az_quickstart/issues/5539)
+- [#5538](https://github.com/az-digital/az_quickstart/issues/5538)
+- [#5540](https://github.com/az-digital/az_quickstart/issues/5540)
+- [#5537](https://github.com/az-digital/az_quickstart/issues/5537)
+- [#5514](https://github.com/az-digital/az_quickstart/issues/5514)
+
+Prompt:
+
+"If we had to define the first implementation wave today, which of these are truly ready once the decision items are settled?"
+
+Facilitator reminder:
+
+Keep the discussion anchored on immediate impact. The first wave should improve navigation, naming, announcements, and reachability in places users will notice right away.
+
+Likely decision to capture:
+
+- Confirm the first wave or identify dependencies that still block it.
+
+### 6. Ownership and Next Steps
+
+Prompts:
+
+1. "Who owns the Phase 0 policy and verification decisions?"
+2. "Who owns keeping the board metadata current after Friday?"
+3. "Which issues need updates immediately after the meeting?"
+4. "What is the explicit signal that allows implementation planning to begin?"
+5. "Who owns converting the preliminary Phase 0 drafts into approved working documents after the meeting?"
+
+Likely decisions to capture:
+
+- Owners
+- Immediate follow-up edits
+- Next planning checkpoint
+
+## Redirect Lines for Common Meeting Drift
+
+If the conversation becomes too implementation-specific:
+
+"Let’s capture that as an implementation note, but keep this meeting focused on whether the work belongs in scope, what phase it belongs in, and whether it is patch-safe or minor-release work."
+
+If the conversation becomes too broad:
+
+"Let’s bring it back to the current decision queue and make sure we leave with clear release and verification decisions."
+
+If the conversation gets stuck on one issue:
+
+"Let’s decide whether this needs a policy decision, a spike, or a delivery issue update, and then keep moving."
+
+## Suggested Closing Script
+
+"We now have a structured program, a defined decision queue, and a clearer sense of what belongs in the first wave. The next step is to reflect today’s decisions in the issues and board metadata, and only then move into implementation planning."