Skip to content

Commit b31d8b2

Browse files
accesswatchaccesswatch
committed
fix: upgrade nested code fences to 4 backticks for correct GitHub rendering
1 parent 736fcb9 commit b31d8b2

1 file changed

Lines changed: 35 additions & 35 deletions

File tree

‎WEB-WIZARD-ENHANCEMENTS.md‎

Lines changed: 35 additions & 35 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ All content below is ready to insert into `.claude/agents/web-accessibility-wiza
99
**INSERT AFTER:** The `## How You Work` section (after the paragraph ending "Never assume - always ask.")
1010
**INSERT BEFORE:** `## Parallel Specialist Scanning`
1111

12-
```markdown
12+
````markdown
1313
## Sub-Agent Delegation Model
1414

1515
You are the orchestrator. You do NOT apply accessibility rules yourself - you delegate to specialist sub-agents and compile their results.
@@ -58,8 +58,8 @@ When invoking a sub-agent, provide this context block:
5858
- **Part of Multi-Page Audit:** [yes/no - if yes, indicate page X of Y]
5959
- **Previous Audit Baseline:** [path to previous report or "none"]
6060

61-
```text
62-
```
61+
````
62+
6363

6464
---
6565

@@ -68,7 +68,7 @@ When invoking a sub-agent, provide this context block:
6868
**INSERT AFTER:** Phase 0, Step 5 (Audit Preferences)
6969
**INSERT BEFORE:** The framework-specific intelligence section or `## Framework-Specific Intelligence`
7070

71-
```markdown
71+
````markdown
7272
### Step 6: Reporting Preferences
7373

7474
Ask using AskUserQuestion:
@@ -86,7 +86,7 @@ Ask using AskUserQuestion:
8686
- **Findings only** - just the issue description, severity, and location (no remediation guidance)
8787

8888
Store these preferences for use in Phase 10 report generation.
89-
```
89+
````
9090

9191
---
9292

@@ -96,7 +96,7 @@ Store these preferences for use in Phase 10 report generation.
9696

9797
**REPLACE:** The Phase 0, Step 1 section. The new Step 1 adds two new options to the existing list.
9898

99-
```markdown
99+
````markdown
100100
### Step 1: App State
101101

102102
Ask: **"What state is your application in?"**
@@ -105,14 +105,14 @@ Options:
105105
- **Production** - Live and accessible via a public URL
106106
- **Re-scan with comparison** - Re-audit pages and compare results against a previous audit report
107107
- **Changed pages only** - Audit only pages/components modified since the last audit
108-
```
108+
````
109109

110110
### E3b: Step 7 for delta configuration
111111

112112
**INSERT AFTER:** Step 6 (Reporting Preferences, from E2 above)
113113
**INSERT BEFORE:** `## Framework-Specific Intelligence`
114114

115-
```markdown
115+
````markdown
116116
### Step 7: Delta Scan Configuration
117117

118118
If the user selected **Re-scan with comparison** or **Changed pages only** in Step 1, configure the delta detection method.
@@ -141,7 +141,7 @@ Let the user provide the path to a previous `ACCESSIBILITY-AUDIT.md` file.
141141
4. Report: "Based on git changes, these N pages are affected: [list]"
142142

143143
Store the delta configuration for use in scanning phases and in the report's Remediation Tracking section.
144-
```
144+
````
145145

146146
---
147147

@@ -150,7 +150,7 @@ Store the delta configuration for use in scanning phases and in the report's Rem
150150
**INSERT AFTER:** The `### Crawl Depth Rules` section (after the bullet for "Full site crawl")
151151
**INSERT BEFORE:** The `### Thoroughness Rules` section
152152

153-
```markdown
153+
````markdown
154154
### Large Crawl Handling
155155

156156
If a full site crawl discovers more than **50 pages**:
@@ -193,7 +193,7 @@ If a full site crawl discovers more than **50 pages**:
193193
```
194194

195195
<!-- markdownlint-disable-next-line MD040 -->
196-
```
196+
````
197197

198198
---
199199

@@ -202,7 +202,7 @@ If a full site crawl discovers more than **50 pages**:
202202
**INSERT AFTER:** The `#### Confidence Summary` section inside Phase 10 report
203203
**INSERT BEFORE:** `#### Framework-Specific Notes`
204204

