Skip to content

feat: add CMS Accessibility Specialist agent#349

Open
itlasso wants to merge 4 commits intomsitarzewski:mainfrom
itlasso:feat/cms-accessibility-specialist
Open

feat: add CMS Accessibility Specialist agent#349
itlasso wants to merge 4 commits intomsitarzewski:mainfrom
itlasso:feat/cms-accessibility-specialist

Conversation

@itlasso
Copy link
Copy Markdown
Contributor

@itlasso itlasso commented Mar 26, 2026

What does this PR do?

Adds a new CMS Accessibility Specialist agent to the Engineering Division, specializing in WCAG 2.1 AA compliance, remediation, and accessible development for WordPress and Drupal websites.

Agent Information (if adding/modifying an agent)

  • Agent Name: CMS Accessibility Specialist
  • Category: Engineering
  • Specialty: WCAG 2.1 AA auditing, accessible Gutenberg blocks and Drupal components, video captions, audio transcripts, SVG accessibility, motion/animation controls, screen reader testing (NVDA, JAWS, VoiceOver, TalkBack), and editorial accessibility training

Checklist

  • Follows the agent template structure from CONTRIBUTING.md
  • Includes YAML frontmatter with name, description, color
  • Has concrete code/template examples (for new agents)
  • Tested in real scenarios
  • Proofread and formatted correctly

@msitarzewski
Copy link
Copy Markdown
Owner

Hey @itlasso — thanks for this! Two things to fix:

  1. Malformed filename — the agent file ended up named feat: add CMS Accessibility Specialist agent instead of a proper path like engineering/engineering-cms-accessibility-specialist.md. Looks like the commit message got used as the filename accidentally.

  2. Rebase needed — I just merged feat: add CMS Developer agent (WordPress & Drupal) #318 (CMS Developer), so this will need a rebase to resolve the conflict on that file.

Once those are sorted, this is good to go!

itlasso added 2 commits March 27, 2026 06:31
Added CMS Accessibility Specialist agent covering WCAG 2.1 AA auditing, remediation, accessible Gutenberg block and Drupal component development, video captions, audio transcripts, SVG accessibility, motion and animation controls, assistive technology testing, and editorial accessibility training for WordPress and Drupal websites.
Added a vibe description for CMS Developer role.## What does this PR do?

Adds a new CMS Accessibility Specialist agent to the Engineering Division, specializing in WCAG 2.1 AA compliance, remediation, and accessible development for WordPress and Drupal websites.

## Agent Information (if adding/modifying an agent)

- **Agent Name**: CMS Accessibility Specialist
- **Category**: Engineering
- **Specialty**: WCAG 2.1 AA auditing, accessible Gutenberg blocks and Drupal components, video captions, audio transcripts, SVG accessibility, motion/animation controls, screen reader testing (NVDA, JAWS, VoiceOver, TalkBack), and editorial accessibility training

## Checklist

- [x] Follows the agent template structure from CONTRIBUTING.md
- [x] Includes YAML frontmatter with `name`, `description`, `color`
- [x] Has concrete code/template examples (for new agents)
- [x] Tested in real scenarios
- [x] Proofread and formatted correctly
@itlasso itlasso force-pushed the feat/cms-accessibility-specialist branch from 40e969e to 85753e0 Compare March 27, 2026 10:32
@itlasso
Copy link
Copy Markdown
Contributor Author

itlasso commented Mar 27, 2026

@msitarzewski rebased and added the vibe field — ready for review. Thanks!

@itlasso
Copy link
Copy Markdown
Contributor Author

itlasso commented Mar 27, 2026

@msitarzewski fixed the filename and moved it to the correct path, and rebased — should be good to go now. Thanks!

@mhc222
Copy link
Copy Markdown

mhc222 commented Mar 30, 2026

Code Review

1 issue found (the engineering-cms-developer.md change adding vibe: is correct).


Issue 1 — Section headers on new agent don't match required template format (score: 100)

engineering-cms-accessibility-specialist.md uses non-standard heading text throughout. The convert.sh script matches these headers exactly to split agents into tool-specific formats.

Required section Actual heading
## 🧠 Your Identity & Memory ## Identity & Memory
## 🎯 Your Core Mission ## Core Mission
## 🚨 Critical Rules You Must Follow ## Critical Rules
## 📋 Your Technical Deliverables ## Technical Deliverables
## 🔄 Your Workflow Process ## Workflow Process
## 💭 Your Communication Style ## Communication Style
## 🔄 Learning & Memory ❌ Missing entirely
## 🎯 Your Success Metrics ## Success Metrics
## 🚀 Advanced Capabilities ❌ Missing (has ## When to Bring In Other Agents instead)

Each heading needs the correct emoji prefix and full Your phrasing per the CONTRIBUTING.md template (§ Agent File Structure). This matches the same issue flagged in PR #357 and #356 from the same author.


Reviewed by Code Reviewer agent. Issues are only reported at confidence ≥80/100.

@mhc222 mhc222 mentioned this pull request Mar 30, 2026
5 tasks
Added correct emoji prefixes and "Your" phrasing to all section headers. Added missing Learning & Memory and Advanced Capabilities sections. Replaced When to Bring In Other Agents with Advanced Capabilities.
@itlasso
Copy link
Copy Markdown
Contributor Author

itlasso commented Mar 31, 2026

@msitarzewski @mhc222 fixed all section headers with correct emoji prefixes and "Your" phrasing. Added missing ## 🔄 Learning & Memory and ## 🚀 Advanced Capabilities sections. Ready for re-review. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants