Accessibility Checklist logo

Accessibility Checklist

Community
ilyasibrahim
accessibility-checklist

WCAG AA accessibility checklist and verification protocols for Somali dialect classifier dashboard. Covers keyboard navigation, screen readers, color contrast, ARIA labels, and accessibility testing procedures.

Overview

Publisherilyasibrahim
Repositoryclaude-agents-coordination
Skill nameaccessibility-checklist
Stars
83
Forks
15
Bundled files
Instructions only
LicenseUnlicense
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 ilyasibrahim on GitHub. Read the source before you install it.

Installation

Install the Accessibility Checklist 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.
  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/ilyasibrahim/claude-agents-coordination.git /tmp/claude-agents-coordination
mkdir -p .claude/skills
cp -r /tmp/claude-agents-coordination/claude-project/skills/frontend/accessibility-checklist .claude/skills/accessibility-checklist
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Accessibility Checklist 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 Checklist 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 Checklist 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 Checklist (WCAG AA)

Keyboard Navigation

✅ Requirements

Tab Order:

  • All interactive elements reachable via Tab
  • Logical tab order (left-to-right, top-to-bottom)
  • Skip links provided for repetitive navigation
  • No keyboard traps

Interactive Elements:

  • Buttons activate with Enter/Space
  • Links activate with Enter
  • Form inputs accessible via Tab
  • Dropdowns navigable with Arrow keys
  • Modals closable with Escape

Testing:

1. Unplug mouse
2. Navigate entire dashboard using only keyboard
3. Verify all features accessible
4. Check tab order is logical

Focus Indicators

✅ Requirements

Visibility:

  • Focus indicators visible on ALL interactive elements
  • Minimum 2px outline or 3px box-shadow
  • Sufficient color contrast (3:1 minimum)
  • Not removed with outline: none unless replaced

Implementation:

css
/* Good focus states */
.btn:focus-visible {
  outline: 3px solid var(--tableau-blue);
  outline-offset: 3px;
}

.data-toggle__option:focus-visible {
  outline: 2px solid var(--data-blue-primary);
  outline-offset: 2px;
  z-index: 1;
}

/* Chart canvas focus */
canvas:focus-visible {
  outline: 2px solid var(--data-cyan-primary);
  outline-offset: 2px;
  border-radius: 4px;
}

Color Contrast

✅ Requirements (WCAG AA)

Normal Text (< 18px):

  • Minimum 4.5:1 contrast ratio

Large Text (≥ 18px or 14px bold):

  • Minimum 3:1 contrast ratio

UI Components:

  • Buttons: 3:1 minimum
  • Form inputs: 3:1 border contrast
  • Icons: 3:1 against background

Verified Combinations:

