agentleFS
Sign inStart free
ManojDevHub1ManojDevHub1/visual-engineering-suite/skills/accessibility-performance-audit/SKILL.md

accessibility-performance-audit

Skill1 starsChanged 26 days agoMITView on GitHub

Inspect semantic markup, keyboard accessibility, visible focus states, accessible names, color contrast, and responsive reflow, and audit frontend implementations for WCAG 2.1 AA compliance and visual performance.

The file

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 8 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill to audit frontend implementations for WCAG 2.1 AA accessibility compliance, keyboard navigability, responsive reflow …

    line 9
  2. Very specific:

    Markup Inspection: Run audit-markup.js to catch missing alt attributes, unlabelled buttons, and removed focus outlines.

    line 13
  3. Distinctive:

    WCAG 2.1 AA Verification: Check contrast ratios (≥4.5:1 for normal text, ≥3:1 for graphical objects) using the WCAG Checklist.

    line 14
  4. Distinctive:

    Verify normal body copy achieves at least 4.5:1 against surface background.

    line 34
  5. Distinctive:

    Verify large headers (≥24px) achieve at least 3:1.

    line 35
  6. Distinctive:

    Verify borders of input controls and active button outlines meet 3:1 contrast against adjacent background.

    line 36
  7. Very specific:

    Ensure all interactive links and buttons can be focused via Tab key.

    line 39
  8. Very specific:

    Verify focus indicators are distinct and clearly visible (focus-visible:ring-2 focus-visible:ring-offset-2).

    line 40
  9. Distinctive:

    Verify dropdowns or modals trap and release focus properly.

    line 41
  10. Distinctive:

    Ensure no horizontal scrolling or clipped button text.

    line 45
  11. Distinctive:

    Verify touch targets are at least 44x44px.

    line 46

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Accessibility & Performance Audit Skill

Use this skill to audit frontend implementations for WCAG 2.1 AA accessibility compliance, keyboard navigability, responsive reflow integrity, and visual performance.

Core Responsibilities

  1. Markup Inspection: Run audit-markup.js to catch missing alt attributes, unlabelled buttons, and removed focus outlines.
  2. WCAG 2.1 AA Verification: Check contrast ratios (≥4.5:1 for normal text, ≥3:1 for graphical objects) using the WCAG Checklist.
  3. Reflow & Overflow Checks: Identify responsive failure modes down to 320px viewports using the Responsive Reflow Guide.
  4. Actionable Remediation: Provide prioritized, line-level code fixes.

Step-by-Step Procedure

1. Run Automated Markup Accessibility Audit

Scan component files for syntax-level accessibility violations:

node skills/accessibility-performance-audit/scripts/audit-markup.js <path-to-component-or-directory>

Review flagged items:

  • Missing image alt attributes.
  • Icon buttons missing aria-label.
  • outline: none without accessible focus ring.
  • Fixed pixel widths causing mobile overflow.

2. Verify Color Contrast Ratios

  • Verify normal body copy achieves at least 4.5:1 against surface background.
  • Verify large headers (≥24px) achieve at least 3:1.
  • Verify borders of input controls and active button outlines meet 3:1 contrast against adjacent background.

3. Verify Keyboard Navigability & Focus Indicators

  • Ensure all interactive links and buttons can be focused via Tab key.
  • Verify focus indicators are distinct and clearly visible (focus-visible:ring-2 focus-visible:ring-offset-2).
  • Verify dropdowns or modals trap and release focus properly.

4. Verify Responsive Reflow (320px–1440px)

  • Render or inspect page at 320px and 390px widths.
  • Ensure no horizontal scrolling or clipped button text.
  • Verify touch targets are at least 44x44px.

5. Final Report Synthesis

Combine findings into an engineering report with exact remediation code blocks.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free