diff --git a/.copilot-tracking/changes/2026-03-08/copilot-a11y-agents-changes.md b/.copilot-tracking/changes/2026-03-08/copilot-a11y-agents-changes.md
new file mode 100644
index 0000000..58cc24b
--- /dev/null
+++ b/.copilot-tracking/changes/2026-03-08/copilot-a11y-agents-changes.md
@@ -0,0 +1,58 @@
+<!-- markdownlint-disable-file -->
+# Release Changes: Custom Copilot Agents for AODA WCAG 2.2 Accessibility
+
+**Related Plan**: copilot-a11y-agents-plan.instructions.md
+**Implementation Date**: 2026-03-08
+
+## Summary
+
+Create two declarative GitHub Copilot agents (A11y Detector and A11y Resolver) with supporting WCAG 2.2 instructions and prompt files for AODA compliance.
+
+## Changes
+
+### Added
+
+* `.github/agents/a11y-detector.agent.md` — A11y Detector agent definition with static analysis and runtime scanning protocol (8,484 chars)
+* `.github/agents/a11y-resolver.agent.md` — A11y Resolver agent definition with 18-row remediation table and verify-fix workflow (7,820 chars)
+* `.github/instructions/wcag22-rules.instructions.md` — WCAG 2.2 Level AA compliance rules auto-applied to TSX/JSX/TS/HTML/CSS files, organized by POUR principles
+* `.github/instructions/a11y-remediation.instructions.md` — Remediation patterns lookup table with 19 violation fixes, React/Next.js code examples, and anti-patterns
+* `.github/prompts/a11y-scan.prompt.md` — Quick scan prompt delegating to A11y Detector agent with URL and scope inputs
+* `.github/prompts/a11y-fix.prompt.md` — Quick fix prompt delegating to A11y Resolver agent with file and violations inputs
+
+### Modified
+
+### Removed
+
+## Additional or Deviating Changes
+
+* No deviations from plan. All phases executed as specified.
+
+## Release Summary
+
+**Total files affected:** 6 files created, 0 modified, 0 removed
+
+**Files created:**
+
+* `.github/agents/a11y-detector.agent.md` — A11y Detector agent definition (8,484 chars) with 5-step protocol for static analysis and runtime scanning
+* `.github/agents/a11y-resolver.agent.md` — A11y Resolver agent definition (7,820 chars) with 6-step protocol for remediation and verification
+* `.github/instructions/wcag22-rules.instructions.md` — WCAG 2.2 Level AA rules organized by POUR principles, auto-applied to TSX/JSX/TS/HTML/CSS
+* `.github/instructions/a11y-remediation.instructions.md` — 19-row remediation lookup table with React/Next.js code examples and anti-patterns
+* `.github/prompts/a11y-scan.prompt.md` — Quick scan prompt delegating to A11y Detector with URL and scope inputs
+* `.github/prompts/a11y-fix.prompt.md` — Quick fix prompt delegating to A11y Resolver with file and violations inputs
+
+**ADO Work Items:**
+
+* Epic AB#2012: AODA WCAG 2.2 Copilot Integration
+* Feature AB#2013: Custom Copilot Agents for Accessibility (child of AB#2012)
+* User Story AB#2014: A11y Detector agent (child of AB#2013)
+* User Story AB#2015: A11y Resolver agent (child of AB#2013)
+* User Story AB#2016: WCAG 2.2 compliance instructions (child of AB#2013)
+* User Story AB#2017: Quick-action prompt files (child of AB#2013)
+
+**Git:**
+
+* Branch: `feature/2014-copilot-a11y-agents` from `main`
+* Commit: `feat(agents): add AODA WCAG 2.2 accessibility detector and resolver agents AB#2014`
+* PR: #9 targeting `main` with `Fixes AB#2014 AB#2015 AB#2016 AB#2017`
+
+**Validation:** ESLint 0 errors, 7/7 tests passing, all frontmatter validated
diff --git a/.copilot-tracking/plans/2026-03-08/copilot-a11y-agents-plan.instructions.md b/.copilot-tracking/plans/2026-03-08/copilot-a11y-agents-plan.instructions.md
index 8c9d799..c2a7d5f 100644
--- a/.copilot-tracking/plans/2026-03-08/copilot-a11y-agents-plan.instructions.md
+++ b/.copilot-tracking/plans/2026-03-08/copilot-a11y-agents-plan.instructions.md
@@ -56,64 +56,64 @@ Create two declarative GitHub Copilot agents — A11y Detector and A11y Resolver
 
 ## Implementation Checklist
 
-### [ ] Implementation Phase 1: Create Agent Definition Files
+### [x] Implementation Phase 1: Create Agent Definition Files
 
 <!-- parallelizable: true -->
 
-* [ ] Step 1.1: Create `.github/agents/` directory and `a11y-detector.agent.md`
+* [x] Step 1.1: Create `.github/agents/` directory and `a11y-detector.agent.md`
   * Details: [copilot-a11y-agents-details.md](.copilot-tracking/details/2026-03-08/copilot-a11y-agents-details.md) (Lines 12-75)
-* [ ] Step 1.2: Create `.github/agents/a11y-resolver.agent.md`
+* [x] Step 1.2: Create `.github/agents/a11y-resolver.agent.md`
   * Details: [copilot-a11y-agents-details.md](.copilot-tracking/details/2026-03-08/copilot-a11y-agents-details.md) (Lines 77-141)
 
-### [ ] Implementation Phase 2: Create Supporting Instructions Files
+### [x] Implementation Phase 2: Create Supporting Instructions Files
 
 <!-- parallelizable: true -->
 
