microsoft/hve-core

Public

mirrored from https://github.com/microsoft/hve-coreAvailable

CodeCommitsIssuesPull requestsActionsInsightsSecurity
83a260607c12fda28c813d44de416bad498156ff

Branches

Tags

  • No tags available.
0Branches0Tags
Go to file
Add file
Code

Clone

HTTPS

Download ZIP

docs/getting-started/accessibility-planner.md

66lines · modecode

1---
2title: Accessibility Planner Quickstart
3description: A five-minute walkthrough of starting the Accessibility Planner, selecting frameworks, mapping success criteria, and handing off a dual-format backlog
4sidebar_position: 10
5sidebar_label: Accessibility Planner Quickstart
6keywords:
7 - accessibility planner
8 - quickstart
9 - WCAG 2.2
10 - Section 508
11 - getting started
12author: Microsoft
13ms.date: 2026-05-28
14ms.topic: tutorial
15estimated_reading_time: 5
16---
17
18This quickstart walks you through a first Accessibility Planner session: starting the agent, selecting frameworks, mapping success criteria, and handing off a backlog. The full agent reference lives in [Accessibility Planner](../agents/accessibility/accessibility-planner.md).
19
20> [!NOTE]
21> The planner produces planning artifacts, not a conformance certification. Findings still require review by a qualified accessibility professional.
22
23## Prerequisites
24
25* The Accessibility collection installed (see [Collections](collections.md)).
26* A workspace with the product surfaces you intend to assess, or a PRD, BRD, RAI plan, or security plan to seed Phase 1.
27
28## Step 1: Start the planner
29
30Open the chat agent picker and select **Accessibility Planner**. The agent reads or creates `state.json` under `.copilot-tracking/accessibility/{project-slug}/` and begins Phase 1 (Discovery).
31
32If no upstream artifact exists, the planner enters capture mode and asks three to five focused questions per turn to build the surface inventory, audience scope, and regulatory drivers. If a PRD, BRD, RAI plan, or security plan exists, the matching entry mode pre-populates discovery and asks you to confirm the extracted values.
33
34## Step 2: Select frameworks
35
36At Phase 2, the planner presents the five supported frameworks as a multi-select, with `wcag-22@AA` and `section-508` pre-checked as defaults:
37
38* `wcag-22`: WCAG 2.2 success criteria
39* `aria-apg`: ARIA Authoring Practices
40* `coga`: Cognitive Accessibility
41* `section-508`: Section 508 (Revised)
42* `en-301-549`: EN 301 549
43
44Confirm the conformance level for each framework you keep, and record a reason for any framework you disable.
45
46## Step 3: Map success criteria
47
48In Phase 3, the planner maps your in-scope surfaces against the selected frameworks. Each success criterion resolves to a target compliance state with an evidence pointer. Criteria shared across frameworks emit cross-references so you map them once.
49
50## Step 4: Assess risk and evidence
51
52Phases 4 and 5 classify the plan-level risk tier and build the evidence register, tradeoff log, and work-item seeds. For each unresolved gap, you record either a mitigation or an accept-with-tradeoff decision.
53
54## Step 5: Hand off the backlog
55
56At Phase 6, the planner renders the work-item seeds into dual-format ADO and GitHub backlog files, attaches autonomy tiers, sanitizes content, and emits the planning disclaimer. Import the format that matches your tracking system.
57
58## Next Steps
59
60* [Cross-Planner Integration](cross-planner-integration.md) for how accessibility evidence flows to and from the Security, RAI, and SSSC planners.
61* [Accessibility Reviewer](../agents/accessibility/accessibility-reviewer.md) to audit a codebase against the same frameworks.
62
63<!-- markdownlint-disable MD036 -->
64*🤖 Crafted with precision by ✨Copilot following brilliant human instruction,
65then carefully refined by our team of discerning human reviewers.*
66<!-- markdownlint-enable MD036 -->
67