fix(a11y): convert all Mermaid YAML header blocks to inline accTitle/accDescr syntax

.github/ISSUE_TEMPLATE/README.md

@@ -3,8 +3,8 @@ title: "Issue Templates Directory"
 description: "Standardized issue templates for the LightSpeedWP organization. Templates for bugs, features, documentation, and custom issues with automation integration."
 name: "Issue Templates"
 file_type: documentation
-version: v1.7
-last_updated: "2026-06-18"
+version: v1.8
+last_updated: "2026-06-19"
 created_date: "2025-10-20"
 authors: ["LightSpeed Team"]
 maintainer: "LightSpeed Team"
@@ -46,11 +46,9 @@ For advanced usage, see the [Issue Template Index](./README.md) and individual t
 ## 🗂️ Issue Template Workflow
 
 ```mermaid
----
-accTitle: Issue template workflow
-accDescr: Shows the flow from user selecting a template through auto-labeling, agent processing, and routing to project boards.
----
 flowchart TD
+    accTitle: Issue template workflow
+    accDescr: Shows the flow from user selecting a template through auto-labeling, agent processing, and routing to project boards.
     A[User Creates Issue] --> B{Select Template}
     B -->|Bug Report| C[Bug Template]
     B -->|Feature Request| D[Feature Template]

.github/README.md

@@ -4,9 +4,9 @@ title: LightSpeed .github Community Health Repository
 description: Central hub for all shared GitHub templates, Copilot instructions, workflow
   automation, labeling systems, and community health files across the LightSpeed WordPress
   organisation
-version: '3.6'
+version: '3.7'
 created_date: '2025-01-15'
-last_updated: '2026-06-18'
+last_updated: '2026-06-19'
 authors:
 - LightSpeed Team
 maintainer: LightSpeed Team
@@ -62,10 +62,6 @@ This repository's `.github` folder serves as the **single source of truth** for
 ## GitHub Template Ecosystem Architecture
 
 ```mermaid
