Skip to content
Back to skills

Evaluate

ASecurity

Run accessibility checks and discover issues mapped to WCAG criteria

  • 2 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added October 17, 2026
ai-agents

Security analysis

A100/100

Scanned October 17, 2026

npx -y skills add bromso/metapowers --skill evaluate --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Evaluate?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Evaluate
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/bromso-evaluate/badge)](https://www.skillsdirectory.com/skills/bromso-evaluate)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
description: Run accessibility checks and discover issues mapped to WCAG criteria
---

# Evaluate

Evaluate "$ARGUMENTS" for accessibility issues. Run automated and manual checks, discover barriers, and map each issue to specific WCAG success criteria.

## Prerequisites

Read `.metapowers/accessibility/$ARGUMENTS/01-scope.md`. If this file does not exist, tell the user:

> Phase 1 (Scope) has not been completed for "$ARGUMENTS". Run `/accessibility:scope $ARGUMENTS` first, or use `--skip-checks` to bypass.

If `--skip-checks` is present in $ARGUMENTS, skip this check and log to `.metapowers/accessibility/$ARGUMENTS/skip-log.md`.

## Process

1. **Read context files:**
   - Read `.metapowers/accessibility/$ARGUMENTS/01-scope.md` for audit scope and target pages
   - Read `plugins/accessibility/shared/wcag-21-aa-criteria.md` for the full criteria reference

2. **Automated evaluation:**
   - Read the source code of the target pages/components
   - Check for: missing alt text, missing form labels, heading hierarchy violations, missing ARIA attributes, color contrast issues, missing lang attribute, keyboard trap risks

3. **Manual evaluation:**
   - Trace keyboard navigation flow — can all interactive elements be reached and operated?
   - Check focus visibility — is focus indicator visible on every interactive element?
   - Check reading order — does DOM order match visual order?
   - Check form error handling — are errors identified and described in text?
   - Check dynamic content — are updates announced via ARIA live regions?

4. **Map each issue to WCAG criteria:**
   - For each issue found, identify the specific WCAG success criterion violated
   - Classify severity: Critical (blocks access), Major (significant barrier), Minor (inconvenience)
   - Note the location (file, line, component)

5. **Write the artifact** to `.metapowers/accessibility/$ARGUMENTS/02-evaluate.md` with sections:
   - **Issues Found** — each issue with WCAG mapping, severity, location
   - **Conformance Status** — per-principle pass/fail summary
   - **Critical Barriers** — issues that completely block access
   - **Positive Findings** — what's already working well

## Output

The evaluation results written to `.metapowers/accessibility/$ARGUMENTS/02-evaluate.md`. Present a summary to the user highlighting:
- Total issues found by severity
- Critical barriers requiring immediate attention
- WCAG principles with most violations

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.