audit-method

Audits web interfaces for WCAG 2.2 accessibility, performance, and responsive defects with measured evidence.

Updated Aug 12, 2026
One-click install
npx skills add https://github.com/brunoolf/frontend-craft --skill audit-method-brunoolf
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: audit-method
Source: https://github.com/brunoolf/frontend-craft/tree/main/skills/audit-method
Command: npx skills add https://github.com/brunoolf/frontend-craft --skill audit-method-brunoolf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Web interfaces ship with accessibility barriers, performance regressions, and responsive layout defects that are hard to catch without a systematic checklist. This Skill produces verifiable, read-only audit findings with measured evidence instead of vague opinions, so teams know exactly what is broken, where, and how severe it is. ## Core Features & Use Cases - WCAG 2.2 Accessibility Audit: Checks contrast ratios, keyboard navigation, focus indicators, semantic HTML, touch targets, form error handling, and reduced-motion support against numbered success criteria. - Performance Diagnosis: Hunts CLS causes, LCP blockers, bundle bloat, layout-thrashing animations, oversized images, and React re-render patterns. - Responsive Verification: Tests real content at 360px, 768px, 1280px, and wide viewports for horizontal overflow, collapsed touch targets, and iOS viewport bugs like 100vh versus 100dvh. - Searchable Patterns: Provides ready-made regex patterns (e.g., outline-none, <div onClick, tabIndex positive values) to locate candidate defects, each verified before reporting. - Use Case: Before publishing a landing page, run the audit to receive a severity-ranked list of findings like [Bloqueante] header.tsx:42 — WCAG 2.2 SC 1.4.3 — contraste 3.1:1, mínimo 4.5:1, each routed to the agent responsible for fixing it. ## Quick Start Audit this page for accessibility, performance, and responsive issues and report findings with measured evidence and severity.

Frequently Asked Questions about audit-method

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

FAQPage Schema
How do I audit a web page for WCAG 2.2 accessibility?▼

Check contrast ratios (4.5:1 for body text, 3:1 for large text and UI components), keyboard reachability and visible focus indicators, semantic headings and landmarks, labeled form fields, meaningful alt text, and touch targets of at least 24x24 CSS pixels. Report each failure with the measured value and the specific success criterion.

How to find performance problems causing layout shift and slow loading?▼

Look for images without width/height or aspect-ratio, fonts without font-display, content injected above the fold, and missing priority hints on the LCP element. Also check for oversized images served at display size, non-tree-shaken imports, and animations that trigger layout.

What regex patterns detect common accessibility bugs in code?▼

Useful searches include outline-none for removed focus indicators, <div onClick for non-semantic interactivity, positive tabIndex values, img tags missing alt attributes, and 100vh or h-screen which break on iOS Safari. Each match is a candidate that must be verified before reporting.

Does this audit fix the issues it finds?▼

No. The audit is strictly read-only and produces findings with severity, evidence, and a suggested correction. Each finding is routed to the appropriate writing agent such as fc-implementer, fc-design-system, or fc-motion-engineer for the actual fix.

Why does my layout break on mobile Safari with 100vh?▼

The 100vh unit includes the browser chrome on iOS, so full-height sections jump or overflow as the toolbar hides and shows. Use 100dvh instead, which tracks the dynamic viewport height and stays stable during scrolling.