----
-accTitle: GitHub Template Ecosystem Architecture
-accDescr: Flowchart showing the .github repository hub at the center containing community health files, issue templates, PR templates, AI instructions, automation rules, and workflows, flowing to template categories including bug reports, feature requests, documentation, architecture, security, and testing, then to AI and automation systems including auto-labeling, project sync, quality gates, deployment, and analytics, finally connecting to organization repositories
----
 flowchart TB
 accTitle: GitHub template ecosystem architecture
 accDescr {
@@ -208,10 +204,6 @@ This repository is the **canonical, organisation-wide source** for:
 ## GitHub Automation Workflow Process
 
 ```mermaid
----
-accTitle: GitHub Automation Workflow Process
-accDescr: Sequence diagram showing the interaction between a developer, member repository, .github hub, automation system, and project manager during the issue or PR creation process, demonstrating how templates are checked, labels are applied, and projects are synchronized
----
 sequenceDiagram
 accTitle: GitHub automation workflow sequence
 accDescr {
@@ -258,10 +250,6 @@ The `.github` folder is organised for maximum clarity and modularity, grouping r
 ## Repository Structure Visualization
 
 ```mermaid
----
-accTitle: Repository Structure Visualization
-accDescr: Graph showing the .github directory structure including instructions, prompts, agents, workflows, issue templates, pull request templates, saved replies, and automation subdirectories, with connections to their respective ecosystems including coding standards, linting, accessibility instructions, prompts, and automation core configuration
----
 graph TB
 accTitle: Repository structure visualization
 accDescr {
@@ -399,10 +387,6 @@ This diagram illustrates how all components work together to create a seamless d
 ## Complete Integration Flow
 
 ```mermaid
----
-accTitle: Complete Integration Flow
-accDescr: Flowchart showing the developer experience (new contributor, issue creation, PR submission, code review) connecting to .github hub resources (instructions, templates, AI prompts, chat modes, automation), leading to automated processes (auto-labeling, project sync, quality gates, analytics), resulting in quality outcomes (consistent standards, faster onboarding, better tracking, security compliance)
----
 flowchart LR
 accTitle: Complete integration flow for development and governance
 accDescr {

.github/labels.yml

@@ -129,15 +129,15 @@
   description: "Feature or enhancement"
 
 - name: type:design
-  color: 8957E5
+  color: "8957E5"
   description: "Design work"
 
 - name: type:ui
-  color: 8957E5
+  color: "8957E5"
   description: "UI implementation and consistency"
 
 - name: type:epic
-  color: 8957E5
+  color: "8957E5"
   description: "Large multi-scope initiative"
 
 - name: type:story
@@ -185,7 +185,7 @@
   description: "Performance improvement"
 
 - name: type:a11y
-  color: 8957E5
+  color: "8957E5"
   description: "Accessibility"
   aliases:
     - a11y
@@ -197,15 +197,15 @@
     - security
 
 - name: type:compatibility
-  color: 007580
+  color: "007580"
   description: "Compatibility"
 
 - name: type:dependency
-  color: 007580
+  color: "007580"
   description: "Dependency management and updates"
 
 - name: type:integration
-  color: 007580
+  color: "007580"
   description: "Integration"
 
 - name: type:release
@@ -251,7 +251,7 @@
   description: "AI Ops"
 
 - name: type:content-modelling
-  color: 8957E5
+  color: "8957E5"
   description: "Content Modelling"
 
 - name: type:question
@@ -406,7 +406,7 @@
   description: "Analytics & tracking"
 
 - name: area:infrastructure
-  color: 007580
+  color: "007580"
   description: "Infrastructure / hosting / platform"
 
 - name: area:automation
@@ -418,15 +418,15 @@
   description: "Performance-focused work"
 
 - name: area:a11y
-  color: 8957E5
+  color: "8957E5"
   description: "Accessibility-focused work"
 
 - name: area:security
   color: CF222E
   description: "Security-focused work"
 
 - name: area:compatibility
-  color: 007580
+  color: "007580"
   description: "Compatibility and cross-environment concerns"
 
 - name: area:release
@@ -448,11 +448,11 @@
     - ci
 
 - name: area:deployment
-  color: 007580
+  color: "007580"
   description: "Deploy/release operations"
 
 - name: area:dependencies
-  color: 007580
+  color: "007580"
   description: "Composer/npm dependency work"
   aliases:
     - dependencies
@@ -462,7 +462,7 @@
   description: "Dependabot update appears security-related and eligible for guarded automation"
 
 - name: area:integration
-  color: 007580
+  color: "007580"
   description: "3rd-party integrations / ecosystem"
 
 # --- Components (comp:*) ---
@@ -598,23 +598,23 @@
 # --- Compatibility matrix ---
 
 - name: compat:wordpress
-  color: 007580
+  color: "007580"
   description: "WordPress core/Gutenberg compatibility"
 
 - name: compat:php
-  color: 007580
+  color: "007580"
   description: "PHP version compatibility"
 
 - name: compat:woocommerce
-  color: 007580
+  color: "007580"
   description: "WooCommerce versions"
 
 - name: compat:gutenberg
-  color: 007580
+  color: "007580"
   description: "Gutenberg package compatibility"
 
 - name: compat:rtl
-  color: 007580
+  color: "007580"
   description: "RTL languages support"
 
 - name: compat:multisite
@@ -686,7 +686,7 @@
   description: "Show & Tell"
 
 - name: discussion:community
-  color: 8957E5
+  color: "8957E5"
   description: "Community/general"
 
 - name: discussion:feedback

.github/prompts/update-mermaid-diagrams.prompt.md

@@ -5,7 +5,7 @@ description: "Refresh Mermaid diagrams across the repository or targeted paths w
 mode: "agent"
 tools: ["read", "edit", "search", "shell"]
 tags: ["mermaid", "documentation", "a11y", "wcag", "colour-contrast", "readme"]
-last_updated: "2026-06-18"
+last_updated: "2026-06-19"
 ---
 
 # Update Mermaid Diagrams
@@ -20,31 +20,43 @@ Refresh Mermaid diagrams across the repository to conform with the v2.0 standard
 
 ## What to Fix in Every Diagram
 
-### 1. Required accessibility header block
+### 1. Required accessibility attributes — inline format only
 
-Every `\`\`\`mermaid` block must open with a YAML header before the diagram type:
+Every ` ```mermaid ` block must have `accTitle` and `accDescr` placed **inline**, immediately after the diagram type and before any nodes. GitHub's Mermaid renderer does **not** support the YAML `---` front-matter syntax — diagrams using it will show an error instead of rendering.
+
+**Correct format:**
 
 ```text
----
-accTitle: Short accessible title (max 80 chars)
-accDescr: One-sentence description of what the diagram shows.
----
 flowchart LR
+    accTitle: Short accessible title (max 80 chars)
+    accDescr: One-sentence description of what the diagram shows.
     ...
 ```
 
 Use the block form for complex diagrams:
 
 ```text
+flowchart TD
+    accTitle: Title here
+    accDescr {
+      Multi-sentence description for screen readers.
+    }
+    ...
+```
+
+**Do NOT use** the YAML front-matter form (it breaks GitHub rendering):
+
+```text
+❌ WRONG — GitHub cannot render this:
 ---
-accTitle: Title here
-accDescr {
-  Multi-sentence description for screen readers.
-}
+accTitle: Title
+accDescr: Description
 ---
+flowchart LR
+    ...
 ```
 
-Remove any legacy inline `accTitle` / `accDescr` attributes that appear after the diagram type line.
+Remove any YAML `---` header blocks and replace them with inline attributes as shown above.
 
 ### 2. Approved colour palette — replace ALL old `style` declarations
 

.github/reports/audits/2026-06-03-file-organisation-migration-plan-673.md

@@ -4,8 +4,8 @@ title: "#673 Plan - File Organisation Refactoring Migration and Validation"
 description: "Phase 1 migration plan derived from #671 and #672 findings, including dependency graph, phased timeline, validation checklist, and rollback procedures."
 category: audits
 created_date: "2026-06-03"
-last_updated: "2026-06-03"
-version: "v1.0.0"
+last_updated: "2026-06-19"
+version: "v1.0.1"
 owners:
   - LightSpeed Team
 authors:
@@ -53,11 +53,9 @@ This plan is based on:
 ## Dependency Graph
 
 ```mermaid
----
-accTitle: Migration dependency graph for file-organisation refactor
-accDescr: Flowchart showing that reference remediation and boundary decisions feed script migration and then CI guardrails and final validation. Rollback checkpoints are attached after each major phase.
----
 flowchart TD
+    accTitle: Migration dependency graph for file-organisation refactor
+    accDescr: Flowchart showing that reference remediation and boundary decisions feed script migration and then CI guardrails and final validation. Rollback checkpoints are attached after each major phase.
     A[Phase 0 Baseline inventory] --> B[Phase 1 Reference remediation]
     A --> C[Phase 2 Boundary decision for .github or root]
     B --> D[Phase 3 Move or formalise .github scripts and agents remnants]
@@ -72,11 +70,9 @@ flowchart TD
 ## Timeline
 
 ```mermaid
----
-accTitle: Migration timeline
-accDescr: Gantt chart with six short phases across one working week from baseline to sign-off.
----
 gantt
+    accTitle: Migration timeline
+    accDescr: Gantt chart with six short phases across one working week from baseline to sign-off.
     title File Organisation Migration Timeline (Issue #673)
     dateFormat  YYYY-MM-DD
     section Planning

.github/reports/audits/readme-audit-2026-05-31.md

@@ -102,11 +102,9 @@ All README files have been updated recently or were created in the current year,
 **Applied Fix:**
 
 ```mermaid
----
-accTitle: VS Code Workspace Configuration Architecture
-accDescr: Flowchart showing the VS Code configuration hierarchy with three main branches (Extensions, Tasks, Settings) that lead to development tools including AI Agents, Linting tools (ESLint, Stylelint, Markdownlint), Testing (Jest), Build automation, EditorConfig, and Keybindings configuration
----
 flowchart TD
+    accTitle: VS Code Workspace Configuration Architecture
+    accDescr: Flowchart showing the VS Code configuration hierarchy with three main branches (Extensions, Tasks, Settings) that lead to development tools including AI Agents, Linting tools (ESLint, Stylelint, Markdownlint), Testing (Jest), Build automation, EditorConfig, and Keybindings configuration
     A[VS Code Workspace] --> B[Extensions]
     A --> C[Tasks]
     A --> D[Settings]