
Most accessibility failures don’t originate in code. They originate in design decisions made weeks or months earlier.
Last week I published 63 design skills for Claude. The response surprised me, not just the downloads and forks, but the messages. Designers telling me they’d started encoding their own knowledge. Product leads forwarding the repo to their teams. Engineers telling me how much better the results were than starting with the UI.
Every accessibility skill set that exists for AI coding agents is engineer-facing. They audit code. They check WCAG conformance. They validate ARIA attributes and flag contrast ratios. They catch problems after the design decisions have already been made.
By the time an automated audit catches it, the cost to fix it has multiplied tenfold.
I wanted something that nudged me earlier, during design, not after code existed. Building these skills forced me to go much deeper into accessibility than I had before.
What I built
40 skills and 18 commands across 6 plugins, covering the design side of accessibility:
Cognitive accessibility — designing for how people actually think. Cognitive load assessment, plain language, wayfinding, focus and attention, memory load reduction, error prevention, contextual help, and adaptive personalisation. Grounded in the W3C Cognitive and Learning Disabilities Accessibility Task Force (COGA) guidelines.
Inclusive interaction — designing for how people actually move and perceive. Keyboard navigation, touch targets, voice interaction, multi-modal input, motion sensitivity, gesture alternatives, and feedback that works across senses.
Accessible content — structuring content that works for everyone. Meaningful alt text, heading hierarchy, readable content, link text, table accessibility, form labelling, and multimedia accessibility.
Inclusive personas — building user stories and personas that include disability from the start. Not as a separate “accessibility persona” on a slide nobody looks at, but woven into the real picture of who uses your product.
Adaptive interfaces — designing systems that respect user preferences. System preference detection, responsive accessibility, flexible typography, colour independence, simplified views, and information density.
Accessibility decisions — the plugin nobody thinks to build. Documenting why accessibility decisions were made so they survive team changes, redesigns, and the inevitable “why is it like this?” from someone who wasn’t in the room.
The whole collection is free, open source, MIT licensed, and model-agnostic. The skills use the universal SKILL.md format — they work with Claude Code, OpenAI Codex, Gemini CLI, Cursor, and anything else that supports the standard.
Browse the full collection on GitHub →
Why this is different from what exists
The accessibility tools that exist for AI agents ask: does this code comply?
These skills ask: are we making the right design decisions for the humans who will use this?
That’s a fundamentally different question, and it needs to be asked at a fundamentally different point in the process before code, not after.
Here’s what that looks like in practice.
Type /cognitive-accessibility:review and your AI agent runs a full cognitive accessibility review of a flow, assessing cognitive load, plain language, wayfinding, error handling, focus design, and memory demands. It doesn’t check your HTML. It evaluates whether a tired, stressed, unfamiliar user can complete their task without help.
Type /inclusive-personas:generate and it builds a persona set that includes disability as a natural dimension of human diversity with specific assistive technology, specific environments, and specific scenarios that show step by step how someone navigates your product with their actual setup.
Type /accessibility-decisions:handoff and it generates an accessibility specification for engineering, not “make it accessible” but specific HTML elements, keyboard behaviours, screen reader announcements, and test cases for every interactive component.
These are design tools that happen to result in more accessible products.
The skill that surprised me most
When I started building, I assumed the cognitive accessibility plugin would be the hardest. It wasn’t really. The COGA guidelines from W3C gave me a strong framework, and once I had the eight objectives mapped to design patterns, the skills wrote themselves.
The hardest plugin was accessibility decisions.
It’s because the problem it solves is cultural, not technical. The reason accessibility degrades over time isn’t that teams make bad decisions. It’s that good decisions aren’t recorded, so they get reversed by people who weren’t in the room when the decision was made.
A new engineer joins. They see a form with inline error messages and think “a summary banner at the top would be cleaner.” They refactor. They’ve just undone three weeks of user testing that showed participants with cognitive disabilities couldn’t find the banner.
That’s a knowledge preservation problem and it’s exactly the kind of problem that skills are built to solve: encoding institutional knowledge so it persists beyond any individual’s tenure.
Who this is for
If you’re a designer, these skills help you build accessibility into your process from the start, not bolt it on at the end. The cognitive accessibility and inclusive interaction plugins will change how you think about every flow you design.
If you’re a product manager, the inclusive personas and accessibility decisions plugins give you the tools to make informed tradeoffs — and document them so you’re not relitigating the same decisions every quarter.
If you’re an engineering lead, the accessibility decisions handoff skill gives you what you’ve always wanted: a specific, testable accessibility specification instead of a vague instruction to “make it accessible.”
If you’re an accessibility practitioner, these skills amplify your impact. Instead of reviewing every design yourself, you can equip every designer on the team with the knowledge to get it right the first time.
If you build products used by humans, these skills encode a simple principle: accessibility is a design commitment, not a compliance checkbox.
How to use them
With Claude Code
Install everything:
claude install github:Owl-Listener/inclusive-design-skills
Or install a single plugin:
claude install github:Owl-Listener/inclusive-design-skills/cognitive-accessibility
With other AI agents
The skills use the universal SKILL.md format. Copy the skill folders into your tool’s skills directory. They work with Codex, Gemini CLI, Cursor, and any tool that supports the standard.
Without a coding agent
Open any SKILL.md file on GitHub, copy the contents, and paste it as context at the start of a conversation with whatever AI assistant you use. The frameworks and decision criteria work regardless of the tool.
What comes next
This is version 1. It’s comprehensive, but it’s not complete, no accessibility resource ever is.
I particularly want contributions from people with lived experience of disability. The CONTRIBUTING.md has guidelines, and the principle is simple: nothing about us without us.
If you try these skills and find something missing, something wrong, or something that could be better, please open an issue or a pull request. That’s how this gets better over time.
Last weekend I built skills to make builders more effective. This week I built skills to make products more inclusive. I don’t think those are different goals. I think they’re the same goal, seen from different angles.
The best design is the design that works for the most people in the most contexts. That’s not a nice-to-have. It’s the craft.

