skills.rest
dominika-zajac
dominika-zajacCOMMUNITY
Explore all skills by this author →
GitHub

accessibility-fix

Apply accessibility audit fixes to source files and re-verify with chrome-devtools-mcp.

Updated Apr 19, 2026
Search Tags:#automation#accessibility#frontend#audit#fix#wcag
One-click install
npx skills add https://github.com/dominika-zajac/better-frontend-skills --skill accessibility-fix
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility-fix
Source: https://github.com/dominika-zajac/better-frontend-skills/tree/main/skills/accessibility-fix
Command: npx skills add https://github.com/dominika-zajac/better-frontend-skills --skill accessibility-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill takes a completed accessibility audit report (produced by the accessibility-audit skill) and applies fixes directly to source code, then re-runs the audit to verify the results.

Core Features & Use Cases

  • Applies mechanical fixes (lang, viewport, reduced-motion, ARIA attributes) and contextual fixes (alt text, aria-labels, link copy) based on the audit findings.
  • Re-runs the accessibility audit to confirm that changes resolved the reported issues and to surface any new problems introduced during fixes.
  • Provides a structured fix log and verification steps to ensure traceability and repeatability across deployments.

Quick Start

After generating an audit report with accessibility-audit, run accessibility-fix to patch the code and re-run the audit to verify results.

Frequently Asked Questions about accessibility-fix

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I apply accessibility fixes to source code from a WCAG audit report?▼

To apply accessibility fixes from a WCAG audit report, the Skill patches mechanical issues like lang attributes and ARIA roles, then applies contextual fixes like alt text directly to your project source files.

Can I re-run an accessibility audit automatically after patching frontend code?▼

Yes, you can re-run an accessibility audit automatically after patching frontend code. The workflow re-verifies your repository against WCAG guidance to confirm changes resolved reported issues and surface any new problems.

What do I need to automate WCAG compliance fixes across my repository?▼

To automate WCAG compliance fixes you need a completed accessibility audit report, access to the project source code, and the chrome-devtools-mcp tool to verify DOM-tree adjustments and re-audit results.

Does the accessibility fix workflow require the chrome-devtools-mcp tool?▼

Yes, the accessibility fix workflow requires the chrome-devtools-mcp tool to perform desktop and mobile MCP-style audits and verify that applied source code changes pass WCAG re-verification.

What is the best way to ensure accessibility fixes do not introduce new WCAG violations?▼

The best way to ensure accessibility fixes do not introduce new WCAG violations is to re-run the audit immediately after patching to verify results and generate a structured fix log for traceability.

Related Skills

Explore More Software Engineering Skills→
dominika-zajacdominika-zajac

accessibility-audit

Run Lighthouse audits and custom heuristics to report WCAG accessibility issues.

Community
Advanced
sdcorejssdcorejs
2

sdcorejs-repair-loop

Verify, fix, and re-verify review findings until Critical and Important items resolve.

Community
Advanced
sluongngsluongng
6

chrome-devtools

Attach to a live Chrome session via the Chrome DevTools MCP server.

Community
Intermediate
lilbom32lilbom32

accessibility-review

Identify WCAG 2.1 AA compliance gaps in designs and frontend code.

Community
Advanced