DOWNLOADABLE CODEX SKILL · v1.0.0
Review a WordPress page for practical keyboard, structure, contrast, and form issues.
By Abdessalam · Updated
THE WORKFLOW
Review a WordPress page for practical keyboard, structure, contrast, and form issues. It keeps the work tied to evidence and the project’s actual constraints.
The user asks for an accessibility pass on a WordPress page or component. Download the package, inspect its instructions, and adapt its review notes to the project.
EXAMPLE REQUEST
$aboutcodex-wp-accessibility-review Review the skill library filters and download controls for keyboard and screen-reader usability.Prioritized findings or verified fixes tied to user tasks and owning code.
Inspect the extracted package first. For a local project, place the skill folder here:
.agents/skills/aboutcodex-wp-accessibility-review/SKILL.mdOpen the project and inspect the Skills sidebar to locate the skill by name. Follow the skill controls available in your current desktop application.
Open the project in Codex CLI. Use /skills or $aboutcodex-wp-accessibility-review to select the skill explicitly.
Open the project in the Codex IDE extension. Use /skills or $aboutcodex-wp-accessibility-review to select the skill explicitly.
Verify discovery: locate the exact skill name before starting. If missing, check the folder, SKILL.md filename, and name/description frontmatter, then restart the client.
After selecting the skill, use this inspection request:
Read the aboutcodex-wp-accessibility-review skill. Explain its purpose, inputs, and boundaries. Do not edit files or run its workflow yet.Documentation-based guidance, checked September 10, 2026. Client discovery was not independently tested here. OpenAI’s skill documentation. Troubleshoot installation
aboutcodex-wp-accessibility-review/SKILL.md1 KBaboutcodex-wp-accessibility-review/references/NOTES.md452 Baboutcodex-wp-accessibility-review/LICENSE.txt1 KB---
name: "aboutcodex-wp-accessibility-review"
description: "Review a WordPress page for practical keyboard, structure, contrast, and form issues. Use when the user asks for an accessibility pass on a WordPress page or component."
---
# Review WordPress accessibility
Review a WordPress page for practical keyboard, structure, contrast, and form issues.
## Workflow
1. Identify the page purpose and the interactive elements that matter to its main task.
2. Inspect headings, landmarks, link names, labels, focus order, and keyboard access in the rendered page.
3. Check color contrast and visible focus using measured values when tools are available.
4. Trace each issue to its owning block, template, plugin, or stylesheet.
5. Fix authorized issues and repeat the affected keyboard and narrow-screen paths.
Read `references/NOTES.md` before finalizing the work. Follow project instructions and the user's authorized scope. Use available evidence, label assumptions, and never report a check as passing unless it actually ran.
## Deliverable
Prioritized findings or verified fixes tied to user tasks and owning code. State material limitations and link to changed files or rendered evidence when available.
This focused review is not a formal conformance certification or a substitute for testing with disabled users.
Structure checked · 2026-09-10
Required frontmatter, folder layout, file inventory, validator run, and generated ZIP round-trip checked. Workflow behavior has not been independently evaluated.
Package checks confirm file structure. They do not establish that a skill works well on every task.
1.0.0 — Initial instruction-only release with supporting review notes.
Progress stays in this browser. No account needed.
Added interface-specific guidance and a read-only inspection request. The downloadable package is unchanged.
What to do: No re-download needed for this documentation update. Inspect the current version and compare your local changes before replacing a skill.
This log starts with the first recorded review; it is not a reconstruction of earlier revisions.
THE ABOUTCODEX BRIEFING
One workflow to try, one change explained, and one resource to keep. Planned weekly.
Read the sample issue ↗Confirm your email to join. Unsubscribe anytime through a delivered newsletter. Privacy policy.