Accessibility Testing Expert logo

Accessibility Testing Expert

Community
roedyrustam
accessibility-testing-expert

Web accessibility testing with axe-core, Playwright, and WCAG 2.2 / Pengujian aksesibilitas web axe-core, Playwright, dan WCAG 2.2.

Overview

Publisherroedyrustam
Repositoryvibes-plug
Skill nameaccessibility-testing-expert
Stars
117
Forks
27
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 roedyrustam on GitHub. Read the source before you install it.

Installation

Install the Accessibility Testing Expert 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/roedyrustam/vibes-plug/tree/main/skills/accessibility-testing-expert
  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/roedyrustam/vibes-plug.git /tmp/vibes-plug
mkdir -p .claude/skills
cp -r /tmp/vibes-plug/skills/accessibility-testing-expert .claude/skills/accessibility-testing-expert
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Accessibility Testing Expert 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 Testing Expert 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 Testing Expert 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 Testing Expert (2026 Edition)

English | Bahasa Indonesia


English

Orchestration & Integration

  • modern-web-guidance: Evaluates platform accessibility guidelines, ARIA specifications, and :user-valid patterns.
  • visual-ui-auditor: Multimodal vision verification for color contrast, visible focus rings, and spatial layout integrity.
  • global-a11y-i18n-expert: Core WCAG rules, ARIA patterns, and internationalization standards.
  • e2e-testing-expert: Integrating automated accessibility assertions into Playwright/Vitest CI suites.
  • design-system-architect, senior-frontend: Accessible component primitives (Radix UI, Base UI, ARIA patterns).
  • browser-automation-expert: Visual QA audits for focus rings, contrast ratios, and layout flow using Vision LLM agents.
  • anti-slop: Enforces strict accessibility rules (preventing stripped focus outlines, div-soup buttons, and color contrast violations).

Description

Production guide for automated, semi-automated, and manual web accessibility (a11y) testing. Covers WCAG 2.2 Level AA/AAA compliance validation using @axe-core/playwright, Pa11y, Google Lighthouse CI, screen reader verification (NVDA, VoiceOver), keyboard navigation audits, focus management, and color contrast compliance.

Trigger Conditions

  • Running automated accessibility test suites in CI/CD pipelines.
  • Auditing web apps for WCAG 2.1 / 2.2 Level AA compliance and legal accessibility requirements (ADA, EAA).
  • Debugging keyboard traps, missing ARIA labels, or broken screen reader navigation.
  • Writing test cases for focus trapping in modals and custom dialogs.

Core Testing Workflows

1. Automated A11y Testing with Playwright & Axe-Core
typescript
import { test, expect } from '@playwright/test';
import AxeBuilder from '@axe-core/playwright';

test.describe('Accessibility Automated Audits', () => {
  test('homepage should have zero critical or serious a11y violations', async ({ page }) => {
    await page.goto('/');

    const accessibilityScanResults = await new AxeBuilder({ page })
      .withTags(['wcag2a', 'wcag2aa', 'wcag22aa'])
      .disableRules(['color-contrast']) // If tested separately
      .analyze();

    expect(accessibilityScanResults.violations).toEqual([]);
  });

  test('modal dialog should trap focus and pass a11y audit', async ({ page }) => {
    await page.goto('/dashboard');
    await page.click('button#open-modal');

    // Verify modal is open and focused
    const modal = page.locator('[role="dialog"]');
    await expect(modal).toBeVisible();

    const modalAudit = await new AxeBuilder({ page })
      .include('[role="dialog"]')
      .analyze();

    expect(modalAudit.violations).toEqual([]);

    // Verify keyboard escape closes modal
    await page.keyboard.press('Escape');
    await expect(modal).toBeHidden();
  });
});
2. Automated Pa11y CI Configuration (.pa11yci.json)
json
{
  "defaults": {
    "standard": "WCAG2AA",
    "timeout": 15000,
    "runners": ["axe", "htmlcs"],
    "ignore": [
      "WCAG2AA.Principle1.Guideline1_4.1_4_3.G18.Abs"
    ]
  },
  "urls": [
    "http://localhost:3000/",
    "http://localhost:3000/login",
    "http://localhost:3000/pricing",
    "http://localhost:3000/docs"
  ]
}
3. Keyboard & Screen Reader Verification Checklist
  • Tab Navigation: All interactive elements (<button>, <a>, <input>) can receive focus in logical reading order.
  • Focus Indicators: Visible, high-contrast focus rings (outline: 2px solid var(--focus-color) with outline-offset).
  • No Keyboard Traps: Focus can enter and leave components using only Tab, Shift+Tab, and Esc.
  • Landmarks: Proper semantic tags (<header>, <nav>, <main>, <footer>, <aside>).
  • ARIA Attributes: aria-expanded, aria-controls, aria-haspopup, and aria-live updated dynamically.
