include

Plan WCAG 2.2-aligned accessibility audits and remediation for web interfaces.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/snuffomega/pricechart --skill include-snuffomega
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: include
Source: https://github.com/snuffomega/pricechart/tree/main/.agents/skills/include
Command: npx skills add https://github.com/snuffomega/pricechart --skill include-snuffomega

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Accessibility gaps that exclude people who use screen readers, keyboard navigation, assistive tech, or who experience cognitive, motor, or situational impairment.

Core Features & Use Cases

  • WCAG 2.2 guidance for designers: Practical design rules for perceivable, operable, understandable, and robust experiences (contrast, labels, reflow, semantics, ARIA misuse avoidance).
  • Screen reader & keyboard experience design: Reading order, landmarks, heading hierarchy, live regions, focus management, and keyboard interaction patterns.
  • Accessibility testing methodology and remediation planning: Automated vs manual testing, and a structured remediation approach (P0–P3) to make audits actionable.
  • Use cases: Accessibility audits, inclusive design reviews, WCAG compliance checks, form and navigation design, and “is this accessible?” guidance for product UX.

Quick Start

Use the include skill to turn an accessibility concern in a design or UI into a clear, testable audit and remediation plan for all users, including screen reader and keyboard users.

Frequently Asked Questions about include

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

FAQPage Schema
How do I conduct a WCAG 2.2 accessibility audit for a web interface?

Conduct a WCAG 2.2 accessibility audit by applying perceivable, operable, understandable, and robust criteria to identify UX barriers. The process includes automated and manual testing to produce actionable findings with prioritized remediation steps.

What is focus management and keyboard navigation mapping in inclusive design?

Focus management and keyboard navigation mapping define reading order, landmarks, heading hierarchy, and interaction patterns. This inclusive design methodology ensures screen reader and keyboard users can operate web interfaces without encountering barriers.

How do I plan accessibility remediation for screen reader and keyboard barriers?

Plan accessibility remediation by structuring audit findings into a P0–P3 priority framework. This approach categorizes barriers by severity to guide teams in systematically fixing screen reader flow, keyboard navigation, and semantic issues.

Does inclusive design review cover ARIA misuse avoidance and contrast guidelines?

Inclusive design review covers ARIA misuse avoidance and contrast guidelines by applying practical WCAG 2.2 design rules. It evaluates labels, reflow, semantics, and contrast to ensure interfaces are perceivable and operable for users with disabilities.

What is the best way to document screen reader flow for product UX?

Document screen reader flow by mapping reading order, live regions, landmarks, and heading hierarchy within the product UX. This methodology creates explicit testing steps and assistive-tech considerations for evaluating user experiences.