Accessibility Auditor

CategoryCoding
Authorrajudandigam
LicenseMIT
Rating4.40/5
Uses13.5K

What it does

Audit your web interfaces for inclusivity and legal compliance. This skill analyzes your site's structure against WCAG 2.2 and Section 508 standards to ensure users with visual, motor, or cognitive impairments can navigate your product seamlessly. Instead of just flagging errors, it identifies specific failures in keyboard trapping, ARIA labeling, and color contrast ratios, providing the technical "why" behind each issue. It is particularly useful during the QA phase of a sprint or before a public launch to reduce accessibility debt and avoid potential legal compliance risks.

Use cases

  • Pre-deployment QA: Scanning a new landing page to ensure all interactive elements are reachable via keyboard before merging to production.
  • Compliance Gap Analysis: Checking an existing enterprise dashboard against Section 508 requirements to identify missing alt-text or improper heading hierarchies.
  • UI/UX Review: Validating that a new color palette meets AA or AAA contrast ratios for readability across different screen brightness levels.
  • Screen Reader Optimization: Verifying that complex components (like modals or accordions) communicate their state correctly to assistive technologies.

How to use

Provide the URL of the page you want audited. If you have specific components you're worried about (e.g., a complex data table), mention them alongside the link for a deeper dive.
markdown
I want you to act as an Accessibility Auditor who is a web accessibility expert and experienced accessibility engineer. I will provide you with the website link. I would like you to review and check compliance with WCAG 2.2 and Section 508. Focus on keyboard navigation, screen reader compatibility, and color contrast issues. Please write explanations behind the feedback and provide actionable suggestions.

Tips

  • Provide HTML snippets: If the AI cannot access a page due to a login wall or firewall, paste the relevant HTML/CSS code for a more accurate manual audit.
  • Specify the Target Level: Tell the AI if you are aiming for WCAG Level A, AA, or AAA to get feedback tailored to your specific compliance goal.
  • Request Code Fixes: Ask the AI to provide the exact ARIA attributes or CSS changes needed to resolve the flagged issues.
  • Test specific flows: Instead of just a link, describe a user journey (e.g., "Check the checkout flow from cart to payment") to find sequential navigation errors.

Notes

  • Static Analysis Limitation: AI cannot "feel" the physical experience of a screen reader; always verify its suggestions with actual tools like NVDA, VoiceOver, or AXE DevTools.
  • Dynamic Content: Content rendered via complex JavaScript after page load may occasionally be missed if the AI's crawler cannot execute the script.
Join our Telegram