audit

Audit interfaces for multi-modal accessibility blockers and produce a structured report.

3|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/hulusi-tunc/unicorn-skills --skill audit-hulusi-tunc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: audit
Source: https://github.com/hulusi-tunc/unicorn-skills/tree/main/.claude/skills/inclusive-interaction--audit
Command: npx skills add https://github.com/hulusi-tunc/unicorn-skills --skill audit-hulusi-tunc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits interfaces to ensure inclusive multi-modal accessibility across keyboard navigation, touch targets, multi-modal input, gesture alternatives, feedback mechanisms, and motion-sensitivity.

Core Features & Use Cases

  • Phase-based assessment covering keyboard, touch, input methods, feedback, and motion considerations.
  • Output a structured report with a severity matrix, issue list, and prioritized fixes.
  • Use cases include evaluating web, mobile, or desktop interfaces during design reviews or QA sprints.

Quick Start

Run the Inclusive Interaction Audit on the target interface to evaluate multi-modal accessibility.

Frequently Asked Questions about audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit my interface for keyboard navigation and touch target accessibility?▼

To audit keyboard navigation and touch target accessibility, run a phase-based assessment on the target interface. This identifies blockers across form controls and navigation order, producing a structured report with a severity matrix and prioritized fixes.

What is multi-modal accessibility and how does gesture alternative evaluation work?▼

Multi-modal accessibility ensures interfaces support diverse input methods like gestures and keyboards. Evaluating gesture alternatives involves checking if motion-based actions have accessible fallbacks, documenting issues in a structured report with prioritized fixes.

Can I use this accessibility audit for mobile and desktop interfaces during a QA sprint?▼

Yes, this accessibility audit applies to web, mobile, or desktop interfaces undergoing design reviews or QA sprints. It evaluates multi-modal input, feedback mechanisms, and motion-sensitivity across any existing interface to produce a structured severity report.

How do I check if my interface supports reduced-motion preferences and screen reader announcements?▼

Checking reduced-motion preferences and screen reader announcements involves assessing feedback mechanisms and motion considerations. The audit enforces support for these accessibility requirements, documenting failures in a structured issue list with prioritized fixes.

What is the best way to document multi-modal accessibility blockers across an existing interface?▼

The best way to document multi-modal accessibility blockers is through a structured assessment process covering keyboard, touch, input methods, feedback, and motion. This produces a severity matrix, issue list, and prioritized fixes for the target interface.

Does the audit evaluate form controls and navigation order for screen reader compatibility?▼

Yes, the audit evaluates form controls and navigation order with emphasis on screen reader announcements. It identifies accessibility blockers across these elements and outputs a structured report containing a severity matrix and prioritized fixes.