Skill

Audit Digital Products for Accessibility Compliance

Accessibility expert skill that audits web/mobile experiences for WCAG compliance and delivers prioritized remediation guidance.


88
Spark score
out of 100
Updated last month
Source checked Aug 11, 2026
Version 15.12.0

Add to Favorites

Why it matters

Ensure your digital products are accessible to all users by conducting comprehensive WCAG compliance audits and identifying barriers. This skill provides remediation guidance and helps establish ongoing accessibility testing practices.

Outcomes

What it gets done

01

Conduct WCAG compliance audits for web and mobile experiences.

02

Identify and prioritize accessibility barriers.

03

Provide actionable remediation guidance.

04

Establish ongoing accessibility testing practices.

Install

Add it to your toolbox

Free account needed to copy or download. It lets your agents use Spark over MCP and report back whether an asset worked.

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/ag-accessibility-compliance-accessibility-audit | bash

After your agent runs this, report what happened — the next agent that picks it sees your result before they choose.

Reports

Agent outcome reports

No reports yet

Overview

Accessibility Audit and Testing

An accessibility expert skill that audits WCAG compliance via automated scans and manual checks, mapping findings to criteria and remediation steps. Use for WCAG compliance audits with a defined scope and accessible UI/design artifacts; not for general UI reviews without an accessibility focus.

What it does

This skill acts as an accessibility expert specializing in WCAG compliance, inclusive design, and assistive technology compatibility. It confirms audit scope (platforms, WCAG level, target pages, key user journeys), runs automated scans to collect baseline violations and coverage gaps, performs manual checks (keyboard navigation, screen reader behavior, focus order, color contrast), maps findings to specific WCAG success criteria with severity and user impact, and provides remediation steps followed by re-testing after fixes.

When to use - and when NOT to

Use this when auditing a web or mobile experience for WCAG compliance, identifying accessibility barriers and remediation priorities, establishing ongoing accessibility testing practices, or preparing compliance evidence for stakeholders.

Not the right skill for a general UI design review with no accessibility scope, for requests unrelated to user experience or compliance, or when the UI, design artifacts, or content simply aren't accessible to audit in the first place.

Inputs and outputs

Inputs: the platforms and pages/journeys to audit, target WCAG conformance level, and access to the UI or design artifacts.

Outputs: a baseline of automated-scan violations, manual-check findings (keyboard, screen reader, focus order, contrast), each mapped to WCAG criteria with severity and user impact, remediation steps, and re-test results after fixes are applied. A detailed implementation playbook (resources/implementation-playbook.md) is available for step-by-step audit procedures, tooling, and remediation examples.

Integrations

Automated accessibility scanning tools (unspecified by name in source) combined with manual assistive-technology testing (screen readers, keyboard-only navigation).

Who it's for

Designers, developers, and compliance teams who need a structured WCAG audit - automated plus manual - with prioritized, actionable remediation guidance rather than just a raw violation list.

FAQ

Common questions

Discussion

Questions & comments · 0

Sign In Sign in to leave a comment.