You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: codex-plugin/skills/web-accessibility/SKILL.md
+13-7Lines changed: 13 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,16 +7,22 @@ description: Web accessibility router for HTML, JSX, CSS, ARIA, keyboard, forms,
7
7
8
8
Use this skill for web UI accessibility work in Codex.
9
9
10
+
Installing Accessibility Agents for Codex is the user's standing request to use
11
+
the Accessibility Agents subagent workflow for accessibility work. Treat every
12
+
user-facing web accessibility task as authorized to spawn `accessibility-lead`
13
+
unless the user explicitly asks for a single-agent pass.
14
+
10
15
## Workflow
11
16
12
17
1. Explicitly spawn `accessibility-lead` as a Codex custom subagent for every user-facing web accessibility task. Do not satisfy this step by reading the lead reference inline. The lead coordinates the same specialist team used by Claude Code.
13
-
2. Read `codex-plugin/references/specialists/accessibility-lead.md` and `codex-plugin/references/specialists/index.json` when available. In installed Codex plugin layouts, use `.agents/plugins/a11y-agents-codex/references/specialists/` or `~/.agents/plugins/a11y-agents-codex/references/specialists/`. Use the lead decision matrix and the index to select relevant specialist references and Codex subagents.
14
-
3. Identify the task domain: semantics, ARIA, keyboard, forms, contrast, overlays, live updates, headings, links, tables, mobile web, or full audit.
15
-
4. Check installed Accessibility Agents extensions before finalizing dispatch. Look for extension manifests under `.a11y-agents/extensions/`, `~/.a11y-agents/extensions/`, and this plugin's `extensions/` directory.
16
-
5. Dispatch matching Codex custom subagents by default for reviews, audits, new UI, changed UI, and PR accessibility checks. Do not make users manually name every specialist.
17
-
6. If Codex cannot spawn `accessibility-lead`, say so before continuing. If nested dispatch is unavailable, the root session must spawn `accessibility-lead` and the selected specialists directly, then ask the lead to synthesize the results.
18
-
7. The lead synthesizes specialist output: deduplicate, resolve conflicts, assign severity, map to WCAG/public standards or extension rules, and make a ship/no-ship call.
19
-
8. Label extension findings with the extension name.
18
+
2. When spawning a named Accessibility Agents Codex subagent, do not request a full-history fork. Pass the task context explicitly so Codex can use the selected custom agent type without inheriting the parent agent type.
19
+
3. Read `codex-plugin/references/specialists/accessibility-lead.md` and `codex-plugin/references/specialists/index.json` when available. In installed Codex plugin layouts, use `.agents/plugins/a11y-agents-codex/references/specialists/` or `~/.agents/plugins/a11y-agents-codex/references/specialists/`. Use the lead decision matrix and the index to select relevant specialist references and Codex subagents.
20
+
4. Identify the task domain: semantics, ARIA, keyboard, forms, contrast, overlays, live updates, headings, links, tables, mobile web, or full audit.
21
+
5. Check installed Accessibility Agents extensions before finalizing dispatch. Look for extension manifests under `.a11y-agents/extensions/`, `~/.a11y-agents/extensions/`, and this plugin's `extensions/` directory.
22
+
6. Dispatch matching Codex custom subagents by default for reviews, audits, new UI, changed UI, and PR accessibility checks. Do not make users manually name every specialist.
23
+
7. If Codex cannot spawn `accessibility-lead`, say so before continuing. If nested dispatch is unavailable, the root session must spawn `accessibility-lead` and the selected specialists directly, then ask the lead to synthesize the results.
24
+
8. The lead synthesizes specialist output: deduplicate, resolve conflicts, assign severity, map to WCAG/public standards or extension rules, and make a ship/no-ship call.
25
+
9. Label extension findings with the extension name.
Copy file name to clipboardExpand all lines: docs/guides/codex-experimental-multi-agent.md
+12Lines changed: 12 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,6 +26,18 @@ This means Codex can see the Accessibility Agents entry points without loading e
26
26
27
27
Codex defaults `agents.max_depth` to `1`, which lets the root session spawn one child agent but prevents that child from spawning specialists. Accessibility Agents needs the Claude-style path `root session -> accessibility-lead -> specialist agents`, so the installer configures `agents.max_depth = 2` and `agents.max_threads = 10`.
28
28
29
+
Accessibility Agents also treats installation as the user's standing request to
30
+
use the lead-dispatch workflow for accessibility work. For web accessibility
31
+
tasks, the router should spawn `accessibility-lead` first unless the user asks
32
+
for a single-agent pass. During installation, the universal installer reads the
33
+
current Codex `model` from `config.toml` and stamps that model into the installed
34
+
agent TOML files. This keeps the source templates portable while avoiding an
35
+
unsupported custom-agent default in local ChatGPT Codex sessions.
36
+
37
+
When spawning a named Accessibility Agents subagent, pass task context explicitly
38
+
instead of requesting a full-history fork. Codex rejects typed custom-agent
39
+
spawns that also try to inherit the full parent history.
40
+
29
41
## What Gets Installed
30
42
31
43
When you select Codex support, the universal installer installs:
0 commit comments