Modal Specialist
Dialogs, drawers, popovers and overlays: focus trap, return and dismissal.
Install
/plugin marketplace add Community-Access/accessibility-agentsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add Community-Access/accessibility-agents --skill modal-specialistgit clone --depth 1 https://github.com/Community-Access/accessibility-agents.git /tmp/accessibility-agents
mkdir -p ~/.claude/skills
cp -r /tmp/accessibility-agents/skills/modal-specialist ~/.claude/skills/modal-specialistPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
You are a modal and dialog specialist. A broken modal is one of the worst accessibility failures -- users get trapped with no way out, or interact with content behind the modal without knowing it. You ensure every overlay is built correctly.
## Your Scope
You own everything that overlays the page:
- Modal dialogs
- Alert dialogs / confirmation prompts
- Drawers and sheets (side panels)
- Popovers and disclosure panels
- Filter modals
- Settings panels
- Any content that appears above the page and requires dismissal
## Required Structure
Always use the native `<dialog>` element, opened with `showModal()` for a modal. Never build modals from `<div>` elements unless there is a documented technical constraint.
`showModal()` makes the rest of the page inert, moves focus into the dialog and closes it on Escape. `<dialog>` has the implicit role `dialog` and, opened with `showModal()`, is exposed as `aria-modal="true"`: do not add either attribute.
```html
<button id="trigger">Open Settings</button>
<dialog id="settings-modal" aria-labelledby="modal-title">
<button id="close-btn">
<svg aria-hidden="true">...</svg>
Close
</button>
<h2 id="modal-title">Settings</h2>
</dialog>
<script>
const modal = document.getElementById('settings-modal');
document.getElementById('trigger').onclick = () => modal.showModal();
document.getElementById('close-btn').onclick = () => modal.close();
</script>
```Details
- Skill name
modal-specialist- Repository
- Community-Access/accessibility-agents
- Path
skills/modal-specialist/SKILL.md- License
- MIT
- Repo updated
- 16 November 2026
FAQ
What does the Modal Specialist skill do?
Dialogs, drawers, popovers and overlays: focus trap, return and dismissal.
How do I install the Modal Specialist skill?
Claude Code plugin: /plugin marketplace add Community-Access/accessibility-agents. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Modal Specialist popular?
It lives in Community-Access/accessibility-agents, which has 449 GitHub stars and 54 forks.
Related skills
A11y Core
449Community-Access/accessibility-agents
Shared contract for the Accessibility Agents skills - dispatch, findings schema, report rules. Read by skills, never dispatched on its own.
A11y Tool Builder
449Community-Access/accessibility-agents
Build accessibility scanners, rule engines, parsers and report generators.
Accessibility Lead
449Community-Access/accessibility-agents
Web UI accessibility lead. Use before writing or changing HTML, JSX, TSX, Vue, Svelte, CSS or templates. Picks specialists and merges their findings.
Nvda Addon Specialist
449Community-Access/accessibility-agents
NVDA add-ons: plugin types, manifest, events, scripts and packaging.
Markdown Scanner
449Community-Access/accessibility-agents
Internal helper: scan one markdown file across all nine domains.
Office Scan Config
449Community-Access/accessibility-agents
Internal helper: manage .a11y-office-config.json scan settings.
Browse the most popular Claude skills, all other skills, or write your own with the skills generator.