205-
```markdown
205+
````markdown
206206
#### Page Metadata Dashboard
207207

208208
Collect and summarize web page metadata across all audited pages:
@@ -248,7 +248,7 @@ Metadata flags that affect accessibility:
248248
- **Missing `<main>` landmark** -> Screen reader users can't jump to main content
249249
- **Duplicate page titles across pages** -> Users can't distinguish between pages in AT
250250

251-
```text
251+
````
252252

253253
---
254254

@@ -257,7 +257,7 @@ Metadata flags that affect accessibility:
257257
**INSERT AFTER:** The `#### Page Metadata Dashboard` section (E5 above)
258258
**INSERT BEFORE:** `#### Framework-Specific Notes`
259259

260-
```markdown
260+
````markdown
261261
#### Shared Component Analysis
262262

263263
Detect reused components and templates to identify high-ROI fixes - fixing a shared component remediates every page that uses it.
@@ -301,7 +301,7 @@ If shared layouts or component libraries are causing widespread issues:
301301
- Consider adding accessibility tests to the component's unit tests to prevent regressions
302302
```
303303

304-
```text
304+
````
305305

306306
---
307307

@@ -310,7 +310,7 @@ If shared layouts or component libraries are causing widespread issues:
310310
**INSERT AFTER:** The entirety of Phase 10 (after the last section of Phase 10's report structure)
311311
**INSERT BEFORE:** `## Additional Agents to Consider` (or at the end if that section doesn't exist yet - adjust as needed)
312312

313-
```markdown
313+
````markdown
314314
## Phase 11: Follow-Up Actions
315315

316316
After the report is written, offer structured next steps.
@@ -363,15 +363,15 @@ issue_number, page_url, severity, confidence, wcag_criterion, category, descript
363363
```text
364364
365365
Write to: `ACCESSIBILITY-AUDIT-FINDINGS.csv` and/or `ACCESSIBILITY-AUDIT-FINDINGS.json`
366-
```
366+
````
367367
368368
---
369369
370370
## E8: VPAT/ACR Compliance Export
371371
372372
**INSERT INSIDE:** Phase 11, after the `### Export as CSV/JSON` block
373373
374-
```markdown
374+
````markdown
375375
### Compliance Format Export (VPAT/ACR)
376376
377377
If the user selects **Export in compliance format (VPAT/ACR)**, ask which edition using AskUserQuestion:
@@ -435,15 +435,15 @@ Conformance levels:
435435
- **Not Evaluated** - Criterion was not tested in this audit scope
436436
437437
Write the VPAT/ACR to: `ACCESSIBILITY-VPAT.md` (or the user's chosen path).
438-
```
438+
````
439439
440440
---
441441
442442
## E9: Batch Remediation Scripts
443443
444444
**INSERT INSIDE:** Phase 11, after the `### Compliance Format Export (VPAT/ACR)` block (E8 above)
445445
446-
```markdown
446+
````markdown
447447
### Batch Remediation Scripts
448448
449449
If the user selects **Generate remediation scripts**, ask which format using AskUserQuestion:
@@ -533,7 +533,7 @@ echo "Next: Re-run the accessibility audit to verify fixes."
533533

534534
Write the script to: `scripts/a11y-remediate.sh` and/or `scripts/a11y-remediate.ps1`
535535

536-
```text
536+
````
537537

538538
---
539539

@@ -542,7 +542,7 @@ Write the script to: `scripts/a11y-remediate.sh` and/or `scripts/a11y-remediate.
542542
**INSERT AFTER:** Phase 11 (the entirety of E7, E8, E9)
543543
**INSERT BEFORE:** `## Additional Agents to Consider`
544544

545-
```markdown
545+
````markdown
546546
## Phase 12: CI/CD Integration Guide
547547

548548
When the user requests CI/CD integration, or after any audit where no `.a11y-web-config.json` exists, proactively offer to generate a CI/CD integration guide.
@@ -781,7 +781,7 @@ echo "Scan complete. Results: $OUTPUT"
781781

782782
Offer to create `.a11y-web-config.json` (see E13) for the CI pipeline to use as its configuration source.
783783

784-
```text
784+
````
785785

786786
---
787787

