Fix documentation and site accessibility findings (#264-#268) (#271)

* fix(site): show Quick Jumps focus outline and match search box name to its label

Remove outline: none from the .quick-jumps-list a:focus rule so the
site-wide a:focus-visible outline (2px solid, blue) applies to the
Quick Jumps links again (WCAG 2.4.7 Focus Visible). Hover still
underlines the link; the dark-mode and high-contrast rules only change
colors and do not remove the outline.

Remove aria-label="Search documentation" from the site-search input on
every page and on the search page, so the field takes its accessible
name, "Search docs", from its label, which matches the visible
placeholder (WCAG 2.5.3 Label in Name).

Regenerated html/ with npm run build:html.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PmRBrUTuhzYnQBFxUCN6Vr

* docs: clear the known documentation accessibility findings

Emoji (172 findings, four admin guides):
- FACILITATOR_GUIDE.md and FACILITATOR_RESOURCES.md: remove the emoji
  from every heading, from running text and from the Section-Level
  Source Maps. Update every link to the changed anchors in both files
  and in admin/README.md (#-github-classroom-setup-before-day-1 becomes
  #github-classroom-setup-before-day-1, and so on). Describe the pencil
  icon by its button name, "Edit this file", instead of an emoji.
- Point the guide's broken in-page link to a nonexistent
  "Troubleshooting GitHub Classroom Setup" heading at "Known Gotchas",
  the section directly below it.
- FACILITATOR_OPERATIONS.md: remove the emoji from the sample chat
  messages and the narrated demo script.
- CURRICULUM_2.0_ORGANIZATION.md: replace each check mark with the word
  it stood for ("Complete", "Yes") or drop it from lists whose heading
  already says the items are done.

Code block languages (88 findings, 34 files): add a language to every
fenced code block that had none: bash for shell commands, bat for the
Windows batch files, markdown for Markdown source, and text for output,
file trees, conflict examples, sample messages and keystroke steps.
Nothing inside any block changed.

Heading: give admin/classroom admin access.md a title and a sentence of
context.

The documentation check now reports 3 findings, all the deliberate
"bad example" links in Appendix C; the baseline shrinks from 264 to 3.

Regenerated html/ with npm run build:html.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PmRBrUTuhzYnQBFxUCN6Vr

---------

Co-authored-by: Claude <noreply@anthropic.com>

Author: accesswatch

BATCH.md

@@ -18,7 +18,7 @@ Run operations in this sequence for a full podcast build from scratch:
 Validates the podcast catalog, builds episode and challenge bundles, then writes
 all episode and challenge coach scripts to `podcasts\scripts\`.
 
-```
+```bat
 generate-transcripts.bat
 ```
 
@@ -38,7 +38,7 @@ The script echoes each episode name and index as it is processed.
 ffmpeg is required for MP3 output and is located automatically from the
 machine PATH, including after a fresh winget install.
 
-```
+```text
 generate-audio.bat                  generate all 75 episodes
 generate-audio.bat 5                generate episodes 5 and above
 generate-audio.bat 5 10             generate episodes 5 through 10
@@ -54,7 +54,7 @@ before running this command.
 Generates the RSS 2.0 / iTunes-compatible podcast feed and the admin podcast listing.
 Reads MP3 file sizes from `podcasts\audio\` and episode metadata from the catalog.
 
-```
+```bat
 build-rss-feed.bat
 ```
 
@@ -70,7 +70,7 @@ reflect the final MP3 file sizes.
 
 Runs local RSS 2.0 and iTunes compliance checks on `podcasts\feed.xml`.
 
-```
+```bat
 validate-rss-feed.bat
 ```
 
@@ -114,7 +114,7 @@ a PowerShell or bash session at the repo root.
 
 To pass a range to the audio build from npm:
 
-```
+```bash
 npm run build:podcast-audio -- --start 5 --end 10
 ```
 

CONTRIBUTING.md

@@ -100,7 +100,7 @@ git remote -v
 
 Expected output:
 
-```
+```text
 origin    https://github.com/[your-username]/[workshop-repo-name].git (fetch)
 origin    https://github.com/[your-username]/[workshop-repo-name].git (push)
 upstream  https://github.com/[original-owner]/[workshop-repo-name].git (fetch)
@@ -164,7 +164,7 @@ which is not a term NVDA uses. Updated to match NVDA's own terminology."
 
 **Commit message format:**
 
-```
+```text
 type: short summary (under 72 characters)
 
 Optional longer explanation of why the change was made, not just what
@@ -402,7 +402,7 @@ When you open a pull request, fill in the template that appears. If no template
 
 ### PR Title Format
 
-```
+```text
 fix: correct JAWS shortcut for PR review in Section 3
 docs: add alternative macOS exercise for Section 6
 exercise: add bonus challenge for notifications day 2

README.md

@@ -96,7 +96,7 @@ You do **not** need to know how to code to participate and contribute meaningful
 
 This is not a two-day course with two separate syllabi. It is one arc.
 
-```
+```text
 Day 1 - Learn the skill in the browser
   Navigate → Issue → Pull Request → Review → Merge
 
@@ -233,7 +233,7 @@ Every chapter has an "If You Get Stuck" section. Every challenge has a [referenc
 
 > **One repository, everything included.** Clone or fork this repo and you have the complete workshop - all curriculum guides, Accessibility Agents agents and slash commands, YAML issue forms, PR template, and a practice contribution target in `learning-room/`. GitHub Skills modules cannot be bundled here (each participant activates their own copy on their own account), but links are in `.github/ISSUE_TEMPLATE/config.yml`.
 
-```
+```text
 [repo root]/
 ├── README.md                            -- You are here
 ├── CONTRIBUTING.md                      -- How to contribute to this repo

admin/ACCESSIBILITY_TESTING.md

@@ -49,7 +49,7 @@ Use before deploying any new issue template or form.
 
 ### NVDA Testing (Windows)
 
-```
+```text
 1. Press NVDA+Space to enable browse mode on page
 2. Press H to navigate to first heading
 3. Use H repeatedly to scan all headings (should be H1 → H2 → H3, not jumps)
@@ -73,7 +73,7 @@ Use before deploying any new issue template or form.
 
 ### JAWS Testing (Windows)
 
-```
+```text
 1. Press Spacebar to enter browse mode
 2. Press Insert+F6 to open headings list
    - Verify headings are in order (1 → 2 → 3, no jumps)
@@ -97,7 +97,7 @@ Use before deploying any new issue template or form.
 
 ### VoiceOver Testing (macOS)
 
-```
+```text
 1. Press VO+U to open Web Rotor
 2. Navigate to Form Controls section
    - Should list all fields
@@ -275,7 +275,7 @@ Test WITHOUT using the mouse.
 
 When you find an accessibility problem, document it:
 
-```
+```text
 Title: [Accessibility] Form label missing on email field
 
 Description:

admin/AGENTS_ROADMAP.md

@@ -57,7 +57,7 @@ This document tracks the curriculum's alignment with Accessibility Agents versio
 
 **Example:**
 
-```
+```text
 Version 4.x:
 User: @aria-specialist audit this component
 Agent: [Reports 3 ARIA errors]
@@ -75,7 +75,7 @@ Agent: [Returns remediated code for approval]
 **Before (4.x):** No automated compliance reporting.
 **Now (5.0.0+):** Generate VPAT and compliance reports automatically.
 
-```
+```text
 User: @document-csv-reporter generate-vpat audit-findings.json
 Agent: [Exports findings mapped to WCAG 2.2 AA and Section 508]
 Agent: [Generates VPAT template with compliance assertions]
@@ -89,7 +89,7 @@ Output: compliance-report.xlsx
 
 **Capability:**
 
-```
+```text
 Hook configuration:
 {
   "name": "continuous-eval",
@@ -265,7 +265,7 @@ Output: Trend report showing score changes week-over-week
 
 ### Three Teams, 80 Agents, 5 Platforms
 
-```
+```text
 Accessibility Agents 5.0.0
 ├── Team 1: Accessibility (40 agents)
 │   ├── Web (26): Specialists, wizards, coaches