Accessibility
Comprehensive Accessibility Audit & Remediation Plan Generator
Generate detailed accessibility audit reports and actionable remediation plans that ensure WCAG compliance for digital products. This prompt helps accessibility professionals, web developers, and digital teams identify barriers, prioritize fixes, and create roadmaps for inclusive user experiences.
6 blanks to fill in · Added December 2025 · accessibility · WCAG · compliance · remediation · audit
The prompt
6 blanksYou are an expert accessibility auditor with deep knowledge of WCAG 2.1 standards, ADA compliance, and inclusive design principles. Your task is to create a comprehensive accessibility audit report and remediation plan for [DIGITAL PRODUCT TYPE - e.g., website, mobile app, web application]. Product Information: - Product Name: [PRODUCT NAME] - URL/Platform: [PRODUCT URL OR PLATFORM] - Target Conformance Level: [WCAG LEVEL - A, AA, or AAA] - Industry/Sector: [INDUSTRY OR SECTOR] - Primary User Base: [TARGET AUDIENCE DESCRIPTION] Audit Scope: [DESCRIBE WHICH PAGES, FEATURES, OR COMPONENTS TO AUDIT] Generate a detailed audit report and remediation plan that includes: 1. Executive Summary - Overall accessibility score and conformance level - Critical findings count and severity distribution - Estimated impact on users with disabilities - Legal and business risk assessment 2. Audit Methodology - Automated testing tools used - Manual evaluation approach - Assistive technologies tested (screen readers, keyboard navigation, etc.) - User testing conducted (if applicable) 3. Detailed Findings For each accessibility issue identified, provide: - WCAG success criterion violated (with number and level) - Severity level (Critical/High/Medium/Low) - Location/component affected - Current behavior vs. expected behavior - User impact description - Screenshot or code example (where applicable) 4. Prioritized Remediation Roadmap Organize fixes into phases: - Phase 1 (0-30 days): Critical and high-severity issues - Phase 2 (31-90 days): Medium-severity issues and process improvements - Phase 3 (91-180 days): Low-severity issues and optimization For each phase, include: - Specific issues to address - Responsible teams/roles - Estimated effort and resources - Success metrics 5. Implementation Guidelines - Detailed remediation steps for each issue category - Code examples and best practices - Recommended tools and resources - Testing and validation procedures 6. Long-term Accessibility Strategy - Integration of accessibility into development workflow - Training recommendations for teams - Ongoing testing and monitoring plan - Accessibility documentation and governance - User feedback mechanisms Format the output as a professional audit document with clear sections, actionable recommendations, and specific technical guidance that development teams can immediately implement.
Blanks: Product name · Product url or platform · Wcag level a, aa, or aaa · Industry or sector · Target audience description · Describe which pages, features, or components to audit
Fill in the blanks
How to use it
This prompt is designed for accessibility professionals, UX designers, developers, and digital teams conducting WCAG compliance audits. Fill in the bracketed placeholders with specific information about your digital product, including the target conformance level (typically WCAG 2.1 Level AA), scope of audit, and any known accessibility concerns. The prompt generates both diagnostic insights and actionable remediation plans.
Tips
- Start with automated testing tools like WAVE, Axe DevTools, or Lighthouse to quickly identify common issues, but always follow up with manual testing as automated tools miss 65-75% of accessibility barriers
- Prioritize issues based on user impact rather than just technical severity—a minor code violation affecting checkout flow may be more critical than a major violation on a rarely-visited page
- Include specific code examples and before/after comparisons in your remediation guidance to help developers understand exactly what needs to change
- Engage users with disabilities for usability testing when possible—their firsthand feedback reveals real-world barriers that technical audits may miss
- Set realistic remediation timelines based on your team's capacity and prioritize quick wins that demonstrate progress while tackling complex issues systematically
- Document all accessibility decisions, workarounds, and exceptions to create institutional knowledge and prevent regression in future releases
Information Gathering
Before using this prompt, gather essential information about your digital product. Identify the specific pages, features, or user flows that require auditing. Document your target conformance level based on legal requirements or organizational standards. Note any previous accessibility testing results, known issues, or user complaints. If possible, include information about your primary user demographics and any assistive technologies they commonly use. Understanding your development workflow and team structure will help generate more realistic remediation timelines.
Output Framework
The generated audit report follows industry-standard accessibility documentation practices aligned with WCAG 2.1 guidelines. The executive summary provides stakeholder-friendly insights, while detailed findings offer technical depth for developers. The prioritized remediation roadmap organizes fixes by severity and user impact, ensuring critical barriers are addressed first. Implementation guidelines include specific code examples and testing procedures. The long-term strategy section helps embed accessibility into organizational processes, preventing future compliance gaps.
Context and Considerations
Accessibility audits should combine automated testing tools with manual evaluation and user testing for comprehensive coverage. Automated tools typically catch 25-35% of accessibility issues, making human expertise essential. Consider your organization's resources, technical capabilities, and legal obligations when setting remediation timelines. Different industries may have specific compliance requirements beyond WCAG. Factor in the complexity of your technology stack and any third-party components that may require vendor collaboration for full remediation.
Compliance Standards
WCAG 2.1 Level AA is the most widely adopted standard and satisfies most legal requirements including ADA, Section 508, and international accessibility laws. Level A addresses the most basic barriers that completely prevent access. Level AAA represents enhanced accessibility but may not be feasible for all content types. Focus on the four POUR principles: Perceivable, Operable, Understandable, and Robust. Ensure your audit addresses keyboard navigation, screen reader compatibility, color contrast, form accessibility, and error handling as these are common sources of compliance failures.