4. Material Design 3 (M3) Accessibility & State Layer Assertions (https://m3.material.io/foundations/accessible-design/overview)

M3 enforces rigorous interaction states via standardized State Layer Opacities and an expanded 48×48dp Target Size:

1. M3 State Layer Opacity Matrix:

  • Hover: 8% (0.08) overlay of on-surface or primary.
  • Focus: 10% (0.10) overlay with high-contrast ring.
  • Pressed: 10% (0.10) overlay.
  • Dragged: 16% (0.16) overlay.
  • Disabled: Container opacity 38% (0.38), content opacity 38% (0.38).

2. 48×48dp Minimum Touch Target Assertion (Playwright):

typescript
import { test, expect } from '@playwright/test';

test('interactive controls satisfy M3 48x48dp touch target standard', async ({ page }) => {
  await page.goto('/');

  const buttons = page.locator('button, a[role="button"], input[type="checkbox"]');
  const count = await buttons.count();

  for (let i = 0; i < count; i++) {
    const btn = buttons.nth(i);
    const box = await btn.boundingBox();
    if (box && await btn.isVisible()) {
      // M3 requires min 48x48dp bounding box for touch targets
      expect(box.width).toBeGreaterThanOrEqual(48);
      expect(box.height).toBeGreaterThanOrEqual(48);
    }
  }
});
5. Sovereign Anti-Slop A11y Verification Gate

Zero-tolerance accessibility criteria for all generated interfaces:

  • No Stripped Focus Outlines: Zero tolerance for outline: none or focus:outline-none without an explicit, high-contrast replacement ring (focus-visible:ring-2 focus-visible:ring-offset-2).
  • Semantic Elements Only: Ban on non-semantic clickable divs/spans (<div onClick=...>). Every click target must be an authentic <button>, <a>, or provide role="button" + tabIndex={0} + keyboard event handlers (onKeyDown for Enter & Space).
  • Touch Target Minimums: All interactive controls must satisfy WCAG 2.2 SC 2.5.8 (minimum 24×24px, recommended 44×44px with adequate padding).
  • Text Contrast Non-Negotiable: Minimum 4.5:1 for normal body text, 3:1 for large text (18pt / 14pt bold).
  • Meaningful Labels: Zero icon buttons without aria-label or screen-reader-only text (<span className="sr-only">).

Sovereign Execution, Token Efficiency & Invariants

DimensionSovereign Mandate & Deterministic Contract
Frontier Model CascadeMedium / High (Gemini 4 Argon, Claude Sonnet 5.5 High, Muse Wonder High, Composer 2.5 Fast)
Availability FallbackGemini 4 Argon/Pro -> Gemini 3.8 Flash; Claude Opus 5.5 -> Claude Opus 4.6 (Zero unhandled missing-model errors)
KV-Cache & Token ProtocolPin static instructions & schemas at prompt prefix (kv-cache-prefix-optimizer); pass surgical CONTEXT_MAP.md slices (<250 tokens/call) during Swarm Fan-Out
SaaT CLI & MCP DispatchCLI: vibes skill exec accessibility-testing-expert <audit|eval|verify|generate|blueprint> / MCP: vibes_skill_dispatch, vibes_visual_audit, vibes_ast_query, vibes_verify_gate
NFR & Anti-Slop InvariantsLCP < 1.8s, INP < 100ms, CLS < 0.05, 1px crisp borders, 3-tier radius (6px/8px/12px), tabular-nums, 5-state interactive contract; 100% complete zero-placeholder output verified via node scripts/check-anti-slop.js --strict


Bahasa Indonesia

Integrasi Orkestrasi

  • modern-web-guidance: Mengevaluasi pedoman aksesibilitas platform web, spesifikasi ARIA, dan pola form aksesibel.
  • visual-ui-auditor: Verifikasi vision multimodal untuk rasio kontras warna, cincin fokus terlihat, dan integritas tata letak visual.
  • global-a11y-i18n-expert: Pedoman standar WCAG, pola ARIA, dan aksesibilitas internasional.
  • e2e-testing-expert: Integrasi pengujian aksesibilitas otomatis ke pipeline Playwright CI.
  • design-system-architect, senior-frontend: Validasi aksesibilitas komponen headless dan desain UI.
  • anti-slop: Menegakkan aturan aksesibilitas tanpa kompromi (mencegah penghapusan outline fokus, div-soup tombol, dan pelanggaran kontras warna).

Deskripsi

Panduan produksi untuk pengujian aksesibilitas web (a11y) otomatis dan manual. Memastikan kepatuhan terhadap standar WCAG 2.2 Level AA/AAA menggunakan @axe-core/playwright, Pa11y, Lighthouse CI, pengujian screen reader, navigasi keyboard, dan kontras warna.

Kondisi Pemicu

  • Menjalankan audit aksesibilitas otomatis di pipeline CI/CD.
  • Memverifikasi kepatuhan hukum aksesibilitas (WCAG 2.2, ADA, EAA).
  • Menguji alur keyboard dan pembaca layar (screen reader) pada komponen kompleks seperti modal dan dropdown.

Alur Pengujian Otomatis

1. Pengujian Aksesibilitas Otomatis dengan Playwright & Axe-Core
typescript
import { test, expect } from '@playwright/test';
import AxeBuilder from '@axe-core/playwright';

test.describe('Audit Otomatis Aksesibilitas Web', () => {
  test('beranda bebas dari pelanggaran a11y kritis atau serius', async ({ page }) => {
    await page.goto('/');

    const hasilAudit = await new AxeBuilder({ page })
      .withTags(['wcag2a', 'wcag2aa', 'wcag22aa'])
      .analyze();

    expect(hasilAudit.violations).toEqual([]);
  });

  test('dialog modal mengunci fokus keyboard dan lolos audit a11y', async ({ page }) => {
    await page.goto('/dashboard');
    await page.click('button#buka-modal');

    const modal = page.locator('[role="dialog"]');
    await expect(modal).toBeVisible();

    const auditModal = await new AxeBuilder({ page })
      .include('[role="dialog"]')
      .analyze();

    expect(auditModal.violations).toEqual([]);

    // Verifikasi tombol Escape menutup modal
    await page.keyboard.press('Escape');
    await expect(modal).toBeHidden();
  });
});
2. Konfigurasi CI Otomatis Pa11y (.pa11yci.json)
json
{
  "defaults": {
    "standard": "WCAG2AA",
    "timeout": 15000,
    "runners": ["axe", "htmlcs"]
  },
  "urls": [
    "http://localhost:3000/",
    "http://localhost:3000/masuk",
    "http://localhost:3000/harga",
    "http://localhost:3000/dokumentasi"
  ]
}
3. Standar State Layer & Target Sentuh Material Design 3 (M3)
  • Matriks State Layer:
    • Hover: Opacity 8% (0.08)
    • Focus: Opacity 10% (0.10) dengan ring kontras tinggi
    • Pressed: Opacity 10% (0.10)
    • Dragged: Opacity 16% (0.16)
    • Disabled: Opacity kontainer dan konten 38% (0.38)
  • Target Sentuh Minimum 48×48dp: Meskipun aset visual hanya berukuran 24×24px, area sentuh interaktif wajib diperluas menjadi minimal 48×48dp menggunakan padding atau pseudo-elemen ::after.
4. Gerbang Verifikasi Aksesibilitas Anti-Slop
  • Dilarang Menghapus Outline Fokus: Standar nol toleransi untuk outline: none atau focus:outline-none tanpa pengganti ring berlatar kontras tinggi (focus-visible:ring-2 focus-visible:ring-offset-2).
  • Wajib Elemen Semantik: Larangan keras membuat div/span non-semantik yang dapat diklik (<div onClick=...>). Setiap target klik harus merupakan <button>, <a>, atau menyediakan role="button" + tabIndex={0} + penangan keyboard (onKeyDown untuk tombol Enter & Space).
  • Target Sentuh Minimum: Semua kontrol interaktif harus memenuhi standar WCAG 2.2 SC 2.5.8 (minimal 24×24px, direkomendasikan 44×44px dengan padding memadai).
  • Kontras Teks Non-Negosiabel: Minimal rasio 4.5:1 untuk teks biasa, dan 3:1 untuk teks berukuran besar (18pt / 14pt bold).
  • Label Bermakna: Dilarang membuat tombol ikon tanpa aria-label atau teks khusus pembaca layar (<span className="sr-only">).

Matriks Eksekusi Berdaulat, Efisiensi Token & Invarian

DimensiMandat Berdaulat & Kontrak Deterministik
Kaskade Model FrontierMedium / High (Gemini 4 Argon, Claude Sonnet 5.5 High, Muse Wonder High, Composer 2.5 Fast)
Invarian Fallback KetersediaanGemini 4 Argon/Pro -> Gemini 3.8 Flash; Claude Opus 5.5 -> Claude Opus 4.6 (Bebas gagal saat model belum tersedia/kuota penuh)
Protokol Hemat Token & KV-CacheKunci instruksi & skema statis di prefix awal (kv-cache-prefix-optimizer); kirim potongan CONTEXT_MAP.md (<250 token/panggilan) saat Fan-Out
Eksekusi SaaT CLI & MCPCLI: vibes skill exec accessibility-testing-expert <audit|eval|verify|generate|blueprint> / MCP: vibes_skill_dispatch, vibes_visual_audit, vibes_ast_query, vibes_verify_gate
Invarian NFR & Anti-SlopLCP < 1.8s, INP < 100ms, CLS < 0.05, border tegas 1px, radius 3-tier (6px/8px/12px), tabular-nums, kontrak interaktif 5-state; kode 100% tuntas tanpa placeholder diverifikasi melalui node scripts/check-anti-slop.js --strict

Frequently asked questions

What does the Accessibility Testing Expert AI skill do?

Web accessibility testing with axe-core, Playwright, and WCAG 2.2 / Pengujian aksesibilitas web axe-core, Playwright, dan WCAG 2.2.

Why use Accessibility Testing Expert on TypingMind?

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

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/roedyrustam/vibes-plug/tree/main/skills/accessibility-testing-expert. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Accessibility Testing Expert?

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 Testing Expert?

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

Is the Accessibility Testing Expert AI skill free?

Yes. It is published on GitHub by roedyrustam 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 👇