-* [ ] Step 2.1: Create `.github/instructions/wcag22-rules.instructions.md`
+* [x] Step 2.1: Create `.github/instructions/wcag22-rules.instructions.md`
   * Details: [copilot-a11y-agents-details.md](.copilot-tracking/details/2026-03-08/copilot-a11y-agents-details.md) (Lines 145-188)
-* [ ] Step 2.2: Create `.github/instructions/a11y-remediation.instructions.md`
+* [x] Step 2.2: Create `.github/instructions/a11y-remediation.instructions.md`
   * Details: [copilot-a11y-agents-details.md](.copilot-tracking/details/2026-03-08/copilot-a11y-agents-details.md) (Lines 190-250)
 
-### [ ] Implementation Phase 3: Create Prompt Files
+### [x] Implementation Phase 3: Create Prompt Files
 
 <!-- parallelizable: true -->
 
-* [ ] Step 3.1: Create `.github/prompts/a11y-scan.prompt.md`
+* [x] Step 3.1: Create `.github/prompts/a11y-scan.prompt.md`
   * Details: [copilot-a11y-agents-details.md](.copilot-tracking/details/2026-03-08/copilot-a11y-agents-details.md) (Lines 252-285)
-* [ ] Step 3.2: Create `.github/prompts/a11y-fix.prompt.md`
+* [x] Step 3.2: Create `.github/prompts/a11y-fix.prompt.md`
   * Details: [copilot-a11y-agents-details.md](.copilot-tracking/details/2026-03-08/copilot-a11y-agents-details.md) (Lines 287-322)
 
-### [ ] Implementation Phase 4: ADO Work Items and Branching
+### [x] Implementation Phase 4: ADO Work Items and Branching
 
 <!-- parallelizable: false -->
 
-* [ ] Step 4.1: Create ADO Epic, Feature, and User Stories for the agent work
+* [x] Step 4.1: Create ADO Epic, Feature, and User Stories for the agent work
   * Details: [copilot-a11y-agents-details.md](.copilot-tracking/details/2026-03-08/copilot-a11y-agents-details.md) (Lines 326-353)
-* [ ] Step 4.2: Create feature branch and commit with AB# linking
+* [x] Step 4.2: Create feature branch and commit with AB# linking
   * Details: [copilot-a11y-agents-details.md](.copilot-tracking/details/2026-03-08/copilot-a11y-agents-details.md) (Lines 355-377)
 
-### [ ] Implementation Phase 5: Validation
+### [x] Implementation Phase 5: Validation
 
 <!-- parallelizable: false -->
 
-* [ ] Step 5.1: Validate agent file structure and frontmatter
+* [x] Step 5.1: Validate agent file structure and frontmatter
   * Verify YAML frontmatter parses correctly in both agent files
   * Confirm `description` under 120 characters
   * Confirm agent body under 30,000 characters (GitHub.com limit)
   * Verify no `maturity` field in agent frontmatter (per prompt-builder rules)
-* [ ] Step 5.2: Validate instructions file structure
+* [x] Step 5.2: Validate instructions file structure
   * Verify `applyTo` glob patterns match intended file types
   * Confirm instructions files have YAML frontmatter with `description` and `applyTo`
-* [ ] Step 5.3: Validate prompt file structure
+* [x] Step 5.3: Validate prompt file structure
   * Verify prompt files have `description`, `agent`, and `argument-hint` fields
-* [ ] Step 5.4: Run project linting and tests
+* [x] Step 5.4: Run project linting and tests
   * Execute `npm run lint` for ESLint validation
   * Execute `npm run test` for unit test verification
   * Verify no regressions from new files
-* [ ] Step 5.5: Fix minor validation issues
+* [x] Step 5.5: Fix minor validation issues
   * Iterate on lint errors and formatting issues
   * Apply fixes directly when corrections are straightforward
-* [ ] Step 5.6: Report blocking issues
+* [x] Step 5.6: Report blocking issues
   * Document issues requiring additional research
   * Provide user with next steps rather than large-scale inline fixes
 