ForegroundBackgroundRatioStatus
WhiteTableau Blue (#0176D3)4.83:1✅ AA
WhiteTableau Navy (#032D60)13.55:1✅ AAA
Text (#333)White12.63:1✅ AAA
Data Cyan (#33BBEE)White2.4:1❌ (use dark text)

Testing Tool:


Semantic HTML

✅ Requirements

Landmarks:

  • <header> for site/page header
  • <nav> for navigation
  • <main> for main content
  • <aside> for sidebars
  • <footer> for footer

Headings:

  • Logical heading hierarchy (H1 → H2 → H3, no skipping)
  • One H1 per page
  • Headings describe content

Lists:

  • <ul>/<ol> for lists
  • <dl> for definition lists

Buttons vs Links:

  • <button> for actions (submit, toggle, delete)
  • <a> for navigation (go to another page)

Example:

html
<!-- Good semantic structure -->
<header>
  <h1>Somali Dialect Classifier Dashboard</h1>
  <nav aria-label="Main navigation">
    <ul>
      <li><a href="/overview">Overview</a></li>
      <li><a href="/data">Data Sources</a></li>
    </ul>
  </nav>
</header>

<main>
  <section aria-labelledby="metrics-heading">
    <h2 id="metrics-heading">Pipeline Metrics</h2>
    <!-- Content -->
  </section>
</main>

ARIA Labels

✅ Requirements

Icon Buttons:

html
<button aria-label="Delete dataset">
  <svg><!-- trash icon --></svg>
</button>

Status Indicators:

html
<span
  className="status-icon"
  aria-label="Pipeline status: healthy"
  role="img"
>
</span>

Charts (Canvas):

html
<canvas
  aria-label="Bar chart showing dialect distribution: Northern 60%, Southern 25%, Central 15%"
  role="img"
></canvas>

Form Inputs:

html
<label for="dataset-name">Dataset Name</label>
<input
  id="dataset-name"
  type="text"
  aria-describedby="name-help"
/>
<p id="name-help" className="help-text">
  Choose a descriptive name for your dataset
</p>

Alt Text for Images

✅ Requirements

Informative Images:

  • Descriptive alt text explaining content
  • Context-specific descriptions

Decorative Images:

  • alt="" (empty alt attribute)

Examples:

html
<!-- Informative -->
<img
  src="confusion-matrix.png"
  alt="Confusion matrix showing Northern dialect correctly classified 94% of the time, Southern 82%, Central 79%"
/>

<!-- Decorative -->
<img src="decorative-pattern.svg" alt="" />

Charts as Images:

  • Provide detailed description in alt text OR
  • Provide data table alternative

Form Accessibility

✅ Requirements

Labels:

  • All inputs have associated <label>
  • Labels visible (not placeholder-only)
  • Labels describe purpose clearly

Error Messages:

  • Error messages associated via aria-describedby
  • Errors announced to screen readers
  • Error styling includes text/icons (not color-only)

Example:

html
<div className="form-field">
  <label for="source-url">Source URL</label>
  <input
    id="source-url"
    type="url"
    aria-describedby="url-error"
    aria-invalid="true"
  />
  <p id="url-error" className="error-message" role="alert">
    Invalid URL format. Use: https://example.com
  </p>
</div>

Screen Reader Testing

✅ Requirements

Announcement Priorities:

  • Page title describes current page
  • Headings announce hierarchy
  • Landmark regions labeled
  • Dynamic content changes announced

Live Regions:

html
<!-- Status updates -->
<div aria-live="polite" aria-atomic="true">
  {statusMessage}
</div>

<!-- Urgent alerts -->
<div role="alert" aria-live="assertive">
  {errorMessage}
</div>

Testing Tools:

  • macOS: VoiceOver (Cmd+F5)
  • Windows: NVDA (free) or JAWS
  • Chrome extension: ChromeVox

Modal Accessibility

✅ Requirements

Focus Management:

  • Focus moves to modal when opened
  • Focus trapped within modal
  • Focus returns to trigger element when closed
  • Closable with Escape key

ARIA Attributes:

html
<div
  role="dialog"
  aria-modal="true"
  aria-labelledby="dialog-title"
  aria-describedby="dialog-desc"
>
  <h2 id="dialog-title">Delete Dataset?</h2>
  <p id="dialog-desc">
    This action cannot be undone.
  </p>
  <button onClick={confirmDelete}>Delete</button>
  <button onClick={closeModal}>Cancel</button>
</div>

Testing Checklist

Manual Tests

Keyboard:

  • Tab through entire dashboard
  • Activate all interactive elements
  • Verify no keyboard traps
  • Check tab order is logical

Screen Reader:

  • Navigate with headings
  • Read all content
  • Interact with forms
  • Verify dynamic updates announced

Visual:

  • Zoom to 200% (text remains readable)
  • Check focus indicators visible
  • Verify color contrast
  • Test without color (grayscale mode)

Automated Tools

Browser Extensions:

  • axe DevTools (Chrome/Firefox)
  • WAVE (Web Accessibility Evaluation Tool)
  • Lighthouse (Chrome DevTools)

Command:

bash
# Run Lighthouse accessibility audit
npx lighthouse https://dashboard-url --only-categories=accessibility --view

Target Score: Lighthouse Accessibility Score ≥ 95/100


Common Issues & Fixes

Issue: Missing Alt Text

Fix: Add descriptive alt attributes to all images

Issue: Poor Color Contrast

Fix: Use design-system colors (verified contrast ratios)

Issue: No Focus Indicators

Fix: Add :focus-visible styles to all interactive elements

Issue: Inaccessible Charts

Fix: Add aria-label to canvas, provide data table alternative

Issue: Form Errors Not Announced

Fix: Use role="alert" and aria-describedby


When This Skill Activates

This skill auto-invokes when you mention:

  • Accessibility, a11y, WCAG, ARIA
  • Screen readers, VoiceOver, NVDA
  • Keyboard navigation, tab order
  • Focus indicators, focus states
  • Color contrast, contrast ratios
  • Alt text, image descriptions
  • Semantic HTML, landmarks
  • Form accessibility, labels
  • Modal accessibility, dialogs

Version: 1.0.0 Last Updated: 2025-11-06 Project: Somali Dialect Classifier Dashboard

Frequently asked questions

What does the Accessibility Checklist AI skill do?

WCAG AA accessibility checklist and verification protocols for Somali dialect classifier dashboard. Covers keyboard navigation, screen readers, color contrast, ARIA labels, and accessibility testing procedures.

Why use Accessibility Checklist on TypingMind?

Because you install it once and use it with any model. Accessibility Checklist 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 Checklist in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/ilyasibrahim/claude-agents-coordination/tree/main/claude-project/skills/frontend/accessibility-checklist. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Accessibility Checklist?

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 Checklist?

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

Is the Accessibility Checklist AI skill free?

Yes. It is published on GitHub by ilyasibrahim under the Unlicense 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 👇