com um clique
accessibility-audit-report
Write structured accessibility audit reports with findings mapped to WCAG criteria, severity levels, affected components, remediation steps, and a prioritized fix timeline.
Menu
Write structured accessibility audit reports with findings mapped to WCAG criteria, severity levels, affected components, remediation steps, and a prioritized fix timeline.
Write effective prompts for AI coding tools — structure task context, specify constraints, provide examples, and iterate based on output quality. Targets developers using Claude Code, Copilot, Cursor, and similar tools.
Design RESTful and GraphQL APIs with consistent naming conventions, versioning strategy, pagination patterns, error response formats, authentication schemes, and rate limiting — producing a complete API specification.
Create REST and GraphQL integration guides covering authentication flows, pagination strategies, rate limiting, error handling, retry logic, and SDK wrapper patterns. Produces implementation-ready reference documents with code examples.
Write Architecture Decision Records (ADRs) that capture context, options considered, decision rationale, and consequences — creating a searchable decision log for future engineers.
Design and document automation workflows for n8n, Make, Zapier, and Power Automate. Covers trigger-action chain mapping, conditional branching, error handling, retry logic, and workflow diagrams with platform-specific node references.
Design BI reports and analytics views — with metric definitions, data source mapping, filter logic, drill-down paths, and refresh schedules that enable self-service decision-making.
| name | accessibility-audit-report |
| description | Write structured accessibility audit reports with findings mapped to WCAG criteria, severity levels, affected components, remediation steps, and a prioritized fix timeline. |
| metadata | {"displayName":"Accessibility Audit Report","categories":["design","engineering"],"tags":["accessibility","a11y","WCAG","audit-report","remediation","compliance"],"worksWellWithAgents":["accessibility-auditor","code-reviewer","ux-researcher"],"worksWellWithSkills":["component-design-spec","ticket-writing"]} |
Gather the following from the user. If anything is missing, ask before proceeding:
If the user says "just audit everything," push back: "Which user flows are highest traffic or highest risk? Start there — a focused audit produces actionable results, a broad audit produces a backlog nobody reads."
3-5 sentences. State the overall conformance status, the number of issues found by severity, and the single most critical finding. This section is for stakeholders who will not read the full report.
This audit evaluated 12 screens across the checkout flow against WCAG 2.1 AA.
We identified 23 issues: 4 critical, 7 major, 9 minor, and 3 best-practice
recommendations. The most critical finding is that the payment form is entirely
inaccessible to keyboard-only users, blocking approximately 8% of users from
completing purchases.
List what was tested, what was not, and how. Be explicit about tools and versions.
Tested: /cart, /checkout/shipping, /checkout/payment, /checkout/confirmation
Not tested: Account settings, admin dashboard
Methods: axe-core 4.9, NVDA 2024.1 + Chrome, VoiceOver + Safari, manual
keyboard navigation, color contrast analyzer
Provide a scannable table. Every issue in the report must appear here.
| # | Issue | WCAG Criterion | Severity | Component/Page |
|---|---|---|---|---|
| 1 | Payment form not keyboard accessible | 2.1.1 Keyboard | Critical | /checkout/payment |
| 2 | Images missing alt text | 1.1.1 Non-text Content | Major | /cart |
| 3 | Insufficient color contrast on helper text | 1.4.3 Contrast (Minimum) | Minor | Global |
Write one section per issue. Every finding must include all six fields below — no exceptions.
<!-- Before (inaccessible) -->
<div onclick="submit()">Pay Now</div>
<!-- After (accessible) -->
<button type="submit">Pay Now</button>
Severity definitions:
| Severity | Meaning |
|---|---|
| Critical | Blocks a user group from completing a core task. Fix immediately. |
| Major | Causes significant difficulty but a workaround exists. Fix within current sprint. |
| Minor | Causes inconvenience but does not block functionality. Fix within the quarter. |
| Best Practice | Not a WCAG violation but improves the experience. Schedule as capacity allows. |
Group findings by effort and impact to help the team sequence work.
| Low Effort | High Effort | |
|---|---|---|
| High Impact | Fix first (e.g., missing alt text, missing labels) | Plan next (e.g., rebuild inaccessible custom widget) |
| Low Impact | Quick wins (e.g., skip-to-content link) | Backlog (e.g., ARIA live region for non-critical notifications) |
Map findings to concrete timeframes tied to severity.
Week 1-2: All Critical findings (#1, #4)
Week 3-4: All Major findings (#2, #5, #7, #8, #10, #11, #12)
Week 5-8: Minor findings, prioritized by the matrix above
Ongoing: Best-practice recommendations integrated into component library
Include a note on regression prevention: "Add axe-core to CI. Every new component must pass automated a11y checks before merge."
Before delivering the report, verify:
aria-label="Close dialog" to the <button> element at .modal-close" is.