Accessibility Implementation logo

Accessibility Implementation

Community
Omar-Obando
accessibility-implementation

Use when implementing accessible web content following WCAG 2.1 AA standards, semantic HTML, ARIA attributes, keyboard navigation, and screen reader support. Includes accessibility testing, compliance verification, and inclusive design practices. Based on CPACC certification and W3C WCAG standards.

Overview

PublisherOmar-Obando
Repositoryqwen-orchestrator
Skill nameaccessibility-implementation
Stars
53
Forks
13
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by Omar-Obando on GitHub. Read the source before you install it.

Installation

Install the Accessibility Implementation AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/Omar-Obando/qwen-orchestrator/tree/main/skills/accessibility-implementation
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Omar-Obando/qwen-orchestrator.git /tmp/qwen-orchestrator
mkdir -p .claude/skills
cp -r /tmp/qwen-orchestrator/skills/accessibility-implementation .claude/skills/accessibility-implementation
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Accessibility Implementation in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Accessibility Implementation on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Accessibility Implementation is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Accessibility Implementation Skill — Frontend Developer

Overview

This skill provides comprehensive guidance for implementing accessible web content following WCAG 2.1 AA standards. It covers semantic HTML, ARIA attributes, keyboard navigation, screen reader support, and accessibility testing following CPACC certification standards.

When to Use

Use this skill when:

  • Implementing accessible web interfaces
  • Ensuring WCAG 2.1 AA compliance
  • Adding ARIA attributes to components
  • Implementing keyboard navigation
  • Testing with screen readers
  • Creating accessible forms
  • Implementing accessible tables
  • Adding accessible color contrast
  • Creating accessible navigation
  • Implementing accessible modal dialogs
  • Creating accessible charts and graphs
  • Ensuring accessible error messages
  • Implementing accessible focus management
  • Creating accessible landing pages
  • Testing with accessibility tools
  • Conducting accessibility audits
  • Implementing skip navigation links
  • Creating accessible PDFs
  • Ensuring accessible video content
  • Implementing accessible print styles
  • Creating accessible email templates
  • Implementing accessible mobile interfaces
  • Ensuring accessible dark mode

Do NOT use this skill when:

  • Writing backend business logic (use domain-driven skill)
  • Designing database schemas (use database-design skill)
  • Writing API endpoint specifications (use api-design skill)
  • Performing security audits (use security-auditor skill)
  • Writing SQL queries (use sql-best-practices skill)
  • Designing multi-page website layouts (use design-system skill)
  • Analyzing deployment configurations (use deployment skill)
  • Writing documentation (use documentation-best-practices skill)

WCAG 2.1 AA Principles

Perceivable

┌─────────────────────────────────────────────────────────────┐
│              Perceivable Principles                         │
├─────────────────────────────────────────────────────────────┤
│  1.1 Text Alternatives - Provide text alternatives for      │
│      non-text content                                       │
│  1.2 Time-based Media - Provide alternatives for time-based │
│      media                                                  │
│  1.3 Adaptable - Create content that can be presented in    │
│      different ways without losing meaning                 │
│  1.4 Distinguishable - Make it easier for users to see and  │
│      hear content                                           │
└─────────────────────────────────────────────────────────────┘

Operable

┌─────────────────────────────────────────────────────────────┐
│              Operable Principles                            │
├─────────────────────────────────────────────────────────────┤
│  2.1 Keyboard Accessible - Make all functionality available  │
│      from a keyboard                                        │
│  2.2 Enough Time - Provide users enough time to read and    │
│      use content                                            │
│  2.3 Seizures and Physical Reactions - Do not design content │
│      in a way that causes seizures                          │
│  2.4 Navigable - Make it easier for users to find content   │
│      and navigate                                           │
└─────────────────────────────────────────────────────────────┘

Understandable

┌─────────────────────────────────────────────────────────────┐
│              Understandable Principles                      │
├─────────────────────────────────────────────────────────────┤
│  3.1 Readable - Make text readable and understandable       │
│  3.2 Predictable - Make Web pages appear and operate in     │
│      predictable ways                                       │
│  3.3 Input Assistance - Help users avoid and correct mistakes│
└─────────────────────────────────────────────────────────────┘

Robust

┌─────────────────────────────────────────────────────────────┐
│              Robust Principles                              │
├─────────────────────────────────────────────────────────────┤
│  4.1 Compatible - Maximize compatibility with current and   │
│      future user tools                                      │
└─────────────────────────────────────────────────────────────┘

Semantic HTML

Basic Elements

html
<!-- ✅ Good: Semantic elements -->
<header>Site navigation</header>
<main>Main content</main>
<nav>Navigation links</nav>
<article>Article content</article>
<section>Section content</section>
<aside>Sidebar content</aside>
<footer>Footer content</footer>

<!-- ❌ Bad: Non-semantic elements -->
<div class="header">Site navigation</div>
<div class="main">Main content</div>
<div class="nav">Navigation links</div>
<div class="article">Article content</div>
<div class="section">Section content</div>
<div class="aside">Sidebar content</div>
<div class="footer">Footer content</div>

Interactive Elements

html
<!-- ✅ Good: Native interactive elements -->
<button>Click me</button>
<a href="/page">Link text</a>
<input type="text" placeholder="Enter text" />
<select>
  <option>Option 1</option>
</select>

<!-- ❌ Bad: Non-interactive elements with click handlers -->
<div onclick="handleClick()">Click me</div>
<span onclick="handleClick()">Link text</span>

ARIA Attributes

Landmark Roles

