@jahia/agentic 0.0.0

package/dist/opencode/.agents/skills/jahia-content-translate-content/SKILL.md

@@ -0,0 +1,297 @@
+---
+name: jahia-content-translate-content
+description: Adds language support to a Jahia site and translates existing content nodes. Use when asked to add a new language, fill in missing translations, or audit which content lacks i18n values.
+---
+
+# Skill: jahia-content-translate-content
+
+Adds languages to a Jahia site and populates i18n properties on existing content nodes via the GraphQL API.
+
+---
+
+## Prerequisites
+
+- Jahia running at `http://localhost:8080`
+- Credentials: `root` / `root1234` (default)
+- GraphQL endpoint: `http://localhost:8080/modules/graphql`
+
+**Always include both auth flags:**
+```bash
+curl -s -u root:root1234 \
+     -H "Content-Type: application/json" \
+     -H "Origin: http://localhost:8080" \
+     -X POST http://localhost:8080/modules/graphql \
+     -d '{"query": "..."}'
+```
+
+> ⚠️ The `Origin` header is **required** — omitting it returns `Permission denied`.
+
+---
+
+## Step 1 — Enable the new language on the site
+
+Before creating or querying translations, the language must be declared on the site node.
+
+```bash
+# Check currently enabled languages
+curl -s -u root:root1234 \
+  -H "Content-Type: application/json" \
+  -H "Origin: http://localhost:8080" \
+  -X POST http://localhost:8080/modules/graphql \
+  -d '{
+    "query": "{ jcr { nodeByPath(path: \"/sites/mySite\") { properties(names: [\"j:languages\",\"j:defaultLanguage\"]) { name values } } } }"
+  }'
+
+# Add a language (e.g. "fr") — use setPropertiesBatch with the full new list
+curl -s -u root:root1234 \
+  -H "Content-Type: application/json" \
+  -H "Origin: http://localhost:8080" \
+  -X POST http://localhost:8080/modules/graphql \
+  -d '{
+    "query": "mutation { jcr { mutateNode(pathOrId: \"/sites/mySite\") { setPropertiesBatch(properties: [{name: \"j:languages\", values: [\"en\", \"fr\"]}]) { path } } } }"
+  }'
+```
+
+> ⚠️ `j:languages` is a multi-valued property — always pass the **complete** list of languages, not just the new one. Passing only `["fr"]` would remove `"en"`.
+
+---
+
+## Step 2 — Audit content missing translations
+
+Query all i18n-bearing nodes and inspect which ones have empty values for the target language:
+
+```bash
+# Find all content nodes under /sites/mySite/contents
+curl -s -u root:root1234 \
+  -H "Content-Type: application/json" \
+  -H "Origin: http://localhost:8080" \
+  -X POST http://localhost:8080/modules/graphql \
+  -d '{
+    "query": "{ jcr { nodesByQuery(query: \"SELECT * FROM [jmix:i18n] WHERE ISDESCENDANTNODE(\u0027/sites/mySite/contents\u0027) ORDER BY [jcr:path] ASC\", queryLanguage: SQL2) { nodes { path primaryNodeType { name } properties(language: \"fr\") { name value } } } } }"
+  }'
+```
+
+Or query a specific content type:
+
+```bash
+curl -s -u root:root1234 \
+  -H "Content-Type: application/json" \
+  -H "Origin: http://localhost:8080" \
+  -X POST http://localhost:8080/modules/graphql \
+  -d '{
+    "query": "{ jcr { nodesByQuery(query: \"SELECT * FROM [namespace:article] WHERE ISDESCENDANTNODE(\u0027/sites/mySite/contents\u0027)\", queryLanguage: SQL2) { nodes { path properties(language: \"fr\") { name value } } } } }"
+  }'
+```
+
+Look for nodes where i18n fields (`jcr:title`, `body`, etc.) have empty or null `value`.
+
+---
+
+## Step 3 — Set i18n properties
+
+### Single node
+
+```bash
+curl -s -u root:root1234 \
+  -H "Content-Type: application/json" \
+  -H "Origin: http://localhost:8080" \
+  -X POST http://localhost:8080/modules/graphql \
+  -d '{
+    "query": "mutation { jcr { mutateNode(pathOrId: \"/sites/mySite/contents/articles/my-article\") { setPropertiesBatch(properties: [{name: \"jcr:title\", value: \"Mon article\", language: \"fr\"}, {name: \"body\", value: \"<p>Contenu ici</p>\", language: \"fr\"}]) { path } } } }"
+  }'
+```
+
+> ⚠️ Use `setPropertiesBatch` (plural), not `setProperty` (singular — does not exist in the Jahia GraphQL API).
+
+### Critical ordering rule
+
+When a content type has **mandatory** i18n fields (other than `jcr:title`), set those **before** `jcr:title`. Setting `jcr:title` first can trigger a constraint check before all mandatory fields are present.
+
+The safe pattern — set all mandatory i18n fields in a single `setPropertiesBatch` call:
+
+```bash
+curl -s -u root:root1234 \
+  -H "Content-Type: application/json" \
+  -H "Origin: http://localhost:8080" \
+  -X POST http://localhost:8080/modules/graphql \
+  -d '{
+    "query": "mutation { jcr { mutateNode(pathOrId: \"/sites/mySite/contents/articles/my-article\") { setPropertiesBatch(properties: [{name: \"body\", value: \"<p>Contenu ici</p>\", language: \"fr\"}, {name: \"jcr:title\", value: \"Mon article\", language: \"fr\"}]) { path } } } }"
+  }'
+```
+
+---
+
+## Step 4 — Bulk translation with Python
+
+For translating many nodes at once:
+
+```python
+import json
+from urllib.request import Request, urlopen
+
+JAHIA = "http://localhost:8080"
+AUTH = ("root", "root1234")
+
+import base64
+token = base64.b64encode(f"{AUTH[0]}:{AUTH[1]}".encode()).decode()
+HEADERS = {
+    "Content-Type": "application/json",
+    "Origin": JAHIA,
+    "Authorization": f"Basic {token}",
+}
+
+def gql(query):
+    body = json.dumps({"query": query}).encode()
+    req = Request(f"{JAHIA}/modules/graphql", data=body, headers=HEADERS, method="POST")
+    with urlopen(req) as r:
+        d = json.loads(r.read())
+    if "errors" in d:
+        print("ERR:", d["errors"][0]["message"][:120])
+    return d
+
+# 1. List all articles missing French title
+result = gql(
+    '{ jcr { nodesByQuery(query: "SELECT * FROM [namespace:article] '
+    "WHERE ISDESCENDANTNODE('/sites/mySite/contents') "
+    'ORDER BY [jcr:path] ASC", queryLanguage: SQL2) '
+    '{ nodes { path properties(language: "fr") { name value } } } } }'
+)
+
+nodes = result["data"]["jcr"]["nodesByQuery"]["nodes"]
+missing_fr = [
+    n["path"]
+    for n in nodes
+    if not any(p["name"] == "jcr:title" and p["value"] for p in n["properties"])
+]
+
+# 2. Set French translations (replace with actual translated values)
+translations = {
+    "/sites/mySite/contents/articles/article-1": ("Titre FR 1", "<p>Corps FR 1</p>"),
+    "/sites/mySite/contents/articles/article-2": ("Titre FR 2", "<p>Corps FR 2</p>"),
+}
+
+for path, (title, body) in translations.items():
+    r = gql(
+        f'mutation {{ jcr {{ mutateNode(pathOrId: "{path}") {{'
+        f' setPropertiesBatch(properties: ['
+        f'  {{name: "body", value: {json.dumps(body)}, language: "fr"}},'
+        f'  {{name: "jcr:title", value: {json.dumps(title)}, language: "fr"}}'
+        f' ]) {{ path }} }} }} }}'
+    )
+    ok = "errors" not in r
+    print(f"  {'✓' if ok else '✗'} {path.split('/')[-1]}")
+```
+
+---
+
+## Step 5 — Choicelist fields and view-level translations
+
+### Choicelist fields should NOT be i18n
+
+If a CND property uses a choicelist (e.g. `category`, `status`), its stored values are language-agnostic keys like `"featured"` or `"draft"`. The display label is translated **in the view**, not in the JCR.
+
+```tsx
+// In the view component — translate the stored key to a display label
+const STATUS_LABELS: Record<string, Record<string, string>> = {
+  en: { featured: "Featured", draft: "Draft" },
+  fr: { featured: "En vedette", draft: "Brouillon" },
+};
+
+const lang = renderContext.getMainResourceLocale().getLanguage();
+const statusKey = properties.status as string;
+const statusLabel = STATUS_LABELS[lang]?.[statusKey] ?? statusKey;
+```
+
+Do **not** add `i18n` to the CND property for choicelists — the key should be the same in all languages.
+
+### Hardcoded UI strings
+
+View-level strings that are not stored in JCR (button labels, headings, placeholder text) need locale-keyed label maps in the component:
+
+```tsx
+const LABELS = {
+  en: { readMore: "Read more", by: "By" },
+  fr: { readMore: "Lire la suite", by: "Par" },
+};
+
+const t = LABELS[renderContext.getMainResourceLocale().getLanguage()] ?? LABELS.en;
+// Usage: <a>{t.readMore}</a>
+```
+
+---
+
+## Step 6 — Clean up orphaned translation nodes
+
+When you remove the `i18n` flag from a CND property (or delete a language from the site), orphaned `j:translation_XX` child nodes may remain. Inspect and remove them if needed:
+
+```bash
+# Find translation sub-nodes for a content node
+curl -s -u root:root1234 \
+  -H "Content-Type: application/json" \
+  -H "Origin: http://localhost:8080" \
+  -X POST http://localhost:8080/modules/graphql \
+  -d '{
+    "query": "{ jcr { nodeByPath(path: \"/sites/mySite/contents/articles/my-article\") { children { nodes { name primaryNodeType { name } } } } } }"
+  }'
+
+# Delete an orphaned translation node
+curl -s -u root:root1234 \
+  -H "Content-Type: application/json" \
+  -H "Origin: http://localhost:8080" \
+  -X POST http://localhost:8080/modules/graphql \
+  -d '{
+    "query": "mutation { jcr { deleteNode(pathOrId: \"/sites/mySite/contents/articles/my-article/j:translation_fr\") }"
+  }'
+```
+
+---
+
+## Step 7 — Publish translations
+
+After setting i18n properties, republish to make them live:
+
+```bash
+# Publish a single node for a specific language
+curl -s -u root:root1234 \
+  -H "Content-Type: application/json" \
+  -H "Origin: http://localhost:8080" \
+  -X POST http://localhost:8080/modules/graphql \
+  -d '{
+    "query": "mutation { jcr { mutateNode(pathOrId: \"/sites/mySite/contents/articles/my-article\") { publish(languages: [\"fr\"]) } } }"
+  }'
+
+# Publish all articles in both languages
+curl -s -u root:root1234 \
+  -H "Content-Type: application/json" \
+  -H "Origin: http://localhost:8080" \
+  -X POST http://localhost:8080/modules/graphql \
+  -d '{
+    "query": "mutation { jcr { mutateNodesByQuery(query: \"SELECT * FROM [namespace:article] WHERE ISDESCENDANTNODE(\u0027/sites/mySite/contents\u0027)\", queryLanguage: SQL2) { publish(languages: [\"en\", \"fr\"]) } } }"
+  }'
+```
+
+---
+
+## Common errors
+
+| Error | Cause | Fix |
+|-------|-------|-----|
+| `Permission denied` | Missing `Origin` header | Add `-H "Origin: http://localhost:8080"` |
+| i18n property returned empty after set | Missing `language:` in `properties()` query | Add `language: "fr"` to read call |
+| `ConstraintViolationException` on title set | Mandatory i18n field not set first | Use `setPropertiesBatch` with all mandatory fields in one call |
+| Language not appearing in site | `j:languages` mutation only had the new language | Pass the full list: `["en", "fr"]` |
+| Choicelist key changed per language | Property incorrectly declared `i18n` in CND | Remove `i18n` from the CND property; translate keys in the view |
+
+---
+
+## Workflow summary
+
+```
+1. Enable language   → mutateNode j:languages with full list
+2. Audit             → nodesByQuery with properties(language: "XX") to find gaps
+3. Translate         → setPropertiesBatch with language: "XX" for each i18n field
+4. View strings      → add locale-keyed label maps in .server.tsx
+5. Choicelists       → translate keys in the view, not the JCR
+6. Publish           → publish(languages: ["XX"]) for all affected nodes
+7. Verify            → query back with language: "XX" to confirm values
+```

