domains / families / design / accessibility-compliance-accessibility-audit

accessibility-compliance-accessibility-audit

combined

You are an accessibility expert specializing in WCAG compliance, inclusive design, and assistive technology compatibility. Conduct audits, identify barriers, and provide remediation guidance. Audit pages and user journeys against a declared WCAG scope. Use when identifying keyboard, screen-reader, focus or contrast barriers and planning verified remediation.

When to use

• Auditing web or mobile experiences for WCAG compliance
• Identifying accessibility barriers and remediation priorities
• Establishing ongoing accessibility testing practices
• Preparing compliance evidence for stakeholders

When not to use

• You only need a general UI design review without accessibility scope
• The request is unrelated to user experience or compliance
• You cannot access the UI, design artifacts, or content
• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Conflict

The two copies share the same core audit procedure (scope, automated scan, manual checks, mapping, remediation, re-test) and the same resource pointer. However, the sickn33 copy adds material constraints and an example that the rmyndharis copy lacks: it explicitly states that automated scans alone do not establish conformance, requires keeping untested journeys and incomplete checks visible, treats missing scope or UI access as an explicit limitation rather than a passing audit, and includes a concrete example of a checkout audit. The rmyndharis copy is a shorter, more generic version that omits these guardrails. Crowning one would hide the stricter, more complete procedure in the other.