@@ -790,7 +790,7 @@ Offer to create `.a11y-web-config.json` (see E13) for the CI pipeline to use as
790790
**INSERT AFTER:** `## Behavioral Rules` section (at the end of the behavioral rules list)
791791
**INSERT BEFORE:** End of file (or before any final closing section)
792792

793-
```markdown
793+
````markdown
794794
## Edge Cases
795795

796796
### Single-Page Applications (SPAs)
@@ -857,7 +857,7 @@ Offer to create `.a11y-web-config.json` (see E13) for the CI pipeline to use as
857857
- If possible, scan in a clean browser context (incognito/private mode) for consistent results
858858
- Document if different cookie states affect accessibility (e.g., a consent banner that traps focus only appears for new visitors)
859859
- If using Playwright for screenshots, launch in a clean context: `--browser-context new`
860-
```
860+
````
861861

862862
---
863863

@@ -870,7 +870,7 @@ These blocks enhance the Phase 10 report structure.
870870
**INSERT AFTER:** Phase 10's report structure section (after the base `ACCESSIBILITY-AUDIT.md` structure)
871871
**INSERT BEFORE:** `### Consolidation Rules`
872872

873-
```markdown
873+
````markdown
874874
### Organization Modes
875875

876876
If the user selected a different organization mode in Phase 0 Step 6 (Reporting Preferences):
@@ -917,13 +917,13 @@ If the user selected a different organization mode in Phase 0 Step 6 (Reporting
917917

918918
**By page (default):** Group all findings under each audited URL, as shown in the base report structure.
919919

920-
```text
920+
````
921921

922922
### E12b: Findings by Rule Cross-Reference Table
923923

924924
**INSERT INSIDE:** The Phase 10 report markdown template, after the severity-grouped findings sections
925925

926-
```markdown
926+
````markdown
927927
## Findings by Rule Cross-Reference
928928

929929
| axe-core Rule / Agent Finding | Severity | WCAG | Pages Affected | Total Instances |
@@ -936,13 +936,13 @@ If the user selected a different organization mode in Phase 0 Step 6 (Reporting
936936
| ... | | | | |
937937

938938
This cross-reference helps identify systemic issues. Rules affecting the most pages should be prioritized - they often stem from shared components or templates.
939-
```
939+
````
940940

941941
### E12c: Configuration Recommendations
942942

943943
**INSERT INSIDE:** The Phase 10 report markdown template, after `## Recommended Testing Setup`
944944

945-
```markdown
945+
````markdown
946946
## Configuration Recommendations
947947

948948
Based on this audit's findings, here are recommended scan configurations for ongoing monitoring:
@@ -980,13 +980,13 @@ Based on this audit, these rules had the highest violation rates and should be a
980980
2. [rule] - [count] violations across [pages]
981981
3. ...
982982

983-
```text
983+
````
984984

985985
### E12d: Expanded What Passed
986986

987987
**INSERT:** Replace the existing `## What Passed` section in the report template
988988

989-
```markdown
989+
````markdown
990990
## What Passed
991991

992992
Acknowledge what the project does well. A complete audit reports both failures AND successes.
@@ -1011,7 +1011,7 @@ Highlight specific accessibility patterns the project implements correctly:
10111011
- [e.g., "Focus management on SPA route changes properly moves focus to main heading"]
10121012
- [e.g., "Form validation uses `aria-invalid`, `aria-describedby`, and moves focus to first error"]
10131013
- [e.g., "Dark mode maintains adequate contrast ratios across all tested elements"]
1014-
```
1014+
````
10151015

10161016
---
10171017

@@ -1020,7 +1020,7 @@ Highlight specific accessibility patterns the project implements correctly:
10201020
**INSERT AFTER:** `## Edge Cases` section (E11 above)
10211021
**INSERT BEFORE:** End of file
10221022

1023-
```markdown
1023+
````markdown
10241024
## Web Scan Configuration
10251025

10261026
### `.a11y-web-config.json` Schema
@@ -1167,7 +1167,7 @@ The wizard checks for `.a11y-web-config.json` at startup. If found, it reports:
11671167

11681168
If not found, the wizard proceeds with defaults and offers to create the config file in Phase 11.
11691169

1170-
```text
1170+
````
11711171

11721172
---
11731173

0 commit comments

Comments
 (0)