html
<!-- ✅ Good: Semantic landmarks -->
<header role="banner">...</header>
<nav role="navigation">...</nav>
<main role="main">...</main>
<aside role="complementary">...</aside>
<footer role="contentinfo">...</footer>

<!-- Or explicit ARIA -->
<div role="banner">...</div>
<div role="navigation">...</div>

Live Regions

html
<!-- ✅ Good: Live regions for dynamic content -->
<div aria-live="polite" aria-atomic="true">
  <!-- Dynamic content updates here -->
</div>

<div aria-live="assertive" aria-atomic="true">
  <!-- Urgent updates here -->
</div>

<!-- ❌ Bad: No live region for dynamic content -->
<div id="status">...</div>
<!-- Updates not announced -->

Form Accessibility

html
<!-- ✅ Good: Accessible forms -->
<label for="email">Email address</label>
<input type="email" id="email" name="email" aria-describedby="email-hint" />
<span id="email-hint">We'll never share your email</span>

<!-- Error message with aria-live -->
<div role="alert" aria-live="assertive" id="error-message">
  Please enter a valid email address
</div>

<!-- ❌ Bad: Missing labels -->
<input type="email" placeholder="Email" />
<!-- No label -->

Keyboard Navigation

Focus Management

javascript
// ✅ Good: Proper focus management
function openModal() {
  modal.style.display = 'block';
  modal.querySelector('input').focus();
}

function closeModal() {
  modal.style.display = 'none';
  openButton.focus();
}

// Trap focus in modal
function trapFocus(event) {
  if (event.key === 'Tab') {
    const focusableElements = modal.querySelectorAll(
      'button, [href], input, select, textarea, [tabindex]:not([tabindex="-1"])'
    );
    const first = focusableElements[0];
    const last = focusableElements[focusableElements.length - 1];

    if (event.shiftKey && document.activeElement === first) {
      event.preventDefault();
      last.focus();
    } else if (!event.shiftKey && document.activeElement === last) {
      event.preventDefault();
      first.focus();
    }
  }
}

Skip Links

html
<!-- ✅ Good: Skip link for keyboard users -->
<a href="#main-content" class="skip-link">Skip to main content</a>

<nav>
  <ul>
    <li><a href="#main-content">Skip to main content</a></li>
    <li><a href="#footer">Skip to footer</a></li>
  </ul>
</nav>

<main id="main-content">...</main>
<footer id="footer">...</footer>

Color Contrast

WCAG Contrast Requirements

┌─────────────────────────────────────────────────────────────┐
│              Color Contrast Requirements                    │
├─────────────────────────────────────────────────────────────┤
│  Normal Text (14pt/18px bold): 4.5:1 ratio                 │
│  Large Text (18pt/24px or 14pt/18px bold): 3:1 ratio       │
│  UI Components: 3:1 ratio                                   │
│  Graphics: No minimum (but distinguishable)                 │
└─────────────────────────────────────────────────────────────┘

Contrast Checker

css
/* ✅ Good: Sufficient contrast */
.text-primary {
  color: #1a1a1a;
  background-color: #ffffff; /* 16.11:1 ratio */
}

.text-secondary {
  color: #333333;
  background-color: #f5f5f5; /* 12.63:1 ratio */
}

/* ❌ Bad: Insufficient contrast */
.text-muted {
  color: #888888;
  background-color: #ffffff; /* 3.99:1 ratio - fails AA */
}

Testing Tools

Automated Testing

┌─────────────────────────────────────────────────────────────┐
│              Accessibility Testing Tools                    │
├─────────────────────────────────────────────────────────────┤
│  axe-core:      Automated accessibility testing             │
│  WAVE:          Web Accessibility Evaluation Tool           │
│  Lighthouse:    Chrome DevTools accessibility audit         │
│  Accessibility Insights: Microsoft tool for Windows         │
│  Screen Readers: NVDA, JAWS, VoiceOver, TalkBack           │
└─────────────────────────────────────────────────────────────┘

Manual Testing Checklist

[ ] All interactive elements are keyboard accessible
[ ] Focus is visible and logical
[ ] Screen reader announces content correctly
[ ] Color contrast meets AA requirements
[ ] Form labels are associated with inputs
[ ] Error messages are announced
[ ] Skip links work correctly
[ ] Tab order is logical
[ ] Hover effects don't rely on hover alone
[ ] Animations can be paused

Real-World Impact

Before this skill:

  • Inaccessible web content
  • Keyboard users can't navigate
  • Screen reader users miss content
  • Color contrast issues
  • Form accessibility problems

After this skill:

  • Fully accessible web content
  • Keyboard navigation works
  • Screen readers announce correctly
  • Sufficient color contrast
  • Accessible forms and error messages

Cross-References

  • design-system - For accessible design patterns
  • frontend-philosophy - For inclusive design principles
  • testing-strategy - For accessibility testing

References

Frequently asked questions

What does the Accessibility Implementation AI skill do?

Use when implementing accessible web content following WCAG 2.1 AA standards, semantic HTML, ARIA attributes, keyboard navigation, and screen reader support. Includes accessibility testing, compliance verification, and inclusive design practices. Based on CPACC certification and W3C WCAG standards.

Why use Accessibility Implementation on TypingMind?

Because you install it once and use it with any model. Accessibility Implementation is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Accessibility Implementation in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Omar-Obando/qwen-orchestrator/tree/main/skills/accessibility-implementation. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Accessibility Implementation?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Accessibility Implementation?

As many as you like. As long as a model supports skills, you can use Accessibility Implementation with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Accessibility Implementation AI skill free?

Yes. It is published on GitHub by Omar-Obando under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