Overview
This prompt aims to create a detailed web accessibility checklist based on WCAG standards. Web developers and accessibility specialists will benefit by ensuring their websites are inclusive and compliant.
Prompt Overview
Purpose: This checklist aims to ensure web accessibility compliance with WCAG standards for an inclusive user experience.
Audience: It is designed for web developers, designers, and content creators seeking to improve website accessibility.
Distinctive Feature: The checklist categorizes criteria with severity levels and recommended fixes for easy documentation and resolution.
Outcome: Following this checklist will enhance website accessibility, benefiting all users, including those with disabilities.
Quick Specs
- Media: Text
- Use case: Web accessibility auditing
- Techniques: Checklist creation, Issue documentation
- Models: WCAG
- Estimated time: 1-2 hours
- Skill level: Intermediate
Variables to Fill
- [Describe issue] – Describe Issue
- [Explain fix] – Explain Fix
- [WEBSITE URL] – Website Url
Example Variables Block
- [Describe issue]: Images lack alternative text
- [Explain fix]: Add descriptive alt text to images
- [WEBSITE URL]: https://example.com
The Prompt
#CONTEXT:
Adopt the role of an expert web accessibility specialist with extensive knowledge of WCAG standards and best practices for creating accessible, inclusive websites. Your task is to assist the user in developing a comprehensive checklist for auditing a specified website URL for compliance with the latest WCAG guidelines.
#ROLE:
You are an expert web accessibility specialist with extensive knowledge of WCAG standards and best practices for creating accessible, inclusive websites.
#RESPONSE GUIDELINES:
Break down the checklist into the following key categories:
- Perceivable
- Operable
- Understandable
- Robust
- Testing with Assistive Technologies
Under each category, highlight specific criteria to evaluate. Provide a user-friendly format for documenting issues found, including severity levels (High, Medium, Low) and recommended fixes.
Use the following format for each criterion:
- [] Criterion description
- Issue Found: [Describe issue]
- Severity: High | Medium | Low
- Recommended Fix: [Explain fix]
#TASK CRITERIA:
- The checklist must be comprehensive, covering all key aspects of web accessibility as per the latest WCAG guidelines.
- Focus on providing a clear, user-friendly format for documenting issues, severity levels, and recommended fixes.
- Avoid jargon or technical terms that may be difficult for non-experts to understand.
- Prioritize the most critical accessibility issues, ensuring they are prominently highlighted in the checklist.
#INFORMATION ABOUT ME:
- Website URL: [WEBSITE URL]
#RESPONSE FORMAT:
Web Accessibility Compliance Checklist for [WEBSITE URL]
Perceivable
- [] Criterion 1
- Issue Found: [Describe issue]
- Severity: High | Medium | Low
- Recommended Fix: [Explain fix]
- [] Criterion 2
- [] Criterion 3
…
Operable
- [] Criterion 1
- [] Criterion 2
…
Understandable
- [] Criterion 1
- [] Criterion 2
…
Robust
- [] Criterion 1
- [] Criterion 2
…
Testing with Assistive Technologies
- [] Criterion 1
- [] Criterion 2
…
Screenshot Examples
[Insert relevant screenshots after testing]
How to Use This Prompt
- [PERCEIVABLE]: Accessibility of content presentation.
- [OPERABLE]: Functionality and navigation accessibility.
- [UNDERSTANDABLE]: Clarity of content and instructions.
- [ROBUST]: Compatibility with current and future technologies.
- [ASSISTIVE_TECHNOLOGIES]: Testing with screen readers and tools.
- [SEVERITY]: Classification of issues by impact level.
- [RECOMMENDED_FIX]: Suggested solutions for identified issues.
- [WCAG_GUIDELINES]: Standards for web accessibility compliance.
Tips for Best Results
- Text Alternatives: Ensure all non-text content has text alternatives that serve the same purpose.
- Keyboard Navigation: Verify that all interactive elements are accessible via keyboard alone.
- Consistent Navigation: Maintain consistent navigation and identification across pages to aid user orientation.
- Live Region Updates: Use ARIA live regions to announce dynamic content changes to assistive technologies.
FAQ
- What is the purpose of the Perceivable category?
It ensures that all content is accessible to all users, including those with disabilities. - How can I evaluate Operable criteria?
Check if all interactive elements are keyboard accessible and provide sufficient time for user actions. - What does Understandable mean in web accessibility?
Content must be clear and consistent, allowing users to easily navigate and comprehend information. - Why is Robust important for web accessibility?
It ensures content works across various platforms and technologies, including assistive devices.
Compliance and Best Practices
- Best Practice: Review AI output for accuracy and relevance before use.
- Privacy: Avoid sharing personal, financial, or confidential data in prompts.
- Platform Policy: Your use of AI tools must comply with their terms and your local laws.
Revision History
- Version 1.0 (December 2025): Initial release.