bs-accessibility

Generate WCAG/ARIA compliance checklists and actionable accessibility recommendations.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/MaxGiu67/plugin-MUCC --skill bs-accessibility
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bs-accessibility
Source: https://github.com/MaxGiu67/plugin-MUCC/tree/main/brainstorming/skills/bs-accessibility
Command: npx skills add https://github.com/MaxGiu67/plugin-MUCC --skill bs-accessibility

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Checklist accessibility WCAG/ARIA. Use this skill when the user wants to verify accessibility, or says bs accessibility, accessibility, WCAG, ARIA, a11y.

Core Features & Use Cases

  • Generates WCAG 2.1 AA checklist for MVP accessibility verification.
  • Specifies ARIA requirements for interactive components.
  • Performs keyboard navigation and color contrast tests.
  • Writes results to brainstorm/specialists/accessibility.md.

Quick Start

Run the accessibility workflow to generate the WCAG/ARIA checklist and recommendations.

Frequently Asked Questions about bs-accessibility

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

FAQPage Schema
How do I generate a WCAG compliance checklist for my digital product?

To generate a WCAG compliance checklist, the skill audits your digital product against WCAG 2.1 AA standards and outputs a structured checklist with actionable ARIA requirements and accessibility recommendations.

What ARIA requirements do interactive components need for accessibility?

ARIA requirements for interactive components depend on their specific UX flows, but generally include correct roles, states, and properties to ensure screen reader compatibility and keyboard navigation functionality.

Can I use this accessibility checklist for public sector deployments?

Yes, you can use this accessibility checklist for public sector deployments. It generates WCAG/ARIA compliance verification covering B2C contexts, UX flows, and keyboard navigation tests suitable for public sector projects.

What's the best way to verify keyboard navigation and color contrast in UX flows?

The best way to verify keyboard navigation and color contrast is to run a structured accessibility audit that performs specific keyboard tests and contrast checks across your UX flows, producing actionable compliance recommendations.

When do I need an accessibility verification workflow for my project?

You need an accessibility verification workflow when your project requires WCAG/ARIA compliance, particularly for B2C or public sector contexts where interactive components, UX flows, and keyboard navigation must meet accessibility standards.