package/dist/opencode/.agents/skills/jahia-dev/SKILL.md

@@ -0,0 +1,124 @@
+---
+name: jahia-dev
+description: Entry point for Jahia JavaScript module development. Detects your project state and tells you what to do next. Start here if you are new to the project or unsure what skill to use.
+---
+
+# Jahia Dev — Project GPS
+
+You are the entry point for Jahia JavaScript module development. Your job is to assess the current project state and guide the user to the right next skill.
+
+## Step 1 — Detect project state
+
+Run all checks in parallel.
+
+### 1. Module exists?
+
+Search for a `package.json` that references `@jahia/javascript-modules-library` in the current directory or subdirectories:
+
+```bash
+find . -name "package.json" -not -path "*/node_modules/*" | xargs grep -l "@jahia/javascript-modules-library" 2>/dev/null | head -5
+```
+
+- Found → record the module name (from the `name` field in that `package.json`)
+- Not found → module does not exist yet
+
+### 2. Jahia running?
+
+```bash
+curl -s -o /dev/null -w "%{http_code}" http://localhost:8080/cms/login
+```
+
+- `200` → Jahia is running at `http://localhost:8080`
+- Anything else → Jahia is not running
+
+### 3. Content types defined?
+
+```bash
+find src/components -name "definition.cnd" 2>/dev/null | wc -l
+```
+
+Record the count of `.cnd` files found under `src/components`.
+
+### 4. Views defined?
+
+```bash
+find src/components -name "*.server.tsx" -o -name "*.client.tsx" 2>/dev/null | wc -l
+```
+
+Record the count of view files found.
+
+### 5. Page templates defined?
+
+```bash
+find src/templates/Page -type f 2>/dev/null | wc -l
+```
+
+Record the count of files in `src/templates/Page/`. More than 1 means custom templates exist (the default `index.server.tsx` is always present).
+
+---
+
+## Step 2 — Report project state to user
+
+Print a clear, scannable status summary:
+
+```
+📦 Module:          ✅ <module-name> (found)   OR   ❌ not found
+🐳 Jahia:           ✅ running at http://localhost:8080   OR   ❌ not running
+📋 Content types:   <N> defined
+🖼  Views:          <N> defined
+📄 Page templates:  <N> defined
+```
+
+---
+
+## Step 3 — Recommend next action
+
+Use the matrix below to pick exactly one recommendation to highlight:
+
+| Condition | Recommendation |
+|-----------|---------------|
+| No module found | 🚀 **Start here:** invoke `/jahia-dev-create-template-set` to scaffold a new Jahia JavaScript module. |
+| Module found, Jahia not running | 🐳 Your module is ready. Invoke `/jahia-dev-start-local` to start Jahia locally (Docker recommended). |
+| Module + Jahia running, 0 content types | 🎯 Jahia is running! Time to build your first component. Invoke `/jahia-dev-build-component` to create a content type + view. |
+| Module + Jahia running, content types exist, ≤1 page template | 📐 You have components. Invoke `/jahia-dev-create-page-template` to create a page template and start assembling pages. |
+| Module + Jahia running, templates exist (>1) | 🏗 Your module is taking shape! Choose what to do next (see options below). |
+
+When the last condition applies, present all options:
+
+```
+🏗 Your module is taking shape! What would you like to do next?
+  - Add a new component         → /jahia-dev-build-component
+  - Create a content listing    → /jahia-dev-query-content
+  - Review your code for issues → /jahia-dev-review
+  - Screenshot a reference site → /jahia-dev-screenshot
+  - Create a new page template  → /jahia-dev-create-page-template
+  - Clean up boilerplate        → run /jahia-dev-review and look for S10
+```
+
+---
+
+## Step 4 — Print the full skill map
+
+Always print this at the end so the user can navigate anywhere:
+
+```
+## Jahia Development Skills
+
+### Setup
+/jahia-dev-create-template-set   Scaffold a new JS/React module
+/jahia-dev-start-local           Start Jahia locally (Docker or bare metal)
+
+### Building
+/jahia-dev-build-component       Build a complete component (content type + view) ← start here
+/jahia-dev-define-content-type   Define a CND content type and types.ts
+/jahia-dev-create-view           Implement a React view (.server.tsx or .client.tsx Island)
+/jahia-dev-create-page-template  Create a page template with Areas
+
+### Content
+/jahia-dev-query-content         Query JCR content with JCR-SQL2 or useJCRQuery
+
+### Quality
+/jahia-dev-review                Review code for Jahia and generic best practices
+/jahia-dev-screenshot            Screenshot reference URL + Jahia render for visual comparison
+/jahia-dev-debug                 Debug build/deploy/runtime errors end-to-end
+```

