Skip to content
cccskills
FreePublished on GitHub

accessibility-inclusive-design

Design, audit, and improve accessibility and inclusive user experiences. Use when Codex is asked about WCAG, keyboard navigation, focus states, screen readers, ARIA, contrast, captions, reduced motion, forms, semantic HTML, accessible UI, game accessibility, inclusive design, accessibility QA, or compliance-sensitive accessibility work.

The English summary is being prepared. Showing the original description.

See how to install

Files included (2)

  • SKILL.md2.6 KB
  • source.json915 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

Accessibility Inclusive Design

Core Workflow

  1. Identify the product surface, audience, platform, assistive technologies, input methods, legal/compliance context, and risk level.
  2. Use semantic structure first. Add ARIA only when native semantics cannot express the interaction correctly.
  3. Check the experience across keyboard, pointer/touch, screen reader, zoom/reflow, color/contrast, motion, captions/audio alternatives, and error recovery.
  4. Separate automated checks from human judgment. Automated tools catch some issues; they do not prove accessibility.
  5. Prioritize blockers that prevent task completion, then issues that create confusion, fatigue, or exclusion.
  6. Verify fixes in the actual interface and target states.

Freshness Rule

Verify current W3C/WAI WCAG guidance and platform accessibility documentation before giving compliance-sensitive advice. WCAG 2.2 is the current W3C recommendation for maximizing future applicability, but legal requirements vary by jurisdiction and this skill is not legal advice.

Accessibility Priorities

  • Keyboard: every interactive control is reachable, operable, visible on focus, and ordered logically.
  • Semantics: landmarks, headings, labels, buttons, links, forms, tables, lists, and status messages expose correct meaning.
  • Screen readers: dynamic updates, dialogs, menus, comboboxes, errors, and live regions are announced appropriately.
  • Visual access: color contrast, text size, spacing, reflow, zoom, and non-color signals are handled.
  • Motion: animation, parallax, camera shake, flashing, and transitions respect reduced-motion needs.
  • Media: captions, transcripts, audio description, and visual alternatives are considered.
  • Games: provide remapping, subtitles, visual audio cues, difficulty assists, readable UI, pause options, and avoid audio-only critical signals unless intentional.

Deliverable Shape

For accessibility work, provide:

  • Surface and user task
  • Applicable standard or target quality bar
  • Findings by severity
  • Evidence and affected users
  • Recommended fixes
  • Verification steps
  • Remaining compliance or legal uncertainty

References

  • Read references/accessibility-checklist.md when auditing or designing accessible experiences.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

007

Free

Security audit, hardening, threat modeling (STRIDE/PASTA), Red/Blue Team, OWASP checks, code review, incident response, and infrastructure security for any project.

The English summary is being prepared. Showing the original description.

aibot88/sec_skill_store5Updated May 27, 2026

Guides the creation of agile user stories and Gherkin feature files. Use when the user wants to create a user story, write acceptance criteria, define Gherkin scenarios, or author BDD feature files. This should trigger for requests such as Create a user story; Write a user story; I need to write a user story. Part of cursor-rules-java project

The English summary is being prepared. Showing the original description.

aibot88/sec_skill_store5Updated May 27, 2026

Facilitates conversational discovery to create Architectural Decision Records (ADRs) for non-functional requirements using the ISO/IEC 25010:2023 quality model. Use when the user wants to document quality attributes, NFR decisions, security/performance/scalability architecture, or design systems with measurable quality criteria. This should trigger for requests such as Create ADR for Non-functional requirements; Document Non-functional requirements; Capture Non-functional requirements; Generate Non-functional requirements in an ADR. Part of cursor-rules-java project

The English summary is being prepared. Showing the original description.

aibot88/sec_skill_store5Updated May 27, 2026

Run a health check on an existing project: dependency audit, security scan, test runner detection, CI/CD evaluation, and missing configuration analysis. Maps the three execution gates (pre/in/post) from /10x-bootstrapper to an assessment framework for existing codebases. Reads optional context/foundation/stack-assessment.md from /10x-stack-assess to focus checks on identified gaps. Writes context/foundation/health-check.md with findings, prioritized fixes, and an agent-readiness verdict. Use when the user has an existing project and wants to verify its health before working with an agent. Trigger phrases: "health check", "check my project", "audit my project", "is my project healthy", "sprawdź projekt", "audyt projektu", "health-check", "project health". Use AFTER /10x-stack-assess (brownfield chain), BEFORE agent onboarding (m1-l4).

The English summary is being prepared. Showing the original description.

aibot88/sec_skill_store5Updated May 27, 2026

You MUST use this when building projects end-to-end. Orchestrates all 12 team roles — automatically switches between CTO, architect, PM, engineers, SRE, security, DBA, QA, and EM based on the current phase of work. Starts with brainstorming before any implementation.

The English summary is being prepared. Showing the original description.

aibot88/sec_skill_store5Updated May 27, 2026

Use when you need to add or configure Maven plugins in your pom.xml — including quality tools (enforcer, surefire, failsafe, jacoco, pitest, spotbugs, pmd), security scanning (OWASP), code formatting (Spotless), version management, container image build (Jib), build information tracking, and benchmarking (JMH) — through a consultative, modular step-by-step approach that only adds what you actually need. This should trigger for requests such as Add Maven plugins in pom.xml; Improve Maven plugins in pom.xml. Part of cursor-rules-java project

The English summary is being prepared. Showing the original description.

aibot88/sec_skill_store5Updated May 27, 2026

See all skills by aibot88

Report a problem with this skill