diff --git a/.github/agents/a11y-detector.agent.md b/.github/agents/a11y-detector.agent.md
new file mode 100644
index 0000000..0ccd0a9
--- /dev/null
+++ b/.github/agents/a11y-detector.agent.md
@@ -0,0 +1,225 @@
+---
+name: A11y Detector
+description: 'Detects AODA WCAG 2.2 accessibility violations through static code analysis and runtime scanning'
+tools:
+  - read_file
+  - grep_search
+  - semantic_search
+  - file_search
+  - list_dir
+  - run_in_terminal
+  - manage_todo_list
+  - runSubagent
+handoffs:
+  - label: "Fix Violations"
+    agent: A11y Resolver
+    prompt: "Fix the accessibility violations found above"
+    send: false
+---
+
+# A11y Detector
+
+Detects AODA WCAG 2.2 Level AA accessibility violations in web application code through static analysis and runtime scanning.
+
+AODA (Accessibility for Ontarians with Disabilities Act) legally references WCAG 2.0 Level AA, but conforming to WCAG 2.2 Level AA automatically satisfies AODA. WCAG 2.2 adds six new Level A/AA criteria: Focus Not Obscured (2.4.11), Dragging Movements (2.5.7), Target Size Minimum (2.5.8), Consistent Help (3.2.6), Redundant Entry (3.3.7), and Accessible Authentication (3.3.8).
+
+Automated detection covers approximately 35-40% of WCAG 2.2 criteria. Another 25% are partially automatable. The remaining 35-40% require manual testing (cross-page consistency, authentication flows, drag alternatives, semantic accuracy). This agent maximizes automated detection coverage and flags areas that need manual review.
+
+## Top 10 React/Next.js Accessibility Violations
+
+These are the most common violations found in React and Next.js applications:
+
+1. `color-contrast` (1.4.3) — Tailwind/CSS colors with insufficient contrast ratio
+2. `image-alt` (1.1.1) — `<Image>` components missing `alt` prop
+3. `link-name` (2.4.4) — Icon-only links without `aria-label`
+4. `button-name` (4.1.2) — Icon-only buttons without accessible name
+5. `label` (3.3.2) — Form inputs without associated labels
+6. `html-has-lang` (3.1.1) — Missing `lang` attribute in `layout.tsx`
+7. `heading-order` (2.4.6) — Skipping heading levels
+8. `empty-heading` (2.4.6) — Headings with no text content
+9. `document-title` (2.4.2) — Missing or generic page titles
+10. `aria-hidden-focus` (4.1.2) — `aria-hidden` on focusable elements
+
+## Scoring System
+
+This repository uses a weighted impact scoring system:
+
+| Impact Level | Weight | Description |
+|--------------|--------|-------------|
+| Critical | 10 | Blocks access entirely |
+| Serious | 7 | Major barrier to access |
+| Moderate | 3 | Inconvenient but workaround exists |
+| Minor | 1 | Cosmetic or best-practice |
+
+**Grades:** A ≥ 90, B ≥ 70, C ≥ 50, D ≥ 30, F < 30
+
+Scores are broken down by POUR principles: Perceivable (1.x), Operable (2.x), Understandable (3.x), Robust (4.x).
+
+## Required Steps
+
+### Step 1: Understand Scope
+
+Determine what to scan before starting analysis.
+
+1. Ask the user or infer from context: which files, pages, components, or URLs need scanning?
+2. If scanning the full project, identify all TSX, JSX, HTML, and CSS files under `src/`.
+3. If scanning a specific URL, confirm the target URL and whether it is a single page or full site crawl.
+4. Create a checklist of targets using `manage_todo_list`.
+
+### Step 2: Static Code Analysis
+
+Read source files and identify WCAG antipatterns using `read_file`, `grep_search`, and `semantic_search`.
+
+Check for each of these violation patterns:
+
+**Images without alternative text (WCAG 1.1.1):**
+
+* Search for `<img` tags missing `alt` attribute
+* Search for Next.js `<Image` components missing `alt` prop
+* Decorative images should use `alt=""` explicitly, not omit `alt`
+
+**Missing language attribute (WCAG 3.1.1):**
+
+* Check `<html>` element in `layout.tsx` or root HTML template for `lang` attribute
+* Verify the `lang` value matches the content language (for example, `lang="en"`)
+
+**Form inputs without labels (WCAG 3.3.2):**
+
+* Search for `<input`, `<select`, `<textarea` elements
+* Verify each has an associated `<label htmlFor="...">` or `aria-label`/`aria-labelledby`
+* Check that label `htmlFor` values match input `id` values
+
+**Icon-only interactive elements (WCAG 2.4.4 / 4.1.2):**
+
+* Search for links and buttons containing only SVG or icon elements
+* Verify they have `aria-label`, `aria-labelledby`, or visually hidden text
+* Check for links with text like "Click here", "Read more", or "Learn more" (ambiguous link text)
+
+**Heading hierarchy violations (WCAG 2.4.6):**
+
+* Search for all heading elements (`h1` through `h6`)
+* Verify they follow sequential order without skipping levels (h1 → h2 → h3)
+* Check for empty headings (no text content)
+* Verify only one `h1` per page
+
+**Non-semantic interactive elements (WCAG 4.1.2):**
+
+* Search for `<div` or `<span` elements with `onClick` handlers
+* These should be `<button>` or `<a>` elements instead
+* Check for `role="button"` on divs without keyboard event handlers (`onKeyDown`, `onKeyUp`)
+
+**ARIA misuse:**
+
+* Search for `aria-hidden="true"` on elements that contain focusable children
+* Check for invalid `role` values
+* Verify required ARIA attributes are present (for example, `role="checkbox"` needs `aria-checked`)
+* Search for redundant ARIA (for example, `role="button"` on `<button>`)
+
+**CSS and Tailwind issues:**
+
+* Search for `maximum-scale=1` or `user-scalable=no` in viewport meta tags (WCAG 1.4.4)
+* Check for missing `:focus-visible` or `focus:` styles on interactive elements (WCAG 2.4.7)
+* Look for fixed/sticky positioned elements that may obscure focused content (WCAG 2.4.11)
+* Check for interactive elements smaller than 24×24 CSS pixels (WCAG 2.5.8)
+
+**WCAG 2.2 specific checks:**
+
+* Sticky headers/footers that may obscure focused elements — look for `position: sticky` or `position: fixed` without corresponding `scroll-padding-top`/`scroll-padding-bottom` (2.4.11)
+* Drag-only interactions without keyboard/pointer alternatives (2.5.7)
+* Target sizes below 24×24 CSS pixels for interactive elements (2.5.8)
+
+**Useful grep patterns:**
+
+```text
+<img(?![^>]*alt)
+<Image(?![^>]*alt)
+<html(?![^>]*lang)
+<div[^>]*onClick
+<span[^>]*onClick
+maximum-scale
+user-scalable
+aria-hidden
+```
+
+### Step 3: Runtime Scanning (Optional)
+
+Invoke the CLI scanner for deeper analysis using axe-core, IBM Equal Access, and custom Playwright checks.
+
+**Prerequisites:** The user must have the dev server running. Remind them to start it with `npm run dev` if scanning localhost.
+
+**Single page scan:**
+
+```bash
+npx a11y-scan scan --url <url> --format json
+```
+
+**Full site crawl:**
+
+```bash
+npx a11y-scan crawl --url <url> --format json
+```
+
+Parse the JSON output for structured violation data including rule IDs, WCAG criteria, impact levels, affected elements, and suggested fixes.
+
+The scanner runs three engines:
+
+* **axe-core** — Primary engine with WCAG 2.0/2.1/2.2 tags
+* **IBM Equal Access** — Secondary engine for additional coverage
+* **Custom Playwright checks** — Five custom checks: ambiguous-link-text, aria-current-page, emphasis-strong-semantics, discount-price-accessibility, sticky-element-overlap
+
+### Step 4: Report Findings
+
+Produce a structured markdown report organized by impact severity.
+
+**Report structure:**
+
+```markdown
+## Accessibility Scan Results
+
+### Summary
+
+* **Total violations:** {count}
+* **Accessibility score:** {score}/100 (Grade {letter})
+* **By severity:** {critical} critical, {serious} serious, {moderate} moderate, {minor} minor
+
+### POUR Principle Breakdown
+
+| Principle | Score | Violations |
+|-----------|-------|------------|
+| Perceivable (1.x) | {score} | {count} |
+| Operable (2.x) | {score} | {count} |
+| Understandable (3.x) | {score} | {count} |
+| Robust (4.x) | {score} | {count} |
+
+### Critical Violations
+
+#### {violation_title}
+
+* **WCAG Criterion:** {SC number and name}
+* **Impact:** Critical
+* **File:** {file_path}
+* **Element:** {element description or selector}
+* **Description:** {what is wrong}
+* **Suggested fix:** {how to fix it}
+
+### Serious Violations
+...
+
+### Moderate Violations
+...
+
+### Minor Violations
+...
+
+### Items Requiring Manual Review
+
+* {description of what to check manually}
+```
+
+For each violation, provide actionable guidance that the A11y Resolver agent or a developer can act on directly.
+
+### Step 5: Handoff
+
+After completing the report, offer the user the option to hand off to the A11y Resolver agent for automated fixes.
+
+The handoff passes the violation report as context so the Resolver can prioritize and apply fixes in severity order.
diff --git a/.github/agents/a11y-resolver.agent.md b/.github/agents/a11y-resolver.agent.md
new file mode 100644
index 0000000..5cf9667
--- /dev/null
+++ b/.github/agents/a11y-resolver.agent.md
@@ -0,0 +1,225 @@
+---
+name: A11y Resolver
+description: 'Resolves AODA WCAG 2.2 accessibility violations with standards-compliant code fixes'
+tools:
+  - read_file
+  - replace_string_in_file
+  - multi_replace_string_in_file
+  - create_file
+  - grep_search
+  - semantic_search
+  - file_search
+  - list_dir
+  - run_in_terminal
+  - manage_todo_list
+  - get_errors
+  - runTests
+handoffs:
+  - label: "Re-scan"
+    agent: A11y Detector
+    prompt: "Scan the codebase again to verify the fixes applied"
+    send: false
+---
+
+# A11y Resolver
+
+Resolves AODA WCAG 2.2 Level AA accessibility violations with standards-compliant code fixes for React and Next.js applications.
+
+Fixes are applied in priority order: critical → serious → moderate → minor. Each fix follows established WCAG remediation patterns, React/Next.js best practices, and preserves existing functionality.
+
+## Required Steps
+
+### Step 1: Identify Violations
+
+Accept violation input from one of these sources:
+
+1. **Handoff from A11y Detector** — structured violation report with WCAG criteria, impact, file paths, and suggested fixes
+2. **Scan results file** — JSON output from `npx a11y-scan scan` or `npx a11y-scan crawl`
+3. **User description** — manual description of accessibility issues to fix
+
+Parse the input and create a prioritized fix list using `manage_todo_list`, ordered by impact severity.
+
+### Step 2: Analyze Affected Code
+
+For each violation in the fix list:
+
+1. Read the affected source file using `read_file`.
+2. Understand the component structure, props, and rendering logic.
+3. Identify the exact code that causes the violation.
+4. Determine the minimal change needed — avoid refactoring unrelated code.
+
+### Step 3: Apply Fixes
+
+Use the remediation patterns below to fix each violation type. Apply fixes using `replace_string_in_file` or `multi_replace_string_in_file`.
+
+#### Remediation Patterns Reference
+
+| Violation | WCAG SC | Standard Fix |
+|-----------|---------|--------------|
+| Missing `alt` on image | 1.1.1 | Add `alt="Description"` or `alt=""` for decorative images |
+| Missing `alt` on Next.js Image | 1.1.1 | Add `alt` prop: `<Image src={src} alt="Description" />` |
+| Icon-only link or button | 2.4.4 / 4.1.2 | Add `aria-label="Purpose"` or include visually hidden text |
+| Color contrast below 4.5:1 | 1.4.3 | Darken text or lighten background to meet ratio |
+| Missing form label | 3.3.2 | Add `<label htmlFor="inputId">` or `aria-label` on the input |
+| Missing `lang` attribute | 3.1.1 | Add `lang="en"` to `<html>` element in `layout.tsx` |
+| Skipped heading levels | 2.4.6 | Use sequential heading levels: h1 → h2 → h3 |
+| No skip navigation link | 2.4.1 | Add `<a href="#main" className="sr-only focus:not-sr-only">Skip to main content</a>` |
+| `div` used as button | 4.1.2 | Replace `<div onClick={...}>` with `<button onClick={...}>` |
+| Missing focus indicator | 2.4.7 | Add `:focus-visible` CSS with visible outline or ring |
+| Focus obscured by sticky element | 2.4.11 | Add `scroll-padding-top` matching sticky header height |
+| Small target size | 2.5.8 | Ensure ≥ 24×24 CSS pixels with padding or min-width/min-height |
+| No `aria-live` for dynamic content | 4.1.3 | Add `role="status"` or `aria-live="polite"` to update region |
+| Duplicate IDs | 4.1.2 | Use React `useId()` hook for unique IDs per instance |
+| Zoom disabled via viewport meta | 1.4.4 | Remove `maximum-scale=1` and `user-scalable=no` |
+| Ambiguous link text | 2.4.4 | Replace "Click here"/"Read more" with descriptive text |
+| Missing `aria-current="page"` | 1.3.1 | Add `aria-current="page"` to active navigation links |
+| Non-semantic emphasis | Best practice | Replace `<b>` with `<strong>`, `<i>` with `<em>` |
+
+#### React and Next.js Specific Patterns
+
+**Unique IDs with `useId()`:**
+
+```tsx
+import { useId } from 'react';
+
+function FormField({ label }: { label: string }) {
+  const id = useId();
+  return (
+    <>
+      <label htmlFor={id}>{label}</label>
+      <input id={id} />
+    </>
+  );
+}
+```
+
+**Next.js Image with alt text:**
+
+```tsx
+import Image from 'next/image';
+
+<Image src="/photo.jpg" alt="Description of the image content" width={400} height={300} />
+```
+
+**Language attribute in layout.tsx:**
+
+```tsx
+export default function RootLayout({ children }: { children: React.ReactNode }) {
+  return (
+    <html lang="en">
+      <body>{children}</body>
+    </html>
+  );
+}
+```
+
+**Focus management with useRef:**
+
+```tsx
+import { useRef, useEffect } from 'react';
+
+function Dialog({ isOpen }: { isOpen: boolean }) {
+  const headingRef = useRef<HTMLHeadingElement>(null);
+  useEffect(() => {
+    if (isOpen) headingRef.current?.focus();
+  }, [isOpen]);
+  return <h2 ref={headingRef} tabIndex={-1}>Dialog Title</h2>;
+}
+```
+
+**Aria-live region for dynamic updates:**
+
+```tsx
+<div role="status" aria-live="polite">
+  {statusMessage}
+</div>
+```
+
+#### WCAG 2.2 Specific Fixes
+
+**Focus Not Obscured (2.4.11):**
+
+```css
+html {
+  scroll-padding-top: 4rem; /* Match sticky header height */
+}
+```
+
+**Target Size Minimum (2.5.8):**
+
+```css
+button, a {
+  min-width: 24px;
+  min-height: 24px;
+}
+
+/* Or use padding for icon buttons */
+.icon-button {
+  padding: 0.5rem;
+}
+```
+
+**Dragging Movements (2.5.7):**
+
+For any drag interaction, provide an equivalent keyboard or single-pointer alternative (for example, arrow buttons to reorder, a select menu to move items, or click-to-place).
+
+#### Common Anti-Patterns to Avoid
+
+Do NOT apply these patterns — they create new accessibility issues:
+
+* **`tabIndex` greater than 0** — Disrupts natural tab order. Use `tabIndex={0}` or `tabIndex={-1}` only.
+* **`role="button"` on a `div` without keyboard handlers** — Must also add `onKeyDown` for Enter and Space, and `tabIndex={0}`. Prefer using a real `<button>` element instead.
+* **`aria-hidden="true"` on focusable elements** — Screen readers skip the element but keyboard focus still reaches it, creating a confusing experience.
+* **Removing outline without replacement** — `outline: none` without a visible `:focus-visible` alternative removes the focus indicator entirely.
+* **Empty `alt` on informative images** — `alt=""` marks an image as decorative. Only use it when the image truly conveys no information.
+* **`aria-label` overriding visible text** — When an element has visible text, `aria-label` overrides it for screen readers, causing a mismatch. Use `aria-labelledby` to reference the visible text instead.
+* **Multiple `aria-live` regions** — Too many live regions create excessive announcements. Use one status region per logical area.
+
+### Step 4: Verify Fixes
+
+After applying fixes:
+
+1. Check for TypeScript/lint errors using `get_errors`.
+2. Run the test suite:
+
+   ```bash
+   npm run test
+   ```
+
+3. If a dev server is running, re-scan the affected pages:
+
+   ```bash
+   npx a11y-scan scan --url <url> --format json
+   ```
+
+4. Compare before/after violation counts and scores.
+
+### Step 5: Report
+
+Produce a summary of changes made:
+
+```markdown
+## Remediation Summary
+
+### Changes Applied
+
+| File | Violation Fixed | WCAG SC | Impact |
+|------|----------------|---------|--------|
+| {path} | {description} | {criterion} | {level} |
+
+### Impact
+
+* **Violations before:** {count}
+* **Violations after:** {count}
+* **Violations fixed:** {count}
+* **Score improvement:** {before} → {after}
+
+### Remaining Issues
+
+* {violations that could not be fixed automatically}
+* {items requiring manual review or design decisions}
+```
+
+### Step 6: Handoff
+
+After reporting, offer the user the option to hand off to the A11y Detector agent for a verification re-scan to confirm all fixes are effective and no regressions were introduced.
diff --git a/.github/instructions/a11y-remediation.instructions.md b/.github/instructions/a11y-remediation.instructions.md
new file mode 100644
index 0000000..4cd7b37
--- /dev/null
+++ b/.github/instructions/a11y-remediation.instructions.md
@@ -0,0 +1,135 @@
+---
+description: 'AODA WCAG 2.2 accessibility remediation patterns and code fix recipes for web components'
+applyTo: '**/*.tsx, **/*.jsx, **/*.ts, **/*.html, **/*.css'
+---
+
+# Accessibility Remediation Patterns
+
+## Fix Prioritization
+
+Apply fixes in order of impact severity:
+
+1. **Critical** (score impact 10) — missing alt on informative images, no keyboard access, focus traps
+2. **Serious** (score impact 7) — color contrast failures, missing form labels, ambiguous links
+3. **Moderate** (score impact 3) — heading order violations, missing lang on parts
+4. **Minor** (score impact 1) — best practice issues, non-semantic emphasis elements
+
+## Remediation Lookup Table
+
+| Violation ID | WCAG SC | Fix |
+|---|---|---|
+| `image-alt` | 1.1.1 | Add `alt="Description"` for informative images or `alt=""` for decorative images. |
+| `image-alt-nextjs` | 1.1.1 | Add `alt` prop to `<Image>` component: `<Image alt="Description" ... />`. |
+| `color-contrast` | 1.4.3 | Darken text or lighten background to achieve at least 4.5:1 ratio for normal text and 3:1 for large text. |
+| `link-name` | 2.4.4 | Add `aria-label="Purpose"` or include visually hidden text inside the link. |
+| `button-name` | 4.1.2 | Add `aria-label="Action"` or visible text content inside `<button>`. |
+| `label` | 3.3.2 | Add `<label htmlFor="inputId">Label text</label>` or `aria-label` on the input. |
+| `html-has-lang` | 3.1.1 | Add `lang="en"` to `<html>` in root `layout.tsx`. |
+| `heading-order` | 2.4.6 | Use sequential heading levels only (h1 → h2 → h3); do not skip levels. |
+| `bypass` | 2.4.1 | Add a skip navigation link as the first focusable element on the page. |
+| `focus-visible` | 2.4.7 | Add `:focus-visible` CSS rule with a visible outline (e.g., `outline: 2px solid`). |
+| `target-size` | 2.5.8 | Ensure interactive target is at least 24×24 CSS pixels using padding or min-width/min-height. |
+| `focus-not-obscured` | 2.4.11 | Add `scroll-padding-top` matching the sticky header height to prevent focus obscuring. |
+| `aria-live` | 4.1.3 | Add `role="status"` or `aria-live="polite"` on containers with dynamic content updates. |
+| `duplicate-id` | 4.1.2 | Replace hardcoded IDs with `useId()` hook to guarantee uniqueness across instances. |
+| `meta-viewport` | 1.4.4 | Remove `maximum-scale=1` and `user-scalable=no` from viewport meta tag. |
+| `link-in-text-block` | 2.4.4 | Replace "Click here" or "Read more" with descriptive link text that conveys the destination. |
+| `aria-current-page` | 1.3.1 | Add `aria-current="page"` to the active navigation link. |
+| `non-semantic-emphasis` | Best practice | Replace `<b>` with `<strong>` and `<i>` with `<em>` for semantic emphasis. |
+| `div-as-button` | 4.1.2 | Replace `<div onClick={...}>` with a `<button>` element that provides keyboard and screen reader support. |
+
+## React and Next.js Code Patterns
+
+### Unique IDs with useId
+
+```tsx
+import { useId } from 'react';
+
+function FormField({ label }: { label: string }) {
+  const id = useId();
+  return (
+    <div>
+      <label htmlFor={id}>{label}</label>
+      <input id={id} type="text" />
+    </div>
+  );
+}
+```
+
+### Next.js Image with Alt Text
+
+```tsx
+import Image from 'next/image';
+
+// Informative image
+<Image src="/hero.jpg" alt="Team collaborating in a meeting room" width={800} height={400} />
+
+// Decorative image
+<Image src="/bg-pattern.svg" alt="" aria-hidden="true" width={200} height={200} />
+```
+
+### Focus Management After Navigation
+
+```tsx
+import { useRef, useEffect } from 'react';
+
+function PageContent({ title }: { title: string }) {
+  const headingRef = useRef<HTMLHeadingElement>(null);
+
+  useEffect(() => {
+    headingRef.current?.focus();
+  }, []);
+
+  return <h1 ref={headingRef} tabIndex={-1}>{title}</h1>;
+}
+```
+
+### Live Region for Dynamic Content
+
+```tsx
+import { useState } from 'react';
+
+function StatusMessage() {
+  const [message, setMessage] = useState('');
+
+  return (
+    <div aria-live="polite" role="status">
+      {message}
+    </div>
+  );
+}
+```
+
+### Skip Navigation Link
+
+```tsx
+<a href="#main-content" className="sr-only focus:not-sr-only focus:absolute focus:p-2 focus:bg-white focus:z-50">
+  Skip to main content
+</a>
+```
+
+### Focus Visible CSS
+
+```css
+:focus-visible {
+  outline: 2px solid #1a73e8;
+  outline-offset: 2px;
+}
+```
+
+### Scroll Padding for Sticky Headers
+
+```css
+html {
+  scroll-padding-top: 4rem; /* Match the sticky header height */
+}
+```
+
+## Common Anti-Patterns to Avoid
+
+* **`tabIndex` greater than 0** — Creates unpredictable focus order. Use `tabIndex={0}` for custom focusable elements or `tabIndex={-1}` for programmatic focus only.
+* **`role="button"` on `div` without keyboard handlers** — Must also add `onKeyDown` for Enter and Space. Prefer a native `<button>` element instead.
+* **`aria-hidden="true"` on focusable elements** — Hides the element from screen readers while it remains in the tab order, creating a "ghost" tab stop. Remove `aria-hidden` or remove the element from tab order.
+* **`maximum-scale=1` in viewport meta** — Prevents pinch-to-zoom, violating SC 1.4.4. Remove `maximum-scale` and `user-scalable=no` from the viewport meta tag.
+* **Empty headings** — Screen readers announce "heading level N" with no content. Remove empty headings or add descriptive text.
+* **Generic link text** — "Click here", "Read more", "Learn more" without context. Use descriptive text or `aria-label` that explains the destination.
diff --git a/.github/instructions/wcag22-rules.instructions.md b/.github/instructions/wcag22-rules.instructions.md
new file mode 100644
index 0000000..72c2d10
--- /dev/null
+++ b/.github/instructions/wcag22-rules.instructions.md
@@ -0,0 +1,99 @@
+---
+description: 'AODA WCAG 2.2 Level AA compliance rules for accessibility in web components'
+applyTo: '**/*.tsx, **/*.jsx, **/*.ts, **/*.html, **/*.css'
+---
+
+# WCAG 2.2 Level AA Compliance Rules
+
+## AODA and WCAG 2.2 Context
+
+Ontario's Accessibility for Ontarians with Disabilities Act (AODA) legally requires WCAG 2.0 Level AA conformance for web content. WCAG 2.2 is backwards compatible with WCAG 2.0 — conforming to WCAG 2.2 Level AA automatically satisfies AODA requirements. Target WCAG 2.2 Level AA to exceed AODA minimums and anticipate policy updates.
+
+## Perceivable
+
+| SC | Title | Rule |
+|---|---|---|
+| 1.1.1 | Non-text Content | Provide `alt` text on every `<img>` and `<Image>` component; use `alt=""` for decorative images. |
+| 1.2.2 | Captions (Prerecorded) | Provide captions for all prerecorded audio content in synchronized media. |
+| 1.3.1 | Info and Relationships | Use semantic HTML (`<nav>`, `<main>`, `<header>`, `<table>`) to convey structure, not visual styling alone. |
+| 1.3.2 | Meaningful Sequence | Ensure DOM order matches the visual reading order; do not rely on CSS to reorder content. |
+| 1.3.3 | Sensory Characteristics | Do not rely solely on shape, color, size, or location to convey instructions (e.g., "click the red button"). |
+| 1.3.4 | Orientation | Do not restrict display to a single orientation unless essential. |
+| 1.3.5 | Identify Input Purpose | Use `autocomplete` attributes on input fields that collect personal data (name, email, address). |
+| 1.4.3 | Contrast (Minimum) | Maintain at least 4.5:1 contrast ratio for normal text and 3:1 for large text (≥18pt or ≥14pt bold). |
+| 1.4.4 | Resize Text | Text must be resizable up to 200% without loss of content or functionality; do not set `maximum-scale=1` in viewport meta. |
+| 1.4.5 | Images of Text | Use real text instead of images of text; exceptions for logos and essential images. |
+| 1.4.10 | Reflow | Content must reflow to a single column at 320 CSS px width without horizontal scrolling. |
+| 1.4.11 | Non-text Contrast | UI components and graphical objects must have at least 3:1 contrast against adjacent colors. |
+| 1.4.12 | Text Spacing | Content must remain functional when users override line height to 1.5×, letter spacing to 0.12em, word spacing to 0.16em, paragraph spacing to 2×. |
+| 1.4.13 | Content on Hover or Focus | Hover/focus-triggered content must be dismissible, hoverable, and persistent until dismissed. |
+
+## Operable
+
+| SC | Title | Rule |
+|---|---|---|
+| 2.1.1 | Keyboard | All functionality must be operable via keyboard; use `<button>` and `<a>` instead of `div` with click handlers. |
+| 2.1.2 | No Keyboard Trap | Ensure focus can leave every component using standard keyboard navigation (Tab, Shift+Tab, Escape). |
+| 2.2.1 | Timing Adjustable | If a time limit exists, provide a way to turn off, adjust, or extend it. |
+| 2.2.2 | Pause, Stop, Hide | Provide controls to pause, stop, or hide moving, blinking, or auto-updating content. |
+| 2.3.1 | Three Flashes | Content must not flash more than three times per second. |
+| 2.4.1 | Bypass Blocks | Provide a skip navigation link as the first focusable element on each page. |
+| 2.4.2 | Page Titled | Every page must have a unique, descriptive `<title>`. |
+| 2.4.3 | Focus Order | Focus order must follow a logical sequence matching the visual layout. |
+| 2.4.4 | Link Purpose (In Context) | Link text must describe its destination; avoid "Click here" or "Read more" without context. |
+| 2.4.6 | Headings and Labels | Use descriptive headings in sequential order (h1 → h2 → h3); do not skip heading levels. |
+| 2.4.7 | Focus Visible | Focused elements must have a visible focus indicator; use `:focus-visible` with a distinct outline. |
+| 2.4.11 | Focus Not Obscured (Minimum) | **NEW 2.2** — Focused element must not be entirely hidden by sticky headers, footers, or overlays; use `scroll-padding-top`. |
+| 2.5.7 | Dragging Movements | **NEW 2.2** — Any drag operation must have a single-pointer alternative (e.g., tap, click). |
+| 2.5.8 | Target Size (Minimum) | **NEW 2.2** — Pointer targets must be at least 24×24 CSS pixels, or provide sufficient spacing. |
+
+## Understandable
+
+| SC | Title | Rule |
+|---|---|---|
+| 3.1.1 | Language of Page | Set `lang="en"` on the `<html>` element in the root `layout.tsx`. |
+| 3.1.2 | Language of Parts | Mark content in a different language with the appropriate `lang` attribute on its container. |
+| 3.2.1 | On Focus | Focus alone must not trigger a change of context (navigation, form submit). |
+| 3.2.2 | On Input | Changing a form input value must not automatically trigger a change of context without warning. |
+| 3.2.3 | Consistent Navigation | Navigation menus must appear in the same relative order across pages. |
+| 3.2.4 | Consistent Identification | Components with the same function must be identified consistently across pages. |
+| 3.2.6 | Consistent Help | **NEW 2.2** — Help mechanisms (contact info, chat, FAQ links) must appear in the same relative position across pages. |
+| 3.3.1 | Error Identification | Identify form errors in text and describe the error to the user. |
+| 3.3.2 | Labels or Instructions | Provide labels or instructions for user input; every input must have an associated label. |
+| 3.3.3 | Error Suggestion | When an input error is detected, suggest a correction if known. |
+| 3.3.4 | Error Prevention (Legal, Financial, Data) | For legal/financial submissions, allow review, confirmation, or reversal before final submit. |
+| 3.3.7 | Redundant Entry | **NEW 2.2** — Do not require users to re-enter information already provided in the same session; auto-populate or offer selection. |
+| 3.3.8 | Accessible Authentication (Minimum) | **NEW 2.2** — Authentication must not require a cognitive function test (memorize, transcribe, calculate) unless an alternative is provided. |
+
+## Robust
+
+| SC | Title | Rule |
+|---|---|---|
+| 4.1.2 | Name, Role, Value | All UI components must have an accessible name and expose correct role and state via HTML semantics or ARIA. |
+| 4.1.3 | Status Messages | Dynamic status updates (success, error, progress) must use `role="status"` or `aria-live="polite"` so screen readers announce them without focus change. |
+
+> **Note**: SC 4.1.1 Parsing was removed in WCAG 2.2 as it is obsolete in modern HTML.
+
+## React and Next.js Rules
+
+* Always provide an `alt` prop on `<Image>` components from `next/image`; use `alt=""` with `aria-hidden="true"` for decorative images.
+* Use `htmlFor` (not `for`) on `<label>` elements when associating with form controls.
+* Use the `useId()` hook to generate unique element IDs; never hardcode IDs that may duplicate across component instances.
+* Include `lang="en"` on the `<html>` element in the root `layout.tsx`.
+* Prefer semantic HTML elements (`<button>`, `<nav>`, `<main>`, `<section>`) over ARIA roles on generic elements.
+* Use `aria-live="polite"` or `role="status"` regions for dynamic content updates (e.g., loading states, form feedback).
+* Manage focus programmatically with `useRef()` and `useEffect()` after route changes or modal opens.
+* Add a skip navigation link as the first child of `<body>` using `className="sr-only focus:not-sr-only"`.
+
+## Scoring System Reference
+
+This repository uses a weighted scoring model:
+
+| Impact Level | Weight | Examples |
+|---|---|---|
+| Critical | 10 | Missing alt text on informative images, no keyboard access |
+| Serious | 7 | Color contrast failures, missing form labels |
+| Moderate | 3 | Heading order violations, missing lang on parts |
+| Minor | 1 | Best practice issues, non-semantic emphasis |
+
+Grades: A (≥90), B (≥70), C (≥50), D (≥30), F (<30).
diff --git a/.github/prompts/a11y-fix.prompt.md b/.github/prompts/a11y-fix.prompt.md
new file mode 100644
index 0000000..2fce2da
--- /dev/null
+++ b/.github/prompts/a11y-fix.prompt.md
@@ -0,0 +1,19 @@
+---
+description: 'Fix accessibility violations in the current file or project'
+agent: A11y Resolver
+argument-hint: '[file=current] [violations=...]'
+---
+
+# Accessibility Fix
+
+## Inputs
+
+* ${input:file:current}: (Optional, defaults to current) Target file or "project" for full project scan.
+* ${input:violations}: (Optional) Specific violation IDs or descriptions to fix.
+
+## Requirements
+
+1. Determine fix scope from user input (specific file, specific violations, or full project).
+2. If violations provided, apply targeted fixes.
+3. If no violations specified, scan current file for issues and fix them.
+4. Verify fixes with tests.
diff --git a/.github/prompts/a11y-scan.prompt.md b/.github/prompts/a11y-scan.prompt.md
new file mode 100644
index 0000000..4857c71
--- /dev/null
+++ b/.github/prompts/a11y-scan.prompt.md
@@ -0,0 +1,19 @@
+---
+description: 'Run an AODA WCAG 2.2 accessibility scan on the current project'
+agent: A11y Detector
+argument-hint: '[url=http://localhost:3000] [scope=page|site]'
+---
+
+# Accessibility Scan
+
+## Inputs
+
+* ${input:url:http://localhost:3000}: (Optional, defaults to http://localhost:3000) Target URL to scan.
+* ${input:scope:page}: (Optional, defaults to page) Scan scope: `page` for single page or `site` for full crawl.
+
+## Requirements
+
+1. Determine scan scope from user input (single page vs site crawl).
+2. If URL provided, run runtime scan via CLI.
+3. If no URL, perform static code analysis of the workspace.
+4. Report findings in structured format.