package/dist/opencode/.agents/skills/jahia-dev-accessibility/SKILL.md

@@ -0,0 +1,271 @@
+---
+name: jahia-dev-accessibility
+description: Audits a Jahia JS module for WCAG 2.1 AA accessibility violations using axe-core and Playwright. Runs automated checks against all live pages, reports violations by severity, and fixes them in the React views and CSS. Invoke after building components or before final review.
+allowed-tools: Bash, Read, Write, Edit
+---
+
+# Skill: jahia-dev-accessibility
+
+Runs a live accessibility audit against all published pages of the site, reports violations, and fixes them in the source code.
+
+---
+
+## Step 1 — Confirm pages are live
+
+You need the list of public page URLs. Look for `pages.json` in the module root first:
+
+```bash
+cat pages.json 2>/dev/null || echo "not found"
+```
+
+If absent, derive URLs from the site structure or ask the user. All pages must be accessible at `http://localhost:8080`.
+
+---
+
+## Step 2 — Install audit tooling
+
+Check if `@axe-core/playwright` and `playwright` are available:
+
+```bash
+node -e "require('@axe-core/playwright'); require('playwright'); console.log('ok')" 2>/dev/null || echo "missing"
+```
+
+If missing, install temporarily (project-local, not committed):
+
+```bash
+npm install --no-save @axe-core/playwright playwright
+npx playwright install chromium --with-deps
+```
+
+---
+
+## Step 3 — Run the audit
+
+Save this script as `/tmp/a11y-audit.mjs` and run it:
+
+```js
+import { chromium } from "playwright";
+import { AxeBuilder } from "@axe-core/playwright";
+import { readFileSync } from "fs";
+
+const urls = JSON.parse(readFileSync("pages.json", "utf-8"));
+
+const browser = await chromium.launch({ args: ["--no-sandbox"] });
+const page = await browser.newPage();
+
+for (const url of urls) {
+  console.log(`\n${"=".repeat(60)}\nAuditing: ${url}\n${"=".repeat(60)}`);
+  await page.goto(url, { waitUntil: "networkidle", timeout: 30_000 });
+
+  const results = await new AxeBuilder({ page })
+    .withTags(["wcag2a", "wcag2aa", "wcag21aa"])
+    .analyze();
+
+  if (results.violations.length === 0) {
+    console.log("✅ No violations found.");
+    continue;
+  }
+
+  for (const v of results.violations) {
+    console.log(`\n[${v.impact?.toUpperCase()}] ${v.id}: ${v.description}`);
+    console.log(`Help: ${v.helpUrl}`);
+    for (const node of v.nodes) {
+      console.log(`  Target: ${node.target.join(" > ")}`);
+      console.log(`  HTML:   ${node.html}`);
+      if (node.failureSummary) {
+        console.log(`  Fix:    ${node.failureSummary}`);
+      }
+    }
+  }
+}
+
+await browser.close();
+```
+
+```bash
+node /tmp/a11y-audit.mjs 2>&1 | tee /tmp/a11y-report.txt
+```
+
+---
+
+## Step 4 — Interpret results
+
+Group violations by impact. Focus on `critical` and `serious` first — they contribute most to a poor score.
+
+Common violations in Jahia JS modules and their fixes:
+
+### 🔴 Critical / Serious
+
+**`color-contrast`** — text fails WCAG AA contrast ratio (4.5:1 for normal text, 3:1 for large text)
+```css
+/* Bad */
+color: #aaa; background: #fff;
+
+/* Fix — use a contrast checker: https://webaim.org/resources/contrastchecker/ */
+color: #595959; /* 7:1 ratio on white */
+```
+
+**`image-alt`** — `<img>` missing `alt` attribute
+```tsx
+/* Bad */
+<img src={buildNodeUrl(props.image)} />
+
+/* Fix — use content from CND, fall back to empty string for decorative */
+<img src={buildNodeUrl(props.image)} alt={props.imageAlt ?? ""} />
+```
+Add `- imageAlt (string) i18n` to the CND and `imageAlt?: string` to `types.ts`.
+
+**`button-name`** — `<button>` or `<a>` is empty (icon-only without label)
+```tsx
+/* Bad */
+<button><svg>...</svg></button>
+
+/* Fix */
+<button aria-label="Open menu"><svg aria-hidden="true">...</svg></button>
+```
+
+**`landmark-one-main`** — page has no `<main>` landmark
+```tsx
+/* Fix — wrap page content in <main> */
+<main id="main-content">
+  {/* page content */}
+</main>
+```
+
+**`page-has-heading-one`** — page has no `<h1>` element
+```tsx
+/* Fix — ensure the hero or first section renders an <h1> */
+<h1>{props.title}</h1>
+```
+
+**`link-name`** — `<a>` with no accessible text
+```tsx
+/* Bad */
+<a href={url}><img src="..." /></a>
+
+/* Fix */
+<a href={url}><img src="..." alt={props.linkLabel ?? "Learn more"} /></a>
+```
+
+### 🟡 Moderate
+
+**`heading-order`** — headings skip levels (e.g. `<h1>` → `<h3>`)
+```tsx
+/* Review: the first heading in a component should be h2 (after the page h1) */
+/* Section titles: h2, subsections: h3 */
+```
+
+**`region`** — content is outside landmark regions  
+Wrap page sections in semantic elements: `<header>`, `<nav>`, `<main>`, `<footer>`, `<section aria-label="...">`.
+
+**`list`** — `<ul>` or `<ol>` contains elements other than `<li>`
+```tsx
+/* Bad */
+<ul>
+  <div>item</div>
+</ul>
+
+/* Fix */
+<ul>
+  <li>item</li>
+</ul>
+```
+
+**`html-has-lang`** — `<html>` element missing `lang` attribute  
+This is set at the page template level. Verify the template registered in `src/templates/` includes `lang`:
+```tsx
+/* In the page template */
+<html lang={currentLanguage ?? "en"}>
+```
+Jahia provides the language via `useServerContext()`:
+```tsx
+import { useServerContext } from "@jahia/javascript-modules-library";
+const { currentLanguage } = useServerContext();
+```
+
+**`aria-required-children`** — ARIA role is missing required children  
+Avoid misusing ARIA roles. Prefer native HTML elements (`<ul>/<li>`, `<table>/<tr>/<td>`).
+
+---
+
+## Step 5 — Fix in source
+
+For each violation:
+
+1. Identify the component: match `node.target` HTML to a `.server.tsx` file
+2. Edit the view to apply the fix
+3. If the fix requires a new CND field (e.g. `imageAlt`), update `definition.cnd` and `types.ts`
+4. Run `yarn build && yarn jahia-deploy`
+
+After all fixes:
+
+```bash
+# Re-run the audit to verify violations are resolved
+node /tmp/a11y-audit.mjs 2>&1 | grep -E "(CRITICAL|SERIOUS|MODERATE|No violations)"
+```
+
+Iterate until only `minor` violations remain (or none).
+
+---
+
+## Step 6 — Proactive checks beyond axe-core
+
+axe-core catches ~30–40% of WCAG issues automatically. Also check manually:
+
+- **Keyboard navigation**: can every interactive element (link, button, form field) be reached with Tab?
+- **Focus indicators**: is `:focus` visible on all interactive elements?
+  ```css
+  /* Ensure focus ring is never suppressed globally */
+  /* Bad */
+  * { outline: none; }
+  /* Fix — use :focus-visible */
+  :focus-visible { outline: 2px solid #0969da; outline-offset: 2px; }
+  ```
+- **Skip link**: add a "Skip to main content" link as the first focusable element
+  ```tsx
+  <a href="#main-content" className={styles.skipLink}>Skip to main content</a>
+  ```
+  ```css
+  .skipLink {
+    position: absolute;
+    top: -100%;
+    left: 0;
+    background: #000;
+    color: #fff;
+    padding: 8px 16px;
+    z-index: 999;
+  }
+  .skipLink:focus { top: 0; }
+  ```
+- **Motion**: if any CSS animation exists, wrap it in `@media (prefers-reduced-motion: no-preference)`
+- **Touch targets**: interactive elements should be at least 44×44px
+
+---
+
+## Step 7 — Report summary
+
+After fixing, report:
+
+```
+## Accessibility Audit Summary
+
+Pages audited: N
+Violations fixed:
+  - [critical] color-contrast: 3 instances → fixed (updated CSS contrast ratios)
+  - [serious] image-alt: 2 instances → fixed (added imageAlt CND field)
+  - [serious] button-name: 1 instance → fixed (added aria-label to icon button)
+  - [moderate] heading-order: 2 instances → fixed (restructured h2/h3 hierarchy)
+
+Remaining violations: N (all minor / informational)
+
+Axe tags checked: wcag2a, wcag2aa, wcag21aa
+```
+
+---
+
+## References
+
+- WebAIM Contrast Checker: https://webaim.org/resources/contrastchecker/
+- axe-core rules: https://dequeuniversity.com/rules/axe/
+- WCAG 2.1 Quick Ref: https://www.w3.org/WAI/WCAG21/quickref/
+- MDN ARIA: https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA