signalproof-accessibility

Reviews interfaces for keyboard operation, focus, contrast, and screen-reader accessibility.

Updated Aug 15, 2026
One-click install
npx skills add https://github.com/docreo/Signalproof-Skills --skill signalproof-accessibility-docreo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: signalproof-accessibility
Source: https://github.com/docreo/Signalproof-Skills/tree/main/skills/signalproof-accessibility
Command: npx skills add https://github.com/docreo/Signalproof-Skills --skill signalproof-accessibility-docreo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Interface changes and UI reductions often silently break accessibility: controls become unreachable by keyboard, focus indicators disappear, status depends on color alone, or text clips at larger display scaling. This Skill provides a governed review contract that catches these regressions before they ship. ## Core Features & Use Cases - Structured Accessibility Review Pass: Systematically checks keyboard reachability, tab/focus order, focus visibility, semantic names/roles/states, contrast, zoom and scaling, pointer target size, form labels, captions, and reduced-motion support. - Explicit Status and STOP Conditions: Emits clear review outcomes (ACCESSIBILITY REVIEW PASS IN SCOPE, ACCESSIBILITY FINDING, REMEDIATION REQUIRED, BLOCKED, STOP) and halts when a design removes the only accessible interaction path or relies on color alone for consequential state. - Honest Scope Boundaries: Distinguishes an accessibility review from formal compliance certification, preventing scoped findings from being misrepresented as universal conformance claims. - Use Case: Before shipping a redesigned settings panel, run this review to verify every consequential control is keyboard-operable, focus order is logical, error states are not color-only, and content remains readable at 200% zoom. ## Quick Start Review this interface change for keyboard operability, focus visibility, contrast, screen-reader semantics, and reduced-motion support, then report findings and remediation steps.

Frequently Asked Questions about signalproof-accessibility

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

FAQPage Schema
How do I review a UI change for accessibility regressions?▼

Run a structured review pass covering keyboard reachability, tab and focus order, focus visibility, semantic labels, contrast, zoom and scaling, form labels, captions, and reduced motion. Test representative workflows end to end rather than isolated controls.

What should an accessibility review checklist include?▼

Include keyboard operability of consequential controls, visible focus and logical focus order, semantic names/roles/states for assistive technologies, non-color-only status indicators, sufficient contrast, scalable text without clipping, captions for media, and reduced-motion support.

Does an accessibility review certify WCAG compliance?▼

No. A scoped accessibility review produces findings and remediation evidence for the tested workflows, not formal compliance certification. Representing a limited review as universal accessibility or compliance certification is explicitly a STOP condition.

When should an accessibility review block a release?▼

Block when a design removes the only accessible interaction path, consequential state depends on color alone, or required information becomes unreadable at supported scaling. These are STOP conditions requiring remediation before proceeding.

Can accessibility testing cover only individual components?▼

Isolated control checks are insufficient. The review requires testing representative workflows so that focus order, status announcements, and equivalent access to consequential actions are verified